[JBoss JIRA] (RF-12232) [CDK] Support "varStatus" attribute on c:forEach
by Paul Dijou (JIRA)
Paul Dijou created RF-12232:
-------------------------------
Summary: [CDK] Support "varStatus" attribute on c:forEach
Key: RF-12232
URL: https://issues.jboss.org/browse/RF-12232
Project: RichFaces
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: cdk
Affects Versions: 4.2.1.Final
Environment: All
Reporter: Paul Dijou
Right now, when using {{<c:forEach>}} tag on a CDK template.xml, you will have a "for" loop in Java code. There is no way to do simple logic in the template like knowing your current index inside the loop, etc...
An idea would be to support the {{varStatus}} attribute from the original {{<c:forEach>}}. This attribute maps to the name of a bean which contains util methods and evolve at each iteration of the loop.
Here is a sample:
{code:xml}
<c:forEach var="child" items="#{component.getChildren()}" varStatus="status">
// Inside code
</c:forEach>
{code}
Would generate something like:
{code:java}
LoopTagStatus status = new LoopTagStatus();
for(UIComponent child : component.getChildren()) {
// Inside code
status.next();
}
{code}
The javadoc of the original {{LoopTagStatus}} from JSTL is [here|http://docs.oracle.com/javaee/5/jstl/1.1/docs/api/javax/servlet/jsp/...]. Our LoopTagStatus would have the method and one more : the {{next()}} method. This one would increment the current index of the LoopTagStatus in order to be updated for the next iteration.
We could also add any other usefull methods to this bean.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (RF-12249) CDK: generates both get* and is* methods for boolean/Boolean expressions
by Lukáš Fryč (JIRA)
Lukáš Fryč created RF-12249:
-------------------------------
Summary: CDK: generates both get* and is* methods for boolean/Boolean expressions
Key: RF-12249
URL: https://issues.jboss.org/browse/RF-12249
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: cdk
Affects Versions: 4.2.0.Final
Reporter: Paul Dijou
Generate both "get..." and "is..." method for Boolean and boolean attributes
If you have an attribute like :
{code:java}
@Attribute
abstract public boolean isClosable();
{code}
This will generate a "isClosable()" method of course. But, then, trying to access it in a template like :
{code:xml}
<c:if test="#{alert.closable}">
{code}
Will crash since JSF try to call the "getClosable()" method. The workaround is to write :
{code:xml}
<c:if test="#{alert.isClosable()}">
{code}
But it would be nicer if the "geClosable()" method was generated in the same time of the "isClosable()" method.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (RF-12266) progressBar: CSS contains text-color and color
by Christophe Roussy (JIRA)
Christophe Roussy created RF-12266:
--------------------------------------
Summary: progressBar: CSS contains text-color and color
Key: RF-12266
URL: https://issues.jboss.org/browse/RF-12266
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-misc
Affects Versions: 4.2.1.Final
Environment: Firefox, Windows
Reporter: Christophe Roussy
text-color in progressbar css, is this standard css ?
*.rf-pb-rmng {
height: 13px;
white-space: nowrap;
width: 200px;
position: relative;
border-width: 1px;
border-style: solid;
border-color: #C4C0B9;
border-radius: 0px;
overflow: hidden;
color: #000000;
font-family: Arial, Verdana, sans-serif ;
font-size: 11px;
font-weight: bold;
text-color: #000000;
background-color: #ffffff;
padding: 0px;
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (RF-11924) showcase - rich:context - tree ContextMenu - header of popup should be bigger
by Juraj Huska (JIRA)
Juraj Huska created RF-11924:
--------------------------------
Summary: showcase - rich:context - tree ContextMenu - header of popup should be bigger
Key: RF-11924
URL: https://issues.jboss.org/browse/RF-11924
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-menu, component-output, component-panels-layout-themes, showcase, skinning
Affects Versions: 4.1.0.Final
Environment: showcase app - 4.2.0-SNAPSHOT
all browsers
Reporter: Juraj Huska
Priority: Trivial
Attachments: contextMenuPopup.png
The header of popup invoked from contextMenu in demos for rich:contextMenu, sample tree contextMenu is in some cases too small, and the cross for hiding the popup overlap with the header label.
It is when the body of the popup is small in width. For example it is so when user select node USA, then the header of popup adapts the size of body, and the problem is there. Please see the screenshot for further reference.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months