I've found a similar extension that is setup for the new extension model: https://addons.mozilla.org/en-US/firefox/addon/hccbe-google%E3%83%96%E3%83%83%E3%82%AF%E3%83%9E%E3%83%BC%E3%82%AF%E6%8B%A1%E5%BC%B5/
I haven't found any missing features from GMarks - but I mainly used the simplest feature-set, aside from setting up the path separator for tags. On Tue, Sep 5, 2017 at 4:37 PM, Jammer <[email protected]> wrote: > Fellow Gmarks users, > > I learned recently that Mozilla has changed the way extensions will need > to be written. Based on my understanding of the information from Mozilla, > starting with FF release 57 (to be released in Nov. 2017) the only > extensions that will work are extensions that have been rewritten to follow > their new WebExtensions framework. This means that unless Gmarks is > migrated to this new framework, this beloved tool will cease to work. I > wonder if there is any super programmers in our community that would like > to take on the challenge of helping to migrate this awesome tool to the new > framework. > > The written text from Mozilla is posted below (and here is the link if > you'd rather go to the official page: https://support.mozilla.org/ > en-US/kb/firefox-add-technology-modernizing?as=u&utm_source=inproduct): > > > Firefox add-on technology is modernizing > > Add-ons > <https://support.mozilla.org/en-US/kb/find-and-install-add-ons-add-features-to-firefox> > allow you to add extra features and functionality to Firefox, modify the > Firefox user interface and change its appearance. There are several types > of add-ons but extensions are the most common. Anyone can create an > extension and make it available for download. > > > What's happening? > > In the past, add-ons often stopped working each time a new version of > Firefox was released, because developers had to update them every six weeks > to keep them compatible. Since add-ons could also modify Firefox internal > code directly, it was possible for bad actors to include malicious code in > an innocent-looking add-on. > > > To address these issues, and as part of broader efforts to modernize > Firefox <https://blog.nightly.mozilla.org/> as a whole, we’ve been > transitioning > <https://blog.mozilla.org/addons/2015/08/21/the-future-of-developing-firefox-add-ons/> > to a new framework for developing Firefox extensions. Outside of rare > instances, add-ons created with the new standard, called WebExtensions > <https://developer.mozilla.org/Add-ons/WebExtensions/What_are_WebExtensions>, > won’t break in new Firefox releases. You can still personalize Firefox with > add-ons the same way you do now, except they won’t break in new Firefox > releases. > > > *Note:* Starting in Firefox 57, which will be released in November 2017, > only add-ons built with this new technology will work in Firefox. These are > indicated by the "Compatible with Firefox 57+" label on addons.mozilla.org > (AMO). Add-ons built with the old technology are labeled "Legacy" in the > Add-ons Manager (about:addons) tab. > > If an add-on does not have the "Compatible with 57+" label or has the > "Legacy" label, the developer may be in the process of transitioning to the > new technology. > > We are aware that certain add-ons will not be transitioning to the new > standard; we will continue to assist developers to the fullest possible > extent. As we get closer to November, we will suggest suitable replacements > of add-ons not making the transition. > > > If you are a user of Firefox Nightly, please note that Firefox 57 reached > the Nightly channel <https://www.mozilla.org/firefox/nightly/all/> on > August 2, 2017. Legacy add-ons will be disabled, but will be enabled again > if the developer releases a compatible update. > > > In the meantime, you can check if an add-on is planned for migration > <http://arewewebextensionsyet.com/#addons> (popular add-ons only), look > for alternatives > <https://discourse.mozilla-community.org/t/favorite-webextensions/17087/3> > or reach out to the developer to inquire if they will migrate their add-on. > You may find developer contact information on the right side of the add-on > listing on AMO. > > > *We recommend that you install add-ons with the "Compatible with Firefox > 57+" label to ensure compatibility with Firefox beyond November 2017.* > > If you are the developer of a legacy add-on, resources are available > <https://wiki.mozilla.org/Add-ons/developer/communication> to help you > migrate to the new standard. > > > Best regards. > > -- > You received this message because you are subscribed to the Google Groups > "GMarks" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/gmarks. > For more options, visit https://groups.google.com/d/optout. > -- Thomas Harning Jr. (http://about.me/harningt) -- You received this message because you are subscribed to the Google Groups "GMarks" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/gmarks. For more options, visit https://groups.google.com/d/optout.
