Quoting Nathan Ingersoll [EMAIL PROTECTED]:
One idea I discussed with Vincent today is that our lack of releases
has caused many users to lose interest and stop taking notice of the
project. I realize that there is a lot of talk surrounding changes to
core infrastructure (data lib, graphics,
Build log for Enlightenment DR 0.17 on 2008-07-29 07:10:50 -0700
Build logs are available at http://download.enlightenment.org/tests/logs
Packages that failed to build:
enna http://download.enlightenment.org/tests/logs/enna.log
epdf http://download.enlightenment.org/tests/logs/epdf.log
Carsten wrote:
On Thu, 17 Jul 2008 05:58:24 -0400 Jose Gonzalez [EMAIL PROTECTED] babbled:
Ok, now for a proposed api for evas vgfx objects -- a very simple
one, but general enough to allow for the overwhelming majority of vgfx uses
(and certainly ones for most 'real-time' use
Carsten wrote:
On Thu, 17 Jul 2008 04:36:05 -0400 Jose Gonzalez [EMAIL PROTECTED] babbled:
As the subject states, let me make a (relatively) short summary of some
proposed changes and additions to the evas gfx api -- and I'll deal with only
gradients and a possible vgfx-objs
Carsten wrote:
On Sat, 19 Jul 2008 05:56:53 -0400 Jose Gonzalez [EMAIL PROTECTED] babbled:
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'
Vincent wrote:
Quoting Nathan Ingersoll [EMAIL PROTECTED]:
One idea I discussed with Vincent today is that our lack of releases
has caused many users to lose interest and stop taking notice of the
project. I realize that there is a lot of talk surrounding changes to
core
