Actions

Archived

Difference between revisions of "Joomla! 1.6 Development Status"

From Joomla! Documentation

Line 1: Line 1:
{| class="wikitable" style="font-size: 95%; padding:2px; width: auto;"
+
{| class="wikitable" style="font-size: 90%; padding:2px; width: auto;"
!Task
+
|Task
!Blocker
+
|Blocker
!Status
+
|Status
!Contact person
+
|Contact person
!Description
+
|Description
 
|-
 
|-
!Implement JForm library
+
|Implement JForm library
 
|Alpha
 
|Alpha
 
|95%
 
|95%
Line 12: Line 12:
 
|This library allows to create forms from XML definition files. See the introduction at http://tinyurl.com/psj6c6
 
|This library allows to create forms from XML definition files. See the introduction at http://tinyurl.com/psj6c6
 
|-
 
|-
!Implement new event triggers
+
|Implement new event triggers
 
|Alpha
 
|Alpha
 
|60%
 
|60%
Line 18: Line 18:
 
|onBeforeRender, triggers in JForm, onContentDisplay etc.
 
|onBeforeRender, triggers in JForm, onContentDisplay etc.
 
|-
 
|-
!Implement new controller dispatcher
+
|Implement new controller dispatcher
 
|Alpha
 
|Alpha
 
|100%
 
|100%
Line 24: Line 24:
 
|See the discussion at http://tinyurl.com/qlh5bg where Louis explained how this works in 1.6
 
|See the discussion at http://tinyurl.com/qlh5bg where Louis explained how this works in 1.6
 
|-
 
|-
!Upgrade to Mootools 1.2
+
|Upgrade to Mootools 1.2
 
|Alpha
 
|Alpha
 
|90%
 
|90%
Line 30: Line 30:
 
|This is mostly finished but there are a few things to do. For example how to load more library. See the discussion at http://tinyurl.com/p5cvbc
 
|This is mostly finished but there are a few things to do. For example how to load more library. See the discussion at http://tinyurl.com/p5cvbc
 
|-
 
|-
!Javascript translation
+
|Javascript translation
 
|Alpha
 
|Alpha
 
|100%
 
|100%
Line 36: Line 36:
 
|This is implemented and finished. Take a look at JOpenID Javascript class and mod_login for details
 
|This is implemented and finished. Take a look at JOpenID Javascript class and mod_login for details
 
|-
 
|-
!New extension updater work
+
|New extension updater work
 
|Alpha
 
|Alpha
 
|80%
 
|80%
Line 42: Line 42:
 
|New extension updater is implemented, but not finished yet.
 
|New extension updater is implemented, but not finished yet.
 
|-
 
|-
!Conversion of INI to JSON
+
|Conversion of INI to JSON
 
|Alpha
 
|Alpha
 
|100%
 
|100%
Line 48: Line 48:
 
|We now use JSON format for storing parameters in the database. This is completed for core components.
 
|We now use JSON format for storing parameters in the database. This is completed for core components.
 
|-
 
|-
!Nested categories
+
|Nested categories
 
|Alpha
 
|Alpha
 
|70%
 
|70%
Line 54: Line 54:
 
|
 
|
 
|-
 
|-
!Access control list (ACL)
+
|Access control list (ACL)
 
|Alpha
 
|Alpha
 
|10%
 
|10%
Line 60: Line 60:
 
|
 
|
 
|-
 
|-
!Replace Contacts with Contact Directory
+
|Replace Contacts with Contact Directory
 
|Alpha
 
|Alpha
 
|30%
 
|30%
Line 66: Line 66:
 
|Replacement of files is ready, however there are some parts which aren't working
 
|Replacement of files is ready, however there are some parts which aren't working
 
|-
 
|-
!User management system
+
|User management system
 
|Alpha
 
|Alpha
 
|5%
 
|5%
Line 72: Line 72:
 
|The new com_members needs to be proof checked.
 
|The new com_members needs to be proof checked.
 
|-
 
|-
!JContent class
+
|JContent class
 
|Alpha
 
|Alpha
 
|0%
 
|0%
Line 78: Line 78:
 
|JContent is a class that will allow us to have a generic way to fire plugins on content
 
|JContent is a class that will allow us to have a generic way to fire plugins on content
 
|-
 
|-
!Documenting the triggers, finishing them
+
|Documenting the triggers, finishing them
 
|
 
|
 
|10%
 
|10%
Line 84: Line 84:
 
|The triggers for JForm need to be implemented in the respective extension, which has not happened yet. We need a plan for this one.
 
|The triggers for JForm need to be implemented in the respective extension, which has not happened yet. We need a plan for this one.
 
|-
 
|-
!MVCing backend components
+
|MVCing backend components
 
|
 
|
 
|20%
 
|20%
Line 90: Line 90:
 
|Most of the back-end components have MVC file structure, but they are not fully MVC yet
 
|Most of the back-end components have MVC file structure, but they are not fully MVC yet
 
|-
 
|-
!Parameters for templates in the database
+
|Parameters for templates in the database
 
|
 
|
 
|50%
 
|50%
Line 96: Line 96:
 
|Especially the UI will take a lot of work, we might have to change the database for this one.
 
|Especially the UI will take a lot of work, we might have to change the database for this one.
 
|-
 
|-
!Add template parameter set to menu item creation
+
|Add template parameter set to menu item creation
 
|
 
|
 
|10%
 
|10%
Line 102: Line 102:
 
|
 
|
 
|-
 
|-
!Refactoring parameters
+
|Refactoring parameters
 
|
 
|
 
|0%
 
|0%
Line 108: Line 108:
 
|A review of the current parameters and implementing new ones for the new category system.
 
|A review of the current parameters and implementing new ones for the new category system.
 
|-
 
|-
!Comments system
+
|Comments system
 
|
 
|
 
|0%
 
|0%
Line 114: Line 114:
 
|It will be donated by JXtended and will be added to trunk somewhere in the beta phase.
 
|It will be donated by JXtended and will be added to trunk somewhere in the beta phase.
 
|-
 
|-
!Hooks for external authentication systems
+
|Hooks for external authentication systems
 
|
 
|
 
|0%
 
|0%
Line 120: Line 120:
 
|Need to be implemented in JUser and in the code where Usergroups are managed. Maybe we need a JUsergroupclass
 
|Need to be implemented in JUser and in the code where Usergroups are managed. Maybe we need a JUsergroupclass
 
|-
 
|-
!Database driven install log
+
|Database driven install log
 
|
 
|
 
|0%
 
|0%
Line 126: Line 126:
 
|
 
|
 
|-
 
|-
!Refactoring of cache
+
|Refactoring of cache
 
|
 
|
 
|0%
 
|0%
Line 132: Line 132:
 
|
 
|
 
|-
 
|-
!PDF generation system
+
|PDF generation system
 
|
 
|
 
|0%
 
|0%
Line 138: Line 138:
 
|We are thinking of dropping this feature. See the discussion at http://tinyurl.com/obv5j6
 
|We are thinking of dropping this feature. See the discussion at http://tinyurl.com/obv5j6
 
|-
 
|-
!Convert all layouts to semantic and XHTML strict
+
|Convert all layouts to semantic and XHTML strict
 
|
 
|
 
|0%
 
|0%
Line 144: Line 144:
 
|There are some efforts going on for this. See the topic at http://tinyurl.com/qrb39k
 
|There are some efforts going on for this. See the topic at http://tinyurl.com/qrb39k
 
|-
 
|-
!Timezones, JDate and Datetime (gregorian, julian, shamsi, hijri, jewish, buddhist, ethiopian, chinese and french calendar)
+
|Timezones, JDate and Datetime (gregorian, julian, shamsi, hijri, jewish, buddhist, ethiopian, chinese and french calendar)
 
|
 
|
 
|0%
 
|0%
Line 150: Line 150:
 
|
 
|
 
|-
 
|-
!Refactoring all components to use JForm
+
|Refactoring all components to use JForm
 
|
 
|
 
|10%
 
|10%
Line 156: Line 156:
 
|
 
|
 
|-
 
|-
!JError refactoring
+
|JError refactoring
 
|
 
|
 
|5%
 
|5%
Line 162: Line 162:
 
|
 
|
 
|-
 
|-
!Captcha helpers for forms
+
|Captcha helpers for forms
 
|
 
|
 
|0%
 
|0%
Line 168: Line 168:
 
|This will be possible using JForm triggers. We are not going to bundle a Captcha library in core package
 
|This will be possible using JForm triggers. We are not going to bundle a Captcha library in core package
 
|-
 
|-
!Localising invalid token message
+
|Localising invalid token message
 
|
 
|
 
|0%
 
|0%
Line 174: Line 174:
 
|die('Invalid Token') will be replaced by jexit(JText::_('JInvalid_Token'))
 
|die('Invalid Token') will be replaced by jexit(JText::_('JInvalid_Token'))
 
|-
 
|-
!Ability to select multiple categories for some views
+
|Ability to select multiple categories for some views
 
|
 
|
 
|0%
 
|0%
Line 180: Line 180:
 
|
 
|
 
|-
 
|-
!New sample content
+
|New sample content
 
|
 
|
 
|0%
 
|0%
Line 186: Line 186:
 
|
 
|
 
|-
 
|-
!Reformat translation files to adhere to proper INI specs
+
|Reformat translation files to adhere to proper INI specs
 
|
 
|
 
|0%
 
|0%
Line 192: Line 192:
 
|In 1.6 we will use PHP's own INI parser and will namespace strings. For example "Weblinks_Category_Fieldname" or "Config_Application_Name"
 
|In 1.6 we will use PHP's own INI parser and will namespace strings. For example "Weblinks_Category_Fieldname" or "Config_Application_Name"
 
|-
 
|-
!Migration script from 1.5 to 1.6
+
|Migration script from 1.5 to 1.6
 
|
 
|
 
|0%
 
|0%
Line 198: Line 198:
 
|
 
|
 
|-
 
|-
!Consolidating com_content modules into two modules
+
|Consolidating com_content modules into two modules
 
|
 
|
 
|0%
 
|0%
Line 204: Line 204:
 
|
 
|
 
|-
 
|-
!Queue redirects
+
|Queue redirects
 
|
 
|
 
|0%
 
|0%
Line 210: Line 210:
 
|
 
|
 
|-
 
|-
!Add module assignment to menu items creation
+
|Add module assignment to menu items creation
 
|
 
|
 
|0%
 
|0%
Line 216: Line 216:
 
|
 
|
 
|-
 
|-
!Replace JParameter with JForm-compatibilitylayer
+
|Replace JParameter with JForm-compatibilitylayer
 
|
 
|
 
|0%
 
|0%
Line 222: Line 222:
 
|We did not deeply investigate this yet. It would help to see what is needed for this
 
|We did not deeply investigate this yet. It would help to see what is needed for this
 
|-
 
|-
!Go to menu instead of menutype when clicking menuname
+
|Go to menu instead of menutype when clicking menuname
 
|
 
|
 
|0%
 
|0%
Line 228: Line 228:
 
|Usability thing: its not intuitive, that you have to click that small icon in the menu manager to see the actual menu, while you can only change the name of the menutype when clicking the menuname."
 
|Usability thing: its not intuitive, that you have to click that small icon in the menu manager to see the actual menu, while you can only change the name of the menutype when clicking the menuname."
 
|-
 
|-
!Ability to load additional layouts with a template
+
|Ability to load additional layouts with a template
 
|
 
|
 
|0%
 
|0%
Line 234: Line 234:
 
|
 
|
 
|-
 
|-
!Help System Expansion
+
|Help System Expansion
 
|
 
|
 
|0%
 
|0%

Revision as of 14:46, 3 August 2009

Replacement filing cabinet.png
This page has been archived - Please Do Not Edit or Create Pages placed in this namespace. The pages in the Archived namespace exist only as a historical reference, it will not be improved and its content may be incomplete.
Task Blocker Status Contact person Description
Implement JForm library Alpha 95% Rob Schley, Andrew Eddie This library allows to create forms from XML definition files. See the introduction at http://tinyurl.com/psj6c6
Implement new event triggers Alpha 60% onBeforeRender, triggers in JForm, onContentDisplay etc.
Implement new controller dispatcher Alpha 100% See the discussion at http://tinyurl.com/qlh5bg where Louis explained how this works in 1.6
Upgrade to Mootools 1.2 Alpha 90% Louis Landry, Ercan Özkaya This is mostly finished but there are a few things to do. For example how to load more library. See the discussion at http://tinyurl.com/p5cvbc
Javascript translation Alpha 100% This is implemented and finished. Take a look at JOpenID Javascript class and mod_login for details
New extension updater work Alpha 80% Samuel Moffatt New extension updater is implemented, but not finished yet.
Conversion of INI to JSON Alpha 100% We now use JSON format for storing parameters in the database. This is completed for core components.
Nested categories Alpha 70% Hannes Papenberg
Access control list (ACL) Alpha 10% Hannes Papenberg, Louis Landry
Replace Contacts with Contact Directory Alpha 30% Gergő Erdősi Replacement of files is ready, however there are some parts which aren't working
User management system Alpha 5% The new com_members needs to be proof checked.
JContent class Alpha 0% Anthony Ferrara JContent is a class that will allow us to have a generic way to fire plugins on content
Documenting the triggers, finishing them 10% Louis Landry, Rob Schley, Andrew Eddie The triggers for JForm need to be implemented in the respective extension, which has not happened yet. We need a plan for this one.
MVCing backend components 20% Most of the back-end components have MVC file structure, but they are not fully MVC yet
Parameters for templates in the database 50% Hannes Papenberg Especially the UI will take a lot of work, we might have to change the database for this one.
Add template parameter set to menu item creation 10% Hannes Papenberg
Refactoring parameters 0% A review of the current parameters and implementing new ones for the new category system.
Comments system 0% Louis Landry, Andrew Eddie, Rob Schley It will be donated by JXtended and will be added to trunk somewhere in the beta phase.
Hooks for external authentication systems 0% Need to be implemented in JUser and in the code where Usergroups are managed. Maybe we need a JUsergroupclass
Database driven install log 0% Samuel Moffatt
Refactoring of cache 0% Anthony Ferrara
PDF generation system 0% We are thinking of dropping this feature. See the discussion at http://tinyurl.com/obv5j6
Convert all layouts to semantic and XHTML strict 0% Amy Stephen There are some efforts going on for this. See the topic at http://tinyurl.com/qrb39k
Timezones, JDate and Datetime (gregorian, julian, shamsi, hijri, jewish, buddhist, ethiopian, chinese and french calendar) 0% Hannes Papenberg
Refactoring all components to use JForm 10%
JError refactoring 5% Anthony Ferrara
Captcha helpers for forms 0% This will be possible using JForm triggers. We are not going to bundle a Captcha library in core package
Localising invalid token message 0% die('Invalid Token') will be replaced by jexit(JText::_('JInvalid_Token'))
Ability to select multiple categories for some views 0%
New sample content 0%
Reformat translation files to adhere to proper INI specs 0% In 1.6 we will use PHP's own INI parser and will namespace strings. For example "Weblinks_Category_Fieldname" or "Config_Application_Name"
Migration script from 1.5 to 1.6 0%
Consolidating com_content modules into two modules 0% Mark Dexter, Hannes Papenberg
Queue redirects 0% Anthony Ferrara, Rob Schley
Add module assignment to menu items creation 0%
Replace JParameter with JForm-compatibilitylayer 0% We did not deeply investigate this yet. It would help to see what is needed for this
Go to menu instead of menutype when clicking menuname 0% Usability thing: its not intuitive, that you have to click that small icon in the menu manager to see the actual menu, while you can only change the name of the menutype when clicking the menuname."
Ability to load additional layouts with a template 0% Hannes Papenberg
Help System Expansion 0% Marieke van der Tuin, Chris Davenport