On 15 Jan 2009, at 10:34, Quentin Mathé wrote: > Hi David, > > Le 11 janv. 09 à 13:03, David Chisnall a écrit : > >> Hi Everyone, >> >> At the moment, I believe that there are some parts of >> EtoileFoundation >> that depend on parts of AppKit. Is this sensible? > > Hm no. Although it's quite possible I did that as a temporary solution > for a reason I have forgotten. I'll take a look at that.
The example that came to my mind was the XHTML-IM parser, which requires AppKit's NSAttributedString Additions. >> Recent versions of >> GNUstep let you link -gui against tools without getting any errors. >> Does anyone want to be able to use EtoileFoundation without AppKit >> being present? > > Yes, CoreObject for example :-) Is there a good reason for not linking CoreObject against -gui? >> If so, we should create a new framework for Étoilé >> extensions to AppKit (not EtoileUI, since it contains a lot of >> additional functionality). If not, then I have a few other things I >> want to move in to EF. > > It's fine to put AppKit extensions into EtoileUI if they don't overlap > with EUI features. EUI already includes various small AppKit > extensions (mostly categories). I'd rather not use EUI for this kind of thing (e.g. XHTML parsers / generators). It's quite a big framework that provides a fairly specific big new feature, and I think it will confuse developers to have simple AppKit extensions in there. I'd much rather we either had an EtoileAppKit (or something) framework, or we put them in EtoileFoundation. David _______________________________________________ Etoile-discuss mailing list [email protected] https://mail.gna.org/listinfo/etoile-discuss
