You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by gr...@bluebottle.com on 2004/11/04 19:01:39 UTC
Re[5]: CForms, mattkruse-lib, dreamteam sample
Hello gounis,
> hi
> i have a question here:
> i have try to follow
> *-display-pipeline match pattern in forms/sitemap
> here the forms-samples-styling.xsl is called
> this .xsl include forms-advanced-field-styling.xsl
> and the second one include forms-calendar-styling.xsl
> in the last .xsl live the resources-uri parameter
> but where and when is this parameter specified ? (or is something that i
> missed?)
this parameter is not specified anywhere, default value is being used:
<xsl:param name="resources-uri">resources</xsl:param>
the content of the element ("resources") is the default value of this parameter
--
Best regards,
grek@bluebottle.com
Re[6]: CForms, mattkruse-lib, dreamteam sample
Posted by go...@osmosis.gr.
hi grek
On Thu, 4 Nov 2004 grek@bluebottle.com wrote:
> Hello gounis,
>
> > so in a scenario where we have more than one directory for forms
> > (more than one sitemap.xmap) then we need multiple copies of mattkruse-lib
>
> > so is it better to have a common place for this library files or not ?
> > if those files are in a cocoon's common place we dont need a selective
> > "javascript import" mechanism in .xsl
>
> I'm not sure what you mean. Multiple copies of cforms resources (including
> mattkruse-lib) would be solution for relative urls?
in our forms samples:
dreamteam sample has its own resources directory. so if this sample
require a date picker, then a copy of mattkruse-lib must be placed in this
recources directory.
if the mattkruse-lib was in /webapp/stylesheets all sub-sitemaps will be
able to access those files.
>
> Selective "javascript import" is useful for reducing loading unnecessary
> resources. It was the reason for improving xsls.
>
for this perspetive i have just to agree with you
>
--stavros
Re[6]: CForms, mattkruse-lib, dreamteam sample
Posted by gr...@bluebottle.com.
Hello gounis,
> so in a scenario where we have more than one directory for forms
> (more than one sitemap.xmap) then we need multiple copies of mattkruse-lib
> so is it better to have a common place for this library files or not ?
> if those files are in a cocoon's common place we dont need a selective
> "javascript import" mechanism in .xsl
I'm not sure what you mean. Multiple copies of cforms resources (including
mattkruse-lib) would be solution for relative urls?
Selective "javascript import" is useful for reducing loading unnecessary
resources. It was the reason for improving xsls.
--
Best regards,
grek@bluebottle.com
Re[5]: CForms, mattkruse-lib, dreamteam sample
Posted by go...@osmosis.gr.
so in a scenario where we have more than one directory for forms
(more than one sitemap.xmap) then we need multiple copies of mattkruse-lib
so is it better to have a common place for this library files or not ?
if those files are in a cocoon's common place we dont need a selective
"javascript import" mechanism in .xsl
WDYT?
--stavros
On Thu, 4 Nov 2004 grek@bluebottle.com wrote:
> Hello gounis,
>
> > hi
>
> > i have a question here:
>
> > i have try to follow
>
> > *-display-pipeline match pattern in forms/sitemap
> > here the forms-samples-styling.xsl is called
>
> > this .xsl include forms-advanced-field-styling.xsl
>
> > and the second one include forms-calendar-styling.xsl
>
> > in the last .xsl live the resources-uri parameter
> > but where and when is this parameter specified ? (or is something that i
> > missed?)
>
> this parameter is not specified anywhere, default value is being used:
> <xsl:param name="resources-uri">resources</xsl:param>
> the content of the element ("resources") is the default value of this parameter
>
>