Re: [phpslash-users] Messing with phpSlash - a Slashless phpSlash?

[Joe S. <jo...@cm...>]

Hi Mike, 

As I get a couple of minutes here and there I'm taking a look, and will 
probably have some more questions/comments along the way.

On Thu, Apr 25, 2002 at 06:26:07PM -0400, Mike Gifford wrote:
> Hello,
> 
> I mentioned to this list that I was going to try to gut phpSlash so that
> it is possible to build related scripts based on the core security,
> session, organization of phpSlash..
> 
> I've done this here:
> http://www.openconcept.on.ca/empty_phpSlash/
> 
> There's a heck of a lot to rip away from the new interface..  The link
> above is for perhaps a simple web log..  Who knows..  I just wanted
> something that would allow viewing by list or detail, editing, deleting
> & adding new articles.
>

Thanks for putting the effort into this.

How well did the $_PSL['module']['Glossary'] = false; type deal work.  I 
knew it worked for some simple cases, and then haven't pursued it further.  
Just was trying to get more modular for this kind of thing to happen - 
adding new stuff and removing unneeded modules.

> 
> I am hoping to use this as the base of the new Back-End.org .5 code.. 
> I've also got a number of other little scripts (photogallery/postcard,
> links directory, web campaign scripts - for when time and clients
> demand) that would be worth moving into this shell so that they can be
> more secure and also allow seamless integration between different web
> applications.
> 

Your end use may be my answer here but -

What are the main changes for Article_base.class/Article.class from 
Story_base/Story?  It looks so similar that it might be better to extend 
Article from Story and then change/add methods as needed.

The extractStories can accept a field list to reduce the fields returned.  
However, I see that extractStory never got that ability.

But since you may be porting away from phpSlash, I could see moving to a 
new class instead of extending Story.class.

> If anyone has any objections/concerns to the general idea expressed
> here, please let me know..  I am hoping to have code to contribute back
> to phpSlash (and that will be a lot easier if there are commonalities
> between the coding projects)..
> 

No objections here.  I'd really like to see phpSlash flexible enough to be 
used as the framework.  And then build what you need on top of it.

that's all for now.

Joe

> Mike
> -- 
> Mike Gifford, OpenConcept Consulting, http://www.openconcept.ca
> Open Source Web Applications for Social Change
> New Site Launched: http://www.patmartin.org/
> War is a poor chisel to carve out tomorrows. ML King, Jr.
>