On Thu, Apr 14, 2011 at 2:53 PM, Hans-Peter Diettrich <[email protected]> wrote: > I'd separate the construction of metafiles from their use (drawing). Once a > file has been created - be metafile, BMP, PNG, HTML, PDF etc. - its main > purpose is distribution and presentation, not editing. In the simplest case > drawing primitives are recorded in an metafile by e.g. switching the canvas, > and all editing can occur in another application, independent from any > metafile recorder and player. > > When an editor (AutoCad...) uses metafiles to store the entire state of a > project (including invisible objects, symbols...), for later reload and > continued editing, these parts can stay application-specific, and better > should be stored in accordingly application-specific files. A general > metafile should not contain more than the final drawing primitives. For > editable metafiles it will be sufficient to allow for application-specific > extensions, which can be skipped easily by the player base class (like > unknown XML tags). Specific handling then can be built into derived classes.
I am totally lost about how this all applies to fpvectorial. Maybe you could explain more specifically how your ideas would apply to fpvectorial? wiki page: http://wiki.lazarus.freepascal.org/fpvectorial -- Felipe Monteiro de Carvalho -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
