On Thursday 01 December 2005 05:58, Essien Ita Essien wrote: > I've looked at gadget_test/e_mod_main.c, and it looks good to me so far. > > I like how it really simplifies things. A real test IMOHO though, would be > to use one of the existing simple modules (desktop name? or one simpler?), > as the real test bed. It will be a more compelling example, and > bugs/oversights will show up faster. What do you think?
Yeah, definitely, I just hadn't gotten to it yet :) The next bit I'm going to add is config handling. So, you just pass in a data descriptor (EDD) for your main module config, and one for any face specific config (both optional), and have it populate the Gadget.conf and Gadget_Face.conf vars automatically. (They'll be void *, up to the writer to cast it to their struct type before using). After that, it will be easy to bump the gadget_test module up to a fully working clock module :) Then I'll work on moving some other modules over and see what functionality needs to be added/modified to make them easier to use. > > Overall, I think module development just got one huge step in the fun > department, and we can optimize away e_gadget.c to our hearts content... > thnx Brian. Thanks :) Like I said, its just a start, but hopefully in the right direction. -- rephorm ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
