Re: [Phpslash-devel] Blocks Everywere, Navbar control

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

Howdy Joe,

On Thu, 2003-10-02 at 04:24, Joe Stewart wrote:
> On Thu, Oct 02, 2003 at 11:17:04AM -0400, Mike Gifford wrote:
> > I'm writing mostly to find out when the new block feature that you've
> > been working on is likely to get released.  I'm not sure when the next
> > release is planned, but am planning to put out a new release of Back-End
> > CMS very soon.
> Glad to see Back-End development proceeding.  I've been busy moving our
> office.  So hopefully will get cranked back up soon.

Moving takes a heck of a lot of work.

I'm looking forward to the new release of BE..  Quite like our new
installer script..  Not sure if psl decided to adopt the one which was
being circulated a while back.

> So no release from me planned yet.

We've made a lot of improvements over 0.5.4 so wanted to put out a
release to move us closer to the psl numbering..  So the jump for the
next release will be from .5 to .7

> > One of the contributors to Back-End has created some code for bottom
> > blocks to allow for some navigational elements to be dropped in directly
> > here.  This sounded to me like a lot like the flexibility that the PSL
> > team is working for.
> phpSlash supports this with just changing a couple of things now.  The
> -dev branch does already support top and bottom blocks.

How stable is the development branch and is this top/bottom block
function going to carry on to future releases?  I'd assume so, but just
wanted to find out if there was any concern about this.

> > I also wanted to know if there was any attempt to extend the ability to
> > turn on/off navbar links from the config.ini.php file.  I do think it
> > would be useful to allow the more detailed control over what appears in
> > the navbar than by simply turning on/off a module.  Certainly for things
> > like the links. 
> I'd like to see some patches for this, or a web management interface.

We'll certainly keep you up-to-date if we incorporate a change like
this..  Would really want to get your buy-in before implementing it.. 
Not that it would have to be implemented right away, but that it would
be something which would be in future releases.

> I stalled on it with what seemed to be a limitation of the "ini" array
> stuff being limited to one level rather than having nested arrays.

I haven't investigated this, but can understand how that would be a
pain..  It might make sense build rather a web interface so it could be
turned off there as opposed to the ini.

Mike
-- 
Mike Gifford, OpenConcept Consulting
Free Software for Social Change -> http://www.openconcept.ca
Fair Vote Petition - http://www.fairvotecanada.org/petition.php
The master's tools will never dismantle the master's house - A Lorde