Feature proposal : cleanup tabs

[Damien Flament]

Hi,

> What happens, for
>  example, if you leave the IDE open for 30 minutes and do something else? Or
>  have some tabs you just accidentially click all the time but switch away
>  from then within half a second (happens often to me, at least)?

Yes, you're right.

Is there many differents ways to check that the IDE is not used :
The user don't interact with the IDE
The IDE window is not shown in foreground (hidden by others windows)
I think the second is more easy to implement.

> A tab could be
>  marked as "used" when it was viewed for more than 3 seconds or an edit was
>  performed in it (for example).
... when an edit was performed or when the user scrolls (switching to a tab to quickly read some text and re-switching 
to previous tab without edit).
> [...] when the cleanup action is
>  invoked, close all tabs except the 10 (configurable) most recently used
>  ones [...]

I didn't think restricting to a number of tabs would be usefull. The objective is to clean tab bar from unused tabs. And 
you can't anticipate the number of unused tabs. I would be usefull if the algorithm is not effective !

Two things to include in "outdated tabs recognition algorithm" (in my opinion, comments are welcomed) :
A tab is considered opened (time counter reset) after a short amount of time, an edit or scrolling
Tabs can't be outdated when user isn't using the IDE (time counters paused).

Thanks for your comments.
Damien Flament.

On Wednesday 12 January 2011 20:09:34 you wrote:
 Hi!
 
 I had that idea some time ago, too. I really like it.
 However, I think a bit more sophisticated "outdated tab recognition
 algorithm" would make this feature way more useful. What happens, for
 example, if you leave the IDE open for 30 minutes and do something else? Or
 have some tabs you just accidentially click all the time but switch away
 from then within half a second (happens often to me, at least)?
 I would instead propose something like this: Mark tabs as "used" depending
 on user activity, with ascending IDs; then, when the cleanup action is
 invoked, close all tabs except the 10 (configurable) most recently used
 ones, and do not close tabs used within the last 10 minutes. A tab could be
 marked as "used" when it was viewed for more than 3 seconds or an edit was
 performed in it (for example).
 What do you think?
 
 Bye,
 Sven
 
 P.S: I'm also a huge fan of non-dialog UIs (using notification bars or
 something instead). Don't know what you think about this, but foreground
 dialogs always annoy me. :)
 
 
 2011/1/12 Damien Flament <contact.damienflament at gmail.com>
 
 >  Feature proposal : Cleanup tabs
 > 
 > Hi, I am Damien Flament, student at IUP ISI (University Paul Sabatier in
 > 
 > Toulouse).
 > 
 > We are working on tab bar improvement. Yannick Motta already added an
 > option in tabs settings to hide close buttons.
 > 
 > To get current modifications on tab bar go to tab-bar branch on bport
 > repo<http://gitweb.kde.org/clones/kdevplatform/bport/kdevplatform-isi.git
 > /shortlog/refs/heads/tab-bar> .
 > 
 > We want to add a feature to cleanup old tabs. A tab will be outdated when
 > it was not opened after a user-defined amount of time. It is like the
 > Aging Tabs <https://addons.mozilla.org/en-US/firefox/addon/3542/> Firefox
 > extension (without colors).
 > 
 > Feature description
 > 
 > An option will be added to the tab context menu next to "Close [...]"
 > 
 > options:
 >  A confirm dialog will bring up showing the list of outdatted tabs :
 >  
 >  We will add an option in the tabs settings to setup the time after a tab
 > 
 > will
 > 
 > be outdated (in "User Interface" tab) :
 > 
 > P.S. : The "Show close button on tabs" option was added by Yannick Motta.
 > 
 > Waiting for comments and reviews.
 > 
 > Thanks.
 > 
 > Damien Flament,
 > 
 > IUP ISI, Paul Sabatier University (Toulouse)
 > 
 > 
 > --
 > KDevelop-devel mailing list
 > KDevelop-devel at kdevelop.org
 > https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20110113/8e852306/attachment.html>