TabGroups Manager revived: rewrite for WebExtensions

Issue #142 new
grahamperrin
created an issue

From post 17 under Development and Maintenance of TabGroupsManager extension:

Please, do you have a timeline for a rewrite?

Comments (17)

  1. Miguel Angel Romero Lluch

    hi @grahamperrin, I would love to do so, but I unfortunately I can not guarantee to have enough time to fully rewrite all the code from scratch to the new WebExtensions API. TabGroupsManager has a lot of code with some custom parts which may be impossible to migrate to the new API, so it will be difficult and slow, but not impossible.

    I think our best approach in this case would be to start with a small product with the basic functionality (whenever possible based on the idea of the implementation coded in TGM) , and adding more and more functionalities like its currently in TGM.

    There are some points which will really help us here: Having more people involved in the project, specially programmers and people who can give support in the forum threads. Refactoring TGM in different classes will also provide us a way to organize the code easy to maintain and migrate. This is something we really need to do here. * Analise and document the behavior of TGM from a functional and technical point of view, with documents with "Functional Flow Diagrams" of main features which will help us to migrate the original behavior and original code to the new one.

  2. grahamperrin reporter

    Thank you!

    … forum threads. …

    Will you be happy to continue in Mozilla Discourse?

    Elsewhere:

  3. karim kiswarday

    Hi @Miguel Angel Romero Lluch, how many developers are involved in TGM?

    I'm willing to help during my free time but I have not experience to write Firefox extensions.

    Where can we talk about the project?

    EDIT 1 From this post on Stack Overflow, it seems that with the new web extensions is not possible to change the default UI

  4. Miguel Angel Romero Lluch

    I have been testing WebExtension API and it is a nightmare. It is a high level API with a very limited subset of basic browser functionality which lacks all the things we need to port TabGroupsManager. No toolbar widget neither API. No API to create a window with alwaysFocused property true. * Not file data manager APIs. ...

    And so on..., Firefox will be dead by v57. I have read most important extension will break: NoScript, UBlock.. DownloadThemAll All toolbars managers All tab managers.

    There has been a lot of complaints and hundreds of impressive letters sent to Mozilla asking them to stop breaking their extensions this way, but they do not want to listen to their main core developers nor users, its a real pity. https://forum.palemoon.org/viewtopic.php?f=4&t=14201 https://www.reddit.com/r/firefox/comments/6kdr6s/is_anyone_working_on_a_tab_groups_webextension/

    Time to switch to Palemoon.

  5. irishbandit

    Finished switching to palemoon today so far so good. This is the best addon ever and its worth it to switch!! Happy that we have an option that will continue to work. Thank-you so much for all the hard work so that TabGroups Manager revived keeps working!!!

  6. Daniel Do Binau

    A huge thanks to Miguel to all his efforts in keeping this addon alive. But it seems that the time has now finally come to move on.

    I was very anxious at the thought of having to live without TGM which has been the cornerstone of all my browsing for years now. I have literally thousands of tabs in dozens of tab groups in three different profiles that I would need to migrate. The choice was between going to PaleMoon or finding a Chrome add-on that was up for the daunting task.

    After careful research I found that "Tabs Outliner" has everything I need to migrate from TGM and onto Chrome. It is an extremely flexible tool and in many ways even more powerful than TGM. It's VERY highly recommended. If memory usage is an issue, you can couple it with "The great suspender" which does something similar to the TGM "suspend group" feature. But unlike TGM, Tabs Outliner allows you to only open certain tabs within a group, so my memory usage has actually dropped very significantly after switching.

    Migrating everything was a bit of a hassle, and the add-on definitely has a learning curve - but now that I'm done, I'm happy (though nostalgic) to say goodbye to both TGM and Firefox.

  7. Lalo Martins

    I found neither Tab Outliner nor PaleMoon acceptable solutions. Currently trying Waterfox, so far seems promising (latest TGMR works as well as it always has).

  8. Miguel Angel Romero Lluch

    I will gladly support any necessary fix for the extension to work on browsers which still maintain the compatibility with legacy extensions. @James Ahlborn can you please open a new ticket with the description of your issue? IE, something like: "WaterFox - Issue with tab order.."

    Thanks.

  9. Shaun Sole

    Hi Miguel, are you planning to re-write the add-on or create a version for Chrome? If Chrome is easier I'm sure most of the TGM users will happily move over.

    Thanks

  10. Lalo Martins

    TGM is basically impossible with the Chrome extension API. The closest I've seen is using the Chrome app API to write pretty much a new browser.

    The Firefox WebExtension rewrite is another story, as it would AIUI be based on new features Mozilla is adding to the spec. But even then it's not yet clear if it will be possible.

  11. luckz

    The only truly killer feature you could get with nightly Firefox and current Chrome is real 'virtual tabs' that have near-zero RAM requirements when not loaded. API-wise, Lalo has stated everything there was to be stated.

    Mind you things like https://bugzilla.mozilla.org/show_bug.cgi?id=1322485 are only coded for multi-process Firefox, which TGM was never conceived for anyway. Waterfox 56 also is multi-process by default.

  12. Miguel Angel Romero Lluch

    It is impossible to migrate with the current API support offered in WebExtensions. There is no support for horizontal toolbars and no support for file writting. Also there is not a clear way to communicate information between tabs. Neither Mozilla nor Chrome has any scheduled plans to add support for those APIs, and any addons which were relaying on them, will not be able to migrate to WebExtensions for a long time, maybe years in the best case.

  13. Log in to comment