Ed Leafe wrote: > On Dec 14, 2006, at 10:08 AM, Carl Karsten wrote: > >> hmm, maybe this isn't such a good idea. >> >> Add a 4th table: ProductPrice, child of EventProducts. once the >> prducts for an >> event have been selected, the prices (3 per product) need to be >> entered. (yes, >> the price changes for each event.) >> >> So the 'Selected' side of the mover needs to be something that can >> drive a child >> grid. Which makes me think grid. personally, I like using grids >> for my movers >> so that they can have multiple columns with all the features of a >> grid. (like >> being able to click a header and order that column.) > > Well, then you don't want a mover, do you? >
yes and no. I want the UI 'validation' a mover imposes: you can't pick the same Product a 2nd time because it isn't on the 'avalible' side. but on the selected side, I need child data. personally, my idea of a mover is pretty broad: 2 lists/grids/handy selction UI, some select/remove buttons. Carl _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
