arsenetar/dupeguru
1
0
Fork 0
mirror of https://github.com/arsenetar/dupeguru.git synced 2025-03-10 05:34:36 +00:00
Code Releases Wiki Activity

Fix typos in docs

Browse Source
This commit is contained in:
Virgil Dupras 2013-11-28 22:49:26 -05:00
parent 3734bd6f6c
commit 31395d8794
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
hscommon/gui/base.py
View File

@ -17,11 +17,11 @@ class GUIObject:
"""Cross-toolkit "model" representation of a GUI layer object. """Cross-toolkit "model" representation of a GUI layer object.
A ``GUIObject`` is a cross-toolkit "model" representation of a GUI layer object, for example, a A ``GUIObject`` is a cross-toolkit "model" representation of a GUI layer object, for example, a
table. It acts as a cross-toolkit interface to multiple what we call here a :attr:`view`. That table. It acts as a cross-toolkit interface to what we call here a :attr:`view`. That
view is a toolkit-specific controller to the actual view (an ``NSTableView``, a ``QTableView``, view is a toolkit-specific controller to the actual view (an ``NSTableView``, a ``QTableView``,
etc.). In our GUIObject, we need a reference to that toolkit-specific controller because some etc.). In our GUIObject, we need a reference to that toolkit-specific controller because some
actions, have effects on it (for example, prompting it to refresh its data). The ``GUIObject`` actions have effects on it (for example, prompting it to refresh its data). The ``GUIObject``
is typically instantiated before its :attr:`view`, that is why we set it as ``None`` on init. is typically instantiated before its :attr:`view`, that is why we set it to ``None`` on init.
However, the GUI layer is supposed to set the view as soon as its toolkit-specific controller is However, the GUI layer is supposed to set the view as soon as its toolkit-specific controller is
instantiated. instantiated.
@ -31,7 +31,7 @@ class GUIObject:
.. attribute:: view .. attribute:: view
A reference to our toolkit-specific view controller. This view stats as ``None`` and has to A reference to our toolkit-specific view controller. This view starts as ``None`` and has to
be set "manually". There's two times at which we set the view property: On initialization, be set "manually". There's two times at which we set the view property: On initialization,
where we set the view that we'll use for our lifetime, and just before the view is where we set the view that we'll use for our lifetime, and just before the view is
deallocated. We need to unset our view at that time to avoid calls to a deallocated instance deallocated. We need to unset our view at that time to avoid calls to a deallocated instance

2
hscommon/gui/table.py
View File

@ -18,7 +18,7 @@ class Table(MutableSequence, Selectable):
In fact, the Table is very similar to :class:`~hscommon.gui.selectable_list.SelectableList` in In fact, the Table is very similar to :class:`~hscommon.gui.selectable_list.SelectableList` in
practice and differs mostly in principle. Their difference lies in the nature of their items practice and differs mostly in principle. Their difference lies in the nature of their items
theiy manage. With the Table, rows usually have many properties, presented in columns, and they they manage. With the Table, rows usually have many properties, presented in columns, and they
have to subclass :class:`Row`. have to subclass :class:`Row`.
Usually used with :class:`~hscommon.gui.column.Column`. Usually used with :class:`~hscommon.gui.column.Column`.