>>>>> "Joacim" == Joacim Persson <[EMAIL PROTECTED]> writes:
Joacim> It's also the most obvious object-oriented approach. Maybe one
Joacim> day we want to have dynamically loadable insets like `ez' has
Joacim> (wp for AUIS). That would be a lot easier to implement if all
Joacim> the inset-specific code is in one place. I missed the start
Joacim> of this thread; was there some problem with this method? How
Joacim> will these three designs affect the user interface design btw?
At least, if we have a script language, it should be possible to write
(simple) insets in this script language...
Joacim> I can imagine cases when the objects (insets) will be sending
Joacim> their output to something else than a stream, and cases when
Joacim> some insets doesn't implement output methods for all formats;
Joacim> Ascii from figure insets for instance -- wouldn't make much
Joacim> sense in most cases (ascii-graphics? =) (hmm.. it could be
Joacim> nice to be able to search for a figure by its filename; that
Joacim> could be something to export to a find&replace `writer')
Each inset could have a 'bool matches(LString)' method which is called
by the search function. Replace would be more difficult, of course.
JMarc
