gsoc:2009:phdoe
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
gsoc:2009:phdoe [2009/07/24 05:11] – Update Executing timeline mrkschan | gsoc:2009:phdoe [2011/04/06 10:59] – external edit 127.0.0.1 | ||
---|---|---|---|
Line 37: | Line 37: | ||
* July 03 - The first milestone is reached =] JS namespace is clear and going to work on the second milestone. Read the story at [[http:// | * July 03 - The first milestone is reached =] JS namespace is clear and going to work on the second milestone. Read the story at [[http:// | ||
* July 24 - Php files are factored, going to complete a SvnClient for the svn-migration ... Read the story at [[http:// | * July 24 - Php files are factored, going to complete a SvnClient for the svn-migration ... Read the story at [[http:// | ||
+ | * July 28 - cvs2svn is somehow EVIL!!! I'm digging into how svn authenticate from the Http / WebDav perspective ... Read the story at [[http:// | ||
+ | * 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 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 100: | Line 104: | ||
- 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 184: | Line 198: | ||
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.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1