[JBoss JIRA] (RFPL-2979) Metamer: autocomple, calendar (and more): component attributes inputs disappears on component change
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RFPL-2979?page=com.atlassian.jira.plugin.... ]
Jiří Štefek moved RF-12983 to RFPL-2979:
----------------------------------------
Project: RichFaces Planning (was: RichFaces)
Key: RFPL-2979 (was: RF-12983)
Affects Version/s: 4.3.2
(was: 4.3.2)
Component/s: (was: component-input)
> Metamer: autocomple, calendar (and more): component attributes inputs disappears on component change
> ----------------------------------------------------------------------------------------------------
>
> Key: RFPL-2979
> URL: https://issues.jboss.org/browse/RFPL-2979
> Project: RichFaces Planning
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.2
> Environment: RichFaces 4.3.2.Final
> Metamer 4.3.2.20130514-Final
> Weld Servlet (Uber Jar) 20120106-1159
> Apache Tomcat 7.0.35 (already verified on 7.0.40)
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 25.0.1364.172 @ Linux i686, as well as on Firefox 20.0 @ Linux i686
> MyFaces version: 2.1.10
> Reporter: Ján Jamrich
> Assignee: Jiří Štefek
> Labels: myfaces
>
> When perform (it looks like it is caused by it) ajax reguest from (input type) component, all inputs for component attributes disappears from area bottom.
> Components examples influenced by this problem:
> autocomplete
> calendar
> inplaceInput
> inplaceSelect
> inputNumberSlider
> inputNumberSpinner
> select
> Doesn't influence:
> collapsiblePanel in @switchType=ajax
> contextMenu
> dragIndicator/dragSource/dropTarget
> !!! editor
> pickList
> tab/tabPanel
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (RFPL-2978) Push VDL details out of Component Reference
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RFPL-2978?page=com.atlassian.jira.plugin.... ]
Brian Leathem updated RFPL-2978:
--------------------------------
Fix Version/s: 5.0.0.Alpha2
> Push VDL details out of Component Reference
> --------------------------------------------
>
> Key: RFPL-2978
> URL: https://issues.jboss.org/browse/RFPL-2978
> Project: RichFaces Planning
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: doc
> Affects Versions: 5.0.0.Alpha1
> Reporter: Lukáš Fryč
> Fix For: 5.0.0.Alpha2
>
>
> See [Forum Reference].
> ----
> I have noticed each of the components in Component Reference contains referecen data:
>
>
> {code}
> 3.5.2. Reference data
>
> component-type: org.richfaces.CommandLink
> component-class: org.richfaces.component.UICommandLink
> component-family: javax.faces.Command
> renderer-type: org.richfaces.CommandLinkRenderer
> {code}
>
> Similarly, VDL doc contains same information:
>
> {code}
> Tag Information
> Component type org.richfaces.CommandLink
> Tag Name a4j:commandLink
> Renderer Type org.richfaces.CommandLinkRenderer
> Handler Class None
> {code}
>
>
> The advantage of VDL doc is that it is automatically generated and so it doesn't need to be updated manually everytime something is changed.
>
> On the other hand, those are also not information which are used regularly - they are intented for advanced users and use cases.
>
> Thus I suggest to remove the Reference Data from Components Reference.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (RFPL-2978) Push VDL details out of Component Reference
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RFPL-2978?page=com.atlassian.jira.plugin.... ]
Brian Leathem commented on RFPL-2978:
-------------------------------------
An alternative is to pull in the VDL details of the RF docs from the generated docs. This could be done by including the VDL doc in our distributed docs as an appendix for example.
> Push VDL details out of Component Reference
> --------------------------------------------
>
> Key: RFPL-2978
> URL: https://issues.jboss.org/browse/RFPL-2978
> Project: RichFaces Planning
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: doc
> Affects Versions: 5.0.0.Alpha1
> Reporter: Lukáš Fryč
>
> See [Forum Reference].
> ----
> I have noticed each of the components in Component Reference contains referecen data:
>
>
> {code}
> 3.5.2. Reference data
>
> component-type: org.richfaces.CommandLink
> component-class: org.richfaces.component.UICommandLink
> component-family: javax.faces.Command
> renderer-type: org.richfaces.CommandLinkRenderer
> {code}
>
> Similarly, VDL doc contains same information:
>
> {code}
> Tag Information
> Component type org.richfaces.CommandLink
> Tag Name a4j:commandLink
> Renderer Type org.richfaces.CommandLinkRenderer
> Handler Class None
> {code}
>
>
> The advantage of VDL doc is that it is automatically generated and so it doesn't need to be updated manually everytime something is changed.
>
> On the other hand, those are also not information which are used regularly - they are intented for advanced users and use cases.
>
> Thus I suggest to remove the Reference Data from Components Reference.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (RFPL-2967) Component reference - Chapter 16. Functions - markup tags left in the text
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RFPL-2967?page=com.atlassian.jira.plugin.... ]
Pavol Pitonak closed RFPL-2967.
-------------------------------
> Component reference - Chapter 16. Functions - markup tags left in the text
> --------------------------------------------------------------------------
>
> Key: RFPL-2967
> URL: https://issues.jboss.org/browse/RFPL-2967
> Project: RichFaces Planning
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: doc
> Affects Versions: 5.0.0.Alpha1
> Reporter: Juraj Húska
> Assignee: Brian Leathem
> Priority: Minor
> Fix For: 5.0.0.Alpha1
>
> Attachments: functions.png
>
>
> In Chapter 16. Functions, the text looks like:
> {quote}
> The *[function]* r:clientId('id') function returns the client identifier related to the passed component identifier ( *[code]*'id'). If the specified component identifier is not found, null is returned instead.
> {quote}
> Note the redundant [function] and [code] markup info. It is the same for all functions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months