There are currently no plans for any major refactoring, sorry. I completely understand your situation, and use JSLint myself on every project. The current SWFObject codebase is well-established, well-tested, and optimized for compression, so any potential benefits from refactoring the code purely for passing JSLint would be offset by the potential introduction of bugs and/or increased file size.
However, we'd still like to hear any suggestions you may have for improvements. You can post enhancement requests on the SWFObject issues list at http://code.google.com/p/swfobject/issues/list - philip On Tue, Jan 4, 2011 at 1:59 PM, Michael Behan <[email protected]> wrote: > I have run the latest SWFObject (packed and unpacked) through JSLint > - and there is quite a larger number of errors generated. > Unfortunately - these means I cannot use SWFObject on my project > because part of our build process involves JSLint. Are there plans to > make this code pass in JSLint again? > > Thanks a lot > Michael > > -- > You received this message because you are subscribed to the Google Groups > "SWFObject" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<swfobject%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/swfobject?hl=en. > > -- You received this message because you are subscribed to the Google Groups "SWFObject" 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/swfobject?hl=en.
