I wrote:
> ...
>>> As to the above mentioned steps.. I disagree with some of the
>>> arguments,
>>> but they are also not unreasonable - so long as everyone realizes that the
>>> state
>>> of many things in E is still rather basic and are willing to 'break' apis on
>>> major releases
Toma wrote:
> On 30/07/2008, Jose Gonzalez <[EMAIL PROTECTED]> wrote:
>
>> 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
On 30/07/2008, Jose Gonzalez <[EMAIL PROTECTED]> wrote:
> 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 real
One 'alarming' question. Does the name mean anything? Why not pick a
simple and descriptive name, that most people will understand (like
edata, or something a bit more shocking and provokative, without a
leading 'e')
On Wed, 2008-07-30 at 17:04 +0200, Nicolas Aguirre wrote:
> Should we now use ein
On Wed, Jul 30, 2008 at 5:04 PM, Nicolas Aguirre
<[EMAIL PROTECTED]> wrote:
> Should we now use eina instead of evas_data and ecore_data in EFL projects ?
> Why ? Have you benchmarks ? Unit Tests :P ?
You are too quick :) We need to work a little bit more before
switching. But that's the plan.
>
Should we now use eina instead of evas_data and ecore_data in EFL projects ?
Why ? Have you benchmarks ? Unit Tests :P ?
In case of ecore_file for example, functions return Ecore_List. Do you plan
to move gradually to eina ?
I think that's a good plan to unify lists and hashs in EFL :)
Regards,
Hi guys,
So here is a little patch that signature support to eet. It append
at the end of a classic eet file a signature and the public x509
certificate in der format. This change doesn't break file
compatibility as the signature is automatically detected based on the
file content against it's s
Build log for Enlightenment DR 0.17 on 2008-07-30 07:10:23 -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
Packages
