DesignOps - Conventions

Unofficial Content
This documentation is valid for:

Conventions are useful for the essential difference between a designer profile and a developer profile.

In some cases, designers are creating and drawing without considering abstractions. Some of these drawings in the implementation must be, for example, an image. Therefore, the internal details of those components are not imported to GeneXus.

The freedom while designing is so great that there is no single heuristic that allows us to understand today the true meaning of what is drawn. This is why there are conventions to allow the design to be transmitted unambiguously to implementation.

Conventions

Ignore layer

Used when you draw a draft that you do not want to be imported by GeneXus.

Prefix _ (underscore)
Applies to Any element
Example Conventions - Ignore
Notes 1) Since some elements in the application are intended to be standard, the following set of keywords also ignores a layer: 'keyboard', 'status bar'

Static content

Used for defining static content (e.g. a section title) that will be interpreted by GeneXus as a TextBlock. 

Prefix static
Applies to  Text element
Example Conventions - Static

Dynamic content

Used for defining dynamic content (e.g. a customer name) that will be interpreted by GeneXus as a read-only Variable.

Prefix  (none)
Applies to  Text element
Example Conventions - Dynamic

Editable content

Used for defining editable content (i.e. user input) that will be interpreted by GeneXus as an editable Variable.

Prefix input
Applies to  Text element
Example Conventions - Edit

Button control

Used for defining buttons that will be interpreted by GeneXus as a Button control. Also, if the layer defines a link, GeneXus will interpret a call action to the panel defined by the target artboard; otherwise, it will display a dummy message. 

Prefix button
Applies to  Group
Example Conventions - Button

Combo control

Used for defining a combo-box control that will be interpreted by GeneXus as a Variable with Control Type = Combo Box.

Prefix combobox
Applies to  Group
Example Conventions - Combobox

Check control

Used for defining a check-box control that will be interpreted by GeneXus a Variable with Control Type = Check Box.

Prefix checkbox
Applies to  Group
Example Conventions - Checkbox

Radio-button control

Used for defining a radio-button control that will be interpreted by GeneXus as a Variable with Control Type = Radio Button. The elements defined in the group will be the items of the radio-button.

Prefix radiobutton
Applies to  Group
Example Conventions - Radiobutton

List & Carousel

Used for defining a list (vertical scroll) or carousel (horizontal scroll) that will be interpreted by GeneXus as a Grid control with the appropriate item's orientation. 

Prefix (vertical | horizontal) grid
Applies to  Group
Example Conventions - Grid
Notes 1) When orientation is not indicated in the naming convention, GeneXus will try to infer it.
2) It is highly recommended to use symbols as items of the list (reusability).

Navigation bar

Used for rendering the navigation bar for a mobile app panel that will be interpreted by GeneXus as the Application Bar of the target panel.

Prefix navigation
Applies to  Group
Example Conventions - Naviagation
Notes 1) Does not apply for web applications.

Scope

Generators   .NET, .NET Core, Java, Android, Apple, Angular

See also

Availability

These conventions are available as of GeneXus 17.