Module 1. Episode 6. User interface basics

1C Junior Developer training course
Module 1. Basic concepts and skills

Start learning now for free ? https://academy.1ci.com/

Telegram chat: https://t.me/joinchat/DRc2iRL1O5OcAJYpX6RCIA
Blog on Medium: https://medium.com/yellow-universe

#1CiAcademy #1CEnterprise #LowCode

Link to the training course: https://support.1ci.com/hc/en-us/articles/360021920154-Welcome-to-the-1C-Junior-Developer-training-course

Panels
When we start the application, the first thing we see is this Main Window, that has on its sides several different areas called panels.

Let’s open the Panel settings and see what we have here. We don’t have sections yet, so no Section panel for us just now. Next down is the Current section panel, which is this yellow guy right here, containing the links to our Metadata Objects. To the left, we have the Tools panel with the fixed list of the system functions. And an the bottom we have this grey area, that shows the hidden panels.

We can make them visible by dragging and dropping them to any side of the Main window. So, let’s see what exactly it’s all about.

This is the Favourites panel. I’m dropping it here and now I can start marking things as my Favourites: lists, specific data objects, commands, pretty much anything. After I’m done marking I can use these links as shortcuts to my favorite places in the app.The links can be renamed, moved up and down, marked as the most favorite, deleted, etc.

Next one is the Open Items Panel. Let’s drop it down here and now we can see all open forms in tabs, so it’s easier to switch between them.

The last one is the History panel. It remembers everything we opened recently, so you can come back to it when you need.

If I don’t want some of these guys, I can drop them back to this grey area, and they disappear from the Main window.

As a developer, I can set up a default set of panels I want my users to see. It’s done here from the Client application interface. I always prefer to see the open forms as tabs, so I’m adding this panel to the default view; and these are my open items tabs.

As we already saw, the default view can be easily changed by a user. And of course, every user will have their own personal and independent set of settings.

Subsystems
Now let’s talk the Sections panel. The idea behind this is that you might (and, you probably, will) have too many commands to fit into this rather small area.

This is where the subsystems come for the rescue, working as a kind of folders for the commands in this section. Let me create a new subsystem called Lists and place all the catalogs here. I also want all the Documents in another subsystem.

When I try to save the application, the Platform says that there are possible errors. Namely, there are some metadata objects that are not included into any subsystem.

OK, fair point. Let’s add another subsystem called Other and put these two guys in there.

Now the app is running successfully, and here are the commands grouped by the subsystems. By the way, this is the same Section panel we already mentioned. Now, when it’s filled with Subsystems, we can see it and place it anywhere in the Main Window.

What now catch my eyes here are these bullet points, I’m, honestly, not a big fan of.

The good news is that we can replace them with any pictures we want. I’m just opening each subsystem and load the picture I want from the disk and this is already looking better, right? I’d also like to replace this Quick Menu icon. I mean, it’s cute and everything, it’s just has nothing to do with my convenience store.

So, I’m going right here and replacing it with the more appropriate one.

Note, that when we run the app, these pictures do not get loaded from the files they used to live in. They now live right in the app, here in the Common pictures, so they always go with the app whenever it goes.

OK, now. What’s the deal with this empty Quick Menu folder? This is not really a subsystem, it’s just a group you place all your frequently used commands to. We didn’t really discussed what the commands are, so let’s just leave it empty for now. We’ll get back to it pretty soon, I promise.