On Mon, 10 Nov 2014 08:01:36 -0600 Kent Tenney <kten...@gmail.com> wrote:
> Does Leo currently offer the ability to define a tree > structure template? I seem to recall this. > > Such that the great idea above wouldn't require a .leo file > but could live in a @tree node (or some such) Rings a very vague bell for me too, although nothing specific, it might be a long time ago. But I'm sure there are a lot of systems that ready to go tree layouts would be good for, Sphinx but also Django, the Python web framework, it has a somewhat complicated directory layout that is much easier to manage with Leo. OTOH active-path.py plugin is quite good for pulling in the layout after it's been created on disk by the Django utils. Hard to know where the sweet spot is for this. Cheers -Terry > On Mon, Nov 10, 2014 at 7:05 AM, Edward K. Ream <edream...@gmail.com> > wrote: > > On Sun, Nov 9, 2014 at 11:56 AM, Davy Cottet > > <cottet.d...@gmail.com> wrote: > > > >> > > My idea > > [is] to turn Leo complexity to the most simple but complete Sphinx > > editor. > > > > That's a great idea. Leo's rst commands do indeed have way too > > many hidden features. Maybe the set of features used by all of > > Leo's features is a largish subset of those features, but if we can > > do without them so much the better! > > > >> > > it could be possible to build a kind of Leo-Sphinx-template.leo > > containing all the needs of a sphinx project, without even > > modifying Leo's code and writing a new plugin. > > > > Interesting idea. At present, Leo's core rst related code is, of > > course, based on reStructuredText, not sphinx. I have no real > > opinion about whether using sphinx as a foundation would simplify > > things. > > > > QQQQQ > > 1 - First thing would be to give this template all the file/folder > > structure required by Shinx (build,sources, statics, templates, > > setup.py, Makefile...). > > > > 2 - Perhaps use attrib-edit-py to graphically configure conf.py > > parameters... otherwise, maybe just link to edit conf.py or maybe a > > new directive for every parameter (probably useless...) > > > > 3 - Make new menus by introducing right @settings and @commands > > (and even delete some default scary ones for newbies and useless > > for basic Sphinx use). > > > > For example I though about this kind of simple structure for this > > "sphinx-template.leo: > > > > @settings > > @menus > > @menu Sphinx > > @item Configure (gui edit for conf.py ?) or @item Edit > > conf.py and @item Edit conf.py > > @item - > > @menu make > > @item ReST > > [snip] > > > > @item html > > @item epub > > ... > > @menu Open > > @item html > > @item pdf > > @item epub > > > > That seems really easy to call make html or other make commands > > since it's always from the root folder. > > > > [snip] > > QQQQQ > > > > Seems reasonable. > > > >> > > So, I wonder if I'm right thinking of customization with this kind > > of sphinx-template.leo (eg not using myLeoSettings.leo and not > > using plugin system). > > > > The best, most stable code is code that doesn't need to be > > written. So I'm all for it :-) > > > >> > > Does Leo users use to share this kind of personal customized .leo > > file (I'm aware about security problem...). Are there a lot of > > Sphinx/Leo users ? > > > > It's hard to say anything for sure about Leo users because we don't > > know what percentage of them contribute to this group. All I can > > say is that it is not common *here* to share .leo files. However, > > it would clearly be possible to add entries to leoSettings.leo, or > > to put a sphinx-template file into the leo/config folder. It would > > then be conceivable to add support for a my-sphinx-template file... > > > >> > > Do you think it would be a good idea to build this kind of > > templates for vari > > o > > us basic needs (we could think about other static blog > > g > > ing tools like Pelican and this type of editing usages...), I mean > > different set of menus for different use ? > > Personally I think that could be a good way to make the power of > > Leo to really help people without programming skills. > > > > Yes, I think it would be a great idea. > > > >> > > Anyway, I'm beginning scripting around Leo An enjoy it. Thanks to > > the devs for offering that great tool to us python hackers > > :) > > > > You're welcome. > > > > Just so the NSA understands (yes, they *are* monitoring this > > conversation), I assume that you are using the word "hacker" in the > > sense that it first had about 40 years ago, namely a person who > > like to mess around with the internals of systems in order to > > understand it. Since then, the word "hacker" has acquired much > > darker meanings :-) > > > > 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 leo-editor+unsubscr...@googlegroups.com. > > To post to this group, send email to leo-editor@googlegroups.com. > > Visit this group at http://groups.google.com/group/leo-editor. > > For more options, visit https://groups.google.com/d/optout. > -- 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
