[JBoss JIRA] (RF-11588) HeaderClass is ignored on ExtendedDataTable column
by Cody Lerum (Created) (JIRA)
HeaderClass is ignored on ExtendedDataTable column
--------------------------------------------------
Key: RF-11588
URL: https://issues.jboss.org/browse/RF-11588
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.1.0.Milestone3
Reporter: Cody Lerum
When a header class is defined on a rich:column inside an rich:extendedDataTable it is ignored
Assume
{code}
<rich:column headerClass="left" styleClass="left">
<f:facet name="header">Foo</f:facet>
<h:outputText value="Bar" />
</rich:column>
{code}
What is rendered is
{code}
<td>
<div class="rf-edt-rsz-cntr rf-edt-c-j_idt384" style="">
<div class="rf-edt-rsz"></div>
</div>
<div class="rf-edt-hdr-c rf-edt-c-j_idt384 left" style="height: 21px; ">
<div class="rf-edt-hdr-c-cnt">Foo</div>
</div>
</td>
{code}
My style left is applied but the header is one level lower and has rf-edt-hdr-c-cnt style which will always make it center
--
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, 6 months
[JBoss JIRA] Created: (RF-8952) Add <cdk:function> element to template language.
by Alexander Smirnov (JIRA)
Add <cdk:function> element to template language.
------------------------------------------------
Key: RF-8952
URL: https://jira.jboss.org/browse/RF-8952
Project: RichFaces
Issue Type: Task
Security Level: Public (Everyone can see)
Components: CDK
Reporter: Alexander Smirnov
Assignee: Alexander Smirnov
Fix For: 4.0.0.Milestone2
It would be useful to generate html code snippets as Java functions that would be called anywhere from template or java code. For example, html table cells need sofisticated code for iteration while they should be generated inside row elements. The template like this:
<table>
<tbody>
<cdk:call name="renderRows"/>
<cdk:function name="renderRow" >
<tr>
<cdk:call name="renderCells"/>
<cdk:function name="renderCell">
<td>....</td>
</cdk:function>
</tr>
</cdk:function>
</tbody>
</table>
lets to put row/cells rendering logic into Java code (renderRows/renderCells methods ) while template markup still follow desired html code.
P.S. It would be even more convenient to union both calls into single element with name/call attributes.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (RF-12092) a4j:poll : a4j:status never clears
by Robert Gary (JIRA)
Robert Gary created RF-12092:
--------------------------------
Summary: a4j:poll : a4j:status never clears
Key: RF-12092
URL: https://issues.jboss.org/browse/RF-12092
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-push/poll
Affects Versions: 4.2.0.Final
Reporter: Robert Gary
When a4j:poll fires a4j:status correctly displays the request is in progress. However, it never shows it complete. Using any other a4j component will correctly update the a4j:status. So if the a4j:status is stuck showing its waiting because of an a4j:poll if you click on an a4j:commandButton the a4j:status will correctly show its now complete.
<a4j:poll id="ajaxPoll" interval="5000" enabled="true" action="#{faces$DiscoveryStatus.poll}"
render="#{faces$DiscoveryStatus.reRenderStr}"/>
<a4j:status id="a4jstatus">
<f:facet name="start">
<img src='/images/ajax-loader.gif'/>
</f:facet>
<!--<f:facet name="stop">-->
<!--<img src="/appiq/images/minor_icon.gif"/>-->
<!--</f:facet>-->
</a4j:status>
This code works correctly in RF 3.3.3.
--
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, 6 months
[JBoss JIRA] (RF-12081) Problem with RichEditor RF 4.2.0
by phelen harg (JIRA)
phelen harg created RF-12081:
--------------------------------
Summary: Problem with RichEditor RF 4.2.0
Key: RF-12081
URL: https://issues.jboss.org/browse/RF-12081
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-input
Affects Versions: 4.2.0.Final
Reporter: phelen harg
I'm migrating my Application from RF 3.3.3 to RF 4.2.0. But now i'm facing a problem with the richEditor. When I load the the component, all the links in application receive a background like this picture:
Analizing the code with Firebug, I found the problem in the CSS of RichEditor. /org.richfaces.resources/javax.faces.resource/org.richfaces.ckeditor/skins/richfaces/editor.ecss?db=eAHj0yqqAgACGAEl
If I erase the CSS the backgroud disappear. There is some kind of workaround for this?
--
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, 6 months
[JBoss JIRA] (RF-12201) Add common method to all generated CDK component
by Paul Dijou (JIRA)
Paul Dijou created RF-12201:
-------------------------------
Summary: Add common method to all generated CDK component
Key: RF-12201
URL: https://issues.jboss.org/browse/RF-12201
Project: RichFaces
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: cdk
Affects Versions: 4.2.1.Final
Environment: All
Reporter: Paul Dijou
Looking at CDK AbstractComponent, or RendererBase or template.xml, I find lot of code copy/paste again and again. Maybe it could be usefull to have some common methods automatically generated by the CDK. I have some ideas right now, but I guess it will increase with time.
Sometime, I call the method in the "component" var inside the template. Maybe it would not be possible since we can only add methods to the "AbstractComponent". I'm fine with having them there and casting the component at the beginning of the template using {{<cdk:object>}}.
h3. 1) Test if an attribute is present :
{code:xml}
<c:when test="#{component.attributes['brand']!= null and not component.attributes['brand'].equals('')}">
{code}
Can become :
{code:xml}
<c:when test="#{component.hasAttribute('brand')}">
{code}
{code:java}
public boolean hasAttribute(String attributeName) {
// TODO : test if the attribute is present
}
{code}
h3. 2) Test if a facet is present
Same as before but about JSF facets
{code:xml}
<c:when test="#{component.getFacet('brand') != null and component.getFacet('brand').rendered}">
{code}
Become
{code:xml}
<c:when test="#{component.hasFacet('brand')}">
{code}
{code:java}
public boolean hasFacet(String facetName) {
// TODO : test if the facet is present and rendered
}
{code}
h3. 3) The castComponent method
This one is present in like 9 out of 10 AbstractComponent in the Bootstrap sandbox. I don't know how [RF-11668|https://issues.jboss.org/browse/RF-11668] will be resolved. But if we still need to cast the component, having the method in every component by default would be really nice.
h3. 4) 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, 6 months