Jarno, I see your point, and having the ability do define a attribute that has some kind of collection as a value is really helpful sometimes. Therefore, instead of <abc xyz="s,t,u"/>
we could write: <abc> <attr name="xyz">s</attr> <attr name="xyz">t</attr> <attr name="xyz">u</attr> </abc> However, I would not go that far and cascading this approach, giving attributes their own attributes. This is definitively NOT the final word on this and I would like to encourage everyone to voice their opinion. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] > Sent: Wednesday, April 09, 2003 2:17 AM > To: [email protected] > Subject: [Forum] Re:Another way to express attributes? > > > Hi (again), > > The example I enclosed in previous mail was not good. Maybe this > is better? > > <formattedtextfield id="pnlDetailBasic_pidDate"> > <attr name="FormatterFactory"> > <attr name="class">Date > <attr name="par1">dd.MM.yy</attr> > <attr name="par2">dd.MM.yy</attr> > <attr name="par3">ddMMyy</attr> > </attr> > </attr> > <attr name="columns">10</attr> > <attr name="enabled">false</attr> > </formattedtextfield> > > or even further: > > <formattedtextfield id="pnlDetailBasic_pidDate"> > <attr name="FormatterFactory"> > <par name="class">Date > <par name="par1">dd.MM.yy</par> > <par name="par2">dd.MM.yy</par> > <par name="par3">ddMMyy</par> > </par> > </attr> > <attr name="columns">10</attr> > <attr name="enabled">false</attr> > </formattedtextfield> > > Sorry about this thinking in public forum, but I can't help it. > > //jarmo > > > > _______________________________________________ > Forum mailing list > [email protected] > http://mars.lunarpages.com/mailman/listinfo/forum_carlsbadcubes.com > >
