MozillaZine

Firefox & Thunderbird Add-on Converter for SeaMonkey

User Help for Seamonkey and Mozilla Suite
Lemon Juice
 
Posts: 777
Joined: June 1st, 2006, 9:41 am

Post Posted September 22nd, 2014, 1:41 pm

unbeleevabull wrote:OK, updated my list. I used the suggested url test and also reinstalled the ones that just showed an outdated SM version number.

Thanks, this list is good!

Okay, time for update of the compatibility list on the first page, thanks to all for sharing extension names.

Frank Lion wrote:https://addons.mozilla.org/en-US/firefox/addon/pagesaver/

Pearl Crescent Page Saver works after conversion, apart from a parsing error in prefs.xul which prevents this extension's options being accessed.

However, it still takes pics OK, both in 'Visible Portion' and 'Entire Page' modes, but only in .png (default) format. Not a problem for me, as I always use png for everything anyway - but without Options you will not get the usual .jpg alternative choice.

Again a common case of localizations being in different dtd files in Fx and SM. I've updated the converter so now Pearl Crescent Page Saver works fine along with its preferences!
*** SeaMonkey — weird name, sane interface, modern bowels ***
Mouse Gestures for SeaMonkey/Firefox
Convert Fx and TB extensions to SeaMonkey

LoudNoise
Moderator

User avatar
 
Posts: 40048
Joined: October 18th, 2007, 1:45 pm
Location: Next door to the west

Post Posted September 22nd, 2014, 8:10 pm

Lemon Juice wrote:However, I don't plan on spending too much time maintaining it since... (snip)


From the first page :)
Post wrangler
"Choose between the Food Select Feature or other Functions. If no food or function is chosen, Toast is the default."

Lemon Juice
 
Posts: 777
Joined: June 1st, 2006, 9:41 am

Post Posted September 23rd, 2014, 11:49 am

LoudNoise wrote:
Lemon Juice wrote:However, I don't plan on spending too much time maintaining it since... (snip)


From the first page :)

Hm, do you think I have exceeded what is regarded here as too much time? :mrgreen: Some patches for the converter are very easy now and follow the same pattern so if that's the case then it's a matter of minutes to add support for an extension like Pearl Crescent Page Saver :)
*** SeaMonkey — weird name, sane interface, modern bowels ***
Mouse Gestures for SeaMonkey/Firefox
Convert Fx and TB extensions to SeaMonkey

Anonymosity
 
Posts: 8513
Joined: May 7th, 2007, 12:07 pm

Post Posted September 23rd, 2014, 3:40 pm

Scarlettrunner20 wrote:Only a few of my extensions work now with the latest SeaMonkey. Yet SeaMonkey did not tell me the extensions would not work when I upgraded. Was this because most of the extensions were installed using SeaMonkey converter?

Do I need to use SeaMonkey converter again on these extensions? I would never have upgraded had I realized that few extensions would work including Ghostery (which is not one I used the converter on but is the most important extension I have).

SeaMonkey will not notify of updates to extensions for the "wrong" application, just as Firefox will not notify of theme updates for the "wrong" platform. I have to check manually (from the addons site) to see if those things are updated. The problem is probably related to that.

I have not had to use the converter again after updating SeaMonkey, for extensions that I converted to install there. Did you check the max version for the target application in install.rdf in the extensions? I bump up the max version before installing an addon to make sure that I will not have a problem after installing a new version of SeaMonkey. You can do that with the converter. I use a max version of 3.*. Your first problem is probably also related to that.

tonymec

User avatar
 
Posts: 717
Joined: October 15th, 2004, 2:58 am
Location: Ixelles (Brussels Capital Region, Belgium)

Post Posted September 23rd, 2014, 4:30 pm

Anonymosity wrote:
Scarlettrunner20 wrote:Only a few of my extensions work now with the latest SeaMonkey. Yet SeaMonkey did not tell me the extensions would not work when I upgraded. Was this because most of the extensions were installed using SeaMonkey converter?

Do I need to use SeaMonkey converter again on these extensions? I would never have upgraded had I realized that few extensions would work including Ghostery (which is not one I used the converter on but is the most important extension I have).

SeaMonkey will not notify of updates to extensions for the "wrong" application, just as Firefox will not notify of theme updates for the "wrong" platform. I have to check manually (from the addons site) to see if those things are updated. The problem is probably related to that.

I have not had to use the converter again after updating SeaMonkey, for extensions that I converted to install there. Did you check the max version for the target application in install.rdf in the extensions? I bump up the max version before installing an addon to make sure that I will not have a problem after installing a new version of SeaMonkey. You can do that with the converter. I use a max version of 3.*. Your first problem is probably also related to that.


See also this KB article about overriding the compatibility check manually, and read the examples. The Nightly Tester Tools and (for Firefox) Add-on Compatibility Reporter extensions have "friendlier" UIs than about:config to disable that check. Of course, if you disable compatibility checking and an extensions starts to misbehave, it becomes your job to disable it manually.
Best regards,
Tony

Lemon Juice
 
Posts: 777
Joined: June 1st, 2006, 9:41 am

Post Posted September 23rd, 2014, 5:33 pm

Compatibility check (maxVersion) is not a problem in the majority of cases because extensions whose maxVersion is 2.1 or higher for SM (or 4 or higher for Fx) are compatible by default so even if maxVersion is 2.26 the addon will still work after upgrading SM to 2.29. Converted addons are (by default) compatible with 2.* versions so this covers all possible 2.x releases and potentially 3.* releases too by the "compatible by default" rule. There are some rare exceptions to this rule like extensions with binary components or themes that strictly obey maxVersion.

That's why it is not necessary to disable compatibility checking for the converted extensions to work nor to bump their maxVersion. If they stop working then it's for some other reason.
*** SeaMonkey — weird name, sane interface, modern bowels ***
Mouse Gestures for SeaMonkey/Firefox
Convert Fx and TB extensions to SeaMonkey

patrickjdempsey

User avatar
 
Posts: 23734
Joined: October 23rd, 2008, 11:43 am
Location: Asheville NC

Post Posted September 23rd, 2014, 6:17 pm

Hmm. Any extension may choose to have strict compatibility if the <em:strictCompatibility>true</em:strictCompatibility> property is set in the install manifest. Might be something worth checking for and removing if discovered.
Tip of the day: If it has "toolbar" in the name, it's crap.
What my avatar is about: https://addons.mozilla.org/en-US/seamonkey/addon/sea-fox/

tonymec

User avatar
 
Posts: 717
Joined: October 15th, 2004, 2:58 am
Location: Ixelles (Brussels Capital Region, Belgium)

Post Posted September 23rd, 2014, 8:40 pm

patrickjdempsey wrote:Hmm. Any extension may choose to have strict compatibility if the <em:strictCompatibility>true</em:strictCompatibility> property is set in the install manifest. Might be something worth checking for and removing if discovered.


If they have it, it's often for a very good reason, such as binary components which require a particular XPCOM version (as in Lightning).
Best regards,
Tony

patrickjdempsey

User avatar
 
Posts: 23734
Joined: October 23rd, 2008, 11:43 am
Location: Asheville NC

Post Posted September 24th, 2014, 2:30 am

I'm not talking about those. I'm talking about regular extensions. The reasons these restrictions may exist is usually because of Firefox interface changes. For instance, there are probably a few extensions floating around right now that have strict compatibility set so that someone doesn't install it into a pre-Austrailis version.
Tip of the day: If it has "toolbar" in the name, it's crap.
What my avatar is about: https://addons.mozilla.org/en-US/seamonkey/addon/sea-fox/

Lemon Juice
 
Posts: 777
Joined: June 1st, 2006, 9:41 am

Post Posted September 24th, 2014, 6:24 am

patrickjdempsey wrote:Hmm. Any extension may choose to have strict compatibility if the <em:strictCompatibility>true</em:strictCompatibility> property is set in the install manifest. Might be something worth checking for and removing if discovered.

But as I understand it - if maxVersion is set to 2.* then strictCompatibility should not cause problems in any branch of SM 2.x.x, right?
*** SeaMonkey — weird name, sane interface, modern bowels ***
Mouse Gestures for SeaMonkey/Firefox
Convert Fx and TB extensions to SeaMonkey

Frank Lion

User avatar
 
Posts: 20059
Joined: April 23rd, 2004, 6:59 pm
Location: ... The Exorcist....United Kingdom

Post Posted September 24th, 2014, 1:03 pm

Lemon Juice wrote:
Frank Lion wrote:https://addons.mozilla.org/en-US/firefox/addon/pagesaver/

Again a common case of localizations being in different dtd files in Fx and SM. I've updated the converter so now Pearl Crescent Page Saver works fine along with its preferences!

Many thanks.
Metal Lion latest SeaMonkey & Thunderbird Themes - Sea Monkey and Silver Sea Monkey
"The only thing necessary for the triumph of evil, is for good men to do nothing." - Edmund Burke (attrib.)

tonymec

User avatar
 
Posts: 717
Joined: October 15th, 2004, 2:58 am
Location: Ixelles (Brussels Capital Region, Belgium)

Post Posted October 2nd, 2014, 8:58 am

Lemon Juice wrote:
patrickjdempsey wrote:Hmm. Any extension may choose to have strict compatibility if the <em:strictCompatibility>true</em:strictCompatibility> property is set in the install manifest. Might be something worth checking for and removing if discovered.

But as I understand it - if maxVersion is set to 2.* then strictCompatibility should not cause problems in any branch of SM 2.x.x, right?

The intended use of strictCompatibility is for extensions where the author knows for a fact that one of the very next versions, or maybe one already at the trunk or aurora stage, will be incompatible with the extension. "Normal" extensions should let the default-to-compatible feature do its stuff.
And yes, 2.* means everything until, but not including, 3.0 (if 3.0 ever happens). The problem it might cause is if it's too lax (we're now at 2.32a1; even with strictCompatibility, an incompatible change at, let's say, 2.45 won't be caught if the maxVersion is 2.*).
Best regards,
Tony

Andy Boze

User avatar
 
Posts: 2755
Joined: June 30th, 2005, 9:53 pm
Location: South Bend, IN

Post Posted October 8th, 2014, 11:08 pm

I was sad to find that the JSView extension no longer works with SM 2.30. I came across an article that mentioned a similar extension for Firefox called Phoenix. I thought I'd mention that it seems to work just fine with SM after running it through the wonderful Add-on Converter.
But then again, I may be wrong.

therube

User avatar
 
Posts: 19046
Joined: March 10th, 2004, 9:59 pm
Location: Maryland USA

Post Posted October 9th, 2014, 7:53 am

Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript

Andy Boze

User avatar
 
Posts: 2755
Joined: June 30th, 2005, 9:53 pm
Location: South Bend, IN

Post Posted October 9th, 2014, 11:50 am

Thanks! I like the Phoenix extension, but it's overkill for my needs. Glad to have JSView functioning again.
But then again, I may be wrong.

Return to SeaMonkey Support


Who is online

Users browsing this forum: No registered users and 2 guests