I like the idea that others are going out and trying to find ways to 
integrate the goodness of SWFObject into other frameworks and 
usage-scenarios.  That's good for everyone all around.

However, I think (in my humble opinion) that re-implementing SWFObject 
behavior wholesale entirely is perhaps not a good idea, because as Bobby 
points out, you'll have support and compatibility problems as SWFObject 
moves forward and diverges from the branch you created with your own 
implementation.

CheckPlayer (http://checkplayer.flensed.com/) is a project I started that 
attempts to augment some of SWFObject's functionality. The strategy I took 
was to include the entire SWFObject distribution, as-is, and then provide an 
additional API-set that wraps up some of SWFObjects methods to accomplish 
various tasks.  Granted, there were a few non-public-API parts of SWFObject 
that I had to duplicate, such as the browser/plugin detection code, and the 
expressInstall logic.  But even still, 100% of SWFObject official release is 
used behind the scenes (nothing hacked or replaced), which makes things much 
more reliable, not only for myself, but for any authors that use my code. 
They get the benefit of my library, with the additional flexibility to use 
the core SWFObject API (the rock-solid, tested distribution) in various 
cases where it makes more sense to them (static publishing, for instance).

I say all that to suggest, perhaps your strategy with your jQuery plugin 
could be to provide a jQuery'esque API, but under the covers, still call 
SWFObject API functions.  In doing so, I think you could get the best of 
both worlds (like I tried to do), and I think you'll end up having the two 
projects play more nicely with each other, especially as each project 
advances with new releases down the road.

Also, I think your plugin will be significantly more simple to implement, as 
your only goal would be to provide jQuery style function calls that match up 
to the various SWFObject API functions, not having to re-invent the 
SWFObject wheel.  :)

Just some thoughts.

--Kyle




--------------------------------------------------
From: "Jonathan" <[EMAIL PROTECTED]>
Sent: Monday, October 13, 2008 3:17 PM
To: "SWFObject" <[email protected]>
Subject: jQuery SWFObject Plugin

>
> Hey all,
>
> I've been working on a jQuery port of the SWFObject library.  The goal
> is thus far:
>
> What is the jQuery SWFObject plugin?
> The jQuery SWFObject plugin is an addon for jQuery that offers all the
> unique functionality of SWFObject while replacing and upgrading the
> internal functionality with those already available through jQuery.
>
> And what is SWFObject?
> SWFObject is an easy-to-use and standards-friendly method to embed
> Flash content.
>
> And what is jQuery?
> jQuery is a small but power-packed bundle of javascript functions that
> make writing javascript quick and simple. Selecting elements on your
> page is like using CSS, learning and using functions requires minimal
> fuss, and the learning curve is sometimes described as "zero".
>
> What's difference between this plugin and regular SWFObject?
> First, it's smaller. Where SWFObject needs to create its own
> selectors / DOM loaders / and the like, that functionality has been
> removed and replaced with jQuery's pre-existing ones. Then, it's
> faster. There's little argument that jQuery's functionality is about
> as fast as complaint javascript can get, so now you get these same
> performance benefits in SWFObject. Finally, it's easier. Code looks
> cleaner with jQuery, and it's almost always easier to read and get
> what's going on. Having the power of SWFObject and the environment of
> jQuery is a best-of-both-worlds scenario.
>
> The project page is currently @ http://jquery.thewikies.com/swfobject/
>
> I pass the entire swfobject test suite @ 
> http://jquery.thewikies.com/swfobject/testsuite/
> but there are still many jQuery optimizations that I would like to
> make within the script.
> >
> 

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to