Jean-Marc Lasgouttes writes: > Either these LFUNs are like the others > and having an ascii representation of the > arguments is a must for scripting, or they > are not like the others and they should be > pure C++.
Agree 100% Note that there is absolutely no reason why some "outside of LyX entity", pybliographer say, couldn't send LyX an LFUN to create or modify a citation inset. With the current string interface that is. Modification would require the ability to post a serialized version of the inset through the LyXServer but conceptually everything is there to allow us (you) to do that. Using boost::any closes that door. My understanding is that boost::any cannot be serialized by boost::serialization. So, I think we need to discuss what we want to be able to do with all this. Angus
