Backwards Compatibility
July 25, 2008 - 7:42am — shellscape
Like any other developer, I really appreciate that this component is free and open. However keeping up to date has proven to be a maddening task. It seems that every new release of this component requires review and fixing of the js we've written to work with SWFUpload. Core functions are moved, renamed or their functionality changed.
Now, I realize that this isn't a full time gig for the developers, and again that it is completely free. However I'm having an increasingly difficult time justifying the time that I have to spend to bring my scripts up to date with each new update.
Please have some mercy on us users/developers and either keep some fallback js in your classes or provide some method of backwards compatibility!
API
We have tried to keep the API consistent within each major release.
The API for the "revisions" was eratic. However, that was an unsupported fork under rapid experimental development. So...there you have it.
Since the v2 API was released there have only been additions to the API while we've avoided changes or deletions unless there was bug or inconsistency which required a change but these should be rare. We've tried to stay fairly stable.
Expect big changes in SWFUpload v3 when we move to Flash Player 10 compatibility.
(Disclaimer: development on v3 has not begun yet so don't hold your breath)