El Tuesday 01 April 2008 14:57:04 The DarkMaster escribió:
Andre's idea looks very interesting to me (I never mentioned, by the way,
that EWl or anything else should be reduced to something like GTK. In my
OpenGEU themes I just create GTk themes which look similar to certain E17
themes to
@notdirectedtoanyoneinparticular:
Using Edje to theme a constricted widget library like GTK or QT would be a
complete waste of potential. The only way you will have E, EWL and ETK
looking *the same* will be creating yet another bland constricted library.
In web design consistency (or unity)
Andre's idea looks very interesting to me (I never mentioned, by the way,
that EWl or anything else should be reduced to something like GTK. In my
OpenGEU themes I just create GTk themes which look similar to certain E17
themes to solve the integration issue).
Hope to see any other new about it
Michael Jennings ha scritto:
On Monday, 31 March 2008, at 20:50:20 (+0100),
The DarkMaster wrote:
@Michael: I respect your point of view, but;
@All: I am just saying that the big difference in all of this toolkits's
customization possibilities is just a game stopper for the majority of
El Tuesday 01 April 2008 14:57:04 The DarkMaster escribió:
Andre's idea looks very interesting to me (I never mentioned, by the way,
that EWl or anything else should be reduced to something like GTK.
Oh. I didn't meant to say you wanted that. My point was that complete unity
among different
andres wrote:
El Tuesday 01 April 2008 14:57:04 The DarkMaster escribió:
Andre's idea looks very interesting to me (I never mentioned, by the way,
that EWl or anything else should be reduced to something like GTK.
Oh. I didn't meant to say you wanted that. My point was that complete unity
dj2 wrote:
Ewl themes don't have a 'label' text portion of the button. The button
has a child label widget which is the text.
well, that's not important, each theme file (theme_ewl.edj, theme_etk.edj)
uses the elements as needed, the end result will be the same from the user's
point of view.
El Tuesday 01 April 2008 18:17:01 dan sinclair escribió:
The thing is, you aren't gaining anything. The themer still has to theme
everything twice. All you have is a basic set of images they reference.
Which they could have, and just copy into the themes anyway.
That depends on what the themer
andres wrote:
El Tuesday 01 April 2008 18:17:01 dan sinclair escribió:
The thing is, you aren't gaining anything. The themer still has to theme
everything twice. All you have is a basic set of images they reference.
Which they could have, and just copy into the themes anyway.
That depends on
andres wrote:
Ok, my idea would be something like this. Split themes in two,
a elements.edj file and a theme_ewl.edj, theme_etk.edj, etc. file.
I think I covered all the necessary elements (I checked the test apps from
each toolkit) but feel free to extend it as you wish.
...
El Tuesday 01 April 2008 18:33:22 dan sinclair escribió:
I think this is a lot of effort to save the themer the extra 20 minutes
it will take to change the images in the 3 theme files instead of just one.
This covers much more than images. Textures are groups for a reason. Most
textures will
On Tue, 1 Apr 2008 18:12:24 -0300 andres [EMAIL PROTECTED] babbled:
dj2 wrote:
Ewl themes don't have a 'label' text portion of the button. The button
has a child label widget which is the text.
well, that's not important, each theme file (theme_ewl.edj, theme_etk.edj)
uses the elements
On Tue, 01 Apr 2008 17:33:22 -0400 dan sinclair [EMAIL PROTECTED] babbled:
what you want is a gtk theme engine - and a qt theme engine that can load and
use .edj files - it will be tough work, ut thats is what u want. then they can
follow a scheme of using gfx from them and layout. the problem is
andres wrote:
El Tuesday 01 April 2008 18:33:22 dan sinclair escribió:
I think this is a lot of effort to save the themer the extra 20 minutes
it will take to change the images in the 3 theme files instead of just one.
This covers much more than images. Textures are groups for a reason. Most
@dan:
Allow me start over. I made the mistake of being too specific beforehand.
The original problem was E/EWL/ETK (and GTK/QT) applications appeareance being
inconsistent in distributions like openGEU.
My suggestion is to reuse some design elments, a font color here, a background
texture
dan sinclair wrote:
To what end? What's the point of tying them together like this? It would
be better, in the long run, to just have a single widget library instead
of 3.
The 'one true way' of widgetry with the one true mechanism for
theming,
leading to the possibility of a
Jose Gonzalez wrote:
dan sinclair wrote:
To what end? What's the point of tying them together like this? It would
be better, in the long run, to just have a single widget library instead
of 3.
The 'one true way' of widgetry with the one true mechanism for
theming,
dan sinclair wrote:
The 'one true way' of widgetry with the one true mechanism for
theming,
leading to the possibility of a uniform lookfeel for 'all' apps?
Maybe. But wether 1 or 3 or 15 widget libs, it's really the
one(s) that have
apps written for them that count - and
I think the solution for this is to have the theme creator create
themes for everything: E, EWL, ETK, etc.. and pack them all into one
.edj file
And then have the theme configuration module modified (or cloned) so
that it also sets the ewl and etk themes at the same time.
If ewl/etk lets you do
I think almost everyone is understimating the problem. This is a very bad
issue only Enlightenment has and a lot people asks why does this happen,
even in our OpenGEU FOrums. Even creting EWL, ETK, etc. themes is really
something bad a user has to do. Once you create an E17 theme, it should be
one
On Monday, 31 March 2008, at 18:21:57 (+0100),
The DarkMaster wrote:
I think almost everyone is understimating the problem. This is a very bad
issue only Enlightenment has and a lot people asks why does this happen,
even in our OpenGEU FOrums. Even creting EWL, ETK, etc. themes is really
The DarkMaster wrote:
I think almost everyone is understimating the problem. This is a very bad
issue only Enlightenment has and a lot people asks why does this happen,
even in our OpenGEU FOrums. Even creting EWL, ETK, etc. themes is really
something bad a user has to do. Once you create an
On Mon, Mar 31, 2008 at 2:01 PM, The Rasterman Carsten Haitzler
[EMAIL PROTECTED] wrote:
On Mon, 31 Mar 2008 13:39:14 -0400 dan sinclair [EMAIL PROTECTED] babbled:
The DarkMaster wrote:
I think almost everyone is understimating the problem. This is a very bad
issue only
On Monday, 31 March 2008, at 20:26:51 (+0200),
Dave Andreoli wrote:
From the first line of the home page of e: Enlightenment is a
window manager. Enlightenment is a desktop shell.
Desktop shell is not meant to imply the same thing as desktop
environment. That's why it was written as shell and
On Monday, 31 March 2008, at 20:50:20 (+0100),
The DarkMaster wrote:
@Michael: I respect your point of view, but;
@All: I am just saying that the big difference in all of this toolkits's
customization possibilities is just a game stopper for the majority of
people. Of course, the masses wish
Yeah Michael, I think we agree on the entire line now!
As for the responsibility of creating a distro for the masses based on
Enlightenment, sure I get the responsibility, in fact I participated to this
discussion to see how many people agreed with my point of view and try and
understand if
First sorry for my English.
I am a newcomer and I'd like to help in this project. But I have some question:
I found that e17 theme is e17 theme only, that after applying theme other that
default,
any other EFL app is looking like default theme. I'm a little confused with it.
Is that true ??
On 30 Mar 2008 14:01:02 +0200, Lukasz [EMAIL PROTECTED] wrote:
First sorry for my English.
I am a newcomer and I'd like to help in this project. But I have some
question:
I found that e17 theme is e17 theme only, that after applying theme other
that default,
any other EFL app is
28 matches
Mail list logo
