Re: [Phpslash-devel] Variables.class

[Mike G. <mi...@op...>]

Hi Joe,

On Tue, 2003-07-29 at 07:14, Joe Stewart wrote:
> > Speaking of modules, how is the phpSlash modules code going?  
> Mostly stable.  There is so much flexibility that you can really screw
> things up.  Not sure how I like this part. 

That's the trouble when you give folks enough rope to hang themselves
on.  :)

> Sometimes the bugs have been pretty harsh and unforgiving.

How bad?  Just nasty errors or no errors or worse lost data?

> A few nice things:  
> Easily make a poll, etc on the front page instead of a list of stories.

Ok..  

> The about page can be a story or a block and not necessarily tied to text
> inside a template.

That's good..

> Sections can have different headers and skins.  

How did you set up the header customization?  I'm not even sure where to
start digging..  Is this just built into the standard classes now?  

> If you don't use the TopicBar, you simply don't have that block.  No worry
> about including the class, etc.

There was some talk a while back about making everything a block..  Just
depends on how you want to stack them..

> You can have different footers for the two or three column page.  This is
> important for all CSS pages ( no tables).

Hm..  We haven't incorporated that piece yet..  But can't that all be
done in the index1col -> index3cols templates?

This hasn't been released yet..  Just in the standard CVS module at the
moment, right?

Just trying to figure out where your going so that we can support it
with where we're going with BE at the moment.

> > > I think providing some of the basic common placeholder values to the
> > > template object when initiating it is a natural next step.  We couldn't do
> > > this till we had a slashTemplate class.  Now, we should be able to set
> > > things like rooturl, imageurl, etc. to be provided to all templates.
> > Is someone working on a slashTemplate class?  
> 0.7 includes the slashTemplate class that extends the phplib template
> class.  This allows us to override the set_file method to use absolute
> paths, parent skins, template directories in the module's own directory,
> and as suggested, some initial values for commonly used template
> variables.

Right..  Thought it looked familiar..  just too many files to keep track
of..  

> Previously, we were just using the phplib template class.  So we had keep
> up with the template directory and all variables everywhere.

So what needs to be done to allow template variables to be accessible in
any template?

Mike
-- 
Mike Gifford, OpenConcept Consulting
Free Software for Social Change -> http://www.openconcept.ca
Site Launch - Make Every Vote Count - http://www.fairvotecanada.org
The cruelest lies are often told in silence. -- Robert L Stevenson