gsoc:2009:phdoe
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
gsoc:2009:phdoe [2009/08/05 07:33] – Update executing timeline mrkschan | gsoc:2009:phdoe [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 9: | Line 9: | ||
* Mailing list: phpdoc@lists.php.net | * Mailing list: phpdoc@lists.php.net | ||
* Blog: [[http:// | * Blog: [[http:// | ||
+ | * Live at: [[https:// | ||
===== Abstract ===== | ===== Abstract ===== | ||
Currently, the documentation work is synchronized by cvs. But still, there are potential conflicts due to redundant work. Besides, it's not that easy to share the works or even pipelining the works in a distributed environment. Therefore, a centralized environment is introduced. | Currently, the documentation work is synchronized by cvs. But still, there are potential conflicts due to redundant work. Besides, it's not that easy to share the works or even pipelining the works in a distributed environment. Therefore, a centralized environment is introduced. | ||
Line 40: | Line 41: | ||
* July 29 - a script is written to simulate " | * July 29 - a script is written to simulate " | ||
* August 5 - SvnClient has been implemented and testing are made. However, problems still remain. Read section " | * August 5 - SvnClient has been implemented and testing are made. However, problems still remain. Read section " | ||
+ | * August 13 - I completed the tasks list on my gsoc proposal :p But still... I'm going to keep working on doc-editor ^^ Story at [[http:// | ||
===== UI Structure ===== | ===== UI Structure ===== | ||
Line 103: | Line 105: | ||
- eraseData | - eraseData | ||
+ | * VCSFactory created for replacing VCS specific operation | ||
+ | - getInstance (obtain VCS client based on config DOC_EDITOR_VCS) | ||
* CvsClient created for cvs i/o | * CvsClient created for cvs i/o | ||
- singleton | - singleton | ||
- passwdEncode | - passwdEncode | ||
+ | - authenticate | ||
+ | - checkout | ||
+ | - update | ||
+ | - log | ||
+ | - diff | ||
+ | - commit | ||
+ | * SvnClient created for svn i/o | ||
+ | - singleton | ||
- authenticate | - authenticate | ||
- checkout | - checkout | ||
Line 187: | Line 199: | ||
This section list out ideas for future development. | This section list out ideas for future development. | ||
- | **Further re-structuring the entire thing.** | + | ==== Further re-structuring the entire thing ==== |
+ | === Ideas === | ||
* Create a core module /core, replacing the /php and /js. The core module basically include glues. | * Create a core module /core, replacing the /php and /js. The core module basically include glues. | ||
- | * The core will look for module from /module. /module contains the actual module | + | |
- | * Core will basically glue (concat) controller.php | + | |
- | * Installer will become a script that glues the model.sql | + | * /module-available |
+ | * Core will basically glue (concat) controller.php | ||
+ | * Installer will become a script that glues the model.sql | ||
+ | * ui module naming convention? mod-{module_name}-what? | ||
+ | === Concerns === | ||
+ | * How to handle inter-module interaction? | ||
+ | * For UI, may try having a central registry that register module | ||
+ | * any interaction will be passed through this single agent | ||
+ | * event listener could be used in case for interaction | ||
+ | * if interaction beyond this scope ... may try returning js from XHR that would invoke appropriate handler | ||
+ | ==== WYSIWYG doc-book edit ==== | ||
+ | === Ideas === | ||
+ | * we may try using http:// | ||
+ | * we may supply doc-book elements and attributes, providing appropriate CSS. Plus, doc-book xml <-> html mapping | ||
+ | === Concerns === | ||
+ | * Is wymeditor support doc-book xml <-> html mapping and additional element for its parser? |
gsoc/2009/phdoe.1249457610.txt.gz · Last modified: 2017/09/22 13:28 (external edit)