On Thu, Sep 06, 2007 at 11:26:08AM -0300, Gustavo Sverzut Barbieri wrote: > > Yeah, I agree, it would be cleaner code to have an object for that, since > > it's not related to the > > EcoreEvas.. > > The question would need to be asked for Ecore_X_Window rather than > > Ecore_X_Cursor, since > > the X_Window is an attribute of the EcoreEvas (while the cursor is not). > > I think it will depend on the amount of functions needed and what they do > > (like the cursor_set). I > > would rather see it like : > > cursor = ecore.x.Cursor.shape_get(ecoe.x.Cursor.ARROW) > > ecore_evas.cursor_set(cursor) > > > > rather than : > > cursor = ecore.x.Cursor.shape_get(ecoe.x.Cursor.ARROW) > > win = ecore_evas.window > > win.cursor_set(cursor) > > > > But as I said, it will depend on the amount of functions, if there are 100 > > functions for the > > Ecore_X_Window, it could just 'spam' the ecoreEvas, so using a separate > > class would be better for > > keeping the EcoreEvas code clean. If it's only a few functions, then maybe > > putting the functions in > > EcoreEvas would make the API easier to use. > > What do you think ? > > We can still have common cases helped a bit (like this), but I'd still > like to have XWindow and XCursor classes, EcoreEvas.window_get() would > then return XWindow() instance, that would provide an "xid" parameter. > > Problem is: grep ecore_x_window Ecore_X.h => 109, that's lots of functions! >
hehe, ok, that's indeed a lot of functions, so it would make sense to have it as its own class... Now that I think about it, I should have known that, since that's why I abondonned the idea to implement all of them in the first place.. was too overwhelming :p KaKaRoTo ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
