[GSoC 2009] From Page Versioning to Extension Versioning - Joomla! Forum - community, help and support
hello !
i coding on joomla! project during google summer of code , after. i'm new joomla! framework , i'm getting familiar , testing way 1 should code j! component.
during first part of summer finish page versioning extension done flavio @ last year's gsoc. add following features current existing extension:
1. html code differences in component menu, not content differences. regards code differences content not displayed, differences in html tags , attributes of those. available simple change between html view , current existing content view such user see changed , where.
this feature users willing learn/understand simple html code.
2. front-end article restore users have editing privileges (plugin).
3. search function: date, string available in content, version. if multiple users modifications on article information gets lost or (and if have many versions waste lot of time looking through of them information need revert)
after these features finished final step include in j! 1.6 core.
since i'm working on over month implement other features if requested , enough time.
during second part of summer focus on more ambitious project (i hope manage first steps in order accomplish it) continued after gsoc period.
i'll working on extension should try manage versioning system in generalized manner, applied other extensions existing in joomla! installation. administrator should able choose extensions need tracked changed (parameters modified, updates – modifications, etc.). @ moment, plan start following:
1. develop versioning extension core content component. give me insight further development.
2. create user – friendly interface, through administrators can compare different versions of com_content component.
i appreciate comments on this, since way started important. first step toward system restore extension.
until own blog available feel free take @ current version control component described on flavio's last year blog: http://labs.joomla.org/developer/develo ... ntrol.html
this now. appreciate know advices , suggestions.
i coding on joomla! project during google summer of code , after. i'm new joomla! framework , i'm getting familiar , testing way 1 should code j! component.
during first part of summer finish page versioning extension done flavio @ last year's gsoc. add following features current existing extension:
1. html code differences in component menu, not content differences. regards code differences content not displayed, differences in html tags , attributes of those. available simple change between html view , current existing content view such user see changed , where.
this feature users willing learn/understand simple html code.
2. front-end article restore users have editing privileges (plugin).
3. search function: date, string available in content, version. if multiple users modifications on article information gets lost or (and if have many versions waste lot of time looking through of them information need revert)
after these features finished final step include in j! 1.6 core.
since i'm working on over month implement other features if requested , enough time.
during second part of summer focus on more ambitious project (i hope manage first steps in order accomplish it) continued after gsoc period.
i'll working on extension should try manage versioning system in generalized manner, applied other extensions existing in joomla! installation. administrator should able choose extensions need tracked changed (parameters modified, updates – modifications, etc.). @ moment, plan start following:
1. develop versioning extension core content component. give me insight further development.
2. create user – friendly interface, through administrators can compare different versions of com_content component.
i appreciate comments on this, since way started important. first step toward system restore extension.
until own blog available feel free take @ current version control component described on flavio's last year blog: http://labs.joomla.org/developer/develo ... ntrol.html
this now. appreciate know advices , suggestions.
it occurred me earlier week love have sort of versioning work on new version of article, menu, module, , on, , save without publishing, leaving unchanged version published until have done changes want publish in 1 go. if in terms of project little closer this, great!
Comments
Post a Comment