Nope...Not for this at least...Maybe I should add a big warning sign somewhere in the 4.1 docs. I'm very much ok with breaking backwards compatibility for this particular piece of functionality....It was a great idea at the time, but caused many headaches for me in tacos - and also is considered very very bad programming practive in js. (hence my hatred/distrust of prototype...you can easily find when people started using it more by searching through jira and finding comlaints about the DatePicker in tap not working anymore...changing runtime behaviour of native objects is not ok..)
I have gone to great pains to provide backwards compatible versions of all the other Tapestry.<foo> functions though..(ie you can also submit forms via Tapestry.submit_form() ...something like that..dopn't remember the old function name right now) On 9/7/06, D&J Gredler <[EMAIL PROTECTED]> wrote:
Hi, In Tapestry 4.0 I was using the following JS in a button's onclick handler to cancel a form: "this.form.events.cancel()". I believe this has been replaced with "tapestry.form.cancel(this.form)". I was using the following JS in another button's onclick handler to refresh a form: "this.form.events.refresh()". I believe this has been replaced with "tapestry.form.refresh(this.form)". (Please correct me if any of the above is wrong) What javascript can I use to be compatible with both 4.0 and 4.1? Is it possible? Thanks, Daniel
-- Jesse Kuhnert Tapestry/Dojo/(and a dash of TestNG), team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
