[E-devel] The bleeding edge of edc?

[Jose G. <jos...@ju...>]

      Or rather, what to do with "edc" and its use for representing gfx
components in both edje and evolve... that's the real question here.

      Right now, evolve has no direct 'gfx' representations other than via
edje/edc, and the latter is limited to what has been available in evas so far.
Edje/edc itself deals mostly with defining "groups" -- which are a kind of
'template' for creating stateful, compound evas objs (certain smart objs) from
basic gfx components (ie. the "parts").
      But with an extended set of gfx capabilities for evas (vgfx stuff,
transforms, masks, filters, ...), one can *begin* looking into extending the
descriptions of such parts so that such new gfx aspects can be represented
via edc and/or scripting.

      More could also be done in evolve/edc to introduce *canvas* presentations,
by which I mean something like what Flash/mxml and Silverlight/xaml (and svg)
allow developers/designers to define.

      In fact, I'd encourage those interested in gfx matters to take a look
at those two formats (and the apis behind the relevant libs) and see what
can be learned from them in terms of expressive capabilities so that one can
*begin* getting ideas as to what could also be done in both edje/edc and
evolve/edc (and possibly with scripting and/or C as well).

      Thoughts or comments on this?

____________________________________________________________
Click here for free information on nursing degrees, up to $150/hour
http://thirdpartyoffers.juno.com/TGL2141/fc/Ioyw6i3nEnkrJKQmsKO8b7JLixuV9RDtG9jt3GM18aQCwyTuM9kxb6/