Development of the Taxi interface in version 8.3.4

We observe the expertise of utilizing the brand new Taxi interface and attempt to consider the feedback expressed by companions and customers promptly. Due to this fact, we determined to make a lot of modifications within the very subsequent model of the platform since we think about them reasonably necessary.

“Compact” types

The most significant change is using the advanced, wealthy types in 8.2 utility options without rework. Now, such types look dangerous when the Taxi interface is turned on. Primarily because of the elevated fonts and indents within the new interface. For instance, within the kind beneath, the tabular part is hidden:

Due to this fact, now we have carried out a brand new Scale Possibility property for the managed class. Should you set this property to Compact within the configurator, the shape will mechanically seem like this:

In “technical language” because of this:

  • The system font “Dialogue and Menu Font” is used as the bottom font;
  • Type parts have sizes that correspond to the utmost dimension of features within the interface of model 8.2;
  • The distances between type parts correspond to the maximum distances within the interface of model 8.2;
  • And the spreadsheet doc, chart, Gantt chart, dendrogram, graphical diagram, and geographic diagram are displayed without zooming in.

This model of the shape will not be the primary one. “Compact” types are discordant with the remainder of the interface, and that is solely an auxiliary resolution for the transition interval. Nonetheless, it permits you to switch the whole utility resolution to a brand new platform with minimal prices, after which regularly finalize advanced types for snug work within the new interface.

The “compactness” of types will be managed not just to every kind individually, but for the whole utility resolution as a complete. To do that, now we have carried out a comparable property within the ClientApplicationSettings object, which will be set to the Compact worth. Then all types can be “compact” besides these, for which it’s explicitly said that they need to be displayed on a regular scale.

Disable historical choice past

One other change that turned out to be helpful and necessary is showing off the choice of historical past within the entered subject. There are a variety of duties when the consumer ultimately doesn’t want (and even dangerous) to see the values ​​that he chose within the enter subject earlier. For instance, when it is advisable to select and shut buyer orders. Naturally, in this case, he ought to solely see orders that he has not beforehand processed. And exhibiting the historical choice past, which comprises already processed and closed orders, will solely intrude and confuse him.

Due to this fact, for a lot of utility objects, in addition to for attributes, dimensions, assets, and different configuration objects, now we have carried out a brand new property, ChoiceOnInputHistory, which lets you flexibly manage the show of the historical choice past in varied conditions.

Programmatically configuring panels

The subsequent necessary change is the power to programmatically change the composition and association of panels in the primary window of the consumer utility. In different phrases, now you can programmatically customize the consumer’s workspace relying on any components.

For instance, he was relying on his position. Or depending on the display decision on which 1C: Enterprise is launched. The principal object that’s used to configure is ClientApplicationInterface Settings. It permits you to work with the settings specified within the configurator by the developer and with the scenes that the consumer has set for himself in 1C: Enterprise mode. The constructor has to be created within the first case, and within the second case, it has to be learned from the system settings retailer.

Beneath is an instance of the process on the Begin of work systems and procedures of the final module, which lets you set a particular association of panels relying on the dimensions of the display on which 1C: Enterprise is launched.

New Submenu in Logs

One other change, which will not be so important, however undoubtedly helpful, is the automated formation of the “Create” submenu in doc journals.

Beforehand, if the journal contained several completely different paperwork, urgent the Create button in a separate window would open a listing of available paperwork. From this checklist, it was crucial to pick out the required doc.

Now, in journals containing several paperwork, the platform mechanically creates not a button, however a submenu that comprises available paperwork. This simplifies the creation of recent paperwork and doesn’t distract the consumer from the immediate context of labour:

Change palette

We now have barely modified the colours of the part bar and the command bar of the present part. On some displays, previous colours were regarded as dangerous. Directly they’ve changed into extra “calm”. As well as, the vertically displayed command bar does not have the “Perform Menu” heading because it did earlier then.

Controlling the dimensions of spreadsheet paperwork

When designing the sizes of the Taxi interface parts, we proceeded from a sure font dimension that’s standardly used within the system. Nonetheless, some utility options use an enlarged font, for instance, when displaying stories. Consequently, such reports within the new interface look “too giant”.

Due to this fact, now we have added a brand new property to the ScalingView property for a typical subject displaying a spreadsheet doc. Through the use of this property, you possibly can forcefully cut back the dimensions at which a spreadsheet doc is displayed if that doc makes use of a customized font dimension.

Passing extra parameters to open types

One other helpful change is said to the truth that within the Taxi interface, you can create new information parts straight from the enter subject. Its drop-down checklist comprises a button for creating brand new merchandise.

Beforehand, comparable performance was carried out in utility options utilizing an embedded language. With this new type, the parameters related to the choice have been mechanically transferred. And in addition to this, different parameters might be transmitted that specify the traits of the created information component.

Now, within the new interface, the opening of the type of a brand new component can occur mechanically. Due to this fact, we have added a new customary parameter, AdditionalParameters, to the types of utilized objects. Choice parameters and hyperlinks of choice parameters described as extra (not associated to choice) are mechanically transferred from the enter subject. These values ​​can even be analyzed when creating a new component and opening its type.

As well as, the platform transfers AdditionalParameters from the enter subject not solely to the type of a brand new component but additionally to the chosen style. Thus, if a consumer opens a range type from an enter subject and creates a unique brand element, the platform will mechanically switch Extra Parameters alongside this complete chain in a brand new component.


Related Articles

Latest Articles