Andre Poenitz wrote: > May I suggest a slightly different approach? > > Let's have some MetaInset that's a proper LyX inset, i.e. deriving > from InsetBase, but which mainly acts as a data storage capable to > store attribute and CDATA contents. The parser (expat or whatever) > only generates a tree of these MetaInsets and in a second pass we > transform this into 'real' insets.
Which is nice, in that the 'big', LyX file parser is simple, but nasty in that each individual inset must have it's own little parser to read these data. That's essentially what we have now with Inset::read. Not that I'm saying that that's a bad thing... -- Angus
