Sorry, I didn't realize the difference in release version. I was just trying to point to any reference to using the select widget. I am using CVS HEAD.
On Thu, 2005-04-14 at 09:07 +0200, Wouter Zoons wrote: > you're reading from two different sites: www.andromda.org holds the RC-1 > release docs, and team.andromda.org holds the SNAPSHOT docs, I sent an > email out that something has changed regarding the tables > > so decide what you use: RC-1 or the snapshot, and stick with the proper site > > -- Wouter > > > > > > I am confused as to where to specify the select widget's collection and > > key/value properties. I don't get it. > > > > From > > http://team.andromda.org/docs/andromda-bpm4struts-cartridge/howto8.html : > > > > The 'edition', 'available' and 'buy' widgets > > All these elements make up a specific event, which has been modeled like > > this: > > > > * model an event going out of the page, call it buy > > * for each field model a parameter, specify the appropriate widget > > for each of these parameters (go here if you don't remember how > > to do that), in this example edition is a 'select' and > > available is a 'multibox' > > * add the @andromda.struts.action.tablelink tag to the event, > > the value should be the name of the table > > > > If you wish to include the title parameter but you don't want to have > > it rendered as an input field, then simply use the > > @andromda.struts.view.field.type=plaintext tagged value on that > > parameter. > > > >>From > > http://www.andromda.org/andromda-bpm4struts-cartridge/howto8.html : > > > > Widgets > > Not only hyperlinks can be rendered into a table, basically any kind of > > widget is allowed, just change the @andromda.struts.view.field.type > > tag to any of the known values. The author column (which is controlled > > by the test event parameter) has these tagged values specified: > > > > @andromda.struts.view.field.tablelink=itemList.author > > @andromda.struts.view.field.type=select > > Notice how the cartridge generated dummy data to populate the list. That > > way it's easy to give your application a test-run before doing any > > manual coding. > > > > > > On Wed, 2005-04-13 at 17:08 -0600, Chad Brandon wrote: > > > >>The how-to I would say is pretty good, if you see places where it can be > >>improved, why don't you file an issue in JIRA and I'm sure Wouter will > >>fix the places where you think its unclear. > >> > >>Tim Dysinger wrote: > >> > >> > >>>I'm too new at this to say concisely. We really need to work on a > >>>thorough intro and faq for bpm4struts... > >>> > >>>On Wed, 2005-04-13 at 23:50 +0100, Martin West wrote: > >>> > >>> ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
