i only took a look at the result (not the code), and it made me wonder what exactly is gained by this?
A non-ERT way to use listings package.
implementation wise i find it strange to have code in a collapseable inset (i also tried ERT, as in attached, and found that this is pretty similar ui wise). wouldn't you want to set "code listing" or something like that in the layout box and just start to type away?
This is what I tried to do at first. However, in lyx, every line starts a new paragraph and you will get an extra newline between your program code. This is hard-coded to lyx and I do not see a good solution to this problem. The only way to output things verbatim is through insets like ERT. Whether or not InsetListings should be collapsible is open to discussion. Another problem is that the layout solution does not handle lstinline.
also, why have code as a "child document"? i would think it fits more with "external material"
This also goes to verbatim which is coded as a 'child document' as well. I personally dislike the menu name 'Child document" because child document should be editable (.lyx) document. Anyway, I agree with Georg to put lstinputlisting there, although JMarc seems to prefer 'external material'.
i am not a potential user, but i am not so sure that if you would design clean ui support it would look like this.
The GUI part is weak but that can be improved later by the GUI guys.
more importantly, i have the impression that this is a very big patch to get rid of very little ERT...
Some people do hate ERT. :-)
finally, a little bug: when copy-pasting the inlined code, the inlined setting gets lost
Thanks. I will have a look. Cheers, Bo
