[JBoss JIRA] (RF-13343) Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč edited comment on RF-13343 at 11/13/13 10:42 AM:
------------------------------------------------------------
I think we can leave this option unsupported and re-implement it once it is needed by Framework/Metamer tests, wdyt [~ppitonak]?
was (Author: lfryc):
I think we can leave this option unsupported and re-implement it once it is needed by QE, wdyt [~ppitonak]?
> Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
> ---------------------------------------------------------------------------------------------
>
> Key: RF-13343
> URL: https://issues.jboss.org/browse/RF-13343
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: page-fragments, qe
> Affects Versions: 5.0.0.Alpha2
> Reporter: Lukáš Fryč
>
> As we have discussed in RF-13335, we have two options available for accessing component options:
> * component uses {{BaseComponent}} (RF4 components)
> {code}
> RichFaces.component("j_idt108").options
> {code}
> * component uses {{jQuery UI Widget Factory}} (RF5 components)
> {code}
> $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus")
> {code}
> We can use WebDriver's {{JavascriptExecutor}} to access widget settings.
--
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
12 years, 4 months
[JBoss JIRA] (RF-13343) Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-13343:
---------------------------------
I think we can leave this option unsupported and re-implement it once it is needed by QE, wdyt [~ppitonak]?
> Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
> ---------------------------------------------------------------------------------------------
>
> Key: RF-13343
> URL: https://issues.jboss.org/browse/RF-13343
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: page-fragments, qe
> Affects Versions: 5.0.0.Alpha2
> Reporter: Lukáš Fryč
>
> As we have discussed in RF-13335, we have two options available for accessing component options:
> * component uses {{BaseComponent}} (RF4 components)
> {code}
> RichFaces.component("j_idt108").options
> {code}
> * component uses {{jQuery UI Widget Factory}} (RF5 components)
> {code}
> $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus")
> {code}
> We can use WebDriver's {{JavascriptExecutor}} to access widget settings.
--
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
12 years, 4 months
[JBoss JIRA] (RF-13343) Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-13343:
---------------------------------
Note that Page Fragments can be used without {{setupFragmentFromWidget()}} method,
it just makes Page Fragment use configuration-less.
> Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
> ---------------------------------------------------------------------------------------------
>
> Key: RF-13343
> URL: https://issues.jboss.org/browse/RF-13343
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: page-fragments, qe
> Affects Versions: 5.0.0.Alpha2
> Reporter: Lukáš Fryč
>
> As we have discussed in RF-13335, we have two options available for accessing component options:
> * component uses {{BaseComponent}} (RF4 components)
> {code}
> RichFaces.component("j_idt108").options
> {code}
> * component uses {{jQuery UI Widget Factory}} (RF5 components)
> {code}
> $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus")
> {code}
> We can use WebDriver's {{JavascriptExecutor}} to access widget settings.
--
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
12 years, 4 months
[JBoss JIRA] (RF-13343) Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-13343:
----------------------------
Component/s: qe
> Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
> ---------------------------------------------------------------------------------------------
>
> Key: RF-13343
> URL: https://issues.jboss.org/browse/RF-13343
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: page-fragments, qe
> Affects Versions: 5.0.0.Alpha2
> Reporter: Lukáš Fryč
>
> As we have discussed in RF-13335, we have two options available for accessing component options:
> * component uses {{BaseComponent}} (RF4 components)
> {code}
> RichFaces.component("j_idt108").options
> {code}
> * component uses {{jQuery UI Widget Factory}} (RF5 components)
> {code}
> $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus")
> {code}
> We can use WebDriver's {{JavascriptExecutor}} to access widget settings.
--
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
12 years, 4 months
[JBoss JIRA] (RF-13343) Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-13343:
---------------------------------
We need to remove {{getJsonValue()}} methods()
> Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
> ---------------------------------------------------------------------------------------------
>
> Key: RF-13343
> URL: https://issues.jboss.org/browse/RF-13343
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: page-fragments
> Affects Versions: 5.0.0.Alpha2
> Reporter: Lukáš Fryč
>
> As we have discussed in RF-13335, we have two options available for accessing component options:
> * component uses {{BaseComponent}} (RF4 components)
> {code}
> RichFaces.component("j_idt108").options
> {code}
> * component uses {{jQuery UI Widget Factory}} (RF5 components)
> {code}
> $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus")
> {code}
> We can use WebDriver's {{JavascriptExecutor}} to access widget settings.
--
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
12 years, 4 months
[JBoss JIRA] (RF-13343) Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
by Lukáš Fryč (JIRA)
Lukáš Fryč created RF-13343:
-------------------------------
Summary: Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
Key: RF-13343
URL: https://issues.jboss.org/browse/RF-13343
Project: RichFaces
Issue Type: Task
Security Level: Public (Everyone can see)
Components: page-fragments
Affects Versions: 5.0.0.Alpha2
Reporter: Lukáš Fryč
As we have discussed in RF-13335, we have two options available for accessing component options:
* component uses {{BaseComponent}} (RF4 components)
{code}
RichFaces.component("j_idt108").options
{code}
* component uses {{jQuery UI Widget Factory}} (RF5 components)
{code}
$(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus")
{code}
We can use WebDriver's {{JavascriptExecutor}} to access widget settings.
--
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
12 years, 4 months
[JBoss JIRA] (RF-13335) Page fragments: get rid of commons-lang dependency
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13335?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč edited comment on RF-13335 at 11/13/13 10:31 AM:
------------------------------------------------------------
The {{options}} variable is directly exposed on a component object as follows:
{code}
RichFaces.component("j_idt143:j_idt147").options
{code}
was (Author: lfryc):
The options variable is directly exposed on a component object as follows:
{code}
RichFaces.component("j_idt143:j_idt147").options
{code}
> Page fragments: get rid of commons-lang dependency
> --------------------------------------------------
>
> Key: RF-13335
> URL: https://issues.jboss.org/browse/RF-13335
> Project: RichFaces
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: page-fragments
> Affects Versions: 5.0.0.Alpha2
> Reporter: Lukáš Fryč
> Assignee: Lukáš Fryč
> Fix For: 5.0.0.Alpha2
>
>
> I didn't found reason to leave {{Validate.isTrue}} - this should be replaced by more verbose but dependency free code.
> I did some googling for alternatives to {{StringEscapeUtils.unescapeJava}} and found out few [suggestions for dependency free Java-unescaping|http://stackoverflow.com/questions/3537706/howto-unescape...].
--
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
12 years, 4 months