On Jun 10, 3:13 am, "Ville M. Vainio" <[email protected]> wrote:
>
> Perhaps porting it all would be a bit too big for a starter project.
> You could start by providing the essence of what the plugin does (it
> is reasonably documented) by adding a rclick_qt.py. I don't think
> 100% compatibily is as important as the possibility of having a node
> specific context menu in the first place.
>
OK, sounds good. I'll have a look - was meaning to ask about the
status of rclick.py anyway...
One thing I wanted to ask in the context of some of the recent
discussions about documentation and workflow, is about the actual
workflow of editing the .py files which make up Leo.
The trunk contains (eg) rclick.py, which IIUC is a 'derived' file. In
order to read this into Leo and navigate the outline structure etc. I
have been using "File | New", then "File | Import | Import Derived
File". This gives me an @thin node with the file present as subnodes
etc.
Presumably I should edit this and then ... export as a derived file in
some way, to create a new rclick.py?
I wasn't clear if this was the expected method, or whether there was,
perhaps, a corresponding 'rclick.leo' which I should be generating or
using.
Thanks for answering these newbie questions. I do think the
documentation suffers a bit from (as Edward puts it) the 'curse of
knowledge', and I hope to chip in with some suggestions for
improvement when I can.
Cheers
Jon N
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en
-~----------~----~----~----~------~----~------~--~---
