I've put together a little "state of the union" summary. With all the flurry of
mail and now questions about E17 I thought I'd put this out. I'm happy to
discuss this and I'll try and update the document - maybe put it up on the
website soon? (currently it's just a text file).
....
-------------------------------------------------------------------------------
A quick list of things to do for E 0.17
-------------------------------------------------------------------------------
This "mini-document" is intended for reference for people wanting to be
involved in Enlightenment development for 0.17.0 and beyond. Please read ALL
of this before leaping to conclusions. Any part is subject to review and can
be changed. There is no priority implied here by the order of items.
Evas:
Evas is very much close to being feature-complete. It may have the largest
todo list of any project, but most features are post 1.0. Only a few things
remain to be done for a 1.0. It has been heavily tested for bugs, crashes,
leaks etc. It has partial documentation that needs completion. This is one
of the most mature parts of E right now. It's also one of the most exciting
as it has uses well beyond E itself, and will make development of E and
associated tools child's play in future.
Eet:
This library is night-complete. It's small and simple, but very useful. It
has very little left to be done - just full documentation and a more
expansive data type sterilizer that handles a few more data types. As it
stands it is fully usable, stable and ready to go where applicable.
Edb:
This library is basically complete. Similar to eet but for a different
purpose it is for random access read AND WRITE access to files. Eet is
intended for really fast read, but write-once functionality, making for
much smaller files. Each library has its uses. They can be used together too.
Ecore:
Now being worked on in the SPLIT branch. It's having a rewrite with a much
cleaner API, much more modular, much nicer internals etc. It includes things
that the old Ecore did not. It's MUCH MUCH MUCH better. It basically needs
lots of modules and will be worked on ad-infinitum. Currently it has basic
IPC wrapping, X wrapping, Evas wrapping, job handling, basic event loop,
timers, idlers, signal to event translators, frame buffer driver. A higher
level IPC wrapper has been started to build on top of the lower level
connection handler thats now there. Ecore is literally the core of a lot of
programs to be worked on and gives the infrastructure to do all the basic
"running around" a program has to do internally.
Ebits:
The current ebits does a lot, but is creaking at the edges. It was designed
to do much less than its being used to do now. It needs a complete re-design
and rethink taking into account how it's being used now and how it might be
in the future. This is on the "chopping block" right now and will be gotten
to in due course.
EWL:
This is a very long-term project. It needs work but it will be a long time
coming till its all there.
Ebg:
This is a simple background handling library. It may be that in future Ebits
takes over this role and maybe Ebg just becomes a convenience wrapper around
Ebits.
Ebony:
Dependant on Ebg and Ebits (possibly) this is a tool to create background
files. It will need to be updated as the back-end libraries (Ebg and Ebits)
change.
Etcher:
Dependant on Ebits - if Ebits changes, Etcher needs to change. This will
likely involve a complete rewrite at this stage as Ebits needs to be looked
at hard.
Efsd:
Currently dormant, but a good subsystem for building file managers and
anything that needs to do file stuff. This might benefit from Ecore and its
IPC wrapping, making it much more efficient and streamlined.
Entrance:
In progress at the moment, but also dependant on other subsystems, this
login/display manager is intended to give the E "look & feel" from login as
well. It probably could do with more people, testing, features etc.
E17:
Dormant right now waiting on work on all the libraries/subsystems it depends
on. It will need a rewrite considering all the work going into the libraries
it depends on. For now consider it a glorified "test application".
Etox:
Currently Etox's fate is "unknown". It's a good library and idea.
Abstracting higher-level text formatting, flowing etc. into a library and API
is good, but where exactly Etox will head from here, we don't know.
Estyle:
Lower level than Etox, Estyle just does text string style handling, and
config parsing. It's fate is also currently unknown.
Imlib2:
Imlib2 is complete (feature-wise) but internally needs updates. It needs to
use Freetype2 like Evas does. It could also do with some Doxygen documents
like Ecore, Eet and Evas have (in progress) right now. It probably could
do with some love and attention.
--
--------------- Codito, ergo sum - "I code, therefore I am" --------------------
The Rasterman (Carsten Haitzler) [EMAIL PROTECTED]
[EMAIL PROTECTED]
Mobile Phone: +61 (0)413 451 899 Home Phone: 02 9698 8615
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
enlightenment-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
