Greetings, I've been looking for a project to work on recently, and heard that Enlightenment's Window Manager had been scrapped in favor of a rewrite. This interested me greatly and so I have started digging around in the e17 source tree.
I have noticed throughout that there is a lack of support for new standards coming out of freedesktop.org, and so I was wondering the position of the Enlightenment project on such standards as the WM Spec, Base-dir Spec, Menu Spec, MIME Types Spec, Icon Theme Spec, StartupNotification Spec, etc. There are quite a few good things coming out of freedesktop.org and I think Enlightenment would be missing out greatly to not work with these specifications. As my interest is in the Window Manager paricularily, I am concerned with the lack of UTF-8 text support. The ECore library provides functions for getting/setting window titles, but not the new UTF-8 titles provided for in the freedesktop.org WM Spec. Adding support for UTF-8 also means adding a lot of functions somewhere for handling such strings. For a decent idea of what sorts of functions could be needed, take a look at http://developer.gnome.org/doc/API/2.0/glib/glib-Unicode-Manipulation.html and http://developer.gnome.org/doc/API/2.0/glib/glib-Character-Set-Conversion.html For just a Window Manager, only a rather small subset of those would be needed, but as the e17 libraries do much more than just window management, in the end many of those would probably need to be implemented. UTF-8 is emerging as the standard for all text in the open source world, and I would suggest that all of the e17 libs text handling routings (e.g. in Evas) should deal strictly with UTF-8 strings. So where is Enlightenment trying to go in regard to such specifications? Thanks, Ben
pgp00000.pgp
Description: PGP signature
