Develop prototype of encoding namespaces in portlets for CSS & JS
-----------------------------------------------------------------
Key: RFPL-363
URL: https://jira.jboss.org/jira/browse/RFPL-363
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 4.0.0.ALPHA2
Reporter: Nick Belaevski
Assignee: Nick Belaevski
Fix For: 4.0.0.ALPHA2
This prototype should cover the following issues RF-7571 & RF-7573
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Add Ipad to the platform test plan, and wiki pages
--------------------------------------------------
Key: RFPL-468
URL: https://jira.jboss.org/jira/browse/RFPL-468
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Components: administration, QA, site
Reporter: Jay Balunas
Assignee: Prabhat Jha
Fix For: 4.0.0.M1
The IPad support should be at P3 ( perhaps P2 ) - we'll need to see. The browser matrix should be updates.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Create styling guidelines for restricted semantic layouts using something like tabPanel as an example
-----------------------------------------------------------------------------------------------------
Key: RFPL-94
URL: https://jira.jboss.org/jira/browse/RFPL-94
Project: RichFaces Planning
Issue Type: Task
Components: components
Reporter: Jay Balunas
Assignee: Lex Dmitriev
Priority: Critical
Fix For: 4.0.0.ALPHA2
We need to have an example of style guidelines based on the restricted semantic layouts for tabs, panels, etc... This needs to be detailed enough for documentation for build off of. We will also use this for discussion purposes when talking about individual components and restrictions.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Develop migration process for moving 3.3.X components to 4.0.X
--------------------------------------------------------------
Key: RFPL-437
URL: https://jira.jboss.org/jira/browse/RFPL-437
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Components: administration, components
Reporter: Jay Balunas
Assignee: Jay Balunas
Priority: Critical
Fix For: 4.0.0.ALPHA2
This is the parent jira to track tasks and progress of developing the migration process for moving richfaces components over to 4.0.0.
This is going to include rules for using the UI sandbox, requirements, reviews, etc....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira