On 17 Jul 2007, at 00:21, Yen-Ju Chen wrote: > I think it is a good idea about puting it into EtoileFoundation, > but probably after 0.2 release.
I'll start renaming the classes to from TR* to ET* in preparation, and add it after 0.2 is out if no one has any objections. > Then we can think about how to organize the EtoileFoundation. > For example, there are classes handling thread in EtoileFoundation > while there are also EtoileThread. > My idea is to have them as subprojects of EtoileFoundation So EtoileFoundation becomes a meta-framework, and people can just link to the individual frameworks if they don't need everything? Seems sensible. I'd like to put EtoileThread into EtoileFoundation. > Another thing is that the use of TRXML for Vienna is > because NSXML is not complete and TRXMLParser can tolerate > for bad syntax or truncated xml. > So I think we need to define what TRXML does so that it won't expand > to be a full-featured XML parser identical to NSXMLParser. I have no intention of writing a full-featured XML parser; there are enough of them already. TRXML was meant to support the 10% of XML that 90% of people need. If you need a full XML parser, there's libxml2, and there will be NSXML* eventually. If you just need to deal with simple XML data then there's EtoileXML[1] :-) > Basically having some document in the header is fine. The headers contain some documentation, which I think explains the limited scope. If it doesn't, I'll add something. > There are a few classes in Vienna dealing with XML which may be > useful, > for example, parse date string using libcurl (expensive and should > be rewritten), > pre-process XML data to eliminate bad syntax before parsing, > estimate encoding before xml parser which use string instead > bytes (NSData). > > By the way, Vienna is under Apache 2.0, > which should be compatible with EtoileFoundation. I'd have to check, but as I recall Apache 2.0 has a patent defence clause that makes it incompatible with GPLv2 (GPLv3 has some extra Apache 2-compatibility conditionals). I don't have a problem with making EtoileFoundation incompatible with GPLv2 (although I'd like to keep it compatible with v3 if we can), but I think we should see if anyone else has any objections. David [1] EtoileXML? ETXML? Is the convention to use Etoile* for the framework name and ET* for the prefix? Do we even have a guideline for this yet, or are we still making it up as we go along? _______________________________________________ Etoile-dev mailing list [email protected] https://mail.gna.org/listinfo/etoile-dev
