Siklos/blueprint-compiler
1
0
Fork 0
mirror of https://gitlab.gnome.org/jwestman/blueprint-compiler.git synced 2025-05-04 15:59:08 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

Apply 6 suggestion(s) to 1 file(s)

Browse source
This commit is contained in:
FeRD (Frank Dana) 2022-10-19 12:04:47 +00:00 • committed by Megadash452
parent 0fe58ffc37
commit ba8ec80456
1 changed files with 11 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

16
docs/tutorial.rst
View file

@ -86,7 +86,7 @@ A good place to start is
Naming Widgets
~~~~~~~~~~~~~~
Widgets can be given **name/ID**s so that they can be referenced by other
Widgets can be given a **name/ID** so that they can be referenced by other
widgets in the blueprint.
.. code-block::
@ -301,7 +301,9 @@ Templates
CSS Style Classes
-----------------
.. Unsure if to group styles with widget-specific items
.. TODO: Unsure if to group styles with widget-specific items
Widgets can be given style classes that can be used with your CSS or
`predefined styles <https://gnome.pages.gitlab.gnome.org/libadwaita/doc/1.2/style-classes.html>`_
in libraries like Libadwaita.
@ -350,8 +352,8 @@ window, or pop up when you right-click some other widget. In Blueprint a
``menu`` is a ``Gio.MenuModel`` that can be shown by MenuButtons or other
widgets.
In Blueprint, ``menu``s have *items*, *sections*, and *submenus*.
Like widgets, ``menu``s can also be given a **ID**.
In Blueprint, a ``menu`` can have *items*, *sections*, and *submenus*.
Like widgets, a ``menu`` can also be given an **ID**.
The `Menu Model section of the Gtk.PopoverMenu documentation <https://docs.gtk.org/gtk4/class.PopoverMenu.html#menu-models>`_
has complete details on the menu model.
@ -413,7 +415,7 @@ 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
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 following blueprint code...
@ -429,6 +431,8 @@ The following blueprint code...
\... would look like this:
.. code-block::
---------------------------
| Button |
---------------------------
@ -446,6 +450,8 @@ And the following blueprint code...
\... would look like this:
.. code-block::
---------------------------
| Button |
---------------------------