dataTable: hide unnecessary attributes (rowKey, summary, etc.)
--------------------------------------------------------------
Key: RF-2033
URL: http://jira.jboss.com/jira/browse/RF-2033
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.1.4
Reporter: Aleksej Yanul
Assigned To: Nick Belaevski
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
ToolBar: Add onitem* events (onitemclick etc..)
-----------------------------------------------
Key: RF-1605
URL: http://jira.jboss.com/jira/browse/RF-1605
Project: RichFaces
Issue Type: Task
Affects Versions: 3.1.3
Reporter: Ilya Shaikovsky
Assigned To: Nick Belaevski
Fix For: 3.2.0
corresponding "td" element should be available under "this"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Add disablement possibility to the whole dropDownMenu component.
----------------------------------------------------------------
Key: RF-1290
URL: http://jira.jboss.com/jira/browse/RF-1290
Project: RichFaces
Issue Type: Task
Affects Versions: 3.1.3, 3.2.0
Reporter: Ilya Shaikovsky
Assigned To: Nick Belaevski
Fix For: 3.2.0
Look to dropDownMenu design folder. There is requirements in the specification with 2.0 version. Need to implement them.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
JS API refactoring
------------------
Key: RF-1604
URL: http://jira.jboss.com/jira/browse/RF-1604
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.1.3
Reporter: Ilya Shaikovsky
Assigned To: Nick Belaevski
Fix For: 3.2.0
All "do*" functions should provide "*" aliases (Example - "doShow" should have "show" alias)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.jboss.com/jira/browse/RF-265?page=comments#action_12420342 ]
Svetlana mukhina commented on RF-265:
-------------------------------------
docsupdated
> Separate jars for API, UI, CDK and others
> -----------------------------------------
>
> Key: RF-265
> URL: http://jira.jboss.com/jira/browse/RF-265
> Project: RichFaces
> Issue Type: Feature Request
> Components: planning, docs updated
> Reporter: Igor Shabalov
> Assigned To: Alexander Smirnov
> Priority: Critical
> Fix For: 3.1.0
>
> Original Estimate: 4 weeks
> Remaining Estimate: 4 weeks
>
> We need to split all classes to real UI and reusable API. In addition to this we need to re-think number of jars in CDK.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
dataOrderedList: there is dataDefinitionList in example in 'Component usage' section instaed of dataOrderedList
---------------------------------------------------------------------------------------------------------------
Key: RF-3148
URL: http://jira.jboss.com/jira/browse/RF-3148
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.1.5
Environment: 3.1.5.CR2
Reporter: Tsikhon Kuprevich
Assigned To: Nick Belaevski
dataOrderedList: there is dataDefinitionList in example in 'Component usage' section instaed of dataOrderedList
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.jboss.com/jira/browse/RF-266?page=comments#action_12420344 ]
Svetlana mukhina commented on RF-266:
-------------------------------------
docsupdated
> Merge richfaces/ajax4jsf into single project
> --------------------------------------------
>
> Key: RF-266
> URL: http://jira.jboss.com/jira/browse/RF-266
> Project: RichFaces
> Issue Type: Feature Request
> Components: planning, docs updated
> Reporter: Igor Shabalov
> Assigned To: Alexander Smirnov
> Priority: Critical
> Fix For: 3.1.0
>
>
> Both project needs to be merged into single code base with simultaneous refactoring/restructuring of the project
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.jboss.com/jira/browse/RF-268?page=comments#action_12420343 ]
Svetlana mukhina commented on RF-268:
-------------------------------------
docsupdated
> New components: message and messages
> ------------------------------------
>
> Key: RF-268
> URL: http://jira.jboss.com/jira/browse/RF-268
> Project: RichFaces
> Issue Type: Feature Request
> Components: planning
> Reporter: Igor Shabalov
> Assigned To: Maksim Kaszynski
> Priority: Critical
> Fix For: 3.1.0
>
> Original Estimate: 2 weeks
> Remaining Estimate: 2 weeks
>
> Equivalent of h:message and h:messages, but updated on every ajax requests
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.jboss.com/jira/browse/RF-269?page=comments#action_12420341 ]
Svetlana mukhina commented on RF-269:
-------------------------------------
docsupdated
> New "plain" skin
> ----------------
>
> Key: RF-269
> URL: http://jira.jboss.com/jira/browse/RF-269
> Project: RichFaces
> Issue Type: Feature Request
> Components: planning
> Reporter: Igor Shabalov
> Assigned To: Aleksej Yanul
> Priority: Critical
> Fix For: 3.2.0
>
> Original Estimate: 2 weeks
> Remaining Estimate: 2 weeks
>
> We need some way to define "empty" skin, - skin that contain no formatting data at all.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira