[
https://issues.jboss.org/browse/RF-12802?page=com.atlassian.jira.plugin.s...
]
Juraj Húska commented on RF-12802:
----------------------------------
List of additional features we either discussed on developer forum or not discussed at
all:
* ability to choose between JS API and interactive manipulation with a widget
(setting/obtaining value)
* advanced interactions
* {{WaitingWrapper}}
[
interface|https://github.com/richfaces/richfaces-qa/blob/master/page-frag...]
- there are some predefined waitings for some fragments. This is a convenient way how an
user can call it: e.g.
{{autocomplete.advanced().waitForSuggestionsToBeNotVisible().withTimeout(4);}}
* those waiting are also used in the the methods from public API. Thus there has to be way
how an user can change the timeout for those methods. E.g.
{{autocomplete.type("ala").confirm();}} - the method needs to wait until the
suggestions are not visible, and the user should have an option to set the timeout for it
- thus
{{autocomplete.advanced().setupConfirmWaitForSuggestionsToBeNotVisibleTimeout(3);}}
* HotKey
[
fragment|https://github.com/richfaces/richfaces-qa/blob/master/page-fragm...]
- automatically retrieve the hotkey combination via JS
The automatic detection of widget is not implemented. We will need to investigate on that
more.
Move page fragments from repository qa to richfaces5
----------------------------------------------------
Key: RF-12802
URL:
https://issues.jboss.org/browse/RF-12802
Project: RichFaces
Issue Type: Task
Security Level: Public(Everyone can see)
Components: build/distribution
Affects Versions: 5.0.0.Alpha1
Reporter: Pavol Pitonak
Assignee: Brian Leathem
Fix For: 5.0.0.Alpha2
As discussed on community meeting on Feb 12, we should move page fragments for RichFaces
components to richfaces5 repository so that they are distributed with framework.
We should find out how to prepare them so that they are easy to use for community
members. RichFaces QE/dev need to test internals of components, community members will
probably test only high-level functionality of components. One possible solution would be
to create package "internal" in which there would be page fragments extending
those from "public" package. QE team would then use "internal"
implementations.
--
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