Hey Eric, Le 18 juin 09 à 23:19, Eric Wasylishen a écrit :
> Hi, > I wanted to tidy up EtoileFoundation a bit - I think it can be divided > in to two groups of classes: those which are part of the core of > Etoile, and handy utility classes. I think this would be cleaner, and > help emphasize the really important classes. I'm not entirely convinced by this split, but I don't dislike it either :-) > EtoileFoundation: > ==================== > > ETFilter I'm not sure this class will survive in its current state. It is not used anywhere currently. Feel free to move it to branches/Deprecated/EtoileFoundation. > ETModelDescription > ETObjectChain > ETPropertyValueCoding > ETTransform > ETUTI > ETUUID > Macros > NSObject+Etoile - Reflection code, hopefully soon deprecated when I > write a mirror reflection api using ObjectiveC2 :) hehe :-) > NSObject+Mixins > NSObject+Model > NSObject+Prototypes ok. > EtoileFoundation/Utilities: > ==================== > > ETCArray > ETException - not quite sure what this does.. will this be needed with > ObjC2 style exceptions? These are ObjC exception improvements. e.g. restartable exceptions. See David's paper: <http://www.swan.ac.uk/compsci/research/reports/2008/CSR14-2008.pdf > I haven't played them at all I must say. However I would include them in the main part. > ETGetOptionsDictionary - function for processing command line args > ETHistoryManager I would also put ETHistoryManager with the core classes. I plan to use it in EtoileUI combined with ETPaneLayout to support navigational features. I might miss something, but I think this class should really be named ETHistory and not ETHistoryManager. Each instance manage history entries and not histories, in other words each ETHistoryManager object just represents a simple history. For example, in the WebKit there is WebHistory which contains WebHistoryItem as elements. imo manager classes should only be created when they have no specific corresponding names in the real-word. > ETTranscript - transcript for Smalltalk > NSArray+Map - implementation of "map" as higher order messaging (Does > this belong in the main part of EF?) This should be in the main part imo. > NSFileManager+NameForTempFile > NSFileManager+TempFile One of these two implementations is deprecated and has to be removed, but several modules depend on the old implementation. > NSIndexPath+Etoile > NSIndexSet+Etoile > NSInvocation+Etoile - convenience factory method for NSInvocation > NSString+Etoile - some convenience methods for NSString > NSURL+Etoile - some convenience methods for NSURL ok. > UKPluginsRegistry UKPluginsRegistry should be in the main part but renamed ETPlugInRegistry. It needs improvements but it can be used in various places to load components/plugins and track what has been loaded. Cheers, Quentin. _______________________________________________ Etoile-dev mailing list [email protected] https://mail.gna.org/listinfo/etoile-dev
