On Tue, 21 Aug 2012 16:42:13 +0200 Vincent Torri <[email protected]> said:
> On Tue, Aug 21, 2012 at 4:35 PM, Carsten Haitzler <[email protected]> > wrote: > > On Tue, 21 Aug 2012 13:36:58 +0200 Vincent Torri <[email protected]> > > said: > > > > it's not an event - it's a state. it examines a sequence of keys and if it > > matches a specific sequence, it returns a string to insert. it's used as > > part of keyboard input, but as it can't be sensibly done directly inside > > evas or ecore itself transparently, it has to be done AS you get the > > keystrokes. it's like a highly simplified ecore_imf but doesn't depend on > > any infra. it's directly related to input processing, so ecore-input is > > where it belongs. > > there are also file stuff in eina which is not in eio or ecore_file, > so it's not a good argument. > > Why putting in ecore_input something that does depende only in eina ? because it's related to key input handling. eina-file vs eio is a poor example. eio is much newer than eina-file. and ecore-file is much older than eina-file. it's honestly a file mess there. 3 file api's. ugh. this is logically related to key input handling. eina doesnt handle anything like that (string handling sure - not key input stream handling). > > > > example: you type: > > > > multi_key + a + " and you get... ä > > or > > multi_key + o + ^ and you get... ô > > why not putting that in eina_convert.c. According to what you saya > above, it cold fit nicely in it. > > Anyway, it you still want to let it in ecore_input (but i do not agree > on that point), at least, let it begin with ecore_event_ ecore_event is poor if it's called ecore_input. it's already poorly named and then it just gets longer that it should be. part of input handling is compose handling. it should be ecore_input_* but ecore_event is the silly namespace ecore_INPUT has... i may as well hang around with the silliness and make something logical like ecore_compose :) > Vincent > > > > >> Hey > >> > >> in Ecore_Input, we can see: > >> > >> > >> typedef enum _Ecore_Compose_State > >> { > >> ECORE_COMPOSE_NONE, > >> ECORE_COMPOSE_MIDDLE, > >> ECORE_COMPOSE_DONE > >> } Ecore_Compose_State; > >> > >> EAPI Ecore_Compose_State ecore_compose_get(const Eina_List *seq, > >> char **seqstr_ret); > >> > >> It seems that it has been added for 1.7. Can the one who committed > >> that add the 'event' namespace for the enum and the function, as it > >> should be ? > >> > >> Vincent > >> > >> ------------------------------------------------------------------------------ > >> Live Security Virtual Conference > >> Exclusive live event will cover all the ways today's security and > >> threat landscape has changed and how IT managers can respond. Discussions > >> will include endpoint security, mobile security and the latest in malware > >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > >> _______________________________________________ > >> enlightenment-devel mailing list > >> [email protected] > >> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > >> > > > > > > -- > > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > > The Rasterman (Carsten Haitzler) [email protected] > > > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [email protected] ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
