On Sun, 29 Jun 2008 19:15:52 +0200 (CEST) Vincent Torri <[EMAIL PROTECTED]>
babbled:
>
> Hey,
>
> I am planning to reorganize the header files of evas, which is a big fat
> mess. Then I remembered a discussion on the ML about data types in evas
> and ecore, and their respective performance.
>
On Mon, 30 Jun 2008 15:23:32 +0200 Brian 'morlenxus' Miculcy
<[EMAIL PROTECTED]> babbled:
I think adding these in is a good idea. namespacing sounds good. those seem
important fields - useful. as brian said - the rest is implicit in the .edj
file contents itself and is simply a matter of making th
Build log for Enlightenment DR 0.17 on 2008-07-01 07:10:17 -0700
Build logs are available at http://download.enlightenment.org/tests/logs
Packages that failed to build:
edvi http://download.enlightenment.org/tests/logs/edvi.log
enna http://download.enlightenment.org/tests/logs/enna.log
epdf htt
I like this idea a lot. It would be good to make those fields
mandatory, and hide
themes from the theme configuration dialog if they dont have all of
those fields.
That would really speed up adoption.
Beyond the e/theme/version (which matches the version of E), I would suggest
adding a version for
Heres what Ive just spent the last 30 mins doing...
data {
item: "e/theme/name" "Fireball";
item: "e/theme/version" "1.6";
item: "e/theme/license" "GPL";
item: "e/theme/author""Tom Haste ([EMAIL PROTECTED])";
}
---
data {
item: "etk/theme/name"
On Tue, 1 Jul 2008, Carsten Haitzler (The Rasterman) wrote:
>> I am planning to reorganize the header files of evas, which is a big fat
>> mess. Then I remembered a discussion on the ML about data types in evas
>> and ecore, and their respective performance.
>>
>> So I'm wondering if, before reo
