Agree rejon, but a long voyage begin with short steps.
Totally. here are the priorities I see that are blocking aiki from more use:
>
> 1.) admin interface is shit.
> SOLUTION: Make mockup of new interface, allow any sysGOD/root change
> admin interfaces
>
>
> 2.) widgets are totally too complicated.
> SOLUTION: Simplify and Type widgets.
>
some ideas
- Aiki is a dynamic object. We can create custom classes for each site. For
example:
<aiki->ocal->clipartThumb("SELECT ..FROM AIKI WHERE $1") aiki>
must show a list of clipart ($1 is URL parameter). This can be used in
many widget, also ensuring consistency.
3.) aikimarkup is inconsistent.
> SOLUTION: come up with new
>
The main problem is the backwards compatibility.
5.) need ability to work on test site, and push to live site when
> confirmed changes work (multi-db)
> SOLUTION: add multi-db capability, allow syncing and pushing between
> databases
>
> other step:
- make avaible a copy of open-clipart database (with some restriction) to
allow some developers work with a local copy (sandbox).
6.) bad documentation (but getting better, need more phpdoc and
> in-interface documentation)
>
code is documentation. We need more modular code.
_______________________________________________
Mailing list: https://launchpad.net/~aikiframework-devel
Post to : [email protected]
Unsubscribe : https://launchpad.net/~aikiframework-devel
More help : https://help.launchpad.net/ListHelp
