Re: [E-devel] Module Popup Policy

[Carsten H. (T. R. <ra...@ra...>]

On Thu, 22 Feb 2007 19:15:28 +0100 "Brian 'morlenxus' Miculcy"
<mor...@gm...> babbled:

i think this isn't a matter of forcing gadgets to do 1 thing only, but more a
matter of people writign gadgets for modules to be consistent and do the same
thing - not each person do something different for identical functionality. i
dont see it good to limit this to work 1 way only as then its harder to do
special things when you need to. it's just a matter of better gadget design.

> Hi all,
> 
> there was a small discussion on the irc about the module popup policy.
> Currently each module has his own policy:
> - mixer opens the popup on click
> - net module opens on mouse over, if you click the popup stays open
> - weather opens on mouse over, no click event
> 
> So i think there should be a standard for the module popup.
> Here is my idea:
> 
> Mouse over:
> The mouse over popup is enabled by default. You can disable it using an
> option in the module configuration dialog.
> 
> Click:
> The click locks the popup. This means, if you leave the module icon
> area, the popup isn't closed. If you want to unlock the popup, you need
> to click once again. A nice feedback to the user would be a little lock
> icon.
> If the mouse over popup is disabled, a click would open the popup and
> locks it. To close the popup simply click.
> 
> The mouse over gives you a quick view at the popup without much user
> interaction. The locking mode allows you to have a popup with useful
> informations open, while running some other processes. Example:
> A memory module shows in the popup a list with the top memory eating
> applications (i guess firefox would be at the first position). The list
> is updated every second. If you now lock the popup you would be able to
> kill the applications with some xterm commands - while still having the
> list open and show you informations. Without the locking mode you would
> need to hover the module icon again and again after running a command,
> just to see if there has been something changed. I guess the user would
> open another xterm and run `top` there, so the module popup
> information would be a nice eyecatcher, but doesn't really help.
> Another example would be a calendar module which shows a month view in
> the popup. Sometimes you just want to know a day in the next week,
> sometimes you want to write some email while having the month view on
> screen.
> 
> Imho it's useful. :) Comments?
> 
> Greets,
> Brian 'morlenxus' Miculcy
> 
> -------------------------------------------------------------------------
> 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
> enl...@li...
> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
> 


-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler)    ra...@ra...
裸好多
Tokyo, Japan (東京 日本)