[
https://issues.jboss.org/browse/RF-11208?page=com.atlassian.jira.plugin.s...
]
Brian Leathem commented on RF-11208:
------------------------------------
This all comes to a head when we want pickList to be able to define it's own select
items. Currently the syntax looks like:
{code}
<r:pickList values="..." colmunVar="columnVar"
itemValues="..." var="itemVar"
itemLabel="#{itemVar.title}">
<r:column>
#{columnVar.somAttribute}
</r:column>
</r:pickList>
{code}
where columnVar iterates over the values, and is used as the replacement variable while
rendering the columns
and var iterates over the itemValues, and is used as the replacement variable when
defining the selectItems.
So the question is, if we drop the columnVar, and recycle the "var" attribute
between the two contexts, is that more or less confusing for end-users?
Resolve the ambiguity between the pickLIst "columnVar" and
the orderingList "var"
---------------------------------------------------------------------------------
Key: RF-11208
URL:
https://issues.jboss.org/browse/RF-11208
Project: RichFaces
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: component-selects
Affects Versions: 4.1.0.Milestone1
Reporter: Brian Leathem
Assignee: Brian Leathem
Priority: Trivial
Fix For: 4.1.0.Milestone2
pickList uses the attribute "columnVar" as a replacement EL variable for
defining column data
orderingList uses the attribute "var"
This amibiguity needs to be resolved with a consistent solution.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira