On Fri, 23 Feb 2007 12:03:06 -0500 Sthithaprajna Garapaty <[EMAIL PROTECTED]> wrote:
> What would make more sense is a standard way of handling these > 'information popups' or 'tooltips'. There's no need to force mouse > bindings on them. Just need a class that can simply take text, etc > and turn it into a nice tooltip, and conform to the E theme. > And more importantly, perhaps your focus should not be so narrow onto > modules.. but rather for all of E (I'd like to see some tooltips in > the FM at some point), and perhaps even going into EFL, etc so that > other EFL based apps can also use 'em. We need more than just a simple bit of text if we are to do this properly. A simple bit of text should be as option, but so far all these popups are more complex than that. I'd suggest taking something like the config dialog code, stripping out the standard buttons, making it borderless, and calling it a popup. It can be themed like the rest of E, works the same as dialogs for the programmer (add arbitrary widgets), pops up on mouse over (with a portion under the mouse so the user can click on it without moving), allows click to lock, and has an API for "not on mouse over, but when requested". And allow binding. There is a good case for saying that the menus, desktop switch popups, and run command dialog could be considered as users of this popup code. We have all the code needed, we should just formalise it to the common case. Refactoring anyone? B-)
signature.asc
Description: PGP signature
------------------------------------------------------------------------- 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
