On Thu, Nov 29, 2012 at 4:08 PM, Todd Greenwood-Geer <
[email protected]> wrote:
>
> I'm currently wrapping up a project with about 400 java files and a
> handful of html/bash/python. As a test, I tried importing this project into
> leo, as follows:
>
[snip]
> At this point, I have a few questions:
>
> Q: How could I have referenced the @Path from within the script? I opted
> for the cheap and easy route by simply using '.', and hey, it worked! Is
> that idiomatic?
>
Leo has several global functions in leoGlobals.py that handle directives.
See::
@file leoGlobals.py-->Commands & Directives-->g.Directive utils...
They are not particularly easy to use, though. Look through Leo's sources
for examples.
>
> Q: The real issue I'm having is that when I press Ctrl-S to save, I am
> asked if I want to modify the file...um, for each file. The only way out of
> this is to kill the process. What am I doing wrong? And, this, btw - seems
> at least partly like a bug.
>
It surely is a bug. I might have made a private note to myself about this,
but just in case I'll mark this email as a bug deserving quick attention.
>
> Q: Supposing that I can successfully import a project, how do I make it a
> shadow project?
>
By changing @auto or @file or whatever to @shadow, then saving.
Suggestions:
>
> 1. I first started looking into leo a year or so ago. I thought it was
> amazing, but then dropped it b/c other projects took precedence.
> Personally, I think the 'killer' feature is the ability to embed diagrams
> and notes within the context of code. I'm sure it's possible to open an
> external editor based on the file type...but typically, one is going to
> edit a diagram and that product will spit out it's custom file format. At
> some point you'll use the diagram editor to spit out an image file that
> something like leo could display. It would be so cool if that sort of
> integration could be made smoother. Either do all the editing within leo
> (probably not possible) or have leo invoke the target editor and somehow
> display the image as appropriate.
>
Not a bad idea, but it has low priority at present.
>
> 2. I'm a developer, and I happen to really enjoy programming in python.
> However, even for me, the documentation is a bit daunting. This tool does
> so much, it's a bit overwhelming. In the back of my head, I hear, 'screw
> this, let's get some work done in VIM, iPython, IDEA, etc.". One thing I
> keep wondering is whether I really need to have clone nodes in the type of
> coding I do... I only ever define a function once. However, the ability to
> force my focus onto just a single function is really nice... really
> isolates things.
>
Letting people know what Leo can *already* do has the highest priority. An
improved help system is a start. Creating much simpler tutorials is
another step. Most of this should happen before the next official release.
>
> 3. On the flip side, it took me just a few minutes to add my own key
> bindings to switch between tabs. And the view-rendered for rest, markdown,
> html, etc. is really killer. I'm going to play around with this and
> erlang/rebar/cowboy and see how it fits that programming model. All I can
> ask for are more tutorials that just show you doing your normal work
> routine, and more videos with the same sort of focus.
>
That may happen, but I wouldn't wait for it :-) Please feel free to ask
whatever questions you like. Answering those questions becomes pre-writing
for tutorials and other documentation, so it has very high priority.
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
