label would have to be removed from beanEditBlocks so label position can be controlled... and label would have to have a more complex mechanism to connect to input's id...
Davor Hrg On Thu, Mar 6, 2008 at 12:18 AM, Christoph Jaeger <[EMAIL PROTECTED]> wrote: > 4. for BeanEditForm, have an option to not use <div>s to place labels > and input fields, but use a table instead (or other layout mechanism). > Maybe with the possibility to add columns, this is useful if you would > like to add some explanation or help text next to an input field. > > Christoph > > > Angelo Chen wrote: > > Hi, > > > > Following is a list of features that will make the use of > > beaneditor/beaneditform easy: > > > > 1. RemoveAllExcept: in addition to remove, removeAllExcept will remove all > > the properties except those listed. > > > > 2. Option to disable the display of labels, this is very useful when the > > column contains action links like "delete", "update", etc, if the caption > > has been displayed in the grid row, what's the use of column label? > > > > 3. Option to default the columns to non - sortable until it is turned on, > > say, we have a bean that has 20 properties, very few of them need to be > > sortable, so leaving the heading to be sortable make the screen messy, and > > turning those things off requires a lot of effort, rather make it default. > > > > Care to add what you like to have? > > > > A.C. > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
