On Tue, 1 Jul 2008 23:30:45 +0800 Toma <[EMAIL PROTECTED]> babbled:
i like. :)
> Heres what Ive just spent the last 30 mins doing...
>
> data {
> item: "e/theme/name""Fireball";
> item: "e/theme/version" "1.6";
> item: "e/theme/license" "GPL";
> item: "e/theme/aut
On Friday, 25 July 2008, at 01:10:45 (+1000),
Carsten Haitzler wrote:
> > 3. This whole mess is a very bad idea. Handling versioned
> > dependencies is a much, much harder problem than you realize. And
> > restricting what applications are allowed to peek at a theme's
> > bits is silly. Just m
On Mon, 7 Jul 2008 10:22:50 -0700 Michael Jennings <[EMAIL PROTECTED]> babbled:
> On Monday, 07 July 2008, at 14:23:51 (+0200),
> Dave Andreoli wrote:
>
> > hmmm, this is a problem... we can use:
> > item: "/theme/applications" "e etk ewl";
> >
> > but then we also need multiple "application_v
Well here it is. A final revision with a patch for Bling Bling. Ill
upload some more patches for other default themes later, if theyre
needed/desired.
You can read the spec here:
http://wiki.enlightenment.org/index.php/Edje_theme_labelling
And view the patch in this email.
These fields seem the m
I agree with you KainX. It is a bit of a mess. The application the
theme generally themes is put in the name or filename of it.
And yes, lets stick to KISS to begin with and then go from there. If a
definite need to have those other things is found, then I guess it can
be adopted, but I cant see th
Since the current naming practice for edje parts is to start with a
letter, instead of '/', wouldn't it be better to keep it here:
item: "theme/application/e/version" "xxx"
On Mon, 2008-07-07 at 14:23 +0200, Dave Andreoli wrote:
> - "Toma" <[EMAIL PROTECTED]> ha scritto:
>
> > So change /the
On Monday, 07 July 2008, at 10:22:50 (-0700),
Michael Jennings wrote:
> 1. Use the hierarchy you already have. Don't invent silly additional
> separators (like '_') for no reason.
>
> item: "/theme/application/e/min_version""0.16.999.043";
> item: "/theme/application/ewl/min_version
On Monday, 07 July 2008, at 14:23:51 (+0200),
Dave Andreoli wrote:
> hmmm, this is a problem... we can use:
> item: "/theme/applications" "e etk ewl";
>
> but then we also need multiple "application_version" fiels, like:
> item: "/theme/e_version""xxx"
> item: "/theme/etk_version" "xxx"
>
I think we need to stop guessing / forcing a method of detecting theme
compatibility.
/theme/applications being a set of space-separated values looks very
hackish and not at all useful.
Instead we should let each app decide how they want to handle it..
probably by using their own attribute name.
It
2008/7/7 muzzle <[EMAIL PROTECTED]>:
> Hi
>
> On Mon, Jul 7, 2008 at 3:14 AM, Toma <[EMAIL PROTECTED]> wrote:
>>
>> Ok folks! Heres a final revision. Note the removal of e/ so that it
>> can be universally used without the need to figure out the leading
>> name (if there are any). Also included is
Hi
On Mon, Jul 7, 2008 at 3:14 AM, Toma <[EMAIL PROTECTED]> wrote:
>
> Ok folks! Heres a final revision. Note the removal of e/ so that it
> can be universally used without the need to figure out the leading
> name (if there are any). Also included is 'base_version' to outline
> the base version o
- "Toma" <[EMAIL PROTECTED]> ha scritto:
> So change /theme/base_version to /theme/application_version too?
> Sounds fun. What about themes that contain multiple themes packs? Eg.
> detour? Or the new idea of combining e17 themes with etk and ewl
> components installed? Would items with the s
So change /theme/base_version to /theme/application_version too?
Sounds fun. What about themes that contain multiple themes packs? Eg.
detour? Or the new idea of combining e17 themes with etk and ewl
components installed? Would items with the same name be overwritten by
the last one loaded? Or just
- "Toma" <[EMAIL PROTECTED]> ha scritto:
> Ok folks! Heres a final revision. Note the removal of e/ so that it
> can be universally used without the need to figure out the leading
> name (if there are any). Also included is 'base_version' to outline
> the base version of the application neede
Ok folks! Heres a final revision. Note the removal of e/ so that it
can be universally used without the need to figure out the leading
name (if there are any). Also included is 'base_version' to outline
the base version of the application needed to use the theme. Again,
its a non-specific name so i
Heres what Ive just spent the last 30 mins doing...
data {
item: "e/theme/name" "Fireball";
item: "e/theme/version" "1.6";
item: "e/theme/license" "GPL";
item: "e/theme/author""Tom Haste ([EMAIL PROTECTED])";
}
---
data {
item: "etk/theme/name"
I like this idea a lot. It would be good to make those fields
mandatory, and hide
themes from the theme configuration dialog if they dont have all of
those fields.
That would really speed up adoption.
Beyond the e/theme/version (which matches the version of E), I would suggest
adding a version for
On Mon, 30 Jun 2008 15:23:32 +0200 Brian 'morlenxus' Miculcy
<[EMAIL PROTECTED]> babbled:
I think adding these in is a good idea. namespacing sounds good. those seem
important fields - useful. as brian said - the rest is implicit in the .edj
file contents itself and is simply a matter of making th
I like the idea. The four items you selected are a good selection. We
don't need a description what a theme file themes - because the edje file itself
descripes it. You can get the group parts from the file and so it's
possible to show in a dialog what an edje file exactly does.
We also need a bett
I would say this about covers most of the necessary information.
data {
item: "e/theme/name" "BlingBling";
item: "e/theme/version" "16.999.043";
item: "e/theme/license" "3-Clause BSD";
item: "e/theme/author" "Carsten Rasterman Haitzler & the E17 Team";
}
The 'about' bl
Hmm good call. There are a few more levels you could take aswell, eg.
License, Author... its just a matter of whats really needed. But
thanks for edje and eet, its all details that can be stored in the
files, and we should really take advantage of that.
Toma
2008/6/30 Nick Hughart <[EMAIL PROTECTE
I'd even go a bit further and possibly add something like a minimum E
version required for the theme. There may even be other details that
could be useful. Question is, will anyone else think it's a good idea :)
Toma wrote:
> Hey all!
> I think it would be really great to have a theme name and
Hey all!
I think it would be really great to have a theme name and version
locked in an edj for purpose of identification. Until now the theme
name and version is stored in the filename which is a very flakey and
sometimes misleading way to store this. I think it would be a good
idea to start using
23 matches
Mail list logo
