On Fri, 08 Jul 2011 14:58:19 +0900 Jihoon Kim <jihoon48....@samsung.com> said:
hmmmm ok - i have 2 questions. 1. why should the app CONTROL the effects for the input panel showing/hiding directly? the input panel should be a window managed by the wm and shown and hidden as the wm sees fit, if it animates or not is not the apps decision nor should it be. this really exposes too much direct control imho. 2. getting input panel geometry - this is done via other properties/hints already, why here? the other properties can in theory handle multiple overlayed windows not just keyboard (indicator too and softkey etc.). why should vkbd be different and add an api here? > Hi, EFL developers. > > For supporting virtual keyboard, I'd like to add some APIs. > The detail description of each API is written in the patch file as doxygen > format. > > Would you please review this patch? > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ Magic Quadrant for Content-Aware Data Loss Prevention Research study explores the data loss prevention market. Includes in-depth analysis on the changes within the DLP market, and the criteria used to evaluate the strengths and weaknesses of these DLP solutions. http://www.accelacomm.com/jaw/sfnl/114/51385063/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
