Re: [Phpslash-devel] embracing the future

[Joe S. <joe...@us...>]

On Mon, Oct 27, 2003 at 01:45:48PM +0000, Peter Cruickshank wrote:
> On Sunday 26 Oct 2003 4:24 pm, Luis M wrote:
> 
> ...
> 
> > People should really start trying phpslash-dev module from the cvs. It's
> > pretty much "stable" enough right now to be used in replacement of
> > phpslash-ft. But, remember that's the "experimentation" module. We should
> > probably freeze it as it is right now and do a minor release based on it so
> > that people can try it and we can get an idea of how the migration will be
> > from -ft (current stable release) to -dev. From then on it will be downhill
> > with -dev.
> 
> > Remember that -dev is fully modularized. Everything, every block, story,
> > header behaves in this manner... Great level of "granularity" and also a
> > scary thought that if something goes wrong, it might be hard to know from
> > where the error is coming... that's why we need testing, to improve it to
> > the point that we know for sure we are not missing anything and start
> > replacing our own sites (first) with the minor release (fingers crossed)
> > and deal with possible pitfalls.
> 
> I'm just starting a new project, so thought I'd use -dev. It's been a while 
> since I used phpSlash, so I'm sort of coming at it fresh.
> 
> First impressions on doing a simple default install:
> 
> - I really like the modularisation. The structure is so different tho that  I 
> think it's worth considering calling it 0.8 when it is released (will make it 
> easier to keep Back-End in step with PSL, apart from anything else). Of 
> course, that brings it all scarily close of 1.x... which will be hit by the 
> end of this decade at the current rate :-)
> 
> think it would make it easier to customise skins by making it obvious where 
> the content comes from. (I think Joe mentioned this in the context of using 
> the PEAR template class)
> 

If this isn't working, file a bug report.  The existing templates have not
been moved in the cvs, but it's been tested. 

One thing I don't like.  If your new whiz bang module adds a block type,
The _render.class file has to go in modules/block/blocktypes.

> - The CVS seems to be missing an install guide
> 

True.

> - the last line of config.ini.php is not needed (the ?> element is 
> automatically assumed by PHP)
> 
> - config.ini.php (or INSTALL) should make it clear that phplib needs to be 
> downloaded separately
> 

This is only for a cvs install.  The releases will include phplib.

> - not clear why config-dist.php isnt just config.php - that way you can get a 
> working site by just editng config.ini.php. 
> 

The releases have config-dist.php copied to config.php.

> - Not sure what the point of the show_admin_on_navbar option is. The current 
> note got me confused...
> 

May be time for it to go away.  It's whether you want the login/logout in
the navbar.

> Apart from that, the install was pretty smooth.
> 
> Comments on the example data:
> 
> - it would be great if Home was section 1. Put that down to me being 
> neurotic...
> 

hmm... Sounds good to me.  Should be able to work around with upgrade
scripts.

> - INSTALL should make it clear that the example data assumes that the 
> public_html directory is visible to the web client (I think it would be 
> better if installers were encouraged to install phpslash away from the 
> webroot and then link public_html to the webroot. Not sure whether that would 
> solve problems with the example data tho).
>

??  Can you go into more detail?

This is how I've been installing it -

The files in public_html get installed in the webroot.
Then create a structure like this:
home-phpslash-etc-config.ini.php - config.php has the full path to it.
             -include/


> - Perhaps the date on the 'Congratulations' article should be updated (it says 
> 4-Dec-2000 right now...)
> 
> 
> HTH someone.

thanks for the impression and suggestions.

Joe

> -- 
> Peter
> 
>