I'm not sure if this is related, seems maybe.

I've longed for "specialized Leos": a config file which defines
- menus
- commands
- templates
- ...

which encapsulate the learning curve for an application.

Most apps consist of a set of files:
- source
- configuration
- data
- logs
- doc

I need to learn, or remember:
- where they are
- what they do
- how to troubleshoot
- how to test

All this before addressing the real issue: editing the _content_ of the files
to achieve a desired result.

A Leo 'instance' could be configured such that it understand the architecture,
is loaded with commands and buttons and menu items which understand the
relationships and offer explanations, allowing me to jump right to the
file contents,
or at least obviate a bunch of head scratching.

I'm currently trying to figure out Salt http://saltstack.org (which I
think is TheNextBigThing)
and, the figuring involves understanding the relationship between a
bunch of files:
a relationship which could be codified into a Leo customization which
offered a tree of
nodes having the relevant files loaded as @auto, a set of buttons
which ran scripts
using node contents, context sensitive help ...

One could imagine the same for Apache, LDAP, Pyramid, Samba ...

I've tried several times to implement this sort of thing, my Leo-Fu us
too weak, I
return to doing the actual work I need to do instead of building the
tool to make
the work easier.

Maybe this isn't related to your interests, if so, ... nevermind ...

Thanks,
Kent

On Wed, Sep 26, 2012 at 9:26 AM, Steve Litt <[email protected]> wrote:
> On Wed, 26 Sep 2012 07:42:48 -0500, Edward K. Ream said:
>> On Mon, Sep 24, 2012 at 6:03 PM, Steve Litt
>> <[email protected]> wrote:
>>
>> > I'm not sure if I heard wrong, confabulated some memory or what, but
>> > somewhere I got the impression that you could outline a computer
>> > program in Leo, press a button, and get a Python app with a GUI
>> > interface popping out. Is this true, or was I hallucinating?
>>
>> Interesting questions.  Thanks for asking.
>>
>> If by "press a button" you mean typing Ctrl-S, then Leo is an example
>> of such an app :-)
>>
>> But I suppose you want to run a gui-based program from within Leo.
>
> No. I want to *author* a program within Leo, including data entry
> forms, and then press a button (type Ctrl+S), and have it generate the
> executable I authored in Leo. Then other people just run the program
> from the command line.
>
> [clip]
>
> Edward, I am sooooooo tired of all the hassle I need to go through to
> build an app with a GUI user interface. Qt, Gtk, PythonTk, Java+Swing,
> Rails, even Lazarus -- they're all such a clunky procedure for
> something that *could* be so simple. An input screen is just a set of
> specifications, but most of these tools make it into an event-driven
> bowl of spaghetti.
>
> What would be cool is to outline the input fields that should appear on
> a screen -- what database table row and column they edit, what entry
> and exit routines should be run on the input field, etc. Then press
> Ctrl+S and I get a program. I don't care whether it's a python program,
> or a binary executable, or something else. Just something.
>
>> For truly stand-alone apps, you would proceed similarly, but you would
>> run the app in a separate process.  That way the event loops are
>> separate, and you could use perl or tcl/tk or ruby or whatever.
>
> I don't understand the preceding paragraph, but it sounds like this is
> worth investigating. Is there any documentation on creating an app in
> Leo?
>
> Thanks
>
> SteveT
>
> Steve Litt                *  http://www.troubleshooters.com/
>                           *  http://twitter.com/stevelitt
> Troubleshooting Training  *  Human Performance
>
> --
> 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.
>

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