Zitat von Martin Friebe <[email protected]>: >[...] > But for Lazarus a benefit could be, that such a model could also contain > data, on top of the information hold for synEdit. The Lfm (FormDesigner) > info could become part of this.
What has synedit to do with the form designer? I'm not sure how synedit should handle the unit concept. The lfm is associated with the unit. A unit has a starting file (e.g. unit1.pas) and an arbitrary list of include files, plus the po file of the project/package, the fpdoc xml file and .res files. Each of them work together and need very different code. > The it would only need an appropriate serialize class to save all of them. > > This may simplify the current implementation (even so I admit much based > on assumption on fragmented knowledge) which has to retrieve this info > from the various components. (the need for the source-editor or main ide > to fetch the text from SynEdit) synedit is the 'lines' view of the sources. Most of the lazarus code don't work with lines, but with whole files or absolute positions. > The Model could also carry callback lists, so the anybody who needs to > know that it was loaded or saved could register a callback > Model.AddOnSerailizedCallback( AMethod ) > > AMethod may be called with the reason, why serialization took place (e.g > saved to file) > > > Just starting some basic thought on it. It will be a very long way, and > a very long time before any of this goes into implementation. Mattias _______________________________________________ Lazarus mailing list [email protected] http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
