On Sun, 18 Apr 2010 19:31:45 +0200 mobi phil said:
> On Sun, Apr 18, 2010 at 2:49 PM, Michael 'Mickey' Lauer <
> mic...@vanille-media.de> wrote:
>
> > Am Sonntag, den 18.04.2010, 06:09 +0200 schrieb Vincent Torri:
> > > 2) edje_cc uses only the evas buffer engine. Isn't it time to split the
> >
On Sun, 18 Apr 2010 06:09:01 +0200 (CEST) Vincent Torri
said:
> hey,
>
> after mobi phil mail, i looked at the output of ldd with edje_cc (see
> below). As we are near an alpha release, maybe it's time to optimise it.
> Several things can be improved:
>
> 1) there is an ecore_con dep. Because
On Sun, Apr 18, 2010 at 2:49 PM, Michael 'Mickey' Lauer <
mic...@vanille-media.de> wrote:
> Am Sonntag, den 18.04.2010, 06:09 +0200 schrieb Vincent Torri:
> > 2) edje_cc uses only the evas buffer engine. Isn't it time to split the
> > monolithic Ecore_Evas_Engine structure and dlopen modules ?
>
>
Am Sonntag, den 18.04.2010, 06:09 +0200 schrieb Vincent Torri:
> 2) edje_cc uses only the evas buffer engine. Isn't it time to split the
> monolithic Ecore_Evas_Engine structure and dlopen modules ?
Something like that would be appreciated. Right now in OE we have the
problem that we would have t
hey,
after mobi phil mail, i looked at the output of ldd with edje_cc (see
below). As we are near an alpha release, maybe it's time to optimise it.
Several things can be improved:
1) there is an ecore_con dep. Because ecore_file. Ecore_file is used only
because of ecore_file_exists() (note th
