Carsten Ziegeler wrote:
The current solution for adding own components to Cocoon is to (optionally)
add the role to the cocoon.roles file and to add the component
(configuration)
to the global cocoon.xconf file.
What about providing the possibility to add components/roles on a per
sitemap
level?
Sylvain Wallez wrote:
>
> +1. You already can put any component declaration in ,
:( You know my opinion about ;)
> so it's actually just a matter of reading this declaration in
> an external file.
Yes, with the additional that this is then *official* and *supported* :)
Carsten
Ralph Goers wrote:
>
> Carsten Ziegeler said:
> >
> > Ok, I just reread the thread you're refering to and it seems to me
> > that noone was against it, right? So does anyone mind if I
> just implement it?
> >
> > Carsten
>
> Are you done yet? (That's a big +1).
>
No, I'm currently rewriting/
Carsten Ziegeler wrote:
The current solution for adding own components to Cocoon is to (optionally)
add the role to the cocoon.roles file and to add the component
(configuration)
to the global cocoon.xconf file.
What about providing the possibility to add components/roles on a per
sitemap
level?
Carsten Ziegeler said:
>
> Ok, I just reread the thread you're refering to and it seems to me that
> noone was against it, right? So does anyone mind if I just implement it?
>
> Carsten
Are you done yet? (That's a big +1).
Also, once you have this working it would be nice to see if it could be
b
Ralph Goers wrote:
>
> There was a discussion on this very topic (with pretty much the same
> proposal) here while you were on vacation.
Ups.
> However, as I
> recall it was under one of the topics that I believe you
> deleted. :-)
Yepp...[sound of Carsten whistling]...
> You just can't go
Le 17 déc. 04, à 15:06, Carsten Ziegeler a écrit :
...
..
So all of these components are available in this sitemap and in all
subsitemaps.
Adding this (to 2.2) should be very easy and makes adding own stuff
imho
easier...
Sounds great, +1!
-Bertrand
smime.p7s
Description: S/MIME cryptographic
Carsten Ziegeler wrote:
.
What about providing the possibility to add components/roles on a per
sitemap level?
Where do I sign? 8-)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
--
Carsten Ziegeler wrote:
The current solution for adding own components to Cocoon is to (optionally)
add the role to the cocoon.roles file and to add the component
(configuration)
to the global cocoon.xconf file.
What about providing the possibility to add components/roles on a per
sitemap
level?
Tim Larson wrote:
>
> I like both ideas, because they allow more modular configuration.
> It seems this may also help with virtual hosting via subsitemaps?
I think so, yes.
> Could we allow live updates from changes made to the
> roles-file and config-file like we do for changes to sitemaps?
>
S
On Fri, Dec 17, 2004 at 03:06:20PM +0100, Carsten Ziegeler wrote:
> The current solution for adding own components to Cocoon is to
> (optionally) add the role to the cocoon.roles file and to add
> the component (configuration)to the global cocoon.xconf file.
>
> What about providing the possibili
The current solution for adding own components to Cocoon is to (optionally)
add the role to the cocoon.roles file and to add the component
(configuration)
to the global cocoon.xconf file.
What about providing the possibility to add components/roles on a per
sitemap
level? For example by providing
12 matches
Mail list logo
