[
https://issues.jboss.org/browse/RF-12802?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč edited comment on RF-12802 at 10/4/13 4:00 AM:
----------------------------------------------------------
Juraj, generally the API looks great from my point of view.
-I would like to see information hiding in form of providing interfaces and their
implementation.-
-(a)ImplementedBy(RichFacesCalendar.class) public interface Calendar {}-
(that's achieved by {{advanced()}} method)
Could you please list additional features which we haven't discussed before?: e.g.:
* ability to choose between JS API and interactive manipulation with a widget
(setting/obtaining value)
* advanced interactions
Have you implemented automatic detection of the widget in the page? E.g. rich:calendar can
be find by ".rf-cal" in case there is just one instance in the page (or in the
context of user-defined fragment).
was (Author: lfryc):
Juraj, generally the API looks great from my point of view.
I would like to see information hiding in form of providing interfaces and their
implementation.
@ImplementedBy(RichFacesCalendar.class) public interface Calendar {}
Could you please list additional features which we haven't discussed before?: e.g.:
* ability to choose between JS API and interactive manipulation with a widget
(setting/obtaining value)
* advanced interactions
Have you implemented automatic detection of the widget in the page? E.g. rich:calendar can
be find by ".rf-cal" in case there is just one instance in the page (or in the
context of user-defined fragment).
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