[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [E-devel] Evas Smart objects

On 1/1/07, Brian Mattern <brian.mattern@gmail.com> wrote:
On Mon, Jan 01, 2007 at 03:43:42PM +0100, Jorge Luis Zapata Muga wrote:
> On 7/2/06, The Rasterman Carsten Haitzler <raster@rasterman.com> wrote:
> > On Mon, 19 Jun 2006 01:17:03 +0200 "Jorge Luis Zapata Muga"
> > <jorgeluis.zapata@gmail.com> babbled:
> >
> > > Hi all,
> > > i have some doubts-ideas about evas smart objects,
> > >
> > > 1. the API
> > > in order to add an object to a smart object you have to do
> > > _member_add(o, s) and to delete _member_del(o,s). On the code of both
> > > an evas smart object actually stores the members on a list but theres
> > > no function to retrieve them, Evas_List * _members_get(s), so when you
> > > code an evas smart obejct and you need to keep track of the objects
> > > you have, you need to duplicate the list and code a different function
> > > to do that.
> >
> > a get call would be useful and a good idea. :)
> hi all and happy new year =)
> ive retaken this thread to not add another one about almost the same
> topic (Evas smarts) :)
> i know the get call is indeed usefull, but im having another "problem"
> with evas smarts, the member_add/member_del functions. Wouldnt be good
> to have the smart class also define (if it wants) a member add/del
> callbacks?
> all smart classes define their own api to add a member in case they
> want to track down/do something with the objects added/deleted which
> is good, but imho isnt consistent because if someone uses the "normal
> api" to do that (evas api) the smart object will be in a inconsistent
> status. one solution is to do everything through evas api, do a
> _member_add and the smart callback will be called.
> If the smart also wants to add its own objects in case an object is
> added it still has to differentiate in the callback if the object
> added is its own or another, but isnt a problem i think =)
> what do you think?

_member_add/del are more for internal use of the smart object to tell
evas which objects are part of it (for event, stacking, layering,
purposes). If a smart objects acts like a container, i think it makes
more sense to have a specific api for that (there may be multiple ways
of adding children to that container) rather than using a generic
member_add() with a callback.

I may be misunderstanding your request. If so, could you give a specific
example of what you're proposing?


we have discussed this on irc.
better the way it is right now =)

Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
enlightenment-devel mailing list