- QZion canvas which is used for graphics rendering in QEdje has two implementations: QPainter based and QGraphicsView based, former being currently faster in embedded environments lacking FPU power. QZion API is still very light, containing basic canvas objects (rectangle, image, text) with under 2kLOC / implementation.
- QEdje is the real beef, containing parser for Edje theme files. What I like about Edje format is that it's not based on XML and it still gets compiled into binary mode when deploying, which should minimize the theming performance hit. I tested now only with provided samples, have to check how QEdje handles more complicated Edje themes.
- Thinking why Edje, Evas, E17 etc. haven't become more popular, is the reason technical, just (lack of) community or what?
- My ideas for QEdje developers would be to concentrate more on QGraphicsView backend as it offers more features and should get nice boost with performance improvements in Qt 4.5. Think if inheriting QGraphicsWidgets as QZion objects would offer more than current QGraphicsItems, like layouts and native QWidgets with QGraphicsProxyWidget. IMO Clutter API is currently a good compromize between features and simplicity, so analyze it and copy all suitable ideas into QZion ;-)
I have to study some more Edje format and whether QZion is already providing "enough" features for it, please comment if I have missed something obvious here.