Hello, Thanks for answering.
Yes, the goal would be to make LyX a frontend for restructuredText. As I see it, the user should be able to open (and save) .rst files in lyx without been aware of the lyx internal format at all (ie LyX could be set as the default editor for .rst). The LyX file created would be some sort of temporal file. Converting to and from rst should be a fairly reachable goal, at least for the directives that have a straightforward translation to LyX, as there is already a parser that converts rst to nice python objects ( http://docutils.sourceforge.net/docs/dev/hacking.html ) and there is also a Lyx parser for python, so it's about putting the two together. The Lyx-specific insets (like ERT) would appear on the .rst file as comments, so it would be possible to recover them. As for the document settings, ideally only the changes from the defaults should be reflected on the .rst, although that seems difficult (and also changing the defaults would change the existing file settings). The unimplemented resT features would be normal plaintext in Lyx (or perhaps notes, or some rest-ERT is better?) so they can be used back with the rest tools and warn the user that other lyx exports won't work on them. In this way the user would always be able to use the file in some way other than with sphynx/other resT tools. A secondary goal could be the implementation of a shpinx configuration menu in the document settings (for managing the conf.py file of sphinx) and a sphinx toolbar to call sphinx-build and so on, that would be active by default when opening a .rst file. Hope this sounds reasonable. Zahari. On Tue, Apr 23, 2013 at 3:58 PM, stefano franchi <stefano.fran...@gmail.com>wrote: > Hi Zahari, > > could provide some more details on the use case scenarios for your > possible project? Are you seeing LyX as a possible front end > to interface with resT/Sphinx? Or are there other uses for resT I am > unaware of? I think some developers expressed interests in a LyX--> resT > conversion in the past (Guenter Milde?) and even offered to help on the > docutils side. Perhaps a more detailed description would help us all > understand better what you have in mind. It certainly would help me. > > Cheers, > > Stefano > > > On Tue, Apr 23, 2013 at 4:54 AM, Zahari Dim <zaha...@gmail.com> wrote: > >> Some time ago I was involved in a lab project that would require >> controlling a lot of machines using mostly python. We would need to write a >> lot of documentation, to document the code, but mostly to explain the >> configuration of the machines. >> >> When I proposed using resT/sphinx for that, the idea was ruled out before >> there isn't a good graphical editor for resT and not everybody was >> comfortable with having to learn yet another typesetting system with no gui >> aid. >> >> I think LyX could be good for this problem. I see that adding support >> for resT has been discussed before with some positive opinions. It would >> also allow adding some complex LaTex markup and using the same doc file >> for publication if needed. >> >> Do you believe this could be a good project for GSOC? Does it make sense >> to develop a full proposal? >> >> Thanks, >> >> Zahari. >> > > > > -- > __________________________________________________ > Stefano Franchi > Associate Research Professor > Department of Hispanic Studies Ph: +1 (979) 845-2125 > Texas A&M University Fax: +1 (979) 845-6421 > College Station, Texas, USA > > stef...@tamu.edu > http://stefano.cleinias.org >
