[
https://issues.apache.org/jira/browse/TAPESTRY-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAPESTRY-2288.
------------------------------------------
Resolution: Invalid
Assignee: Howard M. Lewis Ship
I think it is very important to allow control over the Label and other content
related to a field. You may want to put help links or other icons in a label,
omit it in in some cases, or do something we can't even predict at this time.
This is only possible when the contribution to the BeanBlockSource is the Label
and the field together.
Remember also that the BeanEditor is designed as scaffolding; create a basic UI
in a minute and support limited and reasonable customization. In real
applications, there may be (after multiple refactoring passes) use very few
instances of BeanEditor / BeanEditForm.
> Remove Label from BeanBlockSource contributions (edit-blocks)
> -------------------------------------------------------------
>
> Key: TAPESTRY-2288
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2288
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.11
> Reporter: Davor Hrg
> Assignee: Howard M. Lewis Ship
>
> BeanBlockSource contributions for view and edit block are not symetric.
> Edit block must have a label (which is nice and easy to connect it with the
> edit field),
> but this makes edit block unusable for other than default BeanEditor.
> Currently beanEditor uses divs to create layout, I personaly don't like this,
> and prefer tables, but that would not be a problem if it was easy to make
> beanEditor that wraps label and field in a TR,TD...
> Another case would be a BeanEditView component that could be switched
> between edit nad view state easily...
> Another case is a BeanEditor generated for a row inside a grid (horizontal,
> inside TD-s and without labels)
> All this is not possible with edit blocks bound with labels...
> As a proposal for connecting label with field I'd suggest PropertyEditContext,
> and force editBlock contribution to set clientId of the editor inside it onto
> PropertyEditContext.
> This way a label that is supposed to be for that block can know the clientId,
> an by doing this we can avoid putting label and field together inside the
> edit block.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
