On Wed, Sep 06, 2006 at 07:34:48AM +0000, [EMAIL PROTECTED] wrote: <snip> > > It's going to be just about impossible to do this any other > way than with a separate CVS version to work with. >
A branch should work, right? > To me the main issue is not really a 'technical' one pre se, > it's do people really want, and want to help with, such changes? > Right now, I think the response you're going to get from most of us is: "Wait until e17 is out the door." Evas may have issues, but, our main focus at this time is getting a long awaited product released and in the wild. However, this does mean that Evas will also be "in the wild", making drastic API changes more painful on end users of the library. So, maybe we should prioritize the changes (premul seems a higher up candidate). I just don't think that we should take what little dev time we have and suck it into overhauling evas (which, unfortunately, is 'good enough' for our current purposes). Maybe we just need to clarify what changes are planned when we release so that potential users of the lib will be aware of them? rephorm. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
