Yes, I believe it is. I was just hoping my template code was not going to become so messy. I'm not sure my resident web heads are going to take real well to this kind of syntax. I can see them glazing over already as I try to explain this ;-) This seams very laborious for what amount to very simple Create/Read/Update/Delete screens with regular expression/date format driven validation.
Thanks for your help on this. Jake -----Original Message----- From: Akmal Sarhan [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 19, 2002 11:31 AM To: Turbine Users List Subject: Re: DateString value="#if($group.get("$name").value && $group.OID!="_0")$!utilTool.formatDate($group.get("$name").value,$group.get( "$name").validator.DateFormats.get(0))#end" hope this is what you are looking for. Akmal ----- Original Message ----- From: "Jake Fear" <[EMAIL PROTECTED]> To: "Turbine Users List" <[EMAIL PROTECTED]> Sent: Thursday, December 19, 2002 8:25 AM Subject: Re: DateString > I have found one smal problem with this approach. When I want to use it > for unpopulated date input fields in a form I can not figure out how to > prevent it from showing $value in the empty fields. Anyone have any ideas? > > Akmal Sarhan wrote: > > >here is my own solution of this problem: > >in a pull tool called utilTool: > > > > public String formatDate(Date date, String format) > > { > > String d = ""; > > > > if (date != null) > > { > > SimpleDateFormat formatter = new SimpleDateFormat(format); > > > > d = formatter.format(date); > > } > > > > return d; > > } > > > >in the template: > > > >$!utilTool.formatDate($group.get("$name").value,$group.get("$name").validat o > >r.DateFormats.get(0)) > > > >where $group is the prepopulated intake group and $name is the DateString > >field name. > > > >this code will make it possible to update a date according to first rule in > >the intake.xml > >----- Original Message ----- > >From: "Jake Fear" <[EMAIL PROTECTED]> > >To: "Turbine Users List" <[EMAIL PROTECTED]> > >Sent: Tuesday, December 17, 2002 4:53 PM > >Subject: Re: DateString > > > > > > > > > >>That is precisely where I found out about the DateString. I have been > >>looking over the rest of the code as well, and I think there is key > >>feature missing from the org.apache.turbine.services.intake.model.Field > >>class. Maybe I am off the mark here, but it seems like there should be > >>some formatting abilities in the Field class. For example, right now I > >>have things working for reading in new dates and getting them set > >>correctly, but I have no way (that I know of) to control the format of > >>the date when it is rendered via an intake Group/Field. The same > >>capability would be very nice for currency, and maybe even user defined > >>types (maybe user defined types are a stretch given nature of input in > >>web applications;-). > >> > >>Jake > >> > >>Quinton McCombs wrote: > >> > >> > >> > >>>There is work being done to get intake updated. This will include > >>>updating the DTD. I hate to say this, but for now the best source of > >>>information for the field types is the source code for > >>>org.apache.turbine.services.intake.model.FieldFactory. > >>> > >>> > >>> > >>> > >>> > >>>>-----Original Message----- > >>>>From: Jake Fear [mailto:[EMAIL PROTECTED]] > >>>>Sent: Tuesday, December 17, 2002 9:26 AM > >>>>To: Turbine Users List > >>>>Subject: DateString > >>>> > >>>> > >>>>It DateString is missing from the default intake.dtd in the latest > >>>>turbine source. I added it locally and it seems to work just fine > >>>>(however, the Date type in the intake.xml did not). I noticed the > >>>>latest TDK does not have any intake examples, and the documentation > >>>>covers on the the most basic data types. Does anyone know if this > >>>>particular subcomponent is still being actively developed? > >>>> > >>>>Jake > >>>> > >>>> > >>>>-- > >>>>To unsubscribe, e-mail: > >>>><mailto:turbine-user-> [EMAIL PROTECTED]> > >>>>For > >>>>additional commands, > >>>>e-mail: <mailto:[EMAIL PROTECTED]> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>-- > >>>To unsubscribe, e-mail: > >>> > >>> > ><mailto:[EMAIL PROTECTED]> > > > > > >>>For additional commands, e-mail: > >>> > >>> > ><mailto:[EMAIL PROTECTED]> > > > > > >>> > >>> > >>> > >>> > >>> > >> > >>-- > >>To unsubscribe, e-mail: > >> > >> > ><mailto:[EMAIL PROTECTED]> > > > > > >>For additional commands, e-mail: > >> > >> > ><mailto:[EMAIL PROTECTED]> > > > > > >> > >> > > > > > >-- > >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > > > > > > > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
