More HACKING updates.
This commit is contained in:
parent
a9819fe1bc
commit
5b7ee5d382
@ -295,7 +295,7 @@ mainly intended for debugging.
|
||||
|
||||
A new object can be registered by using
|
||||
+objreg.register(_name_, _object_[, scope=_scope_])+. An object should not be
|
||||
registered twice. To update it, `update=True` has to been passed.
|
||||
registered twice. To update it, `update=True` has to be given.
|
||||
|
||||
An object can be retrieved by using +objreg.get(_name_[, scope=_scope_])+. The
|
||||
default scope is `global`.
|
||||
@ -372,15 +372,12 @@ support a count which will be passed in the argument.
|
||||
|
||||
If the function is a method of a class, the `@cmdutils.register` decorator
|
||||
needs to have an `instance=...` parameter which points to the (single/main)
|
||||
instance of the class. Registering commands with multiple instances is not
|
||||
supported. For an example on how to solve that problem, see
|
||||
`qutebrowser.browser.command` which dispatches commands to the currently active
|
||||
tab.
|
||||
instance of the class.
|
||||
|
||||
The `instance` parameter is the name of an object in the object registry, which
|
||||
then gets passed as the `self` parameter to the handler. The `scope` argument
|
||||
selects which object registry (global, per-tab, etc.) to use. See the
|
||||
<<object-registry object registry>> section for details.
|
||||
<<object-registry,object registry>> section for details.
|
||||
|
||||
There are also other arguments to customize the way the command is registered,
|
||||
see the class documentation for `register` in `qutebrowser.commands.utils` for
|
||||
|
3
doc/TODO
3
doc/TODO
@ -130,12 +130,11 @@ style
|
||||
enum/namedtuple).
|
||||
- Config init and some persistent objects should be moved out of QApplication.
|
||||
- Use separate logger for config
|
||||
- Make more stuff private
|
||||
- Don't keep references to parent QObjects!
|
||||
- Use unittest.Mock and especially unittest.patch more.
|
||||
- Use decorators for on_config_changed
|
||||
- Will also make it easier to implement section-changed handlers for
|
||||
:reload
|
||||
- Check where using signals would be better than objreg.get.
|
||||
|
||||
dwb keybindings to possibly implement
|
||||
=====================================
|
||||
|
Loading…
Reference in New Issue
Block a user