Re: Global.conf

On Friday 22 July 2005 6:00, Albert Lash wrote:
> You are right, I guess I was asking why paths are hardcoded as they are. I
> would not be able to access the config:: function from xsl, without using
> the php functionality, i.e. config is not in flow?

If you need stuff in flow then add that in your prepend. But the stream stuff 
can access anything. I don't think there is anything in CVS (maybe) for 
streams but I wrote one for myself a while back that could access stuff. 
Bitflux folks have some nice slide shows that go over that if you look for 
it.

> I read the docs and it says that if a mode is set then config::getSection
> will try to get the mode that is set, but if I have two sections dev and
> live, it gets live even though in the builder the mode is set to dev.

That would be bugzzz then.

> Thanks Joshua, what sort of projects are you working on now?

Still finishing up stuff. Gonna be doing that for a month more then back to Nx 
and playtime. Taking some trips back to Europe again then :)

> Albert
>
> On Thu, 21 Jul 2005, Joshua wrote:
> > On Thursday 21 July 2005 11:04, Albert Lash wrote:
> > > Or master.conf...
> >
> > It doesn't create a constant. Only on some things like paths. It makes a
> > concatenated config which can be accessed using the Config class.
> > Eventually it will turn into a serialize array file file I think.
> >
> > So you can add anything and get it using the config::get (I think --
> > check docs) method.
> >
> > J
> >
> > > Foundry parses this in a manual manner, creating a constant for each
> > > directive. Can this be done dynamically, so that if there is an entry,
> > > a constant (supplied by gloabal.xml or master.xml) is created. That
> > > way, if you edit the structure of global.xml, you don't have to update
> > > foundry.php as well.
> > >
> > >
> > > Thoughts?
> > >
> > > Al