Fix more typos
This commit is contained in:
parent
4bed437d50
commit
530e64e9ec
|
@ -17,7 +17,7 @@ Awesome provides 2 collections of widgets:
|
||||||
|
|
||||||
### Containers
|
### Containers
|
||||||
|
|
||||||
A container is a widgets that wraps another widget. It can be used to add
|
A container is a widget that wraps another widget. It can be used to add
|
||||||
decorations or to modify the content of the child widget.
|
decorations or to modify the content of the child widget.
|
||||||
|
|
||||||
@DOC_container_WIDGET_LIST@
|
@DOC_container_WIDGET_LIST@
|
||||||
|
@ -109,7 +109,7 @@ Result:
|
||||||
### Use a `wibox.layout.align` layout
|
### Use a `wibox.layout.align` layout
|
||||||
The `wibox.layout.align` is a little different. While most layouts will
|
The `wibox.layout.align` is a little different. While most layouts will
|
||||||
ignore any `nil` lines, the `align` layout relies on them so `left`, `middle`
|
ignore any `nil` lines, the `align` layout relies on them so `left`, `middle`
|
||||||
and `right` can be defined
|
and `right` can be defined.
|
||||||
|
|
||||||
Code:
|
Code:
|
||||||
|
|
||||||
|
@ -177,7 +177,7 @@ Code:
|
||||||
### Accessing widgets
|
### Accessing widgets
|
||||||
|
|
||||||
For each widget or container, it is possible to add an `identifier` attribute
|
For each widget or container, it is possible to add an `identifier` attribute
|
||||||
so that it accessed later.
|
so that it can be accessed later.
|
||||||
|
|
||||||
Widgets defined using `setup` can be accessed using these methods:
|
Widgets defined using `setup` can be accessed using these methods:
|
||||||
|
|
||||||
|
@ -191,10 +191,10 @@ the chain has a valid identifier. The last one doesn't require long paths,
|
||||||
but it is not easy to get a specific instance if multiple widgets have the
|
but it is not easy to get a specific instance if multiple widgets have the
|
||||||
same identifier.
|
same identifier.
|
||||||
|
|
||||||
WARNING: The widget identifier must not use reserved name. This includes all
|
WARNING: The widget identifier must not use a reserved name. This includes all
|
||||||
method names, existing widget attributes, `layout` and `widget`. Names should
|
method names, existing widget attributes, `layout` and `widget`. Names should
|
||||||
also respect the Lua variable conventions (case-sensitive, alphanumeric,
|
also respect the Lua variable conventions (case-sensitive, alphanumeric,
|
||||||
underscore characters and non-numeric first character)
|
underscore characters and non-numeric first character).
|
||||||
|
|
||||||
Code:
|
Code:
|
||||||
|
|
||||||
|
|
|
@ -46,7 +46,7 @@ non-exhaustive list of possible errors:
|
||||||
the best way to debug this is either using `print()` or using `gdb`. For
|
the best way to debug this is either using `print()` or using `gdb`. For
|
||||||
this, see the [Debugging tips Readme section](../documentation/01-readme.md.html)
|
this, see the [Debugging tips Readme section](../documentation/01-readme.md.html)
|
||||||
* Deprecated APIs: The Awesome API is not frozen for eternity. After a decade
|
* Deprecated APIs: The Awesome API is not frozen for eternity. After a decade
|
||||||
of development and recent changes to enforce consistency, it doesn't hasn't
|
of development and recent changes to enforce consistency, it hasn't
|
||||||
changed much. This doesn't mean it won't change in the future. Whenever
|
changed much. This doesn't mean it won't change in the future. Whenever
|
||||||
possible, changes won't cause errors but will instead print a deprecation
|
possible, changes won't cause errors but will instead print a deprecation
|
||||||
message in the Awesome logs. These logs are placed in various places
|
message in the Awesome logs. These logs are placed in various places
|
||||||
|
|
|
@ -1,7 +1,7 @@
|
||||||
# Using Cairo and LGI
|
# Using Cairo and LGI
|
||||||
|
|
||||||
These days, Awesome interface is mostly based on a library called LGI. It provides
|
These days, Awesome's interface is mostly based on a library called LGI. It provides
|
||||||
access C libraries such as GTK, GLib, Cairo, Pango, PangoCairo and RSVG using
|
access to C libraries such as GTK, GLib, Cairo, Pango, PangoCairo and RSVG using
|
||||||
Lua code without having to write actual "glue" C code.
|
Lua code without having to write actual "glue" C code.
|
||||||
|
|
||||||
This is done using the GObject-introspection framework. The main advantage is
|
This is done using the GObject-introspection framework. The main advantage is
|
||||||
|
|
Loading…
Reference in New Issue