[E-devel] make efreet error for ppc-apple-darwin

2008-04-01 Thread Christer Sandvik
Hello

How do I remove i386 (-arch i386 ppc)? Is there a lib installed with i386?

Cheers!

Christer.

gcc -g -O2 -o .libs/efreet_alloc efreet_alloc.o -arch i386 ppc -g -Os 
-pipe -Wl,-search_paths_first -Wl,-weak-lgssapi_krb5 -Wl,-weak-lkrb5 
-Wl,-weak-lk5crypto -Wl,-weak-lkrb5support -Wl,-weak-lcom_err 
-Wl,-weak-lresolv  ../../../src/lib/.libs/libefreet.dylib 
/usr/lib/libecore_file.dylib /usr/lib/libecore.dylib -ldl -lm -lcurl
i686-apple-darwin8-gcc-4.0.1: ppc: No such file or directory
make[4]: *** [efreet_alloc] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

If removed in config* and Makefile it still remain:

gcc -g -O2 -o .libs/efreet_test ef_data_dirs.o ef_icon_theme.o ef_ini.o 
ef_utils.o ef_desktop.o ef_menu.o ef_mime.o main.o ef_locale.o -arch ppc 
-g -Os -pipe -Wl,-search_paths_first -Wl,-weak-lgssapi_krb5 
-Wl,-weak-lkrb5 -Wl,-weak-lk5crypto -Wl,-weak-lkrb5support 
-Wl,-weak-lcom_err -Wl,-weak-lresolv  
../../src/lib/.libs/libefreet.dylib 
../../src/lib/.libs/libefreet_mime.dylib 
/Volumes/disk0_2/apps/managers/window/e17/efreet-0.0.3.042/src/lib/.libs/libefreet.dylib
 
/usr/lib/libecore_file.dylib /usr/lib/libecore.dylib -ldl -lm -lcurl
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: warning 
/usr/lib/libecore_file.dylib cputype (7, architecture i386) does not 
match cputype (18) for specified -arch flag: ppc (file not loaded)
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: Undefined symbols:
_ecore_file_exists
_ecore_file_ls
collect2: ld returned 1 exit status
make[4]: *** [efreet_test] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2


-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


Re: [E-devel] Unified theme for apps

2008-04-01 Thread andres
@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) among different pages in the same website 
is attained by repeating design elements (colors, textures, fonts) and 
applying the different design principles (proximity, balance, alignment, 
proprortion) in the same manner across every page. 

To maintain unity among different applications unsing the same widget library, 
both GTK and QT have enforced the design principles (+behaviour) at the 
programming level. This limits the designer to aesthetical changes on the 
design elements. 

I assume neither E, EWL or ETK developers want to create yet another bland 
library. If what I assume is correct then allow me to suggest a solution to 
mantain Unity among all your apps without compromising the freedom that Edje 
provides.

Split the themes in two parts, a smaller theme file that contains textures, 
fonts and colors (the design elements) and another theme file that contains 
the layout and behaviour using GROUP parts to include the design elements of 
the first theme file into it's own.

Designer who want to alter themes in general limit themselves to the first 
file. Designers who want to alter something specific for an specific toolkit 
dives into the second. This limits designers in the second group to a extent, 
they cannot simply replace a texture with another and hope it will work in 
every theme, they will have to consider carefully before overrinding a design 
element. Besides, they will be able of altering other aspects of the 
interfaces (to different extents depending on the toolkit).

An E, EWL or ETK application will not be a carbon copy of another. But unity 
among them will be mantained. If you guys agree I can post a draft for 
this "standard base theme". I have been thinking about this issue since I 
started with the Edje book.

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


[E-devel] Nightly build log for E17 on 2008-04-01 07:09:29 -0700

2008-04-01 Thread Nightly build system
Build log for Enlightenment DR 0.17 on 2008-04-01 07:09:29 -0700
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
engage  http://download.enlightenment.org/tests/logs/engage.log
enna  http://download.enlightenment.org/tests/logs/enna.log
epdf  http://download.enlightenment.org/tests/logs/epdf.log

Packages with no supported build system:
entice, esmart_rsvg, exorcist, python-efl, 

Packages skipped:
camE, enotes, enscribe, epbb, eplay, erss, etk_server, etox, e_utils, 
Evas_Perl, 
evoak, gfx_routines, lvs-gui, med, nexus, notgame, ruby-efl, webcam, 

Packages that build OK:
alarm, bling, calendar, cpu, deskshow, echo, eclair, ecore, edata, edb, 
e_dbus, edje_editor, edje, edje_viewer, edvi, eet, eflame, eflpp, efm_nav, 
efm_path, efreet, elapse, elation, elicit, elitaire, e, embrace, embryo, 
emotion, emphasis, empower, emprint, emu, enesim, engrave, engycad, enhance, 
enity, enterminus, enthrall, entrance_edit_gui, entrance, entropy, envision, 
epeg, ephoto, e_phys, epsilon, epx, equate, esmart, estickies, etk_extra, 
etk, etk-perl, evas, evfs, evolve, ewl, examine, execwatch, exhibit, exml, 
expedite, express, exquisite, extrackt, feh, flame, forecasts, gevas2, iconbar, 
imlib2_loaders, imlib2, Imlib2_Perl, imlib2_tools, language, mail, mem, 
mixer, moon, mpdule, net, news, notification, penguins, pesh, photo, rage, 
rain, screenshot, scrot, slideshow, snow, taskbar, tclock, uptime, weather, 
winselector, wlan, 

Debian GNU/Linux 4.0 \n \l

Linux enlightenment2 2.6.18-4-686 #1 SMP Wed May 9 23:03:12 UTC 2007 i686 
GNU/Linux


See http://download.enlightenment.org/tests/ for details.


-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


Re: [E-devel] make efreet error for ppc-apple-darwin

2008-04-01 Thread Christer Sandvik
Christer Sandvik wrote:
> Hello
>
> How do I remove i386 (-arch i386 ppc)? Is there a lib installed with 
> i386?
I still don't know how to fix this and why are there libraries (ecore 
etc.) with i386?
>
> Cheers!
>
> Christer.
>
> gcc -g -O2 -o .libs/efreet_alloc efreet_alloc.o -arch i386 ppc -g -Os 
> -pipe -Wl,-search_paths_first -Wl,-weak-lgssapi_krb5 -Wl,-weak-lkrb5 
> -Wl,-weak-lk5crypto -Wl,-weak-lkrb5support -Wl,-weak-lcom_err 
> -Wl,-weak-lresolv  ../../../src/lib/.libs/libefreet.dylib 
> /usr/lib/libecore_file.dylib /usr/lib/libecore.dylib -ldl -lm -lcurl
> i686-apple-darwin8-gcc-4.0.1: ppc: No such file or directory
> make[4]: *** [efreet_alloc] Error 1
> make[3]: *** [all-recursive] Error 1
> make[2]: *** [all-recursive] Error 1
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
>
> If removed in config* and Makefile it still remain:
>
> gcc -g -O2 -o .libs/efreet_test ef_data_dirs.o ef_icon_theme.o 
> ef_ini.o ef_utils.o ef_desktop.o ef_menu.o ef_mime.o main.o 
> ef_locale.o -arch ppc -g -Os -pipe -Wl,-search_paths_first 
> -Wl,-weak-lgssapi_krb5 -Wl,-weak-lkrb5 -Wl,-weak-lk5crypto 
> -Wl,-weak-lkrb5support -Wl,-weak-lcom_err -Wl,-weak-lresolv  
> ../../src/lib/.libs/libefreet.dylib 
> ../../src/lib/.libs/libefreet_mime.dylib 
> /Volumes/disk0_2/apps/managers/window/e17/efreet-0.0.3.042/src/lib/.libs/libefreet.dylib
>  
> /usr/lib/libecore_file.dylib /usr/lib/libecore.dylib -ldl -lm -lcurl
> /usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: warning 
> /usr/lib/libecore_file.dylib cputype (7, architecture i386) does not 
> match cputype (18) for specified -arch flag: ppc (file not loaded)
> /usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: Undefined symbols:
> _ecore_file_exists
> _ecore_file_ls
> collect2: ld returned 1 exit status
> make[4]: *** [efreet_test] Error 1
> make[3]: *** [all-recursive] Error 1
> make[2]: *** [all-recursive] Error 1
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
>
>

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


[E-devel] SoC deadline extension...

2008-04-01 Thread Ravenlock
Hello,

I am pleased to announce, for your convenience and ours, Google has
extended the student application deadline by one week.  The new deadline
is April 7th.

We have had a very nice turn out so far.  Keep up the good work.  We
hope to see many more applications in the coming week.

For those of you who may have not yet submitted an application, but
intend to do so  Please take a look at the URL I've added to our
ideas page.  It can point you to some examples of applications being
submitted by other students (at another organization)

If you desire to modify your previously submitted application, and have
any difficulty, please contact myself or your probable mentor.  We can
post a public comment to it which will certainly allow you to edit it at
that time.

-- 
Regards,
Ravenlock




signature.asc
Description: OpenPGP digital signature
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


[E-devel] Imlib2: __imlib_hsv_to_rgb bug

2008-04-01 Thread Dariusz Knociński
Hi All,
I found bug imlib2 library (1.4.1.000) in procedure __imlib_hsv_to_rgb(...), 
old alghoritm wrong 
calculate internal values and produces bad result. I wrote new one and actualy 
testing it. This bug
produce black bottom rect in imlib2_colorspace test program.
Best Regards
-- 
Dariusz Knociński

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


Re: [E-devel] Unified theme for apps

2008-04-01 Thread The DarkMaster
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 if someone else thinks this may be
interesting.

Luca
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


[E-devel] ecore & efreet configure errors for darwin (OS X)

2008-04-01 Thread Christer Sandvik
Fix: If configured under darwin ecore & efreet creates Makefiles "-arch 
i386 ppc", one has to edit them manually or rewrite the script so they 
end up "-arch ppc".

Cheers!

Christer.

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


Re: [E-devel] Unified theme for apps

2008-04-01 Thread Jose Gonzalez
   andres wrote:

> @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) among different pages in the same 
> website 
> is attained by repeating design elements (colors, textures, fonts) and 
> applying the different design principles (proximity, balance, alignment, 
> proprortion) in the same manner across every page. 
>
> To maintain unity among different applications unsing the same widget 
> library, 
> both GTK and QT have enforced the design principles (+behaviour) at the 
> programming level. This limits the designer to aesthetical changes on the 
> design elements. 
>
> I assume neither E, EWL or ETK developers want to create yet another bland 
> library. If what I assume is correct then allow me to suggest a solution to 
> mantain Unity among all your apps without compromising the freedom that Edje 
> provides.
>
> Split the themes in two parts, a smaller theme file that contains textures, 
> fonts and colors (the design elements) and another theme file that contains 
> the layout and behaviour using GROUP parts to include the design elements of 
> the first theme file into it's own.
>
> Designer who want to alter themes in general limit themselves to the first 
> file. Designers who want to alter something specific for an specific toolkit 
> dives into the second. This limits designers in the second group to a extent, 
> they cannot simply replace a texture with another and hope it will work in 
> every theme, they will have to consider carefully before overrinding a design 
> element. Besides, they will be able of altering other aspects of the 
> interfaces (to different extents depending on the toolkit).
>
> An E, EWL or ETK application will not be a carbon copy of another. But unity 
> among them will be mantained. If you guys agree I can post a draft for 
> this "standard base theme". I have been thinking about this issue since I 
> started with the Edje book.
>
>   

  All this might be good ideas and they could inspire people to write
apps/themes in various ways. Both ewl and etk allow one to write
apps that are as unique or as uniform as one wants, since both toolkits
allow the writer to possibly make use of custom edjes for theming
most any standard or custom component. It's up to the writer to design
their app as they see fit - and that's the real power of these toolkits,
that they offer that choice, rather than imposing some 'true-way'.
  Some set of guidelines or theme-structures could help people to
write more uniform, or more unique, or more mixed, or whatever designs,
and it might be useful for various situations or scenarios, but the
toolkits themselves allow for those things to exist - for that kind of
choice.

  Note also that 'theming' does not necessarily mean using edje,
since you can write your app to use custom layouts and objects, and
you could even create some other lib that others could use for that,
along with the toolkits. In fact, with something akin to a 'canvas'
widget, which allows you to arbitrarily position any widget or object,
plus maybe alternative layout mechanisms, one could do pretty much
anything with the toolikts - web-like looking apps, flash-like ones,
etc.





-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


Re: [E-devel] Unified theme for apps

2008-04-01 Thread Dave Andreoli
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
>> people. Of course, the masses wish to have an ergonomic desktop, where
>> everything looks well integrated and not chaotic (Say MacOSX for example).
>> 
>
> E was never intended to cater to the "masses."  There are plenty of
> other "lowest common denominator" options out there already.  I've
> used all of them, even MacOS X, and frankly I'm not even half as
> productive with any of them.
>
>   
>> What I'm trying to explain is that there should be at least an easy
>> way for the common user to set a certain theme for all of his E17
>> related apps.  That's all.
>> 
>
> Assuming the theme is intended to be able to do that, that's fine.  As
> long as everyone realizes that not all theme authors will want to go
> down that road.
>
>   
>> Also for coders/themers, this is just extra work.
>> 
>
> Maybe so, but it's up to the theme author if they want to create an
> "E" theme or an "EWL" theme or both.
>
> If someone wanted to create a tool to speed/simplify converting one
> theme to another, or to facilitate creating themes that work for
> multiple apps/libs, more power to them!  As long as the freedom still
> exists to have separate and distinct themes, I don't think anyone
> would be opposed to such a thing.
>
>   
>> For example, creating a little application able of helping a themer
>> in producing E, EWL, ETK, whatever theme using the same basic pieces
>> of arts for buttons, windows background and various widgets, would
>> be a very nice thing.  That's all.
>> 
>
> I agree.
>
>   
>> Also, for example, when I released OpenGEU Luna Nuova, all of
>> the good review about my distro where saying: it is a very nice distro but I
>> oticed that changing from the Sunshine theme to Moonlight, some parts of
>> certain applications didn't change to dark colors and still looked Golden :)
>> That was the greates draw-back in choosing and recommending the distro! Lol
>> ;)
>> That is, they where saying that the distro whas still a little bugged
>> because of this :)
>> 
>
> Again, if you create a distro based on a certain set of assumptions,
> you bear the responsibility that comes with it.  :-)
>
>   
>> That's how people see the entire story, no matter how you put it,
>> only few people understand that this is a pro. Now, I believe that
>> we'd better help themers do their job better since having the
>> freedom to create themes EASILY should be an important freedom too
>> for anyone, right? I prefer ergonomics desktop, shouldn't I be free
>> to easily and quickly encode one in E?
>> 
>
> This is the key difference:  "facilitate" vs. "dictate"  The former is
> good; the latter is bad.
>
> My original point was that this simply isn't a big deal for the type
> of user (like myself) that E was originally coded for.  That said,
> those who feel it is a significant issue should feel welcome to
> develop the tools necessary to have it however they want it.  In other
> words, facilitate the choice, but don't dictate the policy.
>
> Make sense?  :-)
>
>   
>> That's just how I see the entire fact and of course I am not crazy (why
>> should I be crazy only because I like ergonomic desktops??) and of course
>> I'm trying to push my distro that exact way :)
>> 
>
> Liking things a certain way doesn't make you crazy.  Thinking
> *everyone* should be *forced* to have them that way does.  Hopefully
> the distinction is clear now. :-)
>
> Michael
>
>   
I also agree on all the line now  :)
Dave

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


Re: [E-devel] SoC deadline extension...

2008-04-01 Thread Atton Jonathan
On Tue, 01 Apr 2008 10:47:32 -0500
Ravenlock <[EMAIL PROTECTED]> wrote:

> Hello,
> 
> I am pleased to announce, for your convenience and ours, Google has
> extended the student application deadline by one week.  The new
> deadline is April 7th.
> 
> We have had a very nice turn out so far.  Keep up the good work.  We
> hope to see many more applications in the coming week.
> 
> For those of you who may have not yet submitted an application, but
> intend to do so  Please take a look at the URL I've added to our
> ideas page.  It can point you to some examples of applications being
> submitted by other students (at another organization)
> 
> If you desire to modify your previously submitted application, and
> have any difficulty, please contact myself or your probable mentor.
> We can post a public comment to it which will certainly allow you to
> edit it at that time.
> 

Good :)

How many students are interested currently ? a lot I hope :)


-- 
Regards,
Atton Jonathan <[EMAIL PROTECTED]>

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


Re: [E-devel] Unified theme for apps

2008-04-01 Thread andres
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 toolkits programatically would cause that, not that you 
wanted it. I think we can mantain a good level of unity by limiting ourselves 
only to repetition of the same design elements. 

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.

elements.edj would contain
==
* Groups:
** "texture/base": to be drawn at the bottom (window background)
** "texture/inward": to be drawn inside the bottom (a list background)
** "texture/outward": to be drawn over the bottom (a toolbar's background)
** "texture/primary": for elements that must catch your attention (buttons)
** "texture/secondary": catches attention... not so much (text entries)
** "texture/tertiary": almost the background (tabs, list headers) 

* Fonts:  
** "common": for most text on the screen.
** "labels": for the text over buttons, progressbar, tooltips, etc.
** "menus": for the menus and submenus.

* Color classes:
** "over_base": for text drawn over the base texture
** "over_inward": you can imagine.
** "over_outward": this one too. 
** "over_primary": ...
** "over_secondary": ...
** "over_tertiary": ...

a button in theme_w.edj would be like
===
group {
...
part {
name: "bg";
type: GROUP;
source: "texture/primary";
description {
//buttons height, blah blah
}
}
part {
name: "shadow";
type: IMAGE;
description {
//a black and white image using transparency to shadow 
the button"
}
}
part {
name: "label";
type: TEXT;
description {
text.font: "over_primary";
text.size: gigantic!;
}
  ...
}

...

whatdoyouthink?

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


Re: [E-devel] Unified theme for apps

2008-04-01 Thread dan sinclair
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  
> among different toolkits programatically would cause that, not that you 
> wanted it. I think we can mantain a good level of unity by limiting ourselves 
> only to repetition of the same design elements. 
> 
> 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.
> 
> elements.edj would contain
> ==
> * Groups:
> ** "texture/base": to be drawn at the bottom (window background)
> ** "texture/inward": to be drawn inside the bottom (a list background)
> ** "texture/outward": to be drawn over the bottom (a toolbar's background)
> ** "texture/primary": for elements that must catch your attention (buttons)
> ** "texture/secondary": catches attention... not so much (text entries)
> ** "texture/tertiary": almost the background (tabs, list headers) 
> 
> * Fonts:  
> ** "common": for most text on the screen.
> ** "labels": for the text over buttons, progressbar, tooltips, etc.
> ** "menus": for the menus and submenus.
> 
> * Color classes:
> ** "over_base": for text drawn over the base texture
> ** "over_inward": you can imagine.
> ** "over_outward": this one too. 
> ** "over_primary": ...
> ** "over_secondary": ...
> ** "over_tertiary": ...
> 
> a button in theme_w.edj would be like
> ===
> group {
>   ...
>   part {
>   name: "bg";
>   type: GROUP;
>   source: "texture/primary";
>   description {
>   //buttons height, blah blah
>   }
>   }
>   part {
>   name: "shadow";
>   type: IMAGE;
>   description {
>   //a black and white image using transparency to shadow 
> the button"
>   }
>   }
>   part {
>   name: "label";
>   type: TEXT;
>   description {
>   text.font: "over_primary";
>   text.size: gigantic!;
>   }
>   ...
> }
> 
> ...
> 
> whatdoyouthink?
> 

Ewl themes don't have a 'label' text portion of the button. The button 
has a child label widget which is the text.

This also requires changes to edje as, I don't think, you can load 
multiple theme files and merge them together in memory into a single edj 
file.

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


Re: [E-devel] Unified theme for apps

2008-04-01 Thread andres
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.

> This also requires changes to edje as, I don't think, you can load
> multiple theme files and merge them together in memory into a single edj
> file.
Yep, you are right, and this is my main problem with this method. But it is 
solveable.


PS: arrrg, sorry for the duplicate message.

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


Re: [E-devel] Unified theme for apps

2008-04-01 Thread dan sinclair
andres wrote:
> 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.
> 
>> This also requires changes to edje as, I don't think, you can load
>> multiple theme files and merge them together in memory into a single edj
>> file.
> Yep, you are right, and this is my main problem with this method. But it is 
> solveable.
> 
> 

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.

Seems like a lot of code bloat for no real benefit.

dan

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


Re: [E-devel] Unified theme for apps

2008-04-01 Thread andres
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 wants to do. If he just wants to have 
E/EWL/ETL to be consistent with QT/GTK he only has to alter 
the "elements.edj" file.

The goal is consistent (not 1:1 equally looking) appearence among the EFL 
toolkits without elminating the possibilty of themers altering this or that 
in a specific theme.

If we force layout and behaviour definition in the programming level then I 
don't see the point of an Edje based toolkit library... well I do see some 
benefits, but I would like moar.




-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


Re: [E-devel] Unified theme for apps

2008-04-01 Thread dan sinclair
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 what the themer wants to do. If he just wants to have 
> E/EWL/ETL to be consistent with QT/GTK he only has to alter 
> the "elements.edj" file.
> 
> The goal is consistent (not 1:1 equally looking) appearence among the EFL 
> toolkits without elminating the possibilty of themers altering this or that 
> in a specific theme.
> 
> If we force layout and behaviour definition in the programming level then I 
> don't see the point of an Edje based toolkit library... well I do see some 
> benefits, but I would like moar.
> 

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.

And, who installs elements.edj? Does it ship with all three? How do you 
know when to write it and when not? What happens if Ewl uses an updated 
version that the themer hasn't put the right keys in for? Does it just 
ship with E17? That won't work as Ewl doesn't require E17 and visa versa.

You're suddenly tying E17, Ewl and Etk together when there is no tie 
between then.

dan


-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


Re: [E-devel] Unified theme for apps

2008-04-01 Thread Jose Gonzalez
   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.
>
>
> ...
>
> whatdoyouthink?
>   

  Some of this, or similar, could be used in certain ways by
apps, but I think that ultimately this kind of thing would be best
served by having "theme-builders" kind of apps. Maybe an extension
of edje-editor, or evolve, or whatever.
  Likely best if it were module based so that one could write
modules for building edje-based themes for various kinds of things:
e17 & modules, ewl or etk generic themes, app specific themes, etc.


-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


Re: [E-devel] Unified theme for apps

2008-04-01 Thread andres
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 want to use multiple images with different properties in the 
image{} block. 

> And, who installs elements.edj? Does it ship with all three? How do you
> know when to write it and when not? What happens if Ewl uses an updated
> version that the themer hasn't put the right keys in for? Does it just
> ship with E17? That won't work as Ewl doesn't require E17 and visa versa.
>
Well, this is just a standarization method to ease integration of themes by 
distributors like OpenGEU. Consistency among the files should be mantained by 
the distributors.

> You're suddenly tying E17, Ewl and Etk together when there is no tie
> between then.
Not at all, E17, Ewl and Etk don't have to do absolutely nothing to implement 
this. This is all at theme level. Only a function to allow assembling a theme 
file at runtime would have to be included in Edje.

A libUI.c shared between E17, Ewl and Etk would tie them togheter much more.



-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


Re: [E-devel] Unified theme for apps

2008-04-01 Thread The Rasterman
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 as needed, the end result will be the same from the user's 
> point of view.
> 
> > This also requires changes to edje as, I don't think, you can load
> > multiple theme files and merge them together in memory into a single edj
> > file.
> Yep, you are right, and this is my main problem with this method. But it is 
> solveable.

not directly - but indirectly u can. e17 does just that. it has a defined theme
group/object type, then the key in the edje to look for and it has a fallback
mechanism if there is a specific file specified for a specific object type - if
not fall back to a parent etc. and then find that .edj file- if it supplies the
right edje group, use it, if not, fallback to a parent and so on. default theme
is always a parent as it is assumed to provide everything

-- 
- Codito, ergo sum - "I code, therefore I am" --
The Rasterman (Carsten Haitzler)[EMAIL PROTECTED]


-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


Re: [E-devel] Unified theme for apps

2008-04-01 Thread The Rasterman
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 gtk and qt
will be more limited in their use of edje - but it is about the only sane way
to do it.

> 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 what the themer wants to do. If he just wants to have 
> > E/EWL/ETL to be consistent with QT/GTK he only has to alter 
> > the "elements.edj" file.
> > 
> > The goal is consistent (not 1:1 equally looking) appearence among the EFL 
> > toolkits without elminating the possibilty of themers altering this or that 
> > in a specific theme.
> > 
> > If we force layout and behaviour definition in the programming level then I 
> > don't see the point of an Edje based toolkit library... well I do see some 
> > benefits, but I would like moar.
> > 
> 
> 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.
> 
> And, who installs elements.edj? Does it ship with all three? How do you 
> know when to write it and when not? What happens if Ewl uses an updated 
> version that the themer hasn't put the right keys in for? Does it just 
> ship with E17? That won't work as Ewl doesn't require E17 and visa versa.
> 
> You're suddenly tying E17, Ewl and Etk together when there is no tie 
> between then.
> 
> dan
> 
> 
> -
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> ___
> enlightenment-devel mailing list
> enlightenment-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
> 


-- 
- Codito, ergo sum - "I code, therefore I am" --
The Rasterman (Carsten Haitzler)[EMAIL PROTECTED]


-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


Re: [E-devel] SoC deadline extension...

2008-04-01 Thread Ian C.
Can't really give a definite number as there are more and coming in but 
I will say we've been getting quite a few but feel free to continue to 
turn in more applications till next week! =)
--Ian
Atton Jonathan wrote:
> On Tue, 01 Apr 2008 10:47:32 -0500
> Ravenlock <[EMAIL PROTECTED]> wrote:
>
>   
>> Hello,
>>
>> I am pleased to announce, for your convenience and ours, Google has
>> extended the student application deadline by one week.  The new
>> deadline is April 7th.
>>
>> We have had a very nice turn out so far.  Keep up the good work.  We
>> hope to see many more applications in the coming week.
>>
>> For those of you who may have not yet submitted an application, but
>> intend to do so  Please take a look at the URL I've added to our
>> ideas page.  It can point you to some examples of applications being
>> submitted by other students (at another organization)
>>
>> If you desire to modify your previously submitted application, and
>> have any difficulty, please contact myself or your probable mentor.
>> We can post a public comment to it which will certainly allow you to
>> edit it at that time.
>>
>> 
>
> Good :)
>
> How many students are interested currently ? a lot I hope :)
>
>
>   

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


Re: [E-devel] Unified theme for apps

2008-04-01 Thread dan sinclair
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 
> textures will want to use multiple images with different properties in the 
> image{} block. 
> 

How do you handle padding and insets? The widget libraries all do this 
differently. Ewl uses data encoded into the edje file directly. Not sure 
what e17 and etk do.


>> And, who installs elements.edj? Does it ship with all three? How do you
>> know when to write it and when not? What happens if Ewl uses an updated
>> version that the themer hasn't put the right keys in for? Does it just
>> ship with E17? That won't work as Ewl doesn't require E17 and visa versa.
>>
> Well, this is just a standarization method to ease integration of themes by 
> distributors like OpenGEU. Consistency among the files should be mantained by 
> the distributors.
> 
>> You're suddenly tying E17, Ewl and Etk together when there is no tie
>> between then.
> Not at all, E17, Ewl and Etk don't have to do absolutely nothing to implement 
> this. This is all at theme level. Only a function to allow assembling a theme 
> file at runtime would have to be included in Edje.
> 

But where would these theme file pieces come from. Who installs them. 
You can't just say use them, they have to get installed at some point.


> A libUI.c shared between E17, Ewl and Etk would tie them togheter much more.
> 

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.


dan


-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


Re: [E-devel] Unified theme for apps

2008-04-01 Thread andres
@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 there, across the themes of the different EFL based toolkits. Use a 
QT-GTK theme that kinda fits.

I'm not suggesting some sort of scheme to make all the toolkits look exactly 
the same. Because that would be wrong! They (sort of) behave differently so 
they should (sort of) look differently. I'm suggesting a very mild design 
element reutilization. Unity.

Edje allows most of this today. A single edje file can contain the three 
themes using the same lists of fonts, colors and images. There is no need for 
the two file separation I made before.

My suggestion could be described as a glorified 20-minutes-image-replacement.
Instead of replacing plain images, you replace a slightly more complex 
element, a group. The group represents an image, used in the same way you 
would use an image. But this group would handle resize (and other aspects) 
more intelligently than a plain image.

For QT/GTK a simple extension of the gtk-qt-theme engine could be made that 
imported *some* appareance hints from this Edje theme.

That is all.

I'm sorry for making a mess of things. The specific of these themeing 
guidelines are to be discussed later IF the openGEU guys think they need 
them.

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


Re: [E-devel] Unified theme for apps

2008-04-01 Thread Jose Gonzalez
   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 uniform look&feel 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 of those, it'd have to be the 
apps that
choose to use default theme elements for the standard widgets and little 
else.
  There's a pretty standard component/theming mechanism for simple
web pages - html + css, and you still have the issue that people write these
web pages using whatever designs they like.. and even that isn't considered
enough, they want more variability and uniqueness!




-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


Re: [E-devel] Unified theme for apps

2008-04-01 Thread dan sinclair
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,
> leading to the possibility of a uniform look&feel 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 of those, it'd have to be the 
> apps that
> choose to use default theme elements for the standard widgets and little 
> else.
>   There's a pretty standard component/theming mechanism for simple
> web pages - html + css, and you still have the issue that people write these
> web pages using whatever designs they like.. and even that isn't considered
> enough, they want more variability and uniqueness!
> 
> 

Is Edje not the one true mechanism for theme? A uniform look and feel is 
nice, but you'd notice if you looked, Ewl allows you to override the 
theme on anything you want. At any point in the widget hierarchy. So, 
yes, I think it would be a good idea to have one widget library. And no, 
I don't see why you have to lock the theme in.

I really don't see how your html example is relevant. People can 
re-theme Ewl widgets, they can code in straight Edje if they want. They 
can even embed those Ewl widgets into their Edje application. Guess 
what, they still get variability and uniqueness.

dan

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


Re: [E-devel] Unified theme for apps

2008-04-01 Thread Jose Gonzalez
   dan sinclair wrote:

>>
>>   The 'one true way' of widgetry with the one true mechanism for 
>> theming,
>> leading to the possibility of a uniform look&feel 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 of those, it'd have to be the 
>> apps that
>> choose to use default theme elements for the standard widgets and 
>> little else.
>>   There's a pretty standard component/theming mechanism for simple
>> web pages - html + css, and you still have the issue that people 
>> write these
>> web pages using whatever designs they like.. and even that isn't 
>> considered
>> enough, they want more variability and uniqueness!
>>
>>
>
> Is Edje not the one true mechanism for theme? A uniform look and feel 
> is nice,

  No it's not the one true mechanism - it's one way and that's all.

> but you'd notice if you looked, Ewl allows you to override the theme 
> on anything you want. At any point in the widget hierarchy.

  And you'd notice if you read and paid attention that I've stated
several times that both ewl and etk allow for that.

> So, yes, I think it would be a good idea to have one widget library. 
> And no, I don't see why you have to lock the theme in.
>
> I really don't see how your html example is relevant. People can 
> re-theme Ewl widgets, 

  Look deeper.

> they can code in straight Edje if they want. They can even embed those 
> Ewl widgets into their Edje application. Guess what, they still get 
> variability and uniqueness.
>



-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel