Carsten wrote: > On Thu, 30 Oct 2008 14:46:12 -0700 "Matt Barclay" <[EMAIL PROTECTED]> babbled: > > >> On Thu, Oct 30, 2008 at 2:14 PM, Jose Gonzalez <[EMAIL PROTECTED]> wrote: >> >>> Matt Barclay wrote: >>> >>>> Hello, >>>> >>>> I'm working on an app that let's the user control a chair. In the >>>> app, the user will click on the headrest, armrest, seatback, or >>>> footrest to control its position. Since these pieces of the chair are >>>> not rectangles, I'm planning on using some Embryo scripting to get the >>>> mouse coordinates on the chair, then figure out if the click is inside >>>> of the controllable areas and emit a signal. A much cleaner approach, >>>> I think, would be a part type POLY that would let edje do the heavy >>>> lifting and behave just like RECT. I can't be the first person to run >>>> into this challenge. How have you solved it in the past? How hard >>>> would it be to add POLY to edje? I see evas already has support for >>>> polygons. >>>> >>>> >>> That sounds like a fun and interesting project. :) >>> >> Yeah, mostly because this is our pilot EFL project! It's really >> incredible what these libraries can do and how easy it is to build a >> development process around graphic design, UI scripting, and >> application programming. >> > > you're playing with something that has some bits pretty mature and solid - > other still very much in progress. so be prepared for rough patches - but you > get the general direction we are going - split the worlds of programmer and > ui artist/designer. let the programmer specify core functionality and > behavior. > ie the programmer is like the structural engineer. he builds the foundations > and framework of the building and some of its core infrastructure (piping, > ducts, elevators etc.). then the ui designer comes in with his crew and does > the walls, windows, floors, carpets, furniture, paintings, sculptures etc. > that > gives the thing the "feel" day to day. we of course make arbitrary decisions > where WE think the line is between engineer and designer. mostly based on the > fact that i straddle both sides and know both ends and i make a call as to > which camp it falls in. at the time :) >
And unfortunately you have another set of tough decisions to make for both evas and edje. The 'good' news is that, if desired, we can make evas and edje incorporate most all vgfx stuff that others have, and some further stuff they don't as well, and do so within 3 or 4 months (a bit longer for some extensible aspects). The 'bad' news is that in order to 'revamp' not only the vgfx capabilities, but also add further gfx abilities, each and every set of such revamps will likely mean breaking most of the current engines, and getting much of this into edje will likely mean breakage there too. I'd suggest you consider too ways: Either release evas and edje now, and start a branch for the 'next' breaking versions and concentrate on those.. or start breaking evas and edje now. Because the longer you wait on this, the more difficult and less likely it will actually get done. ____________________________________________________________ Become a Graphic Designer and earn up to $150/ hour. Click here. http://thirdpartyoffers.juno.com/TGL2141/fc/Ioyw6i3oLKk95sK8r7AWnSN2hfEHZR5e34yFceCj6XBiwNiR38077C/ ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
