Eddy, I can't think of any reason, aside the fact that it's implementation-specific... ie. the implementation "decorates" fields that have validation errors with the type of error... but feel free to dive into the code. For me, what's important to note is that those "decorated" fields allow me to control what information is displayed when a valiation error occurs... for instance, using:
<!--B 'MANDATORY:foo'-->You gotta hit me with a foo :)<!--/B--> allows me to send that custom message to the user, when the mandatory object foo is not provided; failing to provide a value for that decorated field will just show "MANDATORY:foo" (not very useful) to the user. hth, -- eokyere On 11/28/05, Eddy Young <[EMAIL PROTECTED]> wrote: > Quoting Geert Bevin <[EMAIL PROTECTED]>: > > > Hi Eddy, > > > > Emmanuel pointed you in the right direction. > > > > About the form tags, take a look at this: > > http://rifers.org/wiki/display/RIFE/Forms > > > > Best regards, > > > > Geert > > > > PS.: RIFE/Crud actually doesn't do much at all beside automatically > > creating templates for you and providing an element structure, most > > of the functionalities are offered by RIFE itself > > Thanks, guys. While waiting for your replies, I dug around a bit and found > the solutions. > > Regarding validation identifiers, can you please explain the reasoning of > using the identifiers as the block names? For example, if > MANDATORY:username is the validation error returned, the corresponding text > block should be named MANDATORY:username ([!B 'MANDATORY:username'][!/B]. > > Regards, > Eddy > > ------------------------------------------------- > This mail sent through IMP: http://horde.org/imp/ > _______________________________________________ > Rife-users mailing list > [email protected] > http://www.uwyn.com/mailman/listinfo/rife-users > _______________________________________________ Rife-users mailing list [email protected] http://www.uwyn.com/mailman/listinfo/rife-users
