On Sunday, 17 December 2006, at 22:13:05 (-0500),
Mike Frysinger wrote:
> it sounds like you're trying to compensate for people who fucked up
> their install and dont know how to properly do things and thereby
> screwing over correct setups ...
>
> if you're honestly trying to make this useful in
On Monday, 18 December 2006, at 12:57:22 (+0900),
Carsten Haitzler wrote:
> it should be broken if your cvs is up to date - i changed apis for
> engines. if its not broken compile-time - its going to be broken
> runtime. :)
I haven't tried to build in probably a week or so. You broke it since
th
On Wed, 20 Dec 2006 17:41:31 -0500 Michael Jennings <[EMAIL PROTECTED]> babbled:
> On Monday, 18 December 2006, at 12:57:22 (+0900),
> Carsten Haitzler wrote:
>
> > it should be broken if your cvs is up to date - i changed apis for
> > engines. if its not broken compile-time - its going to be bro
On Thursday, 21 December 2006, at 11:59:00 (+0900),
Carsten Haitzler wrote:
> btw - non default enabled features are liable for breaks. i am
> adding native colorspace support to engines and this necessitates a
> lot of changes at the engine api level. i am seriously considering
> removing engines
On Wed, 20 Dec 2006 22:16:30 -0500 Michael Jennings <[EMAIL PROTECTED]> babbled:
> On Thursday, 21 December 2006, at 11:59:00 (+0900),
> Carsten Haitzler wrote:
>
> > btw - non default enabled features are liable for breaks. i am
> > adding native colorspace support to engines and this necessitat
Hi all,
I have done a first snapshot of the edje_editor source .
this is the link
http://www.gurumeditation.it/edje_editor-0.1-beta3.tar.gz
It's the very first release so expect various segv
just type make and RUN IN PLACE.
NOTE: The file you are workin on must have a
name, so save at least onc
