Forum OpenACS Development: Re: default, site and blank master templates

4: Re: default, site and blank master templates (response to 3)

Posted by Lars Pind on 01/06/04 03:54 PM

It's called "blank", because that's what it is. It gives you a blank page, nothin' on it.

If you called it top-master, that would (to me) imply that it includes the top navbar -- which is what the site-master currently does.

The reason for the split between site-master and default-master is that the site-master is (supposedly) the stuff that stays constant across your site (login/logout, home page link), whereas you'd switch default-master for different purposes, e.g.:

- Your organization's public pages may have some left-side navigation

- Your organization's "community spaces" may use the group-master template.

- Your "developer home" could use a different navigation -- whatnot.

This is in fact the use-case that's currently implemented in the CVS tree, with the default-master and group-master templates, and the ability to switch between them from /admin/configure.

Would making default-master able to dynamically pick its master template solve your problem? You can fairly easily add a parameter to acs-subsite for that.

/Lars

5: Re: default, site and blank master templates (response to 4)

Posted by Malte Sussdorff on 01/13/04 08:19 PM

Can you give me a reason, why you put the template in /packages/acs-subsite/www ?

Furthermore, wouldn't it make sense to agree to *one* storage facility for *all* templates (e.g. /templates)?

Last but not least, if we do this, would it be possible to automatically load all available templates to be useable in ://admin/configure).

What do you guys think. Jeff, does this interfere with your work.

I'm a little bit annoyed of looking all over my OpenACS installation on places where I can change the look and feel of my site. Gosh, I'm not even willing to write documentation for this as it s***s so much.

8: Re: default, site and blank master templates (response to 5)

Posted by Lars Pind on 01/14/04 09:48 AM

Malte,

It should've gone in acs-subsite/lib/, but we didn't have /lib back then.

I put it in the acs-subsite package, because it's a template for acs-subsite ... just like a package-specific master template typically goes in the package directory, not in www. I believe there was even some discussion about it somewhere.

I agree on the desire for a standard way to store these, with the caveat that I'm thinking you should be able to install a "skin" package, which would include an acs-subsite master template, images, etc.

I don't think it's realistic for a default install to come with all the skins preinstalled.

/Lars

9: Re: default, site and blank master templates (response to 8)

Posted by Malte Sussdorff on 01/14/04 10:45 AM

From a developers perspective I agree it makes sense to put the templates into /packages/acs-subsite/lib. But I still would put them unter /lib/templates or /templates, as this is a more obvious place for the occasional developer to look into. Any package that starts with acs- and looks like core is off limits to the occasional person installing the system (I'd assume) as this is a core package and you don't fuzz with core packages (at least, that's how I behave e.g. with PHP Horde).

OTOH, it is now documented, so if someone searches for the Community Template, this thread can be found ;).

6: Re: default, site and blank master templates (response to 4)

Posted by Malte Sussdorff on 01/13/04 08:21 PM

group-master.adp. I removed the context bar, but refrained from uploading it to CVS. IMHO with the second level navigation, there is not much sense in using the context bar by default for the group-master.adp. But maybe this is just my site with not enough content.