[Catalyst] Meios: A Catalyst Photo Gallery Example

[Max Demian]

The best practice at this point is to have a fully functional
javascript-less/regular forms interface and have your javascript
library attach itself onload and override the onsubmit,etc. handlers
to make your page ajax-ified.

It's not a perfect solution by any means but it can be done fairly cleanly.

(Yes, it is nice to make intranet sites where you don't have to worry
about accessibility, no-javascript, no-css users etc. but...oh well)

On 8/19/05, Christopher H. Laco <claco at chrislaco.com> wrote:
> Matt S Trout wrote:
> > On Fri, Aug 19, 2005 at 02:26:01PM -0700, Adam Jacob wrote:
> >
> >>On Aug 19, 2005, at 1:57 PM, Christopher H. Laco wrote:
> >>
> >>>>It doesn't, by it's very nature as Javascript.
> >>>
> >>>Let rephrase that. I build some fancy forms that use AJAX. What is
> >>>the uer experience for the people without javascript? If the answer
> >>>is "the forms don't work for them", then that is bad.
> >>
> >>Right.  The way to do that would be to change the view you return to
> >>the user; one the ajax-ified, web 2.0 style interface, the other the
> >>normal get/post mechanisms we all know and love.
> >
> >
> > Any view system that can't do that automagically from a single set of
> > templates is insufficiently advanced.
> >
> > Watch This Space.
> >
> 
> Right.
> 
> #1. Browser sniffing on the server-side is flawed. Always.
> #2. Forms [and your site] should always work without javascript. Always.
>   [Well, with the exception of hardcore Intranets]
> 
> Any deviation from those two rules almost always leads to problems.
> Now client-side feature sniffing.. A O K.
> 
> -=Chris
> 
> 
> _______________________________________________
> Catalyst mailing list
> Catalyst at lists.rawmode.org
> http://lists.rawmode.org/mailman/listinfo/catalyst
> 
> 
> 
>