On 07/20/2011 12:16 PM, Chris Conroy wrote: > Agreed these are serious issues facing the FF plugin. For the moment, > we're doing a little bit of wait and see to see if this new release > strategy (specifically the forced rebuild of all extensions) actually > sticks. If it does, we'll certainly need to retool how we spin plugin > builds for new versions of Firefox. > > The size issue will definitely be a problem. In anticipation of that, > we've reduced the compiled output size considerably by turning off some > debug flags, and our plugin supporting 3.0-5.0 clocks in at just 2.0MB. > Long term, we'll probably need to fashion some kind of split binary or > revisit the notion of having every version supported in a single xpi. > > Short term, the unsatisfying answer that I can give to you is that we > will lag Firefox's release schedule. If you rely on the Firefox GWT > DevMode plugin, be sure to keep an instance of a known working version > of firefox around for your development.
It might also be worth contacting Mozilla Developer Network with feedback on this issue. I'll certainly write an email message to Someone, Somewhere on this topic. Also, there was some announcement on one of the Mozilla blogs about a "Mozilla Enterprise" something-or-other panel. As it wasn't open to Mere Mortals it didn't seem interesting to me. It may be worth contacting them on this "keeping up with the Joneses" strategy they seem to have adopted. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
