You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Laurent Trillaud <lt...@jouve.fr> on 2003/10/30 10:05:09 UTC
RE : Skins in the new Portal Engine
Well, if I understand you have only 1 static page that is render by
multiple CSSs.
IMO a portal is not very useful for you, but any way.
You can create a new skin.
1. Put your CSS as usual in skins/MySkin/css,
2. Edit the skins/MySkin/styles/portal-page.xsl to put your single XSL
file. You can ignore other XSLs files. And don't call any other
<xsl:apply-templates/> that are useful to render menu, coplet and so on.
3. If you don't want login, put a pass-through XSL in
skins/MySkin/styles/login-html.xsl
It should work!
Laurent Trillaud
> -----Message d'origine-----
> De : JACOB, ERIC [mailto:eric.jacob@bell.ca]
> Envoyé : mercredi 29 octobre 2003 14:15
> À : users@cocoon.apache.org
> Objet : Skins in the new Portal Engine
>
>
> Hi all,
>
> What I understand, when you want to create a new skin, you have to
write
> many XSL files and switch the skin in the portal sitemap with the
global
> variable:
>
> <map:global-variables>
> <skin>skins/common/</skin>
> </map:global-variables>
>
> But my problem is that I use CSS files to customize my portal with
only
> one
> HTML page... So, I don't want to create different XSL for each skin.
> Instead, I want to use only one set of XSL files with many CSS. How I
can
> use the skin mechanism in Cocoon to achieve that?
>
> See the Zen Garden to know what I mean, a demonstration of what can be
> accomplished visually through CSSbased design.
> http://www.csszengarden.com/
>
> Thank,
>
> Eric Jacob
>
> PS: Sorry, my english is not very good...
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
RE: RE : RE : Skins in the new Portal Engine
Posted by "JACOB, ERIC" <er...@bell.ca>.
Laurent,
That's my problem! I don't want to switch a directory, I want to switch a
CSS. My XSLs are still the same through my skins so I don't want to
duplicate them across many directories. Only my CSSs are going to change
(that is the beauty of CSS). I've already read the documentation for the
portal block and it doesn't help me very much... Maybe I missed something?
Thanks,
Eric
-----Original Message-----
From: Laurent Trillaud [mailto:ltrillaud@jouve.fr]
Sent: Friday, October 31, 2003 8:45 AM
To: users@cocoon.apache.org; eric.jacob@bell.ca
Subject: RE : RE : Skins in the new Portal Engine
Jacob
This variable is design to switch skin, i.e. to switch a directory that
contains both CSSs and XSLs.
You are free to update the tab.xsl and use DIV instead.
For a better understanding, on how a portal page is built, have a look
on
http://cocoon.apache.org/2.1/developing/portal/portal-block.html
Laurent Trillaud
> -----Message d'origine-----
> De : JACOB, ERIC [mailto:eric.jacob@bell.ca]
> Envoyé : jeudi 30 octobre 2003 19:58
> À : users@cocoon.apache.org
> Objet : RE: RE : Skins in the new Portal Engine
>
> Thanks for the reply, but I think my question was not clear enough, so
> I'll
> ask it again differently.
>
> I looked to the XSL files in the portal demo and I was surprised by
the
> use
> of TABLE tags for the layout. I want to use DIV tags with CSS to
control
> the
> style of my hypertext document. In addition, I want a mechanism that
> allows
> the user to change the skin (in my case the CSS file). I'm wondering
how I
> can achieve that within the new Portal Engine. Can I use the global
> variable
> to specify the CSS using this variable in my unique portal-page.xsl
for
> example?
> <map:global-variables>
> <skin>008.css<skin>
> </map:global-variables>
>
> Any suggestions?
>
> Thanks in advance.
>
> Eric Jacob
>
>
> -----Original Message-----
> From: Laurent Trillaud [mailto:ltrillaud@jouve.fr]
> Sent: Thursday, October 30, 2003 4:05 AM
> To: users@cocoon.apache.org; eric.jacob@bell.ca
> Subject: RE : Skins in the new Portal Engine
>
> Well, if I understand you have only 1 static page that is render by
> multiple CSSs.
> IMO a portal is not very useful for you, but any way.
> You can create a new skin.
> 1. Put your CSS as usual in skins/MySkin/css,
> 2. Edit the skins/MySkin/styles/portal-page.xsl to put your single XSL
> file. You can ignore other XSLs files. And don't call any other
> <xsl:apply-templates/> that are useful to render menu, coplet and so
on.
> 3. If you don't want login, put a pass-through XSL in
> skins/MySkin/styles/login-html.xsl
> It should work!
> Laurent Trillaud
>
> > -----Message d'origine-----
> > De : JACOB, ERIC [mailto:eric.jacob@bell.ca]
> > Envoyé : mercredi 29 octobre 2003 14:15
> > À : users@cocoon.apache.org
> > Objet : Skins in the new Portal Engine
> >
> >
> > Hi all,
> >
> > What I understand, when you want to create a new skin, you have to
> write
> > many XSL files and switch the skin in the portal sitemap with the
> global
> > variable:
> >
> > <map:global-variables>
> > <skin>skins/common/</skin>
> > </map:global-variables>
> >
> > But my problem is that I use CSS files to customize my portal with
> only
> > one
> > HTML page... So, I don't want to create different XSL for each skin.
> > Instead, I want to use only one set of XSL files with many CSS. How
I
> can
> > use the skin mechanism in Cocoon to achieve that?
> >
> > See the Zen Garden to know what I mean, a demonstration of what can
be
> > accomplished visually through CSSbased design.
> > http://www.csszengarden.com/
> >
> > Thank,
> >
> > Eric Jacob
> >
> > PS: Sorry, my english is not very good...
> >
> >
> >
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> > For additional commands, e-mail: users-help@cocoon.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
RE : RE : Skins in the new Portal Engine
Posted by Laurent Trillaud <lt...@jouve.fr>.
Jacob
This variable is design to switch skin, i.e. to switch a directory that
contains both CSSs and XSLs.
You are free to update the tab.xsl and use DIV instead.
For a better understanding, on how a portal page is built, have a look
on
http://cocoon.apache.org/2.1/developing/portal/portal-block.html
Laurent Trillaud
> -----Message d'origine-----
> De : JACOB, ERIC [mailto:eric.jacob@bell.ca]
> Envoyé : jeudi 30 octobre 2003 19:58
> À : users@cocoon.apache.org
> Objet : RE: RE : Skins in the new Portal Engine
>
> Thanks for the reply, but I think my question was not clear enough, so
> I'll
> ask it again differently.
>
> I looked to the XSL files in the portal demo and I was surprised by
the
> use
> of TABLE tags for the layout. I want to use DIV tags with CSS to
control
> the
> style of my hypertext document. In addition, I want a mechanism that
> allows
> the user to change the skin (in my case the CSS file). I'm wondering
how I
> can achieve that within the new Portal Engine. Can I use the global
> variable
> to specify the CSS using this variable in my unique portal-page.xsl
for
> example?
> <map:global-variables>
> <skin>008.css<skin>
> </map:global-variables>
>
> Any suggestions?
>
> Thanks in advance.
>
> Eric Jacob
>
>
> -----Original Message-----
> From: Laurent Trillaud [mailto:ltrillaud@jouve.fr]
> Sent: Thursday, October 30, 2003 4:05 AM
> To: users@cocoon.apache.org; eric.jacob@bell.ca
> Subject: RE : Skins in the new Portal Engine
>
> Well, if I understand you have only 1 static page that is render by
> multiple CSSs.
> IMO a portal is not very useful for you, but any way.
> You can create a new skin.
> 1. Put your CSS as usual in skins/MySkin/css,
> 2. Edit the skins/MySkin/styles/portal-page.xsl to put your single XSL
> file. You can ignore other XSLs files. And don't call any other
> <xsl:apply-templates/> that are useful to render menu, coplet and so
on.
> 3. If you don't want login, put a pass-through XSL in
> skins/MySkin/styles/login-html.xsl
> It should work!
> Laurent Trillaud
>
> > -----Message d'origine-----
> > De : JACOB, ERIC [mailto:eric.jacob@bell.ca]
> > Envoyé : mercredi 29 octobre 2003 14:15
> > À : users@cocoon.apache.org
> > Objet : Skins in the new Portal Engine
> >
> >
> > Hi all,
> >
> > What I understand, when you want to create a new skin, you have to
> write
> > many XSL files and switch the skin in the portal sitemap with the
> global
> > variable:
> >
> > <map:global-variables>
> > <skin>skins/common/</skin>
> > </map:global-variables>
> >
> > But my problem is that I use CSS files to customize my portal with
> only
> > one
> > HTML page... So, I don't want to create different XSL for each skin.
> > Instead, I want to use only one set of XSL files with many CSS. How
I
> can
> > use the skin mechanism in Cocoon to achieve that?
> >
> > See the Zen Garden to know what I mean, a demonstration of what can
be
> > accomplished visually through CSSbased design.
> > http://www.csszengarden.com/
> >
> > Thank,
> >
> > Eric Jacob
> >
> > PS: Sorry, my english is not very good...
> >
> >
> >
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> > For additional commands, e-mail: users-help@cocoon.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
RE: RE : Skins in the new Portal Engine
Posted by "JACOB, ERIC" <er...@bell.ca>.
Thanks for the reply, but I think my question was not clear enough, so I'll
ask it again differently.
I looked to the XSL files in the portal demo and I was surprised by the use
of TABLE tags for the layout. I want to use DIV tags with CSS to control the
style of my hypertext document. In addition, I want a mechanism that allows
the user to change the skin (in my case the CSS file). I'm wondering how I
can achieve that within the new Portal Engine. Can I use the global variable
to specify the CSS using this variable in my unique portal-page.xsl for
example?
<map:global-variables>
<skin>008.css<skin>
</map:global-variables>
Any suggestions?
Thanks in advance.
Eric Jacob
-----Original Message-----
From: Laurent Trillaud [mailto:ltrillaud@jouve.fr]
Sent: Thursday, October 30, 2003 4:05 AM
To: users@cocoon.apache.org; eric.jacob@bell.ca
Subject: RE : Skins in the new Portal Engine
Well, if I understand you have only 1 static page that is render by
multiple CSSs.
IMO a portal is not very useful for you, but any way.
You can create a new skin.
1. Put your CSS as usual in skins/MySkin/css,
2. Edit the skins/MySkin/styles/portal-page.xsl to put your single XSL
file. You can ignore other XSLs files. And don't call any other
<xsl:apply-templates/> that are useful to render menu, coplet and so on.
3. If you don't want login, put a pass-through XSL in
skins/MySkin/styles/login-html.xsl
It should work!
Laurent Trillaud
> -----Message d'origine-----
> De : JACOB, ERIC [mailto:eric.jacob@bell.ca]
> Envoyé : mercredi 29 octobre 2003 14:15
> À : users@cocoon.apache.org
> Objet : Skins in the new Portal Engine
>
>
> Hi all,
>
> What I understand, when you want to create a new skin, you have to
write
> many XSL files and switch the skin in the portal sitemap with the
global
> variable:
>
> <map:global-variables>
> <skin>skins/common/</skin>
> </map:global-variables>
>
> But my problem is that I use CSS files to customize my portal with
only
> one
> HTML page... So, I don't want to create different XSL for each skin.
> Instead, I want to use only one set of XSL files with many CSS. How I
can
> use the skin mechanism in Cocoon to achieve that?
>
> See the Zen Garden to know what I mean, a demonstration of what can be
> accomplished visually through CSSbased design.
> http://www.csszengarden.com/
>
> Thank,
>
> Eric Jacob
>
> PS: Sorry, my english is not very good...
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org