You are right this was sloppy on my part. Please add an issue and I'll put together a fix (which will have the ugliness of a new interface that starts with a deprecated method, but such is life).
On Mon, Mar 22, 2010 at 3:58 AM, Otho <taa...@googlemail.com> wrote: > Hi all! > > I migrated a project to Spring 3. To make it work with Tapestry I had to > upgrade to 5.2-Snapshot. > > Now I use RenderSupport.addScript(String scriptSnippet) and > RenderSupport.addScriptLink(String) quite a lot. > Both of them are deprecated and removed but the latter doesn't have a direct > counterpart in the new JavascriptSupport service. > > The JavascriptSupport.importJavaScriptLibrary(Asset asset) makes dynamically > building the script link tedious at least. > > I think this is quite a breaking change of the public API for a lot of apps > which use RenderSupport. > > Is this only a transitional effect due to the beta nature of 5.2, or are > these changes meant as final? > > If it is meant as final: Wouldn't it be better to deprecate the methods in > RenderSupport but keep them in for compatibility with legacy apps and hint > at the new JavascriptSupport for future projects and remove the deprecated > API only at the next major version? > > Regards, > Otho > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
