Hello again!
Many users have informed me of bugs in the new click engine, which is totally awesome because I very rarely get feedback about most new features and about ThunderBrowse in general.
So here’s ThunderBrowse 3.2.6.4, a new version that fixes a lot (if not all) of the bugs introduced in 3.2.6.2. Granted, these are all the bugs that I know of that have been reported by users.
Here’s what has changed:
- onSubmit is now an opt-in feature (because it’s beta and doesn’t work extremely well). If you want to use onSubmit, go to about:config and change extensions.tbrowse.onsubmiton to true. I suggest you create a custom button if you are going to be using this feature a lot.
- Wizard tab options have been fixed.
- Fixed conflicts with extensions that use gestures.
- Fixed settings not saving in the Settings window.
- Made external-default reset to true on uninstall.
Very few other things have been changed.
Summer of Funding is still going well but it looks like Thunderbird 3 tabs is the only thing going into 3.2.7, which isn’t a bad thing.
[...] Developers « Announcing ThunderBrowse 3.2.6.4 [...]
Hard to read, and unclear — what do you mean
“onSubmit is now an opt-in feature (because it’s beta and doesn’t work extremely well). If you want to use onSubmit, go to about:config and change extensions.tbrowse.onsubmiton to true. I suggest you create a custom button if you are going to be using this feature a lot.”
onSubmit? What’s that? When I press ‘send’?
Wizard tabs options been fixed? (sometimes you know your context, but I’m not exactly clear about what feature you are referring to — I may know the feature, but I’m just not getting what feature on what page you are talking about…other times, I’ve no clue what you are talking about even if you weren’t using ‘jargon’…(note: jargon = language internal to the subject area you are working in, or specialized language within the group you are working with; i.e. not necessarily bad, BUT, someone outside of your group or not familiar with the technical terms of the topic matter may not know, but might understand if they knew what you mean…:-))
>>NOTE<< — whatever you do on "uninstall", please be sure to also do it on "disable" — I've been bitten by this with more than one extension — I often disable it first:
1) if I think I don't need it and my ~100 or so extensions are slowing down my browser (or Tbird, or Songbird) too much, OR
2) if I think it may be interfering with another extension I use more, OR
3) trying to debug a problem, OR
4) don't need it 'right now', but want to keep it around for later usage…
So what has happened with more than one extension, is that I disable it due to some problem. It is
turned off, I realize part or most of the problem went away (or sometimes I have to use 'Safe-mode' to reset my interface, whatever), but then, later, I realize I really don't need or want that extension around — and I certainly don't want to re-enable it if it has been causing problems — well the problem there is that it doesn't do it's cleanup on uninstall, if it was already in the disabled state.
So really — all extensions need restore any changes they've made to the UI and store their settings for later "restoration", when (or if) the user re-enables it. If the user uninstalls, then all is good since settings were restored to their pre-addon-install state. It would be the 'most' user friendly, to store any custom settings of the tool into 1 key (in prefs/conig) on 'disable', to minimize space in the prefs DB. Then on re-enable, the prefs could be read out of that key and auto-reapplied, so I wouldn't have to reconfig.
If an app(er, addon) gets uninstalled, it should do similar. Right now, when apps get uninstalled, MANY leave their settings, 'as is' in the user's prefs/config file. This grows with no 'good' way to delete old prefs. If the app-writer really feels they want to leave around the old values, they should compact them into 1 key on app removal (or disabling) and store the config-ops there. They, _certainly_ shouldn't just leave their "turds" all over the users "registry" (prefs.js/about:config data), "for ever".
Really poor form, IMO — as bad as ill-mannered windows applications that people complain about not cleaning up after themselves.
delete anything out of the users config/prefs that it stored, and store the info into a 'extensions.uninstalled..saved_settings’ key so if user later reinstlls, they could pick up where they left off
(should user later ‘re-enable’, I know I’d like to see the tool automatically reapply its setting from the last time I used it)
You'll notice that the onSubmit part has been crossed out meaning that you don't have to worry about it at all. The wizard tabs (which refers to the page in the wizard that deals with tab options) had a bunch of bugs fixed, if you are already a user, you don't need to worry about it.
And about disabling, I'll keep in mind to reset a few things (like homepage and link blocker) but that's pretty much about it. When ThunderBrowse is uninstalled, it deletes all the ThunderBrowse prefs and attempts to change the start page back.
My favorites browsers are Firefox and Thunderbird. Good work! Thanks!!!