-
Notifications
You must be signed in to change notification settings - Fork 25
Detect on install which os the addon gets installed to #135
Comments
I agree. It is a mess. Unfortunately, there is no super easy way how to make it more clear. Let's keep it open and maybe I will figure something out in the near future... |
Detecting the needed information should be possible regarding this:
and
I'm not a developer or such... you need to double check and validate for sure. But it sounds reasonable, there are many more variables listed on that page which might be helpful in that case. The addon then would need to display only options which are relevant to the app and os the addon is installed to (which equals to hiding others). That might be a different problem. I don't know. What do you think? Anyway, I appreciate that you are aware of this and that you keep it in mind.^^ |
Thank you for the hints. The problem is that for the preferences I decided to use built-in FF mechanism. I just defined various options using package.json file and FF is responsible for the presentation. Unfortunately with this approach, there is no place where I can insert some code that will hide/show options etc. :-( I see two potential solutions:
|
Oh, ok. That makes sense... The second options sounds like a mess though, and much work to maintain and supply properly. I have several small addons that have their own settings dialog. It's pretty straight forward to use from a user point of view. I found this on how to create such a options dialog window:
|
About this issue, maybe you could ask for help from the developer of the Classic Toolbar Buttons extension? That extension also uses the built-in FF mechanism, and the options are diferent depending on whether the addon is installed on Firefox, Thunderbird or SeaMonkey. |
Now with this add-on beeing Thunderbird only (#162) you can remove a lot of the |
Display/hide settings in options accordingly and don't mess around with the user too much. :D
On Firefox (win+mac) for example 80% of settings are not relevant...
The text was updated successfully, but these errors were encountered: