mirror of
https://gitlab.gnome.org/jwestman/blueprint-compiler.git
synced 2025-05-04 15:59:08 -04:00
Apply 5 suggestion(s) to 1 file(s)
This commit is contained in:
parent
13e477aa25
commit
e1f972ef16
1 changed files with 5 additions and 5 deletions
|
@ -115,7 +115,7 @@ Write properties inside the curly brackets of a widget:
|
||||||
}
|
}
|
||||||
|
|
||||||
Properties values are *all lowercase* (except strings) and must end with a
|
Properties values are *all lowercase* (except strings) and must end with a
|
||||||
semicolon (;).
|
semicolon (``;``).
|
||||||
|
|
||||||
Property Types
|
Property Types
|
||||||
~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~
|
||||||
|
@ -280,7 +280,7 @@ Custom Widget Classes
|
||||||
|
|
||||||
Some programs have custom widgets defined in their logic, so blueprint
|
Some programs have custom widgets defined in their logic, so blueprint
|
||||||
won't know that they exist. Writing widgets not defined in the GIR will
|
won't know that they exist. Writing widgets not defined in the GIR will
|
||||||
result in an error. Prepend a custom widget with a ``.`` to prevent the
|
result in an error. Prepend a custom widget with a period (``.``) to prevent the
|
||||||
compiler from trying to validate the widget. This is essentially saying
|
compiler from trying to validate the widget. This is essentially saying
|
||||||
the widget has no *namespace*.
|
the widget has no *namespace*.
|
||||||
|
|
||||||
|
@ -327,7 +327,7 @@ Non-property Elements
|
||||||
Some widgets will have elements which are not properties, but they sort
|
Some widgets will have elements which are not properties, but they sort
|
||||||
of act like properties. Most of the time they will be specific only to a
|
of act like properties. Most of the time they will be specific only to a
|
||||||
certain widget. *Styles* is one of these elements, except that styles can
|
certain widget. *Styles* is one of these elements, except that styles can
|
||||||
be used for any widget. Similarly to how every widget has styles,
|
be used for any widget. Similar to how every widget has styles,
|
||||||
``Gtk.ComboBoxText`` has *items*:
|
``Gtk.ComboBoxText`` has *items*:
|
||||||
|
|
||||||
.. code-block::
|
.. code-block::
|
||||||
|
@ -411,11 +411,11 @@ Child Types
|
||||||
|
|
||||||
Child types describe how a child widget is placed on a parent widget. For
|
Child types describe how a child widget is placed on a parent widget. For
|
||||||
example, HeaderBar widgets can have children placed either at the *start*
|
example, HeaderBar widgets can have children placed either at the *start*
|
||||||
or the *end* of the Headerbar. Child widgets of HeaderBars can have the
|
or the *end* of the HeaderBar. Child widgets of HeaderBars can have the
|
||||||
*start* or *end* types. Values for child types a widget can have are
|
*start* or *end* types. Values for child types a widget can have are
|
||||||
defined in the widget's documentation.
|
defined in the widget's documentation.
|
||||||
|
|
||||||
Child types in blueprint are written between square brackets ``[]`` and before
|
Child types in blueprint are written between square brackets (``[`` ``]``) and before
|
||||||
the child the type is for.
|
the child the type is for.
|
||||||
|
|
||||||
The following blueprint code...
|
The following blueprint code...
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue