i guess we could :)
just a few things. your first (big patch) adds features not on the mini-freeze todo list (button bindings) - it'd be good to discuss this first and hear your plans on how to tackle it. remember we likely have discussed things and designs (we do a lot of it on irc).
I known I did some things not on the list, but I have to much spare time at the moment. So I just copied the required fields needed to a struct and made it a config option.
I wont commit such patches before discussion, promise.
it'd be good to join #e and #edevelop on irc.freenode.net. we like to know whats going on - so people don't duplicate effort and that effort is done in the right way :). it'd be good to discuss plans in e-mail/irc.
Done.
we'll be happy to give you access - it would just be nice to not have a few thousand lines of patch to wade through :) do changes in small lots so we can see it happening as it happens. :) the main aim is to keep quality control tight and code clean and maintainable :) we are very glad to have help from people too :)
That was what I hoped to accomplish by have access. No more BIG patches.
sf.net username: sebastid
Sebastian
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
