Hi Tracy, Thanks for the help and the code. I ended up implementing the component myself, as a container of multiple types of editors. Similar to what you implemented really, just with separate editors instead of states.
On Wed, Feb 25, 2009 at 3:06 AM, Tracy Spratt <[email protected]> wrote: > Where will the dataProvider come from? > > > --- In [email protected] <flexcoders%40yahoogroups.com>, Sefi > Ninio <sefi.ni...@...> wrote: > > > > Okay, how about this: > > When defining a combo box as an itemEditor, and specifying the > > editorDataField - How can I specify the combo box dataProvider? > > I can use the model to bind a dp to the combobox, but I'd like to > create a > > generic component that does not have dependencies on external > models... > > > > > > > > On Sun, Feb 22, 2009 at 1:54 PM, Sefi Ninio <sefi.ni...@...> wrote: > > > > > Hi all. > > > > > > I'm looking for a property editor component (or something similar > to the > > > description below): > > > What I need is a table (DG) based name-value pairs editor, where > the value > > > should be displayed as a label. > > > When it gets focus, it should be editable according to the value > defined > > > type (text, stepper, combo box etc.) > > > > > > Sure, I can implement components (as item editors for the DG) > with two > > > states for text/combo box, text/stepper, text/text editor etc. > > > I was wondering if there is a component that already has this > > > functionality. > > > > > > Anyone has any ideas? > > > > > > Thanks > > > > > > > >
