Thanks every one for your contribution to this subject. I have to accept that I got a bit lost on the discussion about databases ;)... anyway, i got a lot of useful informations there.
- @Edward : *"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."* I think you gave me more complicated intentions that are mines... By the way, does that mean that *@bool rst3_call_docutils = False* make Leo use Sphinx for generating html (externally, that's the point) but still use docutil to generate rst files ? I don't think that's really a limitation (at least to begin), but I do not really know yet which rst features are exclusively brought by Sphinx. "*I use sphinx in a stylized way, after creating rST .txt files.*" In fact, that's also what I wanted to do, but just by adding some menu/command shortcuts to run sphinx "make" commands and configure settings plus by integrating sphinx file/folder structure into a .leo model file (if possible...). - From Kent & Thierry exchanges, I deduce that converting a leo tree structure to a folder/file structure is not as trivial as I thought... If I understand well, active-path.py does only the other way ? Are'nt @file & @auto able to generate real files ? Are folders the main problem ? - @Kent*"Such that the great idea above wouldn't require a .leo file but could live in a @tree node (or some such)"*. I think that's exactly what I mean : this "template" idea (maybe I should call it model ?) is no to create another "setting type .leo file" but a "standalone project file" including all settings needed for user to easily work with sphinx (including file/folder structure). To be clear, a user would have simply to download it, open it, and modify directly it's content with his custom parameters, rst contents, templates, Sphinx settings.... - In my mind, the "sweet spot" would be to build the most simple and ready to use interface (ie menus) for a very specific task. Sphinx documentation is the first of them as it involve, I think, much less complexity than a Django project for which we could buid a lot of more complex features (ie shortcuts to create new models, views, urls, Templates...). And the fact is that this Leo based Sphinx editor would be really useful to document any of my further Leo & Phyton projects ;) - Sorry Edward, but I don't really understand what you mean by "*perhaps you can devise a simpler way to drive the script from outline data..*." But I think that's why I'm lost on the database discussion part :D PS : a very practical question to finish : which Leo command return the path of the currently opened .leo project ? -- 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.
