Hi all,

As I have said, I use Leo mostly for documentation. The more I understand about the Leonine way and reStructuredText, the more I use Leo for that. I'm also exploring Pharo Smalltalk and Seaside. One of the things I like most about Smalltalk environment is the ability to select chunks of code and execute them (using the DoIt command). Because Leo is used for me to document more heterogeneous environments I'm thinking in having two possibilities:

The first one is enabling <<section>> markup as in literal programming inside reStructuredText trees. So for example, suppose I have this chunk of a document about how to execute redmine:

[start chunk]

We are going to start testing redmine in the native rails WEBrick server:

.. sourcode:: shell

    cd ~/Programas/Redmine/1.2.1/
    ./script/server -e production

The output will be something like:

[end chunk]

and I want to change it for something like:

[start chunk]

We are going to start testing redmine in the native rails WEBrick server:

<<start redmine with WEBrick>>

The output will be something like:

[end chunk]

and the <<start redmine with WEBrick>> contains:

[start chunk]
.. sourcode:: shell

    cd ~/Programas/Redmine/1.2.1/
    ./script/server -e production

[end chunk]

So I can clone all chunks of code inside chunks of documentation and create a tree-script that contains all chunks, create a derivated file and execute it.

The second option is to have a similar behavior as Smalltalk, selecting pieces of code, may be all the indented code inside a "..sourcecode::" directive and a command to execute it.

Any comments or pointers about how to execute any of them would be greatly appreciated.

Cheers,

Offray

--
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.

Reply via email to