and is more likely to work when javascript is disabled ;) On 5/9/07, Langdon Stevenson <[EMAIL PROTECTED]> wrote: > > Hi Grant > > > Now, rather than describe what I have implemented for this, I am > > looking to hear what others have done in this situation. I don't want > > to taint your voices with my opinion, yet :P Surely there are a > > number of applications that have both a "plain HTML" and Ajax enabled > > version? Or you have a Flash frontend, but want to keep a simple HTML > > admin interface (to the same actions). > > I have found that when building web apps with Cake that use (and more > importantly make good use of) AJAX that I end up building specific views > and controller actions for the job. > > I have found that in the projects that I have built that there is little > benefit from having an AJAX and non-AJAX interface to the same function. > You can certainly do it, but personally I have found that the AJAX > functionality ends up too limited, or the plain HTML version is too complex. > > As a result I often prototype in regular HTML to get a feeling for the > job at hand, then revise the functionality with AJAX. > > This has the added advantage for me that I get two cuts at building the > functionality, so the finished result is usually better thought out. > > Regards, > Langdon > > > >
-- (the old fart) the advice is free, the lack of crankiness will cost you - its a fine line between a real question and an idiot http://blog.samdevore.com/archives/2007/03/05/when-open-source-bugs-me/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
