The only problem with using labelFunctions or itemRenderers for this, is that the default sort mechanism (column header click) doesn't work (see historical low). To avoid having to write sortCompareFunctions, sometimes its easier to just bite the bullet and manually add the nested fields to the top level of the VO; so the object is flat. I know its redundant, but it works with little effort.
-TH --- In [email protected], "Alex Harui" <[EMAIL PROTECTED]> wrote: > > There's a DeepDataGridColumn example on my blog that can do simple > field.subfield > > > > ________________________________ > > From: [email protected] [mailto:[EMAIL PROTECTED] On > Behalf Of ben.clinkinbeard > Sent: Tuesday, June 10, 2008 7:50 PM > To: [email protected] > Subject: [flexcoders] Re: Any best-practice for > labelField="field.innerField" on things like DataGridC > > > > I don't think you can do field.subField but you could use > labelFunctions to accomplish essentially the same thing. Heck, you > might even be able to set dataField = "field.subField" and then use a > generic labelFunction that does something like return > data[column.dataField]. Just a guess on that part but labelFunction is > definitely the core of what you'll need. > > HTH, > Ben > > --- In [email protected] <mailto:flexcoders%40yahoogroups.com> > , "Josh McDonald" dznuts@ wrote: > > > > Hey guys, > > Is there a well-used trick to reference "field.subField" rather than > just > > "field" when setting up datagrid columns? I'd rather not have to > flatten my > > DTOs or add a bunch of redundant get functions if possible - the DTO > is > > bindable and the fields are just public vars. > > > > Cheers, > > -Josh > > > > -- > > "Therefore, send not to know For whom the bell tolls. It tolls for > thee." > > > > :: Josh 'G-Funk' McDonald > > :: 0437 221 380 :: josh@ > > >
