Recent work has created leoPrototypes.py and the leo/proto directory tree. 
But I see now that neither is needed!

- The proto-* commands may as well be defined in @button nodes.
  They depend only on g.execute_shell_commands_with_options.

- Settings associated with the proto-* commands allow the actual prototype 
code to be located anywhere.

The natural place for prototypes is the leo-editor-contrib 
<https://github.com/leo-editor/leo-editor-contrib> repo.  All of us devs 
should be able to add code to the Projects folder there. We would pull the 
code and point our proto-* settings at the appropriate directories. We can 
push our changes to leo-editor-contrib as well.

There is no hurry to do any of this because the proto branch will likely *never 
*be merged into master. Instead, only g.execute_shell_commands_with_options 
will migrate to master.

Your comments, please.

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 https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Reply via email to