[Seaside] Best practice: what actions in form callback: vs. in onChange: | onClick: | on...

John Thornborrow john at pinesoft.co.uk
Tue Jan 15 10:08:05 UTC 2008

Semantically, that entirely depends on if you want the page to refresh
or not i.e. submit via normal post/get or via XmlHTTPRequest - but you
"should" accommodate for both scenarios in case the user agent does not
have JavaScript functionality.


itsme213 wrote:
> Some actions have fairly clear places e.g. if they need form values, or a 
> rendering canvas or script to write on.
> Other actions like model updates I am able to locate in many different 
> places.
> As good design, what kinds of actions should be done in <A> vs. <B> below?
> e.g.
>     html select
>         ...
>         callback: [:val |  <A> ]
>         onChange: (html updater
>             ...
>             callback:[ <B> ])
> Thanks - Sophie
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Pinesoft Computers are registered in England, Registered number: 2914825. Registered office: 266-268 High Street, Waltham Cross, Herts, EN8 7EA

This message has been scanned for viruses by BlackSpider MailControl - www.blackspider.com

More information about the seaside mailing list