Re: [Phpslash-devel] How many page scripts do we need?
Brought to you by:
joestewart,
nhruby
From: Joe S. <joe...@us...> - 2003-04-30 15:44:30
|
On Wed, Apr 23, 2003 at 11:22:15AM -0500, Joe Stewart wrote: > > With the -dev modules, you really don't need all the different > scripts. GET variables can trigger the module and page to use. > A variation is to use the existing phpSlash structure and assign sections for the modules. Otherwise the modules always have the same blocks as the home page. A side note - We've been able to apply arguments to getStories like max and section. What would be the best way to pass these arguments as block options? > For instance they could be called something like: > > index.php?module=Story&page=admin > > How far should this go? All the way to only index.php? and > backend.php? > > The entire admin/ directory can go. > > I'd like to eventually replace the about page with either a block or > story. It's pretty bad now that it can't be modified through the admin > interface. > What else cannot be done through the web interface that maybe should be? Assigning pages to navbar items comes to mind for me. With module sections, there is a lot of flexibility in the page that is presented. - a different header for some sections. ( header block) - different arguments to the modules for some sections. (module block) - multiple module blocks per page. These are probably the major things I've had to do in the scripts. - different skins for different sections (page block) - You can do other weird things like make an entire section a static page using blocks. (page column) Joe |