Gustavo Sverzut Barbieri ha scritto:
On Mon, Feb 25, 2008 at 11:11 PM, Dave [EMAIL PROTECTED] wrote:
Hi list !
As you can see I have worked hard to the editor and to the edje patch in
the last weeks...
Now I think that the patch is ready to be committed, and maybe the
editor can be
Build log for Enlightenment DR 0.17 on 2008-02-26 07:09:07 -0800
Build logs are available at http://download.enlightenment.org/tests/logs
Packages that failed to build:
ecore_li http://download.enlightenment.org/tests/logs/ecore_li.log
edje_editor
Hi,
I allready posted this in the enlightenment forum and there I got directed to
the development list. I hope you can help me with my problem.
I'm currently trying to draw HSV color ranges. I like to build a color dialog
similar to Gimps color chooser.
But I can not get the HSV ranges drawn
Enlightenment CVS wrote:
Enlightenment CVS committal
Author : doursse
Project : e17
Module : libs/ewl
Dir : e17/libs/ewl/src/bin/tests/theme
Modified Files:
Makefile.am
Log Message:
don't install static lib (.a) of plugins. .la files are still installed,
which
On Tuesday, 26 February 2008, at 20:27:44 (+0100),
Kim Woelders wrote:
Would adding AC_DISABLE_STATIC in configure.in accomplish the same thing
without having to change every single Makefile.am?
No, as that would disable static *libraries* as opposed to just static
*modules*. The latter are
Michael Jennings wrote:
On Tuesday, 26 February 2008, at 20:27:44 (+0100),
Kim Woelders wrote:
Would adding AC_DISABLE_STATIC in configure.in accomplish the same thing
without having to change every single Makefile.am?
No, as that would disable static *libraries* as opposed to just
Michael wrote:
about these suggestions, would it be interesting to add them in
the trac main page ?
My point is that I think suggestions might be jumping the gun
a bit, unless the sheer volume of suggestions might help reverse
our previous poor fortune.
Step #1: Get accepted
On Tuesday, 26 February 2008, at 20:07:01 (+),
[EMAIL PROTECTED] wrote:
Actually, I have one that likely others have felt as well: eterm on
new efl libs, or just various ideas for eterm that people might
think of. Eterm is one of the great, classic e apps that many love
and rave about..
On Tuesday, 26 February 2008, at 12:18:26 (-0800),
Eric Sandall wrote:
For now I've modified the e_module-notification package to specify
--prefix=/usr/lib/enlightenment/modules. I will remove that once
this is fixed (or add it to all other modules if they are changed).
This is wrong and
As far as suggestions go, here's my 2 cents:
1. evas filters. That was explained in more detail in previous emails
from this thread.
1.5 Bringing the evas gl engine up to standard.
2. A terminal application using efl (specifically edje, for themes,
utf-8 support and tabs). Since kainx already
On Tuesday, 26 February 2008, at 22:44:21 (+0200),
Viktor Kojouharov wrote:
2. A terminal application using efl (specifically edje, for themes,
utf-8 support and tabs). Since kainx already mentioned that eterm
would require a major rewrite in order to support utf-8, there might
as well be
On Fri, 25 Jan 2008, Christopher Michael wrote:
Sebastian Dransfeld wrote:
lok wrote:
It's not a bug the configure.in are set up this way in most (all?) modules.
They will be installed in `enlightenment-config --module-dir`.
Unless you use the --enable-homedir-install option.
Morlenxus
Le mardi 26 février 2008, vous avez écrit :
On Mon, Feb 25, 2008 at 9:09 PM, raoul [EMAIL PROTECTED] wrote:
Hi there,
I think there is a great stuff missing in efls, it's a web rendering
engine. The main purpose would be to have a full-efl based web browser.
But also have some web
Is there a dedicated person we should send the email to? Or just email the
list? Sorry, not familiar with the etiquette here.
Thanks,
Jess
On Tue, Feb 26, 2008 at 12:25:18PM -0800, Michael Jennings wrote:
On Tuesday, 26 February 2008, at 20:07:01 (+),
[EMAIL PROTECTED] wrote:
Jess wrote:
Is there a dedicated person we should send the email to?
Or just email the list? Sorry, not familiar with the etiquette here.
For greater exposure, feedback, etc. the list here would
clearly be best.
This is something that people here have to build
On Tue, 26 Feb 2008, Kim Woelders wrote:
Michael Jennings wrote:
On Tuesday, 26 February 2008, at 20:27:44 (+0100),
Kim Woelders wrote:
Would adding AC_DISABLE_STATIC in configure.in accomplish the same thing
without having to change every single Makefile.am?
No, as that would disable
Jess wrote:
Is there a dedicated person we should send the email to? Or just email the
list? Sorry, not familiar with the etiquette here.
Recording them into wiki.enlightenment.org would probably be the best
bet. A much more stable and easy to use record then the mailing list.
dan
thanks for the tip will give it a try. But there is still
the issue that the function documentation is wrong. Therefore
It could be that the hsv_color_range function is expecting
different values.
Ok, took a quick look, and... Yeah, that whole imlib2 grad
implementation is screwed..
On Tuesday 26 February 2008 12:30:11 Michael Jennings wrote:
On Tuesday, 26 February 2008, at 12:18:26 (-0800),
Eric Sandall wrote:
For now I've modified the e_module-notification package to specify
--prefix=/usr/lib/enlightenment/modules. I will remove that once
this is fixed (or add it
On Tue, 26 Feb 2008 12:18:26 -0800 (PST) Eric Sandall [EMAIL PROTECTED]
babbled:
as such modules should install in the default prefix e installed in. a module
as such should NOT rely on its installation prefix ever at runtime, SO i could
do:
mkdir ~/tmp-stuff
./configure --prefix=~/tmp-stuff
On Tuesday, 26 February 2008, at 17:50:39 (-0800),
Eric Sandall wrote:
My x86_64 box also installs to /usr/lib. Example, e_module-echo installs to /
usr/lib/enlightenment/modules/echo/linux-gnu-x86_64.
So? Just because you do it one way doesn't mean everyone does it the
same way.
Michael
--
Michael Jennings wrote:
On Tuesday, 26 February 2008, at 17:50:39 (-0800),
Eric Sandall wrote:
My x86_64 box also installs to /usr/lib. Example, e_module-echo installs to /
usr/lib/enlightenment/modules/echo/linux-gnu-x86_64.
So? Just because you do it one way doesn't mean everyone does
Hey,
I have added some ideas in the wiki:
* finishing the win32 port
* adding codec support
* writing a presentation tool (handful for those who will talk in some conf :)
* writing an evince-like prog in full edje
i wanted to add a xenon 2 clone, but the problem is artwork and maybe does
not
23 matches
Mail list logo
