On 3 Feb 2009, at 22:16, Eric Wasylishen wrote: > Hi, > There are several frameworks which haven't been modified in quite a > while, and seem to be superseded by newer frameworks. I'm wondering if > I can move these to the Deprecated directory: > > Frameworks/AddressesKit/ > - David was saying that the AddressKit API is poorly designed, and > we'll need a new one which uses CoreObject (if we need a framework at > all?).
I hate this API more than any other in OS X (with the exception of the keychain, which can be blamed on Classic MacOS), and this implementation manages to be even worse than the Apple one, but I'd rather wait until we had a replacement before deprecating it. > Frameworks/BookmarkKit/ > Frameworks/OrganizeKit/ > Frameworks/CollectionKit/ > - These are all precursors of CoreObject, right? > > Frameworks/DistributedView/ > Frameworks/PaneKit/ > Frameworks/InspectorKit/ > - Looks like EtoileUI will replace the functionality all of these. I'm happy to deprecate all of these. The last three, in particular, keep causing me build failures. Check with Quentin first though... > Frameworks/MultimediaKit/ > - Superseded by MediaKit (though MediaKit doesn't yet play video, so > maybe shouldn't be moved?) Is anything using MultimediaKit? It's GPL'd, so I don't want it to stay in the tree any longer than it has to. > Languages/Io > - Doesn't work, as far as I know I think LanguageKit should be expressive enough now for an Io port front-end. Volunteers? I don't think this has worked for a while though, and isn't connected to the default build, so I'm happy to see it go. David _______________________________________________ Etoile-dev mailing list [email protected] https://mail.gna.org/listinfo/etoile-dev
