Hi Rogério, I like to propose not using commandLink or commandButton for the toolbar items, but instead look-alikes that carry an id. The whole toolbar will submit to one action, and within the action we will have a switch statement to determine which button is pressed.
The reason for the proposal is ease of reuse. For example in many of my forms I have a standard toolbar consisting of "add, delete, edit", and another one consisting of "ok, cancel". With this proposal we can simply copy and paste a fairly complex toolbar and configure only action attribute. The next step is to load the toolbar from a data model. Eagerly awaiting. Regards, Yee -----Original Message----- From: Rogerio Pereira [mailto:[EMAIL PROTECTED] Sent: Saturday, 12 November 2005 10:00 PM To: MyFaces Discussion Subject: before start the toolbar control Hi, I need some advice before start the toolbar component. 1) any suggestions about the name of this toolbar component? 2) i'm thinking in 3 classes at this point (ToolBar, ToolButton and Separator) 3) the ToolButton will render a commandLink and commandButton (showing an image) or just commandLink 4) i need sugestions about directory structure This will help me start the development of this component. -- Yours truly (Atenciosamente), Rogério
