Re: [E-devel] New EFL release cycle 1.0/1.2/1.6
On 04/26/12 13:49, Carsten Haitzler wrote: > We'd like to announce a new release of several Enlightenment components. > This round we have added Eio, Ethumb, Emotion and Elementary. Please > read the NEWS and README files in each release tarball for information > on what has changed, fixed or added. This release also corresponds with > SVN revision number 70490. > > Emotion is a library to handle video playback using Gstreamer, Xine or other > external plugins (VLC) and display video in Evas as a standard object. It also > can handle audio playback too. Eio is here to support Emotion with async IO > API's. > > Ethumb is a thumbnail generator library that supports the freedesktop.org > thumbnailing standards, and is implemented as a dbus service and a client-side > library that handles dealing with that service for you. > > Elementary is our new widget set, built on top of the rest of EFL, to provide > you with standard widgets and behaviour to make it easy to write GUI > applications. ... and elementary/src/examples/layout_example.edc is missing from the tarball too, makes the "make doc" fail. Sorry, I should have check this before, I was too much focused on SVN :-( -- Jérôme Pinot http://ngc891.blogdns.net/ signature.asc Description: Digital signature -- 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 enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] New EFL release cycle 1.0/1.2/1.6
On 04/26/12 13:49, Carsten Haitzler wrote: > We'd like to announce a new release of several Enlightenment components. > This round we have added Eio, Ethumb, Emotion and Elementary. Please > read the NEWS and README files in each release tarball for information > on what has changed, fixed or added. This release also corresponds with > SVN revision number 70490. > > Emotion is a library to handle video playback using Gstreamer, Xine or other > external plugins (VLC) and display video in Evas as a standard object. It also > can handle audio playback too. Eio is here to support Emotion with async IO > API's. > > Ethumb is a thumbnail generator library that supports the freedesktop.org > thumbnailing standards, and is implemented as a dbus service and a client-side > library that handles dealing with that service for you. > > Elementary is our new widget set, built on top of the rest of EFL, to provide > you with standard widgets and behaviour to make it easy to write GUI > applications. Darn, the example.dox files are missing from some release tarballs, so a lot of examples will not be installed. Packagers will have to add back this file from SVN... -- Jérôme Pinot http://ngc891.blogdns.net/ signature.asc Description: Digital signature -- 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 enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] New EFL release cycle 1.0/1.2/1.6
yay! keep rocking. this is gonna be a memorial dot in the history :) On Apr 26, 2012 1:53 PM, "Carsten Haitzler" wrote: > We'd like to announce a new release of several Enlightenment components. > This round we have added Eio, Ethumb, Emotion and Elementary. Please > read the NEWS and README files in each release tarball for information > on what has changed, fixed or added. This release also corresponds with > SVN revision number 70490. > > Emotion is a library to handle video playback using Gstreamer, Xine or > other > external plugins (VLC) and display video in Evas as a standard object. It > also > can handle audio playback too. Eio is here to support Emotion with async IO > API's. > > Ethumb is a thumbnail generator library that supports the freedesktop.org > thumbnailing standards, and is implemented as a dbus service and a > client-side > library that handles dealing with that service for you. > > Elementary is our new widget set, built on top of the rest of EFL, to > provide > you with standard widgets and behaviour to make it easy to write GUI > applications. > > Eina 1.2.0 - > http://download.enlightenment.org/releases/eina-1.2.0.tar.gz > http://download.enlightenment.org/releases/eina-1.2.0.tar.bz2 > > Eet 1.6.0 - > http://download.enlightenment.org/releases/eet-1.6.0.tar.gz > http://download.enlightenment.org/releases/eet-1.6.0.tar.bz2 > > Evas 1.2.0 - > http://download.enlightenment.org/releases/evas-1.2.0.tar.gz > http://download.enlightenment.org/releases/evas-1.2.0.tar.bz2 > > Ecore 1.2.0 - > http://download.enlightenment.org/releases/ecore-1.2.0.tar.gz > http://download.enlightenment.org/releases/ecore-1.2.0.tar.bz2 > > Embryo 1.2.0 - > http://download.enlightenment.org/releases/embryo-1.2.0.tar.gz > http://download.enlightenment.org/releases/embryo-1.2.0.tar.bz2 > > Edje 1.2.0 - > http://download.enlightenment.org/releases/edje-1.2.0.tar.gz > http://download.enlightenment.org/releases/edje-1.2.0.tar.bz2 > > Efreet 1.2.0 - > http://download.enlightenment.org/releases/efreet-1.2.0.tar.gz > http://download.enlightenment.org/releases/efreet-1.2.0.tar.bz2 > > E_dbus 1.2.0 - > http://download.enlightenment.org/releases/e_dbus-1.2.0.tar.gz > http://download.enlightenment.org/releases/e_dbus-1.2.0.tar.bz2 > > Eeze 1.2.0 - > http://download.enlightenment.org/releases/eeze-1.2.0.tar.gz > http://download.enlightenment.org/releases/eeze-1.2.0.tar.bz2 > > Expedite 1.2.0 - > http://download.enlightenment.org/releases/expedite-1.2.0.tar.gz > http://download.enlightenment.org/releases/expedite-1.2.0.tar.bz2 > > Evas Generic Loaders 1.2.0 - > > http://download.enlightenment.org/releases/evas_generic_loaders-1.2.0.tar.gz > > http://download.enlightenment.org/releases/evas_generic_loaders-1.2.0.tar.bz2 > > Eio 1.0.0 - > http://download.enlightenment.org/releases/eio-1.0.0.tar.gz > http://download.enlightenment.org/releases/eio-1.0.0.tar.bz2 > > Emotion 1.0.0 - > http://download.enlightenment.org/releases/emotion-1.0.0.tar.gz > http://download.enlightenment.org/releases/emotion-1.0.0.tar.bz2 > > Ethumb 1.0.0 - > http://download.enlightenment.org/releases/ethumb-1.0.0.tar.gz > http://download.enlightenment.org/releases/ethumb-1.0.0.tar.bz2 > > Elementary 1.0.0 - > http://download.enlightenment.org/releases/elementary-1.0.0.tar.gz > http://download.enlightenment.org/releases/elementary-1.0.0.tar.bz2 > > > -- > - Codito, ergo sum - "I code, therefore I am" -- > The Rasterman (Carsten Haitzler)ras...@rasterman.com > > > > -- > 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 > enlightenment-devel@lists.sourceforge.net > 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 enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
[E-devel] New EFL release cycle 1.0/1.2/1.6
We'd like to announce a new release of several Enlightenment components. This round we have added Eio, Ethumb, Emotion and Elementary. Please read the NEWS and README files in each release tarball for information on what has changed, fixed or added. This release also corresponds with SVN revision number 70490. Emotion is a library to handle video playback using Gstreamer, Xine or other external plugins (VLC) and display video in Evas as a standard object. It also can handle audio playback too. Eio is here to support Emotion with async IO API's. Ethumb is a thumbnail generator library that supports the freedesktop.org thumbnailing standards, and is implemented as a dbus service and a client-side library that handles dealing with that service for you. Elementary is our new widget set, built on top of the rest of EFL, to provide you with standard widgets and behaviour to make it easy to write GUI applications. Eina 1.2.0 - http://download.enlightenment.org/releases/eina-1.2.0.tar.gz http://download.enlightenment.org/releases/eina-1.2.0.tar.bz2 Eet 1.6.0 - http://download.enlightenment.org/releases/eet-1.6.0.tar.gz http://download.enlightenment.org/releases/eet-1.6.0.tar.bz2 Evas 1.2.0 - http://download.enlightenment.org/releases/evas-1.2.0.tar.gz http://download.enlightenment.org/releases/evas-1.2.0.tar.bz2 Ecore 1.2.0 - http://download.enlightenment.org/releases/ecore-1.2.0.tar.gz http://download.enlightenment.org/releases/ecore-1.2.0.tar.bz2 Embryo 1.2.0 - http://download.enlightenment.org/releases/embryo-1.2.0.tar.gz http://download.enlightenment.org/releases/embryo-1.2.0.tar.bz2 Edje 1.2.0 - http://download.enlightenment.org/releases/edje-1.2.0.tar.gz http://download.enlightenment.org/releases/edje-1.2.0.tar.bz2 Efreet 1.2.0 - http://download.enlightenment.org/releases/efreet-1.2.0.tar.gz http://download.enlightenment.org/releases/efreet-1.2.0.tar.bz2 E_dbus 1.2.0 - http://download.enlightenment.org/releases/e_dbus-1.2.0.tar.gz http://download.enlightenment.org/releases/e_dbus-1.2.0.tar.bz2 Eeze 1.2.0 - http://download.enlightenment.org/releases/eeze-1.2.0.tar.gz http://download.enlightenment.org/releases/eeze-1.2.0.tar.bz2 Expedite 1.2.0 - http://download.enlightenment.org/releases/expedite-1.2.0.tar.gz http://download.enlightenment.org/releases/expedite-1.2.0.tar.bz2 Evas Generic Loaders 1.2.0 - http://download.enlightenment.org/releases/evas_generic_loaders-1.2.0.tar.gz http://download.enlightenment.org/releases/evas_generic_loaders-1.2.0.tar.bz2 Eio 1.0.0 - http://download.enlightenment.org/releases/eio-1.0.0.tar.gz http://download.enlightenment.org/releases/eio-1.0.0.tar.bz2 Emotion 1.0.0 - http://download.enlightenment.org/releases/emotion-1.0.0.tar.gz http://download.enlightenment.org/releases/emotion-1.0.0.tar.bz2 Ethumb 1.0.0 - http://download.enlightenment.org/releases/ethumb-1.0.0.tar.gz http://download.enlightenment.org/releases/ethumb-1.0.0.tar.bz2 Elementary 1.0.0 - http://download.enlightenment.org/releases/elementary-1.0.0.tar.gz http://download.enlightenment.org/releases/elementary-1.0.0.tar.bz2 -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- 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 enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
[E-devel] New EFL release cycle 1.0/1.2/1.6 BETA
We'd like to announce a new release cycle beta release of several Enlightenment components. This round we have added Eio, Ethumb, Emotion and Elementary. Emotion is a library to handle video playback using Gstreamer, Xine or other external plugins (VLC) and display video in Evas as a standard object. It also can handle audio playback too. Eio is here to support Emotion with async IO API's. Ethumb is a thumbnail generator library that supports the freedesktop.org thumbnailing standards, and is implemented as a dbus service and a client-side library that handles dealing with that service for you. Elementary is our new widget set, built on top of the rest of EFL, to provide you with standard widgets and behaviour to make it easy to write GUI applications. Eina 1.2.0 - http://download.enlightenment.org/releases/eina-1.2.0-beta.tar.gz http://download.enlightenment.org/releases/eina-1.2.0-beta.tar.bz2 Eet 1.6.0 - http://download.enlightenment.org/releases/eet-1.6.0-beta.tar.gz http://download.enlightenment.org/releases/eet-1.6.0-beta.tar.bz2 Evas 1.2.0 - http://download.enlightenment.org/releases/evas-1.2.0-beta.tar.gz http://download.enlightenment.org/releases/evas-1.2.0-beta.tar.bz2 Ecore 1.2.0 - http://download.enlightenment.org/releases/ecore-1.2.0-beta.tar.gz http://download.enlightenment.org/releases/ecore-1.2.0-beta.tar.bz2 Embryo 1.2.0 - http://download.enlightenment.org/releases/embryo-1.2.0-beta.tar.gz http://download.enlightenment.org/releases/embryo-1.2.0-beta.tar.bz2 Edje 1.2.0 - http://download.enlightenment.org/releases/edje-1.2.0-beta.tar.gz http://download.enlightenment.org/releases/edje-1.2.0-beta.tar.bz2 Efreet 1.2.0 - http://download.enlightenment.org/releases/efreet-1.2.0-beta.tar.gz http://download.enlightenment.org/releases/efreet-1.2.0-beta.tar.bz2 E_dbus 1.2.0 - http://download.enlightenment.org/releases/e_dbus-1.2.0-beta.tar.gz http://download.enlightenment.org/releases/e_dbus-1.2.0-beta.tar.bz2 Eeze 1.2.0 - http://download.enlightenment.org/releases/eeze-1.2.0-beta.tar.gz http://download.enlightenment.org/releases/eeze-1.2.0-beta.tar.bz2 Expedite 1.2.0 - http://download.enlightenment.org/releases/expedite-1.2.0-beta.tar.gz http://download.enlightenment.org/releases/expedite-1.2.0-beta.tar.bz2 Evas Generic Loaders 1.2.0 - http://download.enlightenment.org/releases/evas_generic_loaders-1.2.0-beta.tar.gz http://download.enlightenment.org/releases/evas_generic_loaders-1.2.0-beta.tar.bz2 Eio 1.0.0 - http://download.enlightenment.org/releases/eio-1.0.0-beta.tar.gz http://download.enlightenment.org/releases/eio-1.0.0-beta.tar.bz2 Emotion 1.0.0 - http://download.enlightenment.org/releases/emotion-1.0.0-beta.tar.gz http://download.enlightenment.org/releases/emotion-1.0.0-beta.tar.bz2 Ethumb 1.0.0 - http://download.enlightenment.org/releases/ethumb-1.0.0-beta.tar.gz http://download.enlightenment.org/releases/ethumb-1.0.0-beta.tar.bz2 Elementary 1.0.0 - http://download.enlightenment.org/releases/elementary-1.0.0-beta.tar.gz http://download.enlightenment.org/releases/elementary-1.0.0-beta.tar.bz2 -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] New EFL release cycle 1.0/1.2/1.6 ALPHA
On Sun, 15 Apr 2012 01:19:12 -0400 Michael Blumenkrantz wrote: > On Sun, 15 Apr 2012 14:15:15 +0900 > Carsten Haitzler (The Rasterman) wrote: > > > On Mon, 2 Apr 2012 19:53:28 -0300 Gustavo Sverzut Barbieri > > said: > > > > here's my take - and i'm fast-forwarding including more comments > > from tom later. > > > > FIRST: > > > > 1. just because it isn't used elsewhere in efl or e atm should NOT > > be a reason for exclusion. if it has a good use case somewhere > > that's more than a one-off, it is a candidate to go in a release. > > 2. we have lots of stuff that is barely tested, so testing is very > > good and needed, but it has never been a necessity. we get to test > > and fix eventually. 3. what matters is the IDEA is sane and the API > > is sane. it won't conflict with other parts of efl (nor or in the > > forseeable future). it can be expanded in future. if we have > > missing things or bugs they can be fixed without creating havoc > > with existing apps using the api. the usual thing here. > > > > NOW: > > > > eina model/value. the reason really tom has is that here are 2 new > > fairly hefty api's with really no "use cases" floating about to see > > other than example files or tests. the rest of the reasoning is > > really just justifying this base. so lets focus on this. > > > > i haven't looked beyond a cursory glance thus i have no deep > > meaningful insights, but let me make an attempt. :) > > > > 1. eina value > > > > * it is heftily documented, so i can't complain. > > * it's pretty darned big. > > * it seems very heavyweight in a c world for holding and dealing > > with "values". it smells like the kind of logic u find in bash or > > perl or other scripting langs where variables are dynamically typed > > - they may be a string, a number, a float etc. and they keep > > shifting type based on how you use them = eg a = b + c ... will > > store the numeric result of b + c... as long as both b and c are > > sanely interpretable numbers (even if both strings- of both are > > strings of numbers etc.). so that's what this looks like to me. > > find - if u are writing a scripting engine this can be useful. > > * could you please go into what eina_value is useful for? what did > > you develop it for? what was the driving reason? > > * other than the above questions it seems pretty sane and > > reasonable. i don't see any problem shipping with it as-is > > (API-wise). i will trust that it has been actually used and tested > > and deployed - we just can't/don't see it (thus why i'm asking you > > to tell us about it :)) > > not to weigh in on either side because I don't really care, but > eina_value has been deployed in esql since january. nobody that I > know of uses esql, but it does work. sometimes. Which might also be used in part of the project I'm writing my scripting engine for. So sometime later this year, I expect there will be two users of esql. That changes my "is it too big" decision though, if it's already being used elsewhere in the project via esql. We shall see when I get around to that part of my project. -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world. signature.asc Description: PGP signature -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] New EFL release cycle 1.0/1.2/1.6 ALPHA
On Sun, 15 Apr 2012 14:15:15 +0900 Carsten Haitzler (The Rasterman) wrote: > On Mon, 2 Apr 2012 19:53:28 -0300 Gustavo Sverzut Barbieri > said: > i haven't looked beyond a cursory glance thus i have no deep > meaningful insights, but let me make an attempt. :) You are one up on me then, I've not even so much as looked in its direction. > 1. eina value > > * it is heftily documented, so i can't complain. > * it's pretty darned big. > * it seems very heavyweight in a c world for holding and dealing with > "values". it smells like the kind of logic u find in bash or perl or > other scripting langs where variables are dynamically typed - they > may be a string, a number, a float etc. and they keep shifting type > based on how you use them = eg a = b + c ... will store the numeric > result of b + c... as long as both b and c are sanely interpretable > numbers (even if both strings- of both are strings of numbers etc.). > so that's what this looks like to me. find - if u are writing a > scripting engine this can be useful. > * could you please go into what eina_value is useful for? what did > you develop it for? what was the driving reason? It just so happens that I am writing a scripting engine, for an existing language. LSL, Linden Scripting Language, as invented by Linden Research for their Second Life virtual world platform. Mines a clean room implementation based on their documentation for LSL. LSL is statically typed, so that heavy weightedness that raster describes would not be good. I would prefer to not use something heavy. On the other hand, my script engine actually converts the LSL to Lua, which IS a dynamically typed language. My code has to deal with the differences between the languages, and also has to deal with a pre existing system written in C#. On the gripping hand, the converted code is acting like LSL, and the variables don't actually change type. Though I am leaving the door open to mixing LSL and Lua in scripts. I may have to deal with dynamic typing. Naturally, since I don't actually implement running of the scripts, just converting them to Lua and let Lua run them, my needs are a lot simpler. I do need to implement the LSL functions though, so sometimes the Lua has to call back into my C. Referencing back to the original LSL script from what Lua hands to the C would be useful, and I would already have structures around for that purpose. So right now, I'm not exactly sure if eina_value, or something like it, would be a good match for my scripting engine. I do intend to check it out though, when I get a chance to get back to that project. If eina_value ends up being a large increase in size for me, then I'll just not use it. Exactly the same as I did for elementary. My scripting engine already has a hand rolled solution, but it's not generic like eina_value would be. "Large increase in size" is relative off course. In this scripting engine project I'm not being as anal about size as I am in my current embedded project. lol -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world. signature.asc Description: PGP signature -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] New EFL release cycle 1.0/1.2/1.6 ALPHA
On Sun, 15 Apr 2012 14:15:15 +0900 Carsten Haitzler (The Rasterman) wrote: > On Mon, 2 Apr 2012 19:53:28 -0300 Gustavo Sverzut Barbieri > said: > > here's my take - and i'm fast-forwarding including more comments from tom > later. > > FIRST: > > 1. just because it isn't used elsewhere in efl or e atm should NOT be a reason > for exclusion. if it has a good use case somewhere that's more than a one-off, > it is a candidate to go in a release. > 2. we have lots of stuff that is barely tested, so testing is very good and > needed, but it has never been a necessity. we get to test and fix eventually. > 3. what matters is the IDEA is sane and the API is sane. it won't conflict > with other parts of efl (nor or in the forseeable future). it can be expanded > in future. if we have missing things or bugs they can be fixed without > creating havoc with existing apps using the api. the usual thing here. > > NOW: > > eina model/value. the reason really tom has is that here are 2 new fairly > hefty api's with really no "use cases" floating about to see other than > example files or tests. the rest of the reasoning is really just justifying > this base. so lets focus on this. > > i haven't looked beyond a cursory glance thus i have no deep meaningful > insights, but let me make an attempt. :) > > 1. eina value > > * it is heftily documented, so i can't complain. > * it's pretty darned big. > * it seems very heavyweight in a c world for holding and dealing with > "values". it smells like the kind of logic u find in bash or perl or other > scripting langs where variables are dynamically typed - they may be a string, > a number, a float etc. and they keep shifting type based on how you use them > = eg a = b + c ... will store the numeric result of b + c... as long as both > b and c are sanely interpretable numbers (even if both strings- of both are > strings of numbers etc.). so that's what this looks like to me. find - if u > are writing a scripting engine this can be useful. > * could you please go into what eina_value is useful for? what did you > develop it for? what was the driving reason? > * other than the above questions it seems pretty sane and reasonable. i don't > see any problem shipping with it as-is (API-wise). i will trust that it has > been actually used and tested and deployed - we just can't/don't see it (thus > why i'm asking you to tell us about it :)) not to weigh in on either side because I don't really care, but eina_value has been deployed in esql since january. nobody that I know of uses esql, but it does work. sometimes. > > 2. eina model > > * this is where i have issues. it is yet another object model or well a very > heavily property-based object model somewhat like gobject, the eobj stuff tom > is working on and so on. > * i think this should be held back from release while we have our object > system wars and work out where everyone fits in. eobj stuff has been now up > for comment/review, but eina_model never got a chance for that before it went > into svn. there is just way too much overlap here that needs to be sorted out. > > simple version: > > eobj does callbacks, referencing, parent/child relationships, generic cata > attache (could be seen as properties but is much simpler) and methods and is > varargs centric to cut down overhead. > > eina model does callbacks, referencing, parent/child relationships and > properties, and is single-call centric keeping call overhead higher. > > there is overlap. properties in eobj are done by methods and private data. > > > Hi all, > > > > I'm bit busy at the moment and can't discuss much details, but a > > summary is that I'd really like it to be available as for now. > > > > To clarify few things: > > > > - Eina_Value: it's gold, really. No idea why it was mixed into Model > > discussion. Value purpose is not dependent on Model, although model > > does use it to exchange properties in a safe way. When designing it > > I've researched how glib and qt does that, we could do more with > > optimized handling for arrays. > > > > - Eina_Model: although test coverage is not 100%, it does come with > > much more test than the average code in SVN. ProFUSION is using it for > > customers code without issue, mostly to abstract data access to DB. > > All in all I'm satisfied with the API for MODEL (DATA) usage. > > > > - during Eina_Model development, I create the Interface concept, with > > multiple interfaces per type, and interfaces could extend multiple > > interfaces. But the implementation (internals) assumed for MODEL > > (data) the common case is not to have multiple INDEPENDENT interfaces > > to implement the same, thus I implemented the interface lookups in a > > naive way. THIS is marked in code for future improvements. > > http://trac.enlightenment.org/e/browser/trunk/eina/src/lib/eina_model.c#L524 > > Again, this is an internal issue and can be fixed without changing > > API or ABI. The only synthetic example tha
Re: [E-devel] New EFL release cycle 1.0/1.2/1.6 ALPHA
On Mon, 2 Apr 2012 19:53:28 -0300 Gustavo Sverzut Barbieri said: here's my take - and i'm fast-forwarding including more comments from tom later. FIRST: 1. just because it isn't used elsewhere in efl or e atm should NOT be a reason for exclusion. if it has a good use case somewhere that's more than a one-off, it is a candidate to go in a release. 2. we have lots of stuff that is barely tested, so testing is very good and needed, but it has never been a necessity. we get to test and fix eventually. 3. what matters is the IDEA is sane and the API is sane. it won't conflict with other parts of efl (nor or in the forseeable future). it can be expanded in future. if we have missing things or bugs they can be fixed without creating havoc with existing apps using the api. the usual thing here. NOW: eina model/value. the reason really tom has is that here are 2 new fairly hefty api's with really no "use cases" floating about to see other than example files or tests. the rest of the reasoning is really just justifying this base. so lets focus on this. i haven't looked beyond a cursory glance thus i have no deep meaningful insights, but let me make an attempt. :) 1. eina value * it is heftily documented, so i can't complain. * it's pretty darned big. * it seems very heavyweight in a c world for holding and dealing with "values". it smells like the kind of logic u find in bash or perl or other scripting langs where variables are dynamically typed - they may be a string, a number, a float etc. and they keep shifting type based on how you use them = eg a = b + c ... will store the numeric result of b + c... as long as both b and c are sanely interpretable numbers (even if both strings- of both are strings of numbers etc.). so that's what this looks like to me. find - if u are writing a scripting engine this can be useful. * could you please go into what eina_value is useful for? what did you develop it for? what was the driving reason? * other than the above questions it seems pretty sane and reasonable. i don't see any problem shipping with it as-is (API-wise). i will trust that it has been actually used and tested and deployed - we just can't/don't see it (thus why i'm asking you to tell us about it :)) 2. eina model * this is where i have issues. it is yet another object model or well a very heavily property-based object model somewhat like gobject, the eobj stuff tom is working on and so on. * i think this should be held back from release while we have our object system wars and work out where everyone fits in. eobj stuff has been now up for comment/review, but eina_model never got a chance for that before it went into svn. there is just way too much overlap here that needs to be sorted out. simple version: eobj does callbacks, referencing, parent/child relationships, generic cata attache (could be seen as properties but is much simpler) and methods and is varargs centric to cut down overhead. eina model does callbacks, referencing, parent/child relationships and properties, and is single-call centric keeping call overhead higher. there is overlap. properties in eobj are done by methods and private data. > Hi all, > > I'm bit busy at the moment and can't discuss much details, but a > summary is that I'd really like it to be available as for now. > > To clarify few things: > > - Eina_Value: it's gold, really. No idea why it was mixed into Model > discussion. Value purpose is not dependent on Model, although model > does use it to exchange properties in a safe way. When designing it > I've researched how glib and qt does that, we could do more with > optimized handling for arrays. > > - Eina_Model: although test coverage is not 100%, it does come with > much more test than the average code in SVN. ProFUSION is using it for > customers code without issue, mostly to abstract data access to DB. > All in all I'm satisfied with the API for MODEL (DATA) usage. > > - during Eina_Model development, I create the Interface concept, with > multiple interfaces per type, and interfaces could extend multiple > interfaces. But the implementation (internals) assumed for MODEL > (data) the common case is not to have multiple INDEPENDENT interfaces > to implement the same, thus I implemented the interface lookups in a > naive way. THIS is marked in code for future improvements. > http://trac.enlightenment.org/e/browser/trunk/eina/src/lib/eina_model.c#L524 > Again, this is an internal issue and can be fixed without changing > API or ABI. The only synthetic example that exposes this behavior is > hard. This is example eina_model_04 in SVN, and the "fix" was to force > an unneeded dependency between interfaces. > > - python, which uses the same object implementation for everything, > used a similar naive implementation for almost 10 years before > changing it. > > - the fix for the above problem is suggested in the TODO, it's about > changing the algorithm that sorts the dependencies to consider initial
Re: [E-devel] New EFL release cycle 1.0/1.2/1.6 ALPHA
Dear Gustavo, As I said in IRC yesterday: my intention is *not* to insult you or your code in any way. Whatever I said here is general and could have been applied to anyone's code. If I insulted you, I'm sorry. Now for my comments. On 03/04/12 17:58, Gustavo Sverzut Barbieri wrote: > Discomfitor played with it, as far as I remember he liked its usage in esql. > > The code is stupidly simple and my major concern was with memory usage > and speed. Both were addressed nicely, we can handle structures and > arrays in a fast and space efficient way. > > Its purpose is clear: hold a generic typed value. Then it keeps the > value memory and the pointer to its operations. The operations were > added based on other languages and toolkits. They cover copy, compare > and convert, aside from basic set and get. > As I said, I'm against untested/reviewed/played with API. If this code was indeed tested, played with and "approved" by discomiftor, it's fine. Lets focus our discussion on eina_model then. > What API? It's a model. Composed of named (string) properties with > generic values (strong typed with Eina_Value). Children is a sequence > of other Eina_Model. > > The API clearly reflects that. They are clearly defined at: > > > http://docs.enlightenment.org/auto/eina/group__Eina__Model__Properties__Group.html > > http://docs.enlightenment.org/auto/eina/group__Eina__Model__Children__Group.html > > Other than that, it comes with common use cases in an easy to use way, > like filtering items, searching, sorting and iterating. All of them > based on real world use cases. > > There are default implementations for these using super-generic array > + hash, and efficient array + struct. One is able to override the > operations in order to optimize use-cases, such as talking directly > with DB, or abstract an already existing in-memory data structure. > > The focus is on how to use the common model access. The properties and > children listed above. Do you see anything wrong with them? > > The inheritance and all is a nice thing that came and I exposed them, > but they should not be the focus. They look good in my point of view, > nobody could spot a problem with them, but the inheritance is > secondary to the model usage as a consumer. I haven't played with properties or children enough to comment on them, and that's the problem. :) Also, if the inheritance stuff are not the important part, why are they so heavily exposed and make a big part of the API? > > > Indeed we did had this model thing for a while (since 2008), but the > eina version was written based on real world requirements from > scratch. Then we're not just releasing our code, we did plan it to > benefit everybody. > > I can't get your points of "What's the rush?" I'm not rushing it, it's > there in SVN for a while (+2 months) and I'm just following the EFL > standards of having things on trunk for testing. Raster himself > believes this is the only way to get things tested, so I did it. > Should it go in a branch? There are not branches for other work AFAIK. Yeah, that's what raster thinks is right (me as well), but it depends on the code actually being reviewed and not just sitting there without any attention. I'm not saying it should go in a branch, just "disabled" for the *current* efl release and re-activated and discussed right afterwards. Rush: as I said, I don't think there's any urgent need of that, so getting that in although it was not tested (API) enough is rushing. > > > Could you list the real world example? The eina_model_04 is not a real > world example of DATA model as far as I understand it. Could you > present us with such example? > > Also, the "forced unneeded dep" will still work in future. It will not > be required anymore, but it will still work if that's what concerns > you. > > I fail to see how it breaks API or ABI. The same code will work. Let's > say now there are undefined behaviors, that can be defined later. > POSIX libc is full of such. I take your point there, it doesn't break API, it just encourages abusing the API. Real world example: you want to override the child_set function of the Children interface to filter forbidden children, for example... It's just function overriding for interfaces, it's common. > > > Uh? You gave python as an example of a project that got stuck with API they didn't like for ages and that they changed it after a long while. I said that we wouldn't want to repeat their errors. > Yes, but the existing code still works :-) You were relying on an > undefined behavior by current means. It may be defined later IMO. > > All in all the code is simple to write and can be done. But should we? Yes, but this specific piece of code (without that unneeded dep) will change behaviour and not work after you fix it. You can argue that whoever wrote that code was relying on undefined behaviour, and I'll claim accordingly that we haven't "explored" eina_model enough to know w
Re: [E-devel] New EFL release cycle 1.0/1.2/1.6 ALPHA
On Tue, Apr 3, 2012 at 7:23 AM, Tom Hacohen wrote:
> On 03/04/12 01:53, Gustavo Sverzut Barbieri wrote:
>>
>> To clarify few things:
>>
>> - Eina_Value: it's gold, really. No idea why it was mixed into Model
>> discussion. Value purpose is not dependent on Model, although model
>> does use it to exchange properties in a safe way. When designing it
>> I've researched how glib and qt does that, we could do more with
>> optimized handling for arrays.
>
>
> As I said before, I haven't tested eina_value, I really don't know about
> this one, and that's my problem with it. I don't feel it was tested enough
> (API + code). Perhaps it's ready for prime-time, but without people actually
> playing with it, and real code in EFL actually benefiting from it, it's just
> too hard to know.
Discomfitor played with it, as far as I remember he liked its usage in esql.
The code is stupidly simple and my major concern was with memory usage
and speed. Both were addressed nicely, we can handle structures and
arrays in a fast and space efficient way.
Its purpose is clear: hold a generic typed value. Then it keeps the
value memory and the pointer to its operations. The operations were
added based on other languages and toolkits. They cover copy, compare
and convert, aside from basic set and get.
>> - Eina_Model: although test coverage is not 100%, it does come with
>> much more test than the average code in SVN. ProFUSION is using it for
>> customers code without issue, mostly to abstract data access to DB.
>> All in all I'm satisfied with the API for MODEL (DATA) usage.
>
>
> As I said, it's not just about test coverage, it's about API's validity. I
> just don't think we want to "get stuck" with this API for ages without
> testing it before.
What API? It's a model. Composed of named (string) properties with
generic values (strong typed with Eina_Value). Children is a sequence
of other Eina_Model.
The API clearly reflects that. They are clearly defined at:
http://docs.enlightenment.org/auto/eina/group__Eina__Model__Properties__Group.html
http://docs.enlightenment.org/auto/eina/group__Eina__Model__Children__Group.html
Other than that, it comes with common use cases in an easy to use way,
like filtering items, searching, sorting and iterating. All of them
based on real world use cases.
There are default implementations for these using super-generic array
+ hash, and efficient array + struct. One is able to override the
operations in order to optimize use-cases, such as talking directly
with DB, or abstract an already existing in-memory data structure.
The focus is on how to use the common model access. The properties and
children listed above. Do you see anything wrong with them?
The inheritance and all is a nice thing that came and I exposed them,
but they should not be the focus. They look good in my point of view,
nobody could spot a problem with them, but the inheritance is
secondary to the model usage as a consumer.
> What's the rush? really? We don't depend on it anywhere inside of EFL, so
> there's no real reason to rush it into our release. You can just create a
> profusion lib with the same symbol names and headers and just migrate to
> eina when it's ready and in the next release (if we find it fit then).
Indeed we did had this model thing for a while (since 2008), but the
eina version was written based on real world requirements from
scratch. Then we're not just releasing our code, we did plan it to
benefit everybody.
I can't get your points of "What's the rush?" I'm not rushing it, it's
there in SVN for a while (+2 months) and I'm just following the EFL
standards of having things on trunk for testing. Raster himself
believes this is the only way to get things tested, so I did it.
Should it go in a branch? There are not branches for other work AFAIK.
>> - during Eina_Model development, I create the Interface concept, with
>> multiple interfaces per type, and interfaces could extend multiple
>> interfaces. But the implementation (internals) assumed for MODEL
>> (data) the common case is not to have multiple INDEPENDENT interfaces
>> to implement the same, thus I implemented the interface lookups in a
>> naive way. THIS is marked in code for future improvements.
>>
>> http://trac.enlightenment.org/e/browser/trunk/eina/src/lib/eina_model.c#L524
>> Again, this is an internal issue and can be fixed without changing
>> API or ABI. The only synthetic example that exposes this behavior is
>> hard. This is example eina_model_04 in SVN, and the "fix" was to force
>> an unneeded dependency between interfaces.
>
>
> My example is not synthetic, I stumbled across it in a *real life* example I
> was implementing. And it *DOES* break API/ABI. While the functions may
> remain the same (uncertain) their behaviour is changed, and as you said
> yourself, actual usage ("force an unneeded dep") will change.
>
> Also, this is the tip of the iceberg, we don't know what else lies beneath.
Could you list the
Re: [E-devel] New EFL release cycle 1.0/1.2/1.6 ALPHA
On 03/04/12 01:53, Gustavo Sverzut Barbieri wrote:
> To clarify few things:
>
> - Eina_Value: it's gold, really. No idea why it was mixed into Model
> discussion. Value purpose is not dependent on Model, although model
> does use it to exchange properties in a safe way. When designing it
> I've researched how glib and qt does that, we could do more with
> optimized handling for arrays.
As I said before, I haven't tested eina_value, I really don't know about
this one, and that's my problem with it. I don't feel it was tested
enough (API + code). Perhaps it's ready for prime-time, but without
people actually playing with it, and real code in EFL actually
benefiting from it, it's just too hard to know.
>
> - Eina_Model: although test coverage is not 100%, it does come with
> much more test than the average code in SVN. ProFUSION is using it for
> customers code without issue, mostly to abstract data access to DB.
> All in all I'm satisfied with the API for MODEL (DATA) usage.
As I said, it's not just about test coverage, it's about API's validity.
I just don't think we want to "get stuck" with this API for ages without
testing it before.
What's the rush? really? We don't depend on it anywhere inside of EFL,
so there's no real reason to rush it into our release. You can just
create a profusion lib with the same symbol names and headers and just
migrate to eina when it's ready and in the next release (if we find it
fit then).
>
> - during Eina_Model development, I create the Interface concept, with
> multiple interfaces per type, and interfaces could extend multiple
> interfaces. But the implementation (internals) assumed for MODEL
> (data) the common case is not to have multiple INDEPENDENT interfaces
> to implement the same, thus I implemented the interface lookups in a
> naive way. THIS is marked in code for future improvements.
> http://trac.enlightenment.org/e/browser/trunk/eina/src/lib/eina_model.c#L524
> Again, this is an internal issue and can be fixed without changing
> API or ABI. The only synthetic example that exposes this behavior is
> hard. This is example eina_model_04 in SVN, and the "fix" was to force
> an unneeded dependency between interfaces.
My example is not synthetic, I stumbled across it in a *real life*
example I was implementing. And it *DOES* break API/ABI. While the
functions may remain the same (uncertain) their behaviour is changed,
and as you said yourself, actual usage ("force an unneeded dep") will
change.
Also, this is the tip of the iceberg, we don't know what else lies beneath.
>
> - python, which uses the same object implementation for everything,
> used a similar naive implementation for almost 10 years before
> changing it.
So are you suggesting we should lock ourself to one flawed design just
because others have done the same in the past?
>
> - the fix for the above problem is suggested in the TODO, it's about
> changing the algorithm that sorts the dependencies to consider initial
> ordering as well when pulling the roots of topological sort.
Which changes the behaviour!!!
>
> - interfaces for models/data is more to help people to override a
> single part without having to do much work. For example the sole usage
> of it now is to independently handle properties and children.
But people may have other uses (as shown in my example).
>
> - aside from interfaces exceptional corner cases, I did not see any
> other relevant comment to Model;
Because it was not tested enough. But as I said, there are some other
things that are wrong in the API. I'm 100% sure I've told you about them
in IRC, but maybe also in mail. It's still rough.
>
> - I don't consider the code to be rushed in, as it's in SVN for more
> than 2 months. It went through reviews, documentation, examples and is
> being used in our projects without issues (the found issues were fixed
> in SVN).
It is rushing, I say there are flaws, you admit there are some flaws,
but still we are trying to get it in. Time it has been in svn has little
relevance to this, it's the amount of review it got that matters.
>
> - Removing it because it's not in use is chicken-egg. It will not be
> used if it does not exist. As I said I'm bit busy to code right now,
> but I would use Eina_Model to implement, at least (no particular
> order):
> * SQL loader in esql;
> * Eet loader and saver;
> * Eio browser;
> * Enjoy, allowing plugins to provide backend-independent data (SQL
> as now, but also FS or network/last.fm).
> * Elementary to provide views (genlist/grid variants);
> * Python: to let Python objects be used by C code
> implementing/using Eina_Model.
EFL is released in sync, we can implement it in eina and add it to all
of the above while in svn, like we do with all other features. That's
hardly an excuse...
>
> - I'm bit sad to see that knowing your code is not perfect and
> flagging it with TODO to help others is seen as a bad thing. I always
> m
Re: [E-devel] New EFL release cycle 1.0/1.2/1.6 ALPHA
Hi all, I'm bit busy at the moment and can't discuss much details, but a summary is that I'd really like it to be available as for now. To clarify few things: - Eina_Value: it's gold, really. No idea why it was mixed into Model discussion. Value purpose is not dependent on Model, although model does use it to exchange properties in a safe way. When designing it I've researched how glib and qt does that, we could do more with optimized handling for arrays. - Eina_Model: although test coverage is not 100%, it does come with much more test than the average code in SVN. ProFUSION is using it for customers code without issue, mostly to abstract data access to DB. All in all I'm satisfied with the API for MODEL (DATA) usage. - during Eina_Model development, I create the Interface concept, with multiple interfaces per type, and interfaces could extend multiple interfaces. But the implementation (internals) assumed for MODEL (data) the common case is not to have multiple INDEPENDENT interfaces to implement the same, thus I implemented the interface lookups in a naive way. THIS is marked in code for future improvements. http://trac.enlightenment.org/e/browser/trunk/eina/src/lib/eina_model.c#L524 Again, this is an internal issue and can be fixed without changing API or ABI. The only synthetic example that exposes this behavior is hard. This is example eina_model_04 in SVN, and the "fix" was to force an unneeded dependency between interfaces. - python, which uses the same object implementation for everything, used a similar naive implementation for almost 10 years before changing it. - the fix for the above problem is suggested in the TODO, it's about changing the algorithm that sorts the dependencies to consider initial ordering as well when pulling the roots of topological sort. - interfaces for models/data is more to help people to override a single part without having to do much work. For example the sole usage of it now is to independently handle properties and children. - aside from interfaces exceptional corner cases, I did not see any other relevant comment to Model; - I don't consider the code to be rushed in, as it's in SVN for more than 2 months. It went through reviews, documentation, examples and is being used in our projects without issues (the found issues were fixed in SVN). - Removing it because it's not in use is chicken-egg. It will not be used if it does not exist. As I said I'm bit busy to code right now, but I would use Eina_Model to implement, at least (no particular order): * SQL loader in esql; * Eet loader and saver; * Eio browser; * Enjoy, allowing plugins to provide backend-independent data (SQL as now, but also FS or network/last.fm). * Elementary to provide views (genlist/grid variants); * Python: to let Python objects be used by C code implementing/using Eina_Model. - I'm bit sad to see that knowing your code is not perfect and flagging it with TODO to help others is seen as a bad thing. I always marked like that, while others just omit those. I don't see why it would make it a blocker for inclusion. Again, this code is intended to map data in a common protocol so we reduce code duplication everywhere. It is based on properties and children. It does events signaling to notify of changes. It does reference counting as multiple views may hold the data. And for these cases I really fail to see how it's broken, badly designed or with flaws. What does seems to happen is a confusion with general objects. This is not general object. Don't expect Evas_Object to be converted to Eina_Model because it has nothing to do. What you should expect is every data provider to talk this API and suddenly you could show a list of something in Elementary without effort. []s -- Gustavo On Mon, Apr 2, 2012 at 4:03 AM, Tom Hacohen wrote: > > On 02/04/12 05:39, Carsten Haitzler (The Rasterman) wrote: > > i was hoping/expecting gustavo to appear in this thread and make his > > case. > > > > He's probably unavailable atm. Anyhow, the most important point I raised > is the last one. Given that *nothing* in the efl uses it, why are we > trying to rush it in? -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -- MSN: barbi...@gmail.com Skype: gsbarbieri Mobile: +55 (19) 9225-2202 -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] New EFL release cycle 1.0/1.2/1.6 ALPHA
On 02/04/12 05:39, Carsten Haitzler (The Rasterman) wrote: > i was hoping/expecting gustavo to appear in this thread and make his case. > He's probably unavailable atm. Anyhow, the most important point I raised is the last one. Given that *nothing* in the efl uses it, why are we trying to rush it in? -- Tom. -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] New EFL release cycle 1.0/1.2/1.6 ALPHA
On Mon, 2 Apr 2012 11:39:55 +0900 Carsten Haitzler (The Rasterman) wrote: > On Sun, 01 Apr 2012 18:30:30 +0300 Tom Hacohen > said: > > > On 01/04/12 18:06, Carsten Haitzler (The Rasterman) wrote: > > > gustavo seems to very much disagree :) > > > > Gustavo has his own motives... Though for real, we discussed about > > it in IRC (he and I) and I pointed out some API flaws I found just > > by playing with the API. I'm not saying it's awful and should never > > get in, I'm just saying it's not ready atm. It needs more review, > > more playing time and more usage. And heck, some unit tests... > > > > Even now there are some FIXME in the code about changing API (e.g: > > order of calling of interface functions with interface inheritance). > > > > Also, it's not really needed by anything in the EFL at the moment, > > so there really is no need to rush it in. I would have understood > > the need for rushing if it was a blocker for something, but it's > > not, it's just a random feature... > > i was hoping/expecting gustavo to appear in this thread and make his > case. It's the sort of thing I might want to use, but have not poked at yet. If I'm gonna use it, it would have to be really really good. So unless there is a pressing urgency to get it out right now, I'd leave it to be polished. -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world. signature.asc Description: PGP signature -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] New EFL release cycle 1.0/1.2/1.6 ALPHA
On Sun, 01 Apr 2012 18:30:30 +0300 Tom Hacohen said: > On 01/04/12 18:06, Carsten Haitzler (The Rasterman) wrote: > > gustavo seems to very much disagree :) > > Gustavo has his own motives... Though for real, we discussed about it in > IRC (he and I) and I pointed out some API flaws I found just by playing > with the API. I'm not saying it's awful and should never get in, I'm > just saying it's not ready atm. It needs more review, more playing time > and more usage. And heck, some unit tests... > > Even now there are some FIXME in the code about changing API (e.g: order > of calling of interface functions with interface inheritance). > > Also, it's not really needed by anything in the EFL at the moment, so > there really is no need to rush it in. I would have understood the need > for rushing if it was a blocker for something, but it's not, it's just a > random feature... i was hoping/expecting gustavo to appear in this thread and make his case. -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] New EFL release cycle 1.0/1.2/1.6 ALPHA
On Sun, Apr 1, 2012 at 5:30 PM, Tom Hacohen wrote: > On 01/04/12 18:06, Carsten Haitzler (The Rasterman) wrote: >> gustavo seems to very much disagree :) > > Gustavo has his own motives... Though for real, we discussed about it in > IRC (he and I) and I pointed out some API flaws I found just by playing > with the API. I'm not saying it's awful and should never get in, I'm > just saying it's not ready atm. It needs more review, more playing time > and more usage. And heck, some unit tests... > > Even now there are some FIXME in the code about changing API (e.g: order > of calling of interface functions with interface inheritance). > > Also, it's not really needed by anything in the EFL at the moment, so > there really is no need to rush it in. I would have understood the need > for rushing if it was a blocker for something, but it's not, it's just a > random feature... if there's plans to change API, then I agree with Tom, it must be postponed. Vincent -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] New EFL release cycle 1.0/1.2/1.6 ALPHA
On 01/04/12 18:06, Carsten Haitzler (The Rasterman) wrote: > gustavo seems to very much disagree :) Gustavo has his own motives... Though for real, we discussed about it in IRC (he and I) and I pointed out some API flaws I found just by playing with the API. I'm not saying it's awful and should never get in, I'm just saying it's not ready atm. It needs more review, more playing time and more usage. And heck, some unit tests... Even now there are some FIXME in the code about changing API (e.g: order of calling of interface functions with interface inheritance). Also, it's not really needed by anything in the EFL at the moment, so there really is no need to rush it in. I would have understood the need for rushing if it was a blocker for something, but it's not, it's just a random feature... -- Tom. -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] New EFL release cycle 1.0/1.2/1.6 ALPHA
On Sun, 01 Apr 2012 15:29:19 +0300 Tom Hacohen said: gustavo seems to very much disagree :) > Hey raster, > > I didn't check if you removed them or not, but a reminder: > In my point of view, eina_model/value are not ready for 1.2. They need > better review and more people using them. > > I've already discussed this with a couple of people on IRC (including > yourself ;P). > > Just wanted to make sure it's removed/disabled before release (and added > back right after, probably). > > -- > Tom. > > On 24/03/12 05:40, Carsten Haitzler (The Rasterman) wrote: > > We'd like to announce a new release cycle alpha release of several > > Enlightenment components. This round we have added Eio, Ethumb, Emotion and > > Elementary. > > > > Emotion is a library to handle video playback using Gstreamer, Xine or other > > external plugins (VLC) and display video in Evas as a standard object. It > > also can handle audio playback too. Eio is here to support Emotion with > > async IO API's. > > > > Ethumb is a thumbnail generator library that supports the freedesktop.org > > thumbnailing standards, and is implemented as a dbus service and a > > client-side library that handles dealing with that service for you. > > > > Elementary is our new widget set, built on top of the rest of EFL, to > > provide you with standard widgets and behaviour to make it easy to write GUI > > applications. > > > > Eina 1.2.0 - > > http://download.enlightenment.org/releases/eina-1.2.0-alpha.tar.gz > > http://download.enlightenment.org/releases/eina-1.2.0-alpha.tar.bz2 > > > > Eet 1.6.0 - > > http://download.enlightenment.org/releases/eet-1.6.0-alpha.tar.gz > > http://download.enlightenment.org/releases/eet-1.6.0-alpha.tar.bz2 > > > > Evas 1.2.0 - > > http://download.enlightenment.org/releases/evas-1.2.0-alpha.tar.gz > > http://download.enlightenment.org/releases/evas-1.2.0-alpha.tar.bz2 > > > > Ecore 1.2.0 - > > http://download.enlightenment.org/releases/ecore-1.2.0-alpha.tar.gz > > http://download.enlightenment.org/releases/ecore-1.2.0-alpha.tar.bz2 > > > > Embryo 1.2.0 - > > http://download.enlightenment.org/releases/embryo-1.2.0-alpha.tar.gz > > http://download.enlightenment.org/releases/embryo-1.2.0-alpha.tar.bz2 > > > > Edje 1.2.0 - > > http://download.enlightenment.org/releases/edje-1.2.0-alpha.tar.gz > > http://download.enlightenment.org/releases/edje-1.2.0-alpha.tar.bz2 > > > > Efreet 1.2.0 - > > http://download.enlightenment.org/releases/efreet-1.2.0-alpha.tar.gz > > http://download.enlightenment.org/releases/efreet-1.2.0-alpha.tar.bz2 > > > > E_dbus 1.2.0 - > > http://download.enlightenment.org/releases/e_dbus-1.2.0-alpha.tar.gz > > http://download.enlightenment.org/releases/e_dbus-1.2.0-alpha.tar.bz2 > > > > Eeze 1.2.0 - > > http://download.enlightenment.org/releases/eeze-1.2.0-alpha.tar.gz > > http://download.enlightenment.org/releases/eeze-1.2.0-alpha.tar.bz2 > > > > Expedite 1.2.0 - > > http://download.enlightenment.org/releases/expedite-1.2.0-alpha.tar.gz > > http://download.enlightenment.org/releases/expedite-1.2.0-alpha.tar.bz2 > > > > Evas Generic Loaders 1.2.0 - > > http://download.enlightenment.org/releases/evas_generic_loaders-1.2.0-alpha.tar.gz > > http://download.enlightenment.org/releases/evas_generic_loaders-1.2.0-alpha.tar.bz2 > > > > Eio 1.0.0 - > > http://download.enlightenment.org/releases/eio-1.0.0-alpha.tar.gz > > http://download.enlightenment.org/releases/eio-1.0.0-alpha.tar.bz2 > > > > Emotion 1.0.0 - > > http://download.enlightenment.org/releases/emotion-1.0.0-alpha.tar.gz > > http://download.enlightenment.org/releases/emotion-1.0.0-alpha.tar.bz2 > > > > Ethumb 1.0.0 - > > http://download.enlightenment.org/releases/ethumb-1.0.0-alpha.tar.gz > > http://download.enlightenment.org/releases/ethumb-1.0.0-alpha.tar.bz2 > > > > Elementary 1.0.0 - > > http://download.enlightenment.org/releases/elementary-1.0.0-alpha.tar.gz > > http://download.enlightenment.org/releases/elementary-1.0.0-alpha.tar.bz2 > > > > > -- > This SF email is sponsosred by: > Try Windows Azure free for 90 days Click Here > http://p.sf.net/sfu/sfd2d-msazure > ___ > 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)ras...@rasterman.com -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] New EFL release cycle 1.0/1.2/1.6 ALPHA
Hey raster, I didn't check if you removed them or not, but a reminder: In my point of view, eina_model/value are not ready for 1.2. They need better review and more people using them. I've already discussed this with a couple of people on IRC (including yourself ;P). Just wanted to make sure it's removed/disabled before release (and added back right after, probably). -- Tom. On 24/03/12 05:40, Carsten Haitzler (The Rasterman) wrote: > We'd like to announce a new release cycle alpha release of several > Enlightenment components. This round we have added Eio, Ethumb, Emotion and > Elementary. > > Emotion is a library to handle video playback using Gstreamer, Xine or other > external plugins (VLC) and display video in Evas as a standard object. It also > can handle audio playback too. Eio is here to support Emotion with async IO > API's. > > Ethumb is a thumbnail generator library that supports the freedesktop.org > thumbnailing standards, and is implemented as a dbus service and a client-side > library that handles dealing with that service for you. > > Elementary is our new widget set, built on top of the rest of EFL, to provide > you with standard widgets and behaviour to make it easy to write GUI > applications. > > Eina 1.2.0 - > http://download.enlightenment.org/releases/eina-1.2.0-alpha.tar.gz > http://download.enlightenment.org/releases/eina-1.2.0-alpha.tar.bz2 > > Eet 1.6.0 - > http://download.enlightenment.org/releases/eet-1.6.0-alpha.tar.gz > http://download.enlightenment.org/releases/eet-1.6.0-alpha.tar.bz2 > > Evas 1.2.0 - > http://download.enlightenment.org/releases/evas-1.2.0-alpha.tar.gz > http://download.enlightenment.org/releases/evas-1.2.0-alpha.tar.bz2 > > Ecore 1.2.0 - > http://download.enlightenment.org/releases/ecore-1.2.0-alpha.tar.gz > http://download.enlightenment.org/releases/ecore-1.2.0-alpha.tar.bz2 > > Embryo 1.2.0 - > http://download.enlightenment.org/releases/embryo-1.2.0-alpha.tar.gz > http://download.enlightenment.org/releases/embryo-1.2.0-alpha.tar.bz2 > > Edje 1.2.0 - > http://download.enlightenment.org/releases/edje-1.2.0-alpha.tar.gz > http://download.enlightenment.org/releases/edje-1.2.0-alpha.tar.bz2 > > Efreet 1.2.0 - > http://download.enlightenment.org/releases/efreet-1.2.0-alpha.tar.gz > http://download.enlightenment.org/releases/efreet-1.2.0-alpha.tar.bz2 > > E_dbus 1.2.0 - > http://download.enlightenment.org/releases/e_dbus-1.2.0-alpha.tar.gz > http://download.enlightenment.org/releases/e_dbus-1.2.0-alpha.tar.bz2 > > Eeze 1.2.0 - > http://download.enlightenment.org/releases/eeze-1.2.0-alpha.tar.gz > http://download.enlightenment.org/releases/eeze-1.2.0-alpha.tar.bz2 > > Expedite 1.2.0 - > http://download.enlightenment.org/releases/expedite-1.2.0-alpha.tar.gz > http://download.enlightenment.org/releases/expedite-1.2.0-alpha.tar.bz2 > > Evas Generic Loaders 1.2.0 - > http://download.enlightenment.org/releases/evas_generic_loaders-1.2.0-alpha.tar.gz > http://download.enlightenment.org/releases/evas_generic_loaders-1.2.0-alpha.tar.bz2 > > Eio 1.0.0 - > http://download.enlightenment.org/releases/eio-1.0.0-alpha.tar.gz > http://download.enlightenment.org/releases/eio-1.0.0-alpha.tar.bz2 > > Emotion 1.0.0 - > http://download.enlightenment.org/releases/emotion-1.0.0-alpha.tar.gz > http://download.enlightenment.org/releases/emotion-1.0.0-alpha.tar.bz2 > > Ethumb 1.0.0 - > http://download.enlightenment.org/releases/ethumb-1.0.0-alpha.tar.gz > http://download.enlightenment.org/releases/ethumb-1.0.0-alpha.tar.bz2 > > Elementary 1.0.0 - > http://download.enlightenment.org/releases/elementary-1.0.0-alpha.tar.gz > http://download.enlightenment.org/releases/elementary-1.0.0-alpha.tar.bz2 > -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] New EFL release cycle 1.0/1.2/1.6 ALPHA
On Sat, Mar 24, 2012 at 10:56 AM, Vincent Torri wrote: > currently, for the Windows port, here are the libraries that I > maintain and are working for me (XP, 32 bits): > > evil, eina, eet, evas, ecore, embryo, edje and elementary (add also expedite). > > I know that i had run emotion with gst backend before eio integration. > eio is not currently compiling on Windows. So no emotion on Windows > (word play : ) ) Eio is optional for emotion. It fallback to eina directly if eio is not available. At least the code is in for that purpose, maybe it's not much tested. > help is always welcome :) I have done the first step, installing a windows virtual machine... -- Cedric BAIL -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] New EFL release cycle 1.0/1.2/1.6 ALPHA
Hey currently, for the Windows port, here are the libraries that I maintain and are working for me (XP, 32 bits): evil, eina, eet, evas, ecore, embryo, edje and elementary (add also expedite). I know that i had run emotion with gst backend before eio integration. eio is not currently compiling on Windows. So no emotion on Windows (word play : ) ) About Ethumb, it depends on e_dbus, which depends on dbus. Currently, i didn' succeed in making dbus working on Windows (it's compiling, though) And efreet is not really something that runs on Windows (though i alreday made it work to detect Tango icons set). I'm not sure that I have to support it. Suggestions are welcome wrt that library. I don't think I will be able to find time to make them working on Windows before the release. help is always welcome :) Vincent On Sat, Mar 24, 2012 at 4:40 AM, Carsten Haitzler wrote: > We'd like to announce a new release cycle alpha release of several > Enlightenment components. This round we have added Eio, Ethumb, Emotion and > Elementary. > > Emotion is a library to handle video playback using Gstreamer, Xine or other > external plugins (VLC) and display video in Evas as a standard object. It also > can handle audio playback too. Eio is here to support Emotion with async IO > API's. > > Ethumb is a thumbnail generator library that supports the freedesktop.org > thumbnailing standards, and is implemented as a dbus service and a client-side > library that handles dealing with that service for you. > > Elementary is our new widget set, built on top of the rest of EFL, to provide > you with standard widgets and behaviour to make it easy to write GUI > applications. > > Eina 1.2.0 - > http://download.enlightenment.org/releases/eina-1.2.0-alpha.tar.gz > http://download.enlightenment.org/releases/eina-1.2.0-alpha.tar.bz2 > > Eet 1.6.0 - > http://download.enlightenment.org/releases/eet-1.6.0-alpha.tar.gz > http://download.enlightenment.org/releases/eet-1.6.0-alpha.tar.bz2 > > Evas 1.2.0 - > http://download.enlightenment.org/releases/evas-1.2.0-alpha.tar.gz > http://download.enlightenment.org/releases/evas-1.2.0-alpha.tar.bz2 > > Ecore 1.2.0 - > http://download.enlightenment.org/releases/ecore-1.2.0-alpha.tar.gz > http://download.enlightenment.org/releases/ecore-1.2.0-alpha.tar.bz2 > > Embryo 1.2.0 - > http://download.enlightenment.org/releases/embryo-1.2.0-alpha.tar.gz > http://download.enlightenment.org/releases/embryo-1.2.0-alpha.tar.bz2 > > Edje 1.2.0 - > http://download.enlightenment.org/releases/edje-1.2.0-alpha.tar.gz > http://download.enlightenment.org/releases/edje-1.2.0-alpha.tar.bz2 > > Efreet 1.2.0 - > http://download.enlightenment.org/releases/efreet-1.2.0-alpha.tar.gz > http://download.enlightenment.org/releases/efreet-1.2.0-alpha.tar.bz2 > > E_dbus 1.2.0 - > http://download.enlightenment.org/releases/e_dbus-1.2.0-alpha.tar.gz > http://download.enlightenment.org/releases/e_dbus-1.2.0-alpha.tar.bz2 > > Eeze 1.2.0 - > http://download.enlightenment.org/releases/eeze-1.2.0-alpha.tar.gz > http://download.enlightenment.org/releases/eeze-1.2.0-alpha.tar.bz2 > > Expedite 1.2.0 - > http://download.enlightenment.org/releases/expedite-1.2.0-alpha.tar.gz > http://download.enlightenment.org/releases/expedite-1.2.0-alpha.tar.bz2 > > Evas Generic Loaders 1.2.0 - > http://download.enlightenment.org/releases/evas_generic_loaders-1.2.0-alpha.tar.gz > http://download.enlightenment.org/releases/evas_generic_loaders-1.2.0-alpha.tar.bz2 > > Eio 1.0.0 - > http://download.enlightenment.org/releases/eio-1.0.0-alpha.tar.gz > http://download.enlightenment.org/releases/eio-1.0.0-alpha.tar.bz2 > > Emotion 1.0.0 - > http://download.enlightenment.org/releases/emotion-1.0.0-alpha.tar.gz > http://download.enlightenment.org/releases/emotion-1.0.0-alpha.tar.bz2 > > Ethumb 1.0.0 - > http://download.enlightenment.org/releases/ethumb-1.0.0-alpha.tar.gz > http://download.enlightenment.org/releases/ethumb-1.0.0-alpha.tar.bz2 > > Elementary 1.0.0 - > http://download.enlightenment.org/releases/elementary-1.0.0-alpha.tar.gz > http://download.enlightenment.org/releases/elementary-1.0.0-alpha.tar.bz2 > > -- > - Codito, ergo sum - "I code, therefore I am" -- > The Rasterman (Carsten Haitzler) ras...@rasterman.com > > > -- > This SF email is sponsosred by: > Try Windows Azure free for 90 days Click Here > http://p.sf.net/sfu/sfd2d-msazure > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists
[E-devel] New EFL release cycle 1.0/1.2/1.6 ALPHA
We'd like to announce a new release cycle alpha release of several Enlightenment components. This round we have added Eio, Ethumb, Emotion and Elementary. Emotion is a library to handle video playback using Gstreamer, Xine or other external plugins (VLC) and display video in Evas as a standard object. It also can handle audio playback too. Eio is here to support Emotion with async IO API's. Ethumb is a thumbnail generator library that supports the freedesktop.org thumbnailing standards, and is implemented as a dbus service and a client-side library that handles dealing with that service for you. Elementary is our new widget set, built on top of the rest of EFL, to provide you with standard widgets and behaviour to make it easy to write GUI applications. Eina 1.2.0 - http://download.enlightenment.org/releases/eina-1.2.0-alpha.tar.gz http://download.enlightenment.org/releases/eina-1.2.0-alpha.tar.bz2 Eet 1.6.0 - http://download.enlightenment.org/releases/eet-1.6.0-alpha.tar.gz http://download.enlightenment.org/releases/eet-1.6.0-alpha.tar.bz2 Evas 1.2.0 - http://download.enlightenment.org/releases/evas-1.2.0-alpha.tar.gz http://download.enlightenment.org/releases/evas-1.2.0-alpha.tar.bz2 Ecore 1.2.0 - http://download.enlightenment.org/releases/ecore-1.2.0-alpha.tar.gz http://download.enlightenment.org/releases/ecore-1.2.0-alpha.tar.bz2 Embryo 1.2.0 - http://download.enlightenment.org/releases/embryo-1.2.0-alpha.tar.gz http://download.enlightenment.org/releases/embryo-1.2.0-alpha.tar.bz2 Edje 1.2.0 - http://download.enlightenment.org/releases/edje-1.2.0-alpha.tar.gz http://download.enlightenment.org/releases/edje-1.2.0-alpha.tar.bz2 Efreet 1.2.0 - http://download.enlightenment.org/releases/efreet-1.2.0-alpha.tar.gz http://download.enlightenment.org/releases/efreet-1.2.0-alpha.tar.bz2 E_dbus 1.2.0 - http://download.enlightenment.org/releases/e_dbus-1.2.0-alpha.tar.gz http://download.enlightenment.org/releases/e_dbus-1.2.0-alpha.tar.bz2 Eeze 1.2.0 - http://download.enlightenment.org/releases/eeze-1.2.0-alpha.tar.gz http://download.enlightenment.org/releases/eeze-1.2.0-alpha.tar.bz2 Expedite 1.2.0 - http://download.enlightenment.org/releases/expedite-1.2.0-alpha.tar.gz http://download.enlightenment.org/releases/expedite-1.2.0-alpha.tar.bz2 Evas Generic Loaders 1.2.0 - http://download.enlightenment.org/releases/evas_generic_loaders-1.2.0-alpha.tar.gz http://download.enlightenment.org/releases/evas_generic_loaders-1.2.0-alpha.tar.bz2 Eio 1.0.0 - http://download.enlightenment.org/releases/eio-1.0.0-alpha.tar.gz http://download.enlightenment.org/releases/eio-1.0.0-alpha.tar.bz2 Emotion 1.0.0 - http://download.enlightenment.org/releases/emotion-1.0.0-alpha.tar.gz http://download.enlightenment.org/releases/emotion-1.0.0-alpha.tar.bz2 Ethumb 1.0.0 - http://download.enlightenment.org/releases/ethumb-1.0.0-alpha.tar.gz http://download.enlightenment.org/releases/ethumb-1.0.0-alpha.tar.bz2 Elementary 1.0.0 - http://download.enlightenment.org/releases/elementary-1.0.0-alpha.tar.gz http://download.enlightenment.org/releases/elementary-1.0.0-alpha.tar.bz2 -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
