From: Carsten H. (T. R. <ra...@ra...> - 2012-07-09 09:34:52
|
Well i thought we'd have a weekend of peace and quiet before i sent this. EFL is now in freeze. that means no new features (unless that feature is absolutely needed to solve a bug) until release (planned for end of this month). I am in the middle for bumping the version of all of efl planned for release to 1.6.99 (in preparation for a unified 1.7.0 release). I shall check over changelogs and news files. also i'll go through a bit of a backlog of bug reports too. so what does this mean? 1. we are unifying everything to 1.7 -> we don't have to deal with differing efl lib versions anymore. 2. synchronised lib version is a step on the way to a single efl tree. 3. after 1.7 release efl will start moving over to a single efl tree 1 library at a time, so after 1.7 releases of efl won't come in separate library source trees, but as a single tree build. this means people with svn build scripts, or using git-svn to track and so on are going to have a rough day after this release. :) 4. a unified tree will also break current doc generations scripts on e.org. they will need fixing as we will now have a single efl doc. 5. until release (end of month) the focus is BUG FIXING. getting things clean and neat for a release. if you have EFL bugs - now is a good time to not be quiet. let us know. :) -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ra...@ra... |
From: Carsten H. (T. R. <ra...@ra...> - 2012-07-09 10:04:19
|
On Mon, 09 Jul 2012 12:41:24 +0300 Tom Hacohen <tom...@sa...> said: > On 09/07/12 12:34, Carsten Haitzler (The Rasterman) wrote: > > 3. after 1.7 release efl will start moving over to a single efl tree 1 > > library at a time, so after 1.7 releases of efl won't come in separate > > library source trees, but as a single tree build. this means people with > > svn build scripts, or using git-svn to track and so on are going to have a > > rough day after this release. :) > > By single you mean multiple, right? I.e efl-core, efl-gui and efl-extra > or whatever as we previously discussed? efl efl/configure ... efl/src efl/src/lib efl/src/lib/eina ... efl/src/lib/ecore ... efl/src/lib/evas .. efl/src/bin/evas ... efl/src/bin/edje from memory. single configure for all. still producing multiple libs and pc files, headers etc. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ra...@ra... |
From: Carsten H. (T. R. <ra...@ra...> - 2012-07-09 10:16:05
|
On Mon, 9 Jul 2012 11:08:46 +0100 Michael Blumenkrantz <mic...@gm...> said: > I don't like the dir structure. having to go down 10 directories just to > get to a .c file is not my idea of fun it's 1 more dir compared to now. > On Mon, Jul 9, 2012 at 11:03 AM, Carsten Haitzler <ra...@ra...>wrote: > > > On Mon, 09 Jul 2012 12:41:24 +0300 Tom Hacohen <tom...@sa...> > > said: > > > > > On 09/07/12 12:34, Carsten Haitzler (The Rasterman) wrote: > > > > 3. after 1.7 release efl will start moving over to a single efl tree 1 > > > > library at a time, so after 1.7 releases of efl won't come in separate > > > > library source trees, but as a single tree build. this means people > > with > > > > svn build scripts, or using git-svn to track and so on are going to > > have a > > > > rough day after this release. :) > > > > > > By single you mean multiple, right? I.e efl-core, efl-gui and efl-extra > > > or whatever as we previously discussed? > > > > efl > > efl/configure > > ... > > efl/src > > efl/src/lib > > efl/src/lib/eina > > ... > > efl/src/lib/ecore > > ... > > efl/src/lib/evas > > .. > > efl/src/bin/evas > > ... > > efl/src/bin/edje > > > > from memory. > > > > single configure for all. still producing multiple libs and pc files, > > headers > > etc. > > > > -- > > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > > The Rasterman (Carsten Haitzler) ra...@ra... > > > > > > > > ------------------------------------------------------------------------------ > > Live Security Virtual Conference > > Exclusive live event will cover all the ways today's security and > > threat landscape has changed and how IT managers can respond. Discussions > > will include endpoint security, mobile security and the latest in malware > > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > _______________________________________________ > > enlightenment-devel mailing list > > enl...@li... > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > enlightenment-devel mailing list > enl...@li... > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ra...@ra... |
From: Carsten H. (T. R. <ra...@ra...> - 2012-07-09 13:17:00
|
On Mon, 09 Jul 2012 13:59:27 +0300 Tom Hacohen <tom...@sa...> said: > On 09/07/12 13:03, Carsten Haitzler (The Rasterman) wrote: > > single configure for all. still producing multiple libs and pc files, > > headers etc. > > > > Ah, just a single source tree, got it. :) I thought you were talking > about merging the libs entirely. > > Though, even here we can split core to 2 (base vs graphical)... nah. not doing that. we are going to have a single src. right now they will produce the exact same installed libs/modules/headers/pc files as we get now, just a single configure && make && make install. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ra...@ra... |
From: Wido <wi...@gm...> - 2012-07-09 16:29:14
|
That means that instead of compiling lib-by-lib in the exact order, we will just run one (and only one) configure-make-make install ?? I like that!!! Is there a reason it wasn't done before? On Monday July 9 2012 10:15:07 Carsten Haitzler escribió: > On Mon, 09 Jul 2012 13:59:27 +0300 Tom Hacohen <tom...@sa...> said: > > > On 09/07/12 13:03, Carsten Haitzler (The Rasterman) wrote: > > > single configure for all. still producing multiple libs and pc files, > > > headers etc. > > > > > > > Ah, just a single source tree, got it. :) I thought you were talking > > about merging the libs entirely. > > > > Though, even here we can split core to 2 (base vs graphical)... > > nah. not doing that. we are going to have a single src. right now they will > produce the exact same installed libs/modules/headers/pc files as we get now, > just a single configure && make && make install. > > -- -- Wido |
From: Stefan S. <s.s...@sa...> - 2012-07-09 16:55:27
|
Hello. On 07/09/2012 05:28 PM, Wido wrote: > That means that instead of compiling lib-by-lib in the exact order, we will just run one (and only one) configure-make-make install ?? Yes. > I like that!!! Is there a reason it wasn't done before? Flexibility. Allowing people to only use some of our libs but not all. regards Stefan Schmidt |
From: Carsten H. (T. R. <ra...@ra...> - 2012-07-10 02:37:29
|
On Mon, 9 Jul 2012 12:05:15 -0300 Lucas De Marchi <luc...@pr...> said: > On Mon, Jul 9, 2012 at 6:34 AM, Carsten Haitzler <ra...@ra...> wrote: > > Well i thought we'd have a weekend of peace and quiet before i sent this. > > > > EFL is now in freeze. that means no new features (unless that feature is > > absolutely needed to solve a bug) until release (planned for end of this > > month). > > Well, I'd ask for we talking about the state of e_dbus before that. > The DBus.Properties is still broken, even after the patch José sent. > We might be able to finish fixing it this week, and that will involve > adding new functions. Example of brokenness: "unless that feature is absolutely needed to solve a bug" :) the ultimate get out of jail card :). > EAPI void e_dbus_object_property_get_cb_set(E_DBus_Object *obj, > E_DBus_Object_Property_Get_Cb func); > > And: > > typedef void (*E_DBus_Object_Property_Get_Cb) (E_DBus_Object *obj, > const char *property, int *type, void **value); > > There's a callback per-object, but it should be per-interface. > Otherwise if you have 1 object with 2 interfaces there's no way to > distinguish from each interface the DBus.Properties.Get() is coming > from. Grepping trunk revealed there's no user of such API. How we are > going to fix it without breaking the API/ABI is still undecided. > > So, I'd ask to wait for the freeze until next Friday at least. Not > that it shouldn't be fixed on next version, but it would be good to > have it on this one. asd above. if u need to add a feature to fix a bug - then add it. :) but ONLY if it is to fix a bug. > Lucas De Marchi > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > enlightenment-devel mailing list > enl...@li... > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ra...@ra... |
From: Carsten H. (T. R. <ra...@ra...> - 2012-07-10 02:43:49
|
On Mon, 9 Jul 2012 13:28:56 -0300 Wido <wi...@gm...> said: > That means that instead of compiling lib-by-lib in the exact order, we will > just run one (and only one) configure-make-make install ?? yes. if u dont want a lib built u'll have to --disable it as opposed to just not download/build it. you will download everything we release in 1 big tarball (or src checkout). deal with it. :) > I like that!!! Is there a reason it wasn't done before? 1. save bandwidth so you only download what u need and want, not everything. 2. make it obvious and easy to people to know they can just use a minimal subset of libs we release to make something so they can have a minimal dependency chain 3. save disk space 4. efl grew organically adding new libs to solve new problems over time. it really didn't start life as EFL - it started as 1, then 2 then 3 libs that happened to come from the same team that solved different problems. it was never envisaged as one big project and toolkit set until much later in its lifetime as it became apparent that is what it had in effect become. this move to a single tree reflects that changed reality in a concrete way and saves us time, effort, and improves many things. it hurts the people who want to download less etc. etc. - but it's a sacrifice worth making. > On Monday July 9 2012 10:15:07 Carsten Haitzler escribió: > > On Mon, 09 Jul 2012 13:59:27 +0300 Tom Hacohen <tom...@sa...> > > said: > > > > > On 09/07/12 13:03, Carsten Haitzler (The Rasterman) wrote: > > > > single configure for all. still producing multiple libs and pc files, > > > > headers etc. > > > > > > > > > > Ah, just a single source tree, got it. :) I thought you were talking > > > about merging the libs entirely. > > > > > > Though, even here we can split core to 2 (base vs graphical)... > > > > nah. not doing that. we are going to have a single src. right now they will > > produce the exact same installed libs/modules/headers/pc files as we get > > now, just a single configure && make && make install. > > > > > -- > > -- > Wido -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ra...@ra... |
From: Daniel J. S. <seo...@gm...> - 2012-07-10 04:45:04
|
On Tue, Jul 10, 2012 at 11:43 AM, Carsten Haitzler <ra...@ra...> wrote: > On Mon, 9 Jul 2012 13:28:56 -0300 Wido <wi...@gm...> said: > >> That means that instead of compiling lib-by-lib in the exact order, we will >> just run one (and only one) configure-make-make install ?? > > yes. if u dont want a lib built u'll have to --disable it as opposed to just > not download/build it. you will download everything we release in 1 big > tarball (or src checkout). deal with it. :) > >> I like that!!! Is there a reason it wasn't done before? > > 1. save bandwidth so you only download what u need and want, not everything. > 2. make it obvious and easy to people to know they can just use a minimal > subset of libs we release to make something so they can have a minimal > dependency chain Even with the one big tree, can we use a minimal subset of libs? Not everyone wants to use every libraries in efl and as far as I know that's one of the pros of efl. Daniel Juyung Seo (SeoZ) > 3. save disk space > 4. efl grew organically adding new libs to solve new problems over time. it > really didn't start life as EFL - it started as 1, then 2 then 3 libs that > happened to come from the same team that solved different problems. it was > never envisaged as one big project and toolkit set until much later in its > lifetime as it became apparent that is what it had in effect become. this move > to a single tree reflects that changed reality in a concrete way and saves us > time, effort, and improves many things. it hurts the people who want to > download less etc. etc. - but it's a sacrifice worth making. > >> On Monday July 9 2012 10:15:07 Carsten Haitzler escribió: >> > On Mon, 09 Jul 2012 13:59:27 +0300 Tom Hacohen <tom...@sa...> >> > said: >> > >> > > On 09/07/12 13:03, Carsten Haitzler (The Rasterman) wrote: >> > > > single configure for all. still producing multiple libs and pc files, >> > > > headers etc. >> > > > >> > > >> > > Ah, just a single source tree, got it. :) I thought you were talking >> > > about merging the libs entirely. >> > > >> > > Though, even here we can split core to 2 (base vs graphical)... >> > >> > nah. not doing that. we are going to have a single src. right now they will >> > produce the exact same installed libs/modules/headers/pc files as we get >> > now, just a single configure && make && make install. >> > >> > >> -- >> >> -- >> Wido > > > -- > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > The Rasterman (Carsten Haitzler) ra...@ra... > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > enlightenment-devel mailing list > enl...@li... > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel |
From: Wido <wi...@gm...> - 2012-07-11 01:44:17
|
What about the rest? extra-modules, proto, games, weird stuff? what's going to happen to all of them? On Monday July 9 2012 23:43:35 Carsten Haitzler escribió: > On Mon, 9 Jul 2012 13:28:56 -0300 Wido <wi...@gm...> said: > > > That means that instead of compiling lib-by-lib in the exact order, we will > > just run one (and only one) configure-make-make install ?? > > yes. if u dont want a lib built u'll have to --disable it as opposed to just > not download/build it. you will download everything we release in 1 big > tarball (or src checkout). deal with it. :) > > > I like that!!! Is there a reason it wasn't done before? > > 1. save bandwidth so you only download what u need and want, not everything. > 2. make it obvious and easy to people to know they can just use a minimal > subset of libs we release to make something so they can have a minimal > dependency chain > 3. save disk space > 4. efl grew organically adding new libs to solve new problems over time. it > really didn't start life as EFL - it started as 1, then 2 then 3 libs that > happened to come from the same team that solved different problems. it was > never envisaged as one big project and toolkit set until much later in its > lifetime as it became apparent that is what it had in effect become. this move > to a single tree reflects that changed reality in a concrete way and saves us > time, effort, and improves many things. it hurts the people who want to > download less etc. etc. - but it's a sacrifice worth making. > > > On Monday July 9 2012 10:15:07 Carsten Haitzler escribió: > > > On Mon, 09 Jul 2012 13:59:27 +0300 Tom Hacohen <tom...@sa...> > > > said: > > > > > > > On 09/07/12 13:03, Carsten Haitzler (The Rasterman) wrote: > > > > > single configure for all. still producing multiple libs and pc files, > > > > > headers etc. > > > > > > > > > > > > > Ah, just a single source tree, got it. :) I thought you were talking > > > > about merging the libs entirely. > > > > > > > > Though, even here we can split core to 2 (base vs graphical)... > > > > > > nah. not doing that. we are going to have a single src. right now they will > > > produce the exact same installed libs/modules/headers/pc files as we get > > > now, just a single configure && make && make install. > > > > > > > > > -- -- Wido |
From: Carsten H. (T. R. <ra...@ra...> - 2012-07-11 03:21:25
|
On Tue, 10 Jul 2012 22:44:01 -0300 Wido <wi...@gm...> said: extra-modules are not part of efl - so not relevant. proto is prototype stuff - so nothing will happen to it. if its not part of the set of efl we have releases as 1.x it wont go into the efl tree. ultimately there is a plan to move to git and this efl tree will be a single git module covering "efl". if its not there it doesnt go into that module. we'll have a separate git module for e (if this includes quality apps or not is a question atm - if not we'll have another git module maybe per good quality app) and then another git module for "other stuff" which is everything else. > What about the rest? extra-modules, proto, games, weird stuff? what's going > to happen to all of them? > > On Monday July 9 2012 23:43:35 Carsten Haitzler escribió: > > On Mon, 9 Jul 2012 13:28:56 -0300 Wido <wi...@gm...> said: > > > > > That means that instead of compiling lib-by-lib in the exact order, we > > > will just run one (and only one) configure-make-make install ?? > > > > yes. if u dont want a lib built u'll have to --disable it as opposed to just > > not download/build it. you will download everything we release in 1 big > > tarball (or src checkout). deal with it. :) > > > > > I like that!!! Is there a reason it wasn't done before? > > > > 1. save bandwidth so you only download what u need and want, not everything. > > 2. make it obvious and easy to people to know they can just use a minimal > > subset of libs we release to make something so they can have a minimal > > dependency chain > > 3. save disk space > > 4. efl grew organically adding new libs to solve new problems over time. it > > really didn't start life as EFL - it started as 1, then 2 then 3 libs that > > happened to come from the same team that solved different problems. it was > > never envisaged as one big project and toolkit set until much later in its > > lifetime as it became apparent that is what it had in effect become. this > > move to a single tree reflects that changed reality in a concrete way and > > saves us time, effort, and improves many things. it hurts the people who > > want to download less etc. etc. - but it's a sacrifice worth making. > > > > > On Monday July 9 2012 10:15:07 Carsten Haitzler escribió: > > > > On Mon, 09 Jul 2012 13:59:27 +0300 Tom Hacohen <tom...@sa...> > > > > said: > > > > > > > > > On 09/07/12 13:03, Carsten Haitzler (The Rasterman) wrote: > > > > > > single configure for all. still producing multiple libs and pc > > > > > > files, headers etc. > > > > > > > > > > > > > > > > Ah, just a single source tree, got it. :) I thought you were talking > > > > > about merging the libs entirely. > > > > > > > > > > Though, even here we can split core to 2 (base vs graphical)... > > > > > > > > nah. not doing that. we are going to have a single src. right now they > > > > will produce the exact same installed libs/modules/headers/pc files as > > > > we get now, just a single configure && make && make install. > > > > > > > > > > > > > > > -- > > -- > Wido > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > enlightenment-users mailing list > enl...@li... > https://lists.sourceforge.net/lists/listinfo/enlightenment-users -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ra...@ra... |
From: Wido <wi...@gm...> - 2012-07-11 01:47:18
|
I would like to ask for something that really annoys me, but I don't really think it's a bug. When an entry in the preferences menu doesn't have an icon, you will see the text moved to the side. Would it be possible to resize the icon area to the bigger icon in that menu? You can see what I'm talking in this blog entry http://e17releasemanager.wordpress.com/2012/07/10/enlightenment-hero-of-the-week-illogict-chidambar-zinnoury/ On Monday July 9 2012 06:34:31 Carsten Haitzler escribió: > Well i thought we'd have a weekend of peace and quiet before i sent this. > > EFL is now in freeze. that means no new features (unless that feature is > absolutely needed to solve a bug) until release (planned for end of this month). > > I am in the middle for bumping the version of all of efl planned for release to > 1.6.99 (in preparation for a unified 1.7.0 release). I shall check over > changelogs and news files. also i'll go through a bit of a backlog of bug > reports too. > > so what does this mean? > > 1. we are unifying everything to 1.7 -> we don't have to deal with differing > efl lib versions anymore. > 2. synchronised lib version is a step on the way to a single efl tree. > 3. after 1.7 release efl will start moving over to a single efl tree 1 library > at a time, so after 1.7 releases of efl won't come in separate library source > trees, but as a single tree build. this means people with svn build scripts, or > using git-svn to track and so on are going to have a rough day after this > release. :) > 4. a unified tree will also break current doc generations scripts on e.org. > they will need fixing as we will now have a single efl doc. > 5. until release (end of month) the focus is BUG FIXING. getting things clean > and neat for a release. if you have EFL bugs - now is a good time to not be > quiet. let us know. :) > > > -- -- Wido |
From: Carsten H. (T. R. <ra...@ra...> - 2012-07-11 03:21:32
|
On Tue, 10 Jul 2012 22:47:06 -0300 Wido <wi...@gm...> said: > I would like to ask for something that really annoys me, but I don't really > think it's a bug. > > When an entry in the preferences menu doesn't have an icon, you will see the > text moved to the side. Would it be possible to resize the icon area to the > bigger icon in that menu? it's part of the "get theme 100% ready to ship" -> fix all the missing and duplicated icons. > You can see what I'm talking in this blog entry > http://e17releasemanager.wordpress.com/2012/07/10/enlightenment-hero-of-the-week-illogict-chidambar-zinnoury/ > > On Monday July 9 2012 06:34:31 Carsten Haitzler escribió: > > Well i thought we'd have a weekend of peace and quiet before i sent this. > > > > EFL is now in freeze. that means no new features (unless that feature is > > absolutely needed to solve a bug) until release (planned for end of this > > month). > > > > I am in the middle for bumping the version of all of efl planned for > > release to 1.6.99 (in preparation for a unified 1.7.0 release). I shall > > check over changelogs and news files. also i'll go through a bit of a > > backlog of bug reports too. > > > > so what does this mean? > > > > 1. we are unifying everything to 1.7 -> we don't have to deal with differing > > efl lib versions anymore. > > 2. synchronised lib version is a step on the way to a single efl tree. > > 3. after 1.7 release efl will start moving over to a single efl tree 1 > > library at a time, so after 1.7 releases of efl won't come in separate > > library source trees, but as a single tree build. this means people with > > svn build scripts, or using git-svn to track and so on are going to have a > > rough day after this release. :) > > 4. a unified tree will also break current doc generations scripts on e.org. > > they will need fixing as we will now have a single efl doc. > > 5. until release (end of month) the focus is BUG FIXING. getting things > > clean and neat for a release. if you have EFL bugs - now is a good time to > > not be quiet. let us know. :) > > > > > > > -- > > -- > Wido > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ra...@ra... |
From: Wido <wi...@gm...> - 2012-07-11 03:29:53
|
On Wednesday July 11 2012 00:07:28 Carsten Haitzler escribió: > On Tue, 10 Jul 2012 22:47:06 -0300 Wido <wi...@gm...> said: > > > I would like to ask for something that really annoys me, but I don't really > > think it's a bug. > > > > When an entry in the preferences menu doesn't have an icon, you will see the > > text moved to the side. Would it be possible to resize the icon area to the > > bigger icon in that menu? > > it's part of the "get theme 100% ready to ship" -> fix all the missing and > duplicated icons. While I think having a complete theme is a must, what would happen to other themes? maybe for lazy themers? adding a fallback to resize all icons area to be the same size is not nice for you? > > > You can see what I'm talking in this blog entry > > http://e17releasemanager.wordpress.com/2012/07/10/enlightenment-hero-of-the-week-illogict-chidambar-zinnoury/ > > > > On Monday July 9 2012 06:34:31 Carsten Haitzler escribió: > > > Well i thought we'd have a weekend of peace and quiet before i sent this. > > > > > > EFL is now in freeze. that means no new features (unless that feature is > > > absolutely needed to solve a bug) until release (planned for end of this > > > month). > > > > > > I am in the middle for bumping the version of all of efl planned for > > > release to 1.6.99 (in preparation for a unified 1.7.0 release). I shall > > > check over changelogs and news files. also i'll go through a bit of a > > > backlog of bug reports too. > > > > > > so what does this mean? > > > > > > 1. we are unifying everything to 1.7 -> we don't have to deal with differing > > > efl lib versions anymore. > > > 2. synchronised lib version is a step on the way to a single efl tree. > > > 3. after 1.7 release efl will start moving over to a single efl tree 1 > > > library at a time, so after 1.7 releases of efl won't come in separate > > > library source trees, but as a single tree build. this means people with > > > svn build scripts, or using git-svn to track and so on are going to have a > > > rough day after this release. :) > > > 4. a unified tree will also break current doc generations scripts on e.org. > > > they will need fixing as we will now have a single efl doc. > > > 5. until release (end of month) the focus is BUG FIXING. getting things > > > clean and neat for a release. if you have EFL bugs - now is a good time to > > > not be quiet. let us know. :) > > > > > > > > > > > > -- -- Wido |
From: Carsten H. (T. R. <ra...@ra...> - 2012-07-11 03:54:43
|
On Wed, 11 Jul 2012 00:29:38 -0300 Wido <wi...@gm...> said: > > > On Wednesday July 11 2012 00:07:28 Carsten Haitzler escribió: > > On Tue, 10 Jul 2012 22:47:06 -0300 Wido <wi...@gm...> said: > > > > > I would like to ask for something that really annoys me, but I don't > > > really think it's a bug. > > > > > > When an entry in the preferences menu doesn't have an icon, you will see > > > the text moved to the side. Would it be possible to resize the icon area > > > to the bigger icon in that menu? > > > > it's part of the "get theme 100% ready to ship" -> fix all the missing and > > duplicated icons. > > While I think having a complete theme is a must, what would happen to other > themes? maybe for lazy themers? adding a fallback to resize all icons area to > be the same size is not nice for you? if a theme doesnt include data e falls back to default, which will be guaranteed to provide it. > > > > > You can see what I'm talking in this blog entry > > > http://e17releasemanager.wordpress.com/2012/07/10/enlightenment-hero-of-the-week-illogict-chidambar-zinnoury/ > > > > > > On Monday July 9 2012 06:34:31 Carsten Haitzler escribió: > > > > Well i thought we'd have a weekend of peace and quiet before i sent > > > > this. > > > > > > > > EFL is now in freeze. that means no new features (unless that feature is > > > > absolutely needed to solve a bug) until release (planned for end of this > > > > month). > > > > > > > > I am in the middle for bumping the version of all of efl planned for > > > > release to 1.6.99 (in preparation for a unified 1.7.0 release). I shall > > > > check over changelogs and news files. also i'll go through a bit of a > > > > backlog of bug reports too. > > > > > > > > so what does this mean? > > > > > > > > 1. we are unifying everything to 1.7 -> we don't have to deal with > > > > differing efl lib versions anymore. > > > > 2. synchronised lib version is a step on the way to a single efl tree. > > > > 3. after 1.7 release efl will start moving over to a single efl tree 1 > > > > library at a time, so after 1.7 releases of efl won't come in separate > > > > library source trees, but as a single tree build. this means people with > > > > svn build scripts, or using git-svn to track and so on are going to > > > > have a rough day after this release. :) > > > > 4. a unified tree will also break current doc generations scripts on > > > > e.org. they will need fixing as we will now have a single efl doc. > > > > 5. until release (end of month) the focus is BUG FIXING. getting things > > > > clean and neat for a release. if you have EFL bugs - now is a good time > > > > to not be quiet. let us know. :) > > > > > > > > > > > > > > > > > > > -- > > -- > Wido > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > enlightenment-users mailing list > enl...@li... > https://lists.sourceforge.net/lists/listinfo/enlightenment-users -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ra...@ra... |