Open GoogleCodeExporter opened 9 years ago
Agree.
Essentially TGM-2 should be a UI to replace and extend existing ways tab groups
are displayed, and not a lot more. Extra functions such as suspend or hibernate
tabs groups can apply to other extensions, or even Firefox without TGM, so they
can be "unpackaged" for simplicity.
In other words I see TGM being replaced either by *smaller and simpler
extensions*, or a single *modular* extension. The functions I see as separable
are:
- Providing extra interface options for tab groups - improves how tab groups are displayed, ie via a tab groups bar, nested tab groups, etc. Also includes styling for tab groups (but not tabs themselves)
- Suspend and hibernate tab groups - allows tab groups to be suspended or hibernated (whether or not TGM-2 is installed)
- Backup and restore tab groups - allows tab groups to be saved and restored (as opposed to saving and restoring an entire session)
- Most other functions in TGM are already included in other extensions. For example, styling of loaded/unloaded/suspended tabs is mostly covered in TMP and many other tab extensions, multiple tab handling is handled by Multiple Tab Handler, session save/restore is now inbuilt to Firefox and other extensions.
In other words I'd replace a monolithic complex TGM, by a modular extension or
separate extensions, and I'd use existing functionality from Firefox and other
well known extensions where possible to minimise our work and keep it
lightweight and simple.
Original comment by Stilezy
on 13 Jun 2013 at 12:14
Completely agreed.
Original comment by j...@brandloyal.com
on 13 Jun 2013 at 12:28
Original comment by Stilezy
on 13 Jun 2013 at 2:22
Original comment by Stilezy
on 13 Jun 2013 at 2:29
Original comment by tgmj...@gmx.com
on 9 Sep 2013 at 4:06
Original comment by tgmj...@gmx.com
on 9 Sep 2013 at 4:10
Original comment by tgmj...@gmx.com
on 9 Sep 2013 at 10:55
I agree on all comments, but want to notice that one of the reasons I use TGM
is that FF can't handle lots of tab groups itself.
Before using TGM I tried FF's groups with lots of groups and it was very slow
and almost unusable. I don't know the reason, we may have the same problem if
you use FF groups with TGM
Original comment by ssalg...@gmail.com
on 16 Sep 2013 at 8:22
Firefox at present is dreadful at handling its own tabs, yes. That's
essentially the reason to use TGM.
Original comment by luck...@gmail.com
on 16 Sep 2013 at 8:41
I'd like to point out that Panorama is considered dying, and despite many
protests they are going to remove it completely from FF (search Google). AFAIK,
there is currently no public API in FF that is useful as a base for TGM. And if
they really remove Panorama, there will stay no tab-grouping functionality in
FF at all.
See e.g.
https://bugzilla.mozilla.org/show_bug.cgi?id=836758
and links therein. (But more info surely on Google.)
Original comment by x...@zoznam.sk
on 19 Sep 2013 at 10:42
Hello,
We've been persistently researching future plans for Tab Groups ("Panorama" and
formerly "TabCandy"). As a reminder, issue 12 is a blocker. However, let's
continue to aggregate relevant information.
- Confirmed via Mozilla IRC the absence of public API
- https://github.com/ttaubert/firefox-tabgroups
- http://www.palemoon.org/tabgroups.shtml
- Mozilla bug 836758 plans to install compatible add-on by default for
Panorama users
-- John
Original comment by tgmj...@gmx.com
on 24 Sep 2013 at 8:35
Original issue reported on code.google.com by
j...@brandloyal.com
on 12 Jun 2013 at 9:26