Rev 4d91f58 may be the last rev before committing with g.new_dispatch =
True. The adventurous are invited to set g.new_dispatch = True.
All tests pass. No known problems remain. I have been eating my own dog
food without incident.
This rev completes the difficult and risky phase of the project. The second
phase should be straightforward:
1. Define all commands in official plugins with either
@g.command('command-name') or @cmd('command-name'). This would involve
defining per-class cmd functions.
2. Eliminate the code in plugins_menu.py that creates the invisible "cmd_"
convention for defining commands. This convention is no longer needed now
that @cmd and @g.command exist.
3. Regularize the signatures for all decorated commands:
@g.command('command-name')
def my_command(event=None):
...
@cmd('command-name')
def my_command(self,event=None):
...
This will simplify the unit test: "@test all commands have an event".
4. Remove the g.new_dispatch switch and all code disabled when
g.new_dispatch is True. This includes c.universalCallback, which will move
to the attic.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
