Just as a change of pace from the evas filters/transforms stuff...
here's a simple ability that could be useful in evas right now.
There are many, many kinds of custom evas object types one could
define... and some of these might involve using external libs (either
in their implementation, or just by allowing one to directly use
external apis). For these kinds of objects, one would not want evas to
have a hard dependency on those libs, or even have such objects be
necessarily compiled in.
One could do some of this via smart objs (possibly extended
versions thereof) and native surfaces, but even with that in place
one may not want to implement things that way for efficiency and
other reasons.
So, one may want to be able to have a simple way to define and
add new object types to evas which are optionally compiled, possibly
run-time loadable, have their api in a separate header from the main
Evas.h, and yet have these objs be able to take advantage of evas
internals, as well as use external libs as need be.
Examples of these kinds of evas objects might be a "cairo"
object, an "svg" object, a set of various vgfx kinds of objects,
various raster-image related kinds of objects, and even things like
a full 3d-scene kind of object.
There's a very simple way to have this ability in evas right,
one that requires very few internal additions and no modifications
to any of the current stuff.
Is this something people think would be useful for evas?
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
