Kevin On Mon, 11 Aug 2003 09:42:23 +0100, kevin furze <[EMAIL PROTECTED]> wrote:
>the comment about CSR tags is interesting, are you saying you have an >individual CSR for every element, can you give an example, something like <csr:rule name="XISINPUT" match="FORM/*/INPUT" language="any"> will match all input tags within a form tag any more will cost you :} but you can take a dekko at the ISC rules - that was my starting point >and the idea of ProxyClass, you say a neat one, I assume you have the >equivalent of Field1, Field2, Field3 . . . as properties and then >load/unload as required? Yup again through csr's and does the ..EscapeHTML automatically, plus population of select's also the csr's fiddle with the attributes so I only have to type the property name in the name box - everyting else is done - no #()# it takes too long to type - and any mistyping fails at compile time Also allows for error message display underneath any field that is incorrect <snip> > >out of habit, clear directories sperate the images from the rules from >the csp pages from the javascript and so on. I make use of sub directories for different parts of the app > >kevin > > >Peter Cooper wrote: >> >> Kevin and Sukesh >> >> I have used many approches - except using the form wizard >> >> The COS approach leads to very fast development but is not easily >> accssible for a designer >> >> Doing a lot in the CSP page leads (In my mind) to a difficult to read >> set of pages that mix logic and design stuff >> >> The system that I am currently using is >> >> a) my own CSR tags >> these match *all* form/formobject tags by default rather than ony >> those that have a cspbind attribute >> this means that I can use Dreamweaver to design the layout and all the >> form logic is automatic - I can turn off the binding with an attribute >> "xisnobind" >> >> b) DW to design the pages >> also using DW templates to have a consisten design and css to control >> the look and feel >> >> c) Includes >> Good stuff but have some complexaties like >> i. calling from different directories is a bit difficult >> ii if the include is a self contained form then where should the post >> logic go >> >> d) Subclass of %CSP.Page >> to add my own functionality >> >> e) Proxy classes for the form processing >> this is a neat one (I think) >> The CSP form holds the display - it has a parameter "ProxyClass" >> the processing "OnCancel" "OnPost" etc etc is done here >> the SuperClass of the pages picks up the proxyclass and dispatches to >> it >> >> f) Proxy classes are persistent >> keyed by the sessionID - this allows me to keep the temporary data >> between pages in these classes rather than the %session object >> >> ======= >> So what I have ended up with is a clear (well 99%) separation between >> the design (DW) and the code (ProxyClasses) >> >> >> Peter >
