On 2010-03-05, Janek Kozicki wrote: > rgheck said: (by the date of Fri, 05 Mar 2010 10:18:35 -0500)
... > besides improving that communication, the "only" missing thing is to > be able to declare variables within maxima, and operate on them > later. It means a running maxima session, instead of > standalone/separate calls for each thing. > Ideally I would want to derive calculations within lyx, while > writing comments about it. All with the beauty of latex. > Perhaps I'll start with this communication formatting thing that you > explained, it should be an easy start to get feel of the workings. >> What you are proposing, I think, is somewhat different and looks almost >> like one of LyX's "external" insets. ... >> My sense is that, for full maxima integration, this is definitely the >> easiest way to go. The disadvantage, compared to the current system, is >> that there's no integration with the math insets. > I see. I would prefer to stay within lyx boundaries. A split window, > with the maxima buffer or such. I don't know yet. Storing input in > external file is better than putting it into .lyx as comments, > I didn't know this is possible. maxima runs well even in a text > terminal, it should be possible to pipe this somehow. One more thing to consider is using the lyxserver pipes. E.g. I wrote some experimental "LyX output" for swiginac (a Python wrapper of the ginac C++ library, http://swiginac.berlios.de/) using my LyXServer Python package (available via the LyX wiki) but the other way is also feasible, as the lyxserver is bidirectional. Günter
