On 04/09/12 07:48, David Seikel wrote: > On Tue, 04 Sep 2012 07:40:30 +0100 Christopher Michael > <cp.mich...@samsung.com> wrote: > >> On 04/09/12 07:31, David Seikel wrote: >>> On Tue, 04 Sep 2012 07:19:58 +0100 Christopher Michael >>> <cp.mich...@samsung.com> wrote: >>> >>>> On 04/09/12 05:39, David Seikel wrote: >>>>> On Mon, 03 Sep 2012 20:19:20 +0000 Christopher Michael >>>>> <cpmicha...@comcast.net> wrote: >>>>> >>>>>> On 03/09/2012 07:03 PM, Rafael Antognolli wrote: >>>>>>> Hey devilhorns, >>>>>>> >>>>>>> Didn't you agree that the framespace stuff should be outside of >>>>>>> Evas, and just inside Elementary? I remember that last week you >>>>>>> talked on irc about having a patch available for that, so I can >>>>>>> only understand that you and Gustavo are not discussing about >>>>>>> the same thing. >>>>>> >>>>>> Yea, that was my stance originally...or rather, that was my >>>>>> preference... Except that it cannot be done only inside >>>>>> Elementary. In an ideal world yes, but what happens if someone >>>>>> creates an application which does not use Elementary ? Just uses >>>>>> a bare ecore_evas.. then their objects would not be drawing >>>>>> correctly (read: the could potentially be drawn below the >>>>>> frame). So, in order to support older applications (or >>>>>> applications made using Base EFL, not Elm), we have to handle it >>>>>> in Evas. >>>>> >>>>> I'm still not sure if I want to use Elementary for things, though >>>>> I'm giving it a try in an unimportant project. I've not looked >>>>> much at Wayland yet, but it sounds like a good idea in general. >>>>> Hope it's implemented well, and not just by us, but by the Wayland >>>>> people. >>>>> >>>> I suppose that is a subjective statement really ;) One persons >>>> version of "implemented well" may not match anothers ;) >>>> >>>>> Also Lua stuff, which I intend to write more backend support for >>>>> when I get some time, is below the Elementary level, it's edje >>>>> level stuff. I can see people writing Lua edje proggies that >>>>> don't use Elementary. I intend to write some real examples like >>>>> that. >>>>> >>>> >>>> Well, if/when you do, if you find issues in using Lua under >>>> Wayland, please report them :) >>> >>> I'll know who to spank, er I mean report problems to. B-) >>> >> >> Hahahaha :) You can see that bullseye painted on my back from there >> huh ? :) > > /me hides the can of paint and the still dripping paint brush. > > Er, um, what bullseye painted on your back? >
LMAO :) >>> Seems that the consensus on the other thread is to stick with >>> keeping the Wayland frame stuff in evas and transparent to apps, so >>> I doubt if it will be a problem for me. >>> >> It's really the only way to sanely do it. Well, that was the >> goal...to be as transparent as possible and not have to require a >> bunch of changes on the application side. When all is said and done, >> you should not have any problems (assuming you are doing nothing >> engine specific in your app). > > Yep, that's what I want to see, cross platform transparency. Saves me > from having to worry about it. B-) > Indeed :) That's the idea ;) App developers won't have to worry about if their app will function in Wayland (assuming they have coded generically). dh ------------------------------------------------------------------------------ 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
