QuickProxy 2009.07.19 Approved!

The 3.5.* compatibile release of QuickProxy has finally been approved by the Mozilla editors, after 6 weeks from the initial release. I hope that the time that this took isn’t going to remain for any future versions that are submitted, specifically for versions that are required for future firefox releases. Those using the previous versions should now be able to auto-update to the latest version through Firefox, or you can get it manually by going here.

I wish to thank all my users for being patient while this process ensued, as I wish there was more that I could do to get it pushed through Mozilla’s approval process.

This does bring some good news, as since the release is now public I can begin development and submission of new versions of QuickProxy, allowing me to work on some of the features that I’ve wanted to implement. I held off development while waiting for this to be approved, as last time I went ahead with dev work the extension got knocked back due to the code structure, and I had to re-write and re-test what I had planned anyway.

I want to give a big thank you to all the people that have donated to the extension through the Mozilla website. I initially developed the extension with no expectations of anything in return for the work, so just the fact that some of the users have found value in this extension has made me feel that I’ve accomplished my initial goals with the extension.

Monday, August 31st, 2009 QuickProxy

7 comments on “QuickProxy 2009.07.19 Approved!”

  1. Optimizer says:

    Ozzie, thanks for all of your hard work. Regrettably, even after updating things, my installation of Firefox 3.5.2 is still reporting that QuickProxy is incompatible. 🙁

  2. Optimizer says:

    Looks like I jumped the gun: I installed the update, restarted Firefox and obviously had no luck. I ran an update search again; Firefox then reported it would update on restart. Restarted and voila, everything’s fine. I think the problem was with my system: For some reason, I constantly have a problem where Firefox won’t quit properly, necessitating me to kill its process and start over …

  3. FOverman says:

    Thank you Ozzie!

    I had used another proxy that was not all that user friendly. I so like that I can click and it’s on, click and it’s off.

    I had put off upgrading to FF 3.5 until this was ready, rather than do without it or go to another proxy program.

  4. Searcher123 says:

    Thank you very much for your good work. I worke with your add-on for a long time under FF 3.0.x without any problem and I love it, but under FF 3.5.3 I have seen a strange behavior of QuickProxy in associated with another add-on called “MultiProxy Switch”.

    Under FF 3.0.14 when I was activated a proxy with “GProxy”, the color of your add-on’s icon was changed to green (well, it must be so). But under FF 3.5.3, when I activate a proxy with “MultiProxy Switch”, the color of your add-on’s icon will not be changed at all! It is a problem of your add-on or “MultiProxy Switch” add-on?

    • Ozzie says:

      Currently my addon doesn’t play as nicely as I would like with other proxy modification extensions. The time that it checks for whether the preferences have changed is only run when you focus on the window. I’m playing around with event listeners and the like to see if I can nicely hook into the proxy settings, and update the icon on change, but I’m not having much success with the little free time I have to work on the extension.

      Once this change has been implemented it should be fine to use it with other proxy modifying extensions, but until then to make sure that QuickProxy is displaying the correct proxy type you will need to click on another window, and then click back into FireFox to trigger the detection.

  5. rb says:

    do you have plans to update to 3.6 or 3.7? I’ve manually tweaked my version string so I can test it in 3.7. looks fine, it would just be nice to have the plugin changed instead of doing it myself.

    • Ozzie says:

      Currently I’m working on a closed beta that will have the new version strings in it. I’m trying to get the preferences hooks to work before I release it, although if I can’t get it to work soon then I will release an updated version with the detection as is.

Leave a Comment