On 12/27/11 22:04, Gustavo Sverzut Barbieri wrote: > On Wed, Dec 28, 2011 at 12:57 AM, Christopher Michael > <cpmicha...@comcast.net> wrote: >> On 12/27/11 21:51, Gustavo Sverzut Barbieri wrote: >>> >>> On Wed, Dec 28, 2011 at 12:47 AM, Christopher Michael >>> <cpmicha...@comcast.net> wrote: >>>> >>>> On 12/27/11 21:42, Gustavo Sverzut Barbieri wrote: >>>>> >>>>> >>>>> On Wed, Dec 28, 2011 at 12:34 AM, Christopher Michael >>>>> <cpmicha...@comcast.net> wrote: >>>>>> >>>>>> >>>>>> On 12/27/11 21:26, Gustavo Sverzut Barbieri wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Wed, Dec 28, 2011 at 12:20 AM, Christopher Michael >>>>>>> <cpmicha...@comcast.net> wrote: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On 12/27/11 21:16, Gustavo Sverzut Barbieri wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, Dec 28, 2011 at 12:03 AM, Christopher Michael >>>>>>>>> <cpmicha...@comcast.net> wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On 12/27/11 20:42, Gustavo Sverzut Barbieri wrote: >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Tue, Dec 27, 2011 at 11:01 PM, Christopher Michael >>>>>>>>>>> <cpmicha...@comcast.net> wrote: >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On 12/27/11 16:45, Cedric BAIL wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Tue, Dec 27, 2011 at 8:25 PM, Enlightenment SVN >>>>>>>>>>>>> <no-re...@enlightenment.org> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Log: >>>>>>>>>>>>>> Ecore_Evas (Wayland_Shm): >>>>>>>>>>>>>> >>>>>>>>>>>>>> Add an actual 'frame' to ecore_evas_wayland. (just a boring >>>>>>>>>>>>>> rectangle >>>>>>>>>>>>>> frame w/ the title). >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Couldn't you reuse in some way what Gustavo did in the EWL >>>>>>>>>>>>> backend >>>>>>>>>>>>> ? >>>>>>>>>>>>> >>>>>>>>>>>> Are you referring to the old ewl toolkit here ? >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> he means EWS - Evas+Ecore Windowing System. >>>>>>>>>>> >>>>>>>>>> Ahhh ok. Well, what exactly is ews ? and what use could it be here >>>>>>>>>> ? >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> I'm not following wayland patches, but EWS implements a windowing >>>>>>>>> system, with a window manager and all (decorations provided by >>>>>>>>> elementary's wm). It's single process, so you can run all your >>>>>>>>> elementary_test windows in framebuffer or playstation3. >>>>>>>>> >>>>>>>>> I had no need for things like "frame" windows and such, found it >>>>>>>>> strange. But likely raster is reviewing your code and it does make >>>>>>>>> sense, no idea on my side. >>>>>>>>> >>>>>>>>> >>>>>>>> And I haven't been following ews patches, lol :) But I am curious now >>>>>>>> ... >>>>>>>> how does ews implement a window manager& decorations ? I haven't >>>>>>>> seen >>>>>>>> >>>>>>>> anything in elementary that does decorations (or for that matter, a >>>>>>>> window >>>>>>>> manager). Also not sure if 'single process' would be sufficient in a >>>>>>>> wayland >>>>>>>> case :/ >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> there are no patches, code is in ecore_evas and elementary for months >>>>>>> already. >>>>>>> >>>>>>> ecore_evas posts ecore_events that the manager is supposed to use and >>>>>>> do whatever is required, like adding decorations. >>>>>>> >>>>>>> elementary's code will implement this and register to events, creating >>>>>>> edje to decorate it: >>>>>>> >>>>>>> >>>>>>> >>>>>>> http://trac.enlightenment.org/e/browser/trunk/elementary/src/lib/elu_ews_wm.c >>>>>>> >>>>>> Ahh I see. >>>>>> >>>>>> >>>>>>> as for single process, that what was required. if one added a way to >>>>>>> get windows from other process is just a matter of doing the shm. But >>>>>>> I did not, as wayland was supposed to do it. :-) >>>>>>> >>>>>>> >>>>>>>> Well, we are not making 'frame windows' (as such), just ability for >>>>>>>> ecore_evas to draw it's own "frames" Around windows (read: >>>>>>>> decorations)...or >>>>>>>> for elm to do it, etc. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Still don't get it. What's the need to have these? Isn't just the >>>>>>> window maker (elm_win) to draw its stuff and that's it? what's up with >>>>>>> it at Evas level? >>>>>>> >>>>>> >>>>>> Well, what happens if someone makes an efl app that does not use elm ? >>>>>> Ecore_Evas would still need a way to draw a 'frame' around the window. >>>>> >>>>> >>>>> >>>>> are you kidding or insane? >>>> >>>> >>>> >>>> Just insane ;) >>>> >>>> >>>> What are you going to do? draw the border >>>>> >>>>> >>>>> using only evas commands, no themes? no nothing? >>>> >>>> >>>> Yup. It's just a basic frame (a "boring" rectangle) >>>> >>>> >>>> If you're getting >>>>> >>>>> >>>>> themes, you pull in edje, >>>> >>>> >>>> Right, which is why the ecore_evas frame is just a boring rectangle so we >>>> don't pull in edje there. >>>> >>>> >>>> then not in ecore-evas... a separate >>>>> >>>>> >>>>> library? if so, why not elm? >>>>> >>>>> that's why I put it like that, elm pulls in ecore, evas, ecore_evas >>>>> and edje, all nice to do it... plus ship with a theme :-) >>>>> >>>> Sure, and elm will have the option of doing the window decorations >>>> (frame) >>>> itself if needed/wanted. >>> >>> >>> if nobody is going to use it, why doing it? >>> >> Well, it needs the ability to do it just in case someone makes an app not >> using elm, but still wants to provide a frame. If they are not using elm, >> then ecore_evas can "optionally" draw a basic rectangle frame, OR they can >> supply their own evas_object to handle it. >> >> A simple shot showing the 'frame' for ecore_evas. It's nothing fancy (and is >> not meant to be) but it does/will provide a way to move windows around by >> grabbing the frame. >> >> http://i.imgur.com/9G9EY.jpg >> >> There are no 'borders' on the elm test app in this shot cause I am still >> hashing out that part of the code. > > if we don't do this for fb, directfb, windows or x11, why would we do > it for wayland? > > really, if someone is willing to write barebone app using ecore_evas > directly, he can deal with that, or live without it. >
Right, and if they do, then they would need a way to tell ecore_evas about their frame thus the ability to provide an evas_object to be used for that. If they don't want to provide their own frame, then they can tell ecore_evas to use the 'default boring one'. Either way, a frame is needed by wayland in order to be able to move windows around. Wayland does not provide a way to move a window via code (read: put window @ 10,10). It just does not provide a method for it. All window moves in Wayland are handled via response from the 'input device' (read: mouse). There is nothing akin to ecore_x_window_move(win, 10, 10). In order to 'move' a window in wayland you have to use: wl_shell_surface_move(struct wl_shell_surface *wl_shell_surface, struct wl_input_device *input_device, uint32_t time) which directly takes the input device. So what happens is, you 'grab' the 'frame' w/ button and move the window around. Without a 'frame', there is nothing to grab and thus no way to move the window (in the traditional sense). dh ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
