I've been thinking a lot about this whole EWL/ETK mess. Is there ANY
way for these two projects to co-exist? Even share some of the same
code? Could ETK be merged with EWL (perhaps have separate name spaces
for each API under EWL?), at least then, applications can still link to
EWL but use either API style. That is what we're talking about mainly
here, is the fact that ETK emulates GTK while EWL has a new
implementation. I know this would be a lot of work. There's bound to
be useless duplication, but at least it could be kept to a minimum, and
there wouldn't be this huge fork in the road for new applications (and
existing ones) to make a decision which E toolkit they're going to use.
Are both sides willing to work together to provide a way out of this mess?
If (and I suspect) the answer is no, then I vote for removing ETK and
have it be an outside project. Not that a "vote" has been called...
-Blake
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
