RE: [CFCDev] UI and encapsulation

[Baz]

Hey Phil,   I’d be curious to take a look at a complete example of this, with the parser and everything… is that possible?   Cheers, Baz     From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Duba, Phillip Sent: Friday, January 20, 2006 12:43 PM To: CFCDev@cfczone.org Subject: RE: [CFCDev] UI and encapsulation   Here’s what I use in the application I was referring to in yesterday’s thread on this same/similar subject (hope this goes through) :   <Field Label=”Some form Label” Type=”Text,Select,Radio,etc.” Required=”Page/Group” DestinationTable=”TableName” DestinationField=”FieldName” ChildFields=”ChildField1,ChildField2” ParentField=”ParentField1” Size=”” MaxLength=”” Datasouce=”QueryName” Validation=”Date,Numeric” />   Ok now to answer questions that will come up with what do things mean: -          ChildFields: these are form fields dependent on this one. They are only available in select boxes and the selected value of this field drives the available options of the Child form fields -          ParentField: the field whose selection drives the available options of this select box -          Required: Validation necessary for form submittal. The Page indicates the field is required to submit the form. The Group indicates that if other members of the Group (a parent-tag to field) are filled in, then this field is required to submit the form. -          Datasource: a parent field called Query is defined with a name attribute and that’s what is here.   I hope that help or at least gets you thinking on how you might want to implement a schema yourself. This XML is built using web-based tools that a user (administrator in this case) has access tools to defined pages/groups/fields of this wizard-based application. Thanks,   Phil   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Seth Petry-Johnson Sent: Friday, January 20, 2006 12:32 PM To: CFCDev@cfczone.org Subject: Re: [CFCDev] UI and encapsulation   Baz:  I've never actually done this before, I'm just spouting off ideas from the top of my head :)   And just to make sure we're on the same page, I wasn't suggesting that the XML itself display the form.  Rather, I was suggesting that XML be used to describe the form's metadata and a rendering component would read the XML and create the actual HTML form tags.  [I couldn't tell from your question if I'd made that sufficiently clear or not, so I thought I'd clarify just in case]   On 1/20/06, Baz <[EMAIL PROTECTED]> wrote: Hey Seth,   Can I see an example of some XML you have generated to display a form?   Curious, Baz     ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to cfcdev@cfczone.org with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/cfcdev@cfczone.org ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to cfcdev@cfczone.org with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/cfcdev@cfczone.org ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to cfcdev@cfczone.org with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/cfcdev@cfczone.org