[Tikiwiki-devel] Tiki Packages

[Christian F. <sp...@st...>]

gongo (et al), 

I actually have started this process. there are two problems that i would 
like to solve separately: code encapsulation & tiki bloat (a "real" core 
rewrite).

See "Phase 1.9" on updated 
http://tikiwiki.org/tiki-index.php?page=CoreTwoDev

In a nutshell, my first step is to simply re-organize all that code that
currently exists without rewriting any of it. I want to put all folder in
./lib/* up to the root, and move all tiki-*.php files into the appropriate
folder (that used to be in lib). A Tiki Package is simply a folder of 
similar functionality.

It took me 1/2 hour to google, download, and port a php weather package 
into Tiki:  http://th.steelsun.com/lib/weather/index.php
It was truly stunning how little work i had done and how much potential i 
had.

This is currently underway in SPIDER-CORE branch:
http://tikiwiki.org/tiki-index.php?page=CvsExperimentalBranches

The goal of this 1.9 phase (directory restructing) is to preserve all code
that exists and to add as little as possible. Once functionality is
properly encapsulated from an organizational perspective, then work on
rewriting tikilib,tikisetup, permsissions, etc, etc, etc, (i.e. a new
lean & modular core) can begin and proceed in a much more independent 
fashion. Current features can hopefully get moved to a new core on a piece 
at a time and preserve old feature functionality using the deprecated 
tikilib.

Moving on to 2.0 Phase, I could see several possible cores being written
independently, but sites would still use the same feature packages. For
example, some features may depend on a gongo core, others may not. A
spider core could be extremely fast, but only support a few things. So a
very lean, base API is a must for all cores, and each core can extend
beyond that however they see fit.

My philosophy is to create an environment where all answers can be right.
Tiki's integration of features is great, however a site should not _have_
to accept a feature (stability or speed are main reasons). This power
means specialized packages can be built, or Package releases can move
indendently.

But my main thrust right now is to get things moved around so the real
"core" wars can start (2.0), and each idea can move forward without
affecting/depending on someone else's. My weather package was a simple
test that made me realize this is all very, very achievable.

Btw, i think the current template mechanism - optionally overriding 
only things you are about - is awesome and a very good design.



On 8 Jan 2004 go...@vt... wrote:

> 
> > 
> > Another interesting site is: http://www.opensourcecms.com/
> > 
> > it has installed versions of all open source CMS + more out there. db's 
> > get nuked every hour, but you can login as admin and fiddle with most 
> > everything. great way to compare / contrast concepts and installations.
> 
> tiki installation is still 1.7.4, and read the forum comments on
> http://www.opensourcecms.com/modules.php?name=Forums&file=viewtopic&t=180
> 
> a bit of a shame to see that they have not yet the benefits of
> adodb, tiki-bloat etc :-)
> 
> Interestingly enough, most cmsses in that list (even if you take half 
> of them off for being *nukes) have a module/plugin/add-on/feature
> installation thingy, even far more advanced than what is currently
> in HEAD for tikiwiki.
> 
> Maybe time to take on a reworked core/centralisation of some 
> functionality and to start implementing 
> TikiPackager/TikiInstallFeatureDev.
> 
> any takers?
> 
> grtz,
> Dimitri Smits
> aka Gongo
> 
> 
> 
> ---------------------------------------------------------------------
> Gratis internet toegang en jouw @vt4.net adres op http://www.vt4.net
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Perforce Software.
> Perforce is the Fast Software Configuration Management System offering
> advanced branching capabilities and atomic changes on 50+ platforms.
> Free Eval! http://www.perforce.com/perforce/loadprog.html
> _______________________________________________
> Tikiwiki-devel mailing list
> Tik...@li...
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
> 

[ \ /
[ >X<   sp...@st...   |   http://www.steelsun.com/
[ / \