On 3/28/07, Cedric BAIL <[EMAIL PROTECTED]> wrote: > On Tuesday 27 March 2007 14:39:12 Jorge Luis Zapata Muga wrote: > > Hi all, i have coded several things to ecore_fb, but before doing a > > commit i prefer your opinion or whishlist =) > > > 1. Modules for input devices. Instead of having the input devices > > exclusive (linux_input or ps2/keyboard/tslib combo), ive made an > > abstraction to support input "modules" (for now they are just > > statically linked - its a similar approach to what evas had on the > > beginning with engines). For now we don't need real modules because > > the input modules is the only module type we have. > > > 2. More Input Devices: A while ago i coded the linux_input (event > > devices) support and replace the input devices that were on ecore_fb > > (tslib, keyboard, ps2) to support multiple devices (i.e two mice, > > three keyboards, whatever). I've re-enabled the replaced ones, > > following the module approach. > > That's interresting. I would like to know if you are sending to evas some > device id with the event, and if you did, how ?
No, i just send the event as is, without device info. I read your mail about sending device information *in* the evas event struct, if i recall correctly, whenever you submit an event to evas (i.e _event_feed) you can pass any data with it. It is accessible through Evas_Event_XXX->data. > > > 3. Support for keyboard layouts, in ecore_fb the keyboard layout was > > hard coded to english layout (ascii values only), with this code we > > can use different layouts (spanish, french, or your own), it was coded > > following the keymaps(5) idea. Ive also made a parser for keymaps (the > > files you have under /usr/share/keymaps/) which will export a c source > > file for now, i want to also export an eet file, but it wont be done > > until my eet patch gets in. btw, where's a good place to put this > > application? under /src/bin of ecore? on tests dir in cvs? > > That's really interesting also, for the SDL backend, I need something to > handle keymap. SDL key are easy to convert to Linux key, so it could be > possible we can share code. Did it depend on some ecore_fb functionality or > is it just another part of ecore ? We, indeed, have common code, Ive been thinking on how to actually share it but can't find a good selection right now, i better wait to check on how you implement the sdl abstraction. The keyboard thing was coded from ground-up without any ecore_fb dependency and using as example the kbd package (keymaps, dumpkeys, etc). > > I think I will start looking at ecore_fb when you commit your patch as a base > for an ecore_sdl as it seems you already did all the hard work :) > I might have some issues committing, yesterday my laptop didnt work... dunno what's going on =( > Cedric > > ------------------------------------------------------------------------- > 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 > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > enlightenment-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > ------------------------------------------------------------------------- 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 http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
