You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Michael Wechner <mi...@wyona.com> on 2004/03/02 17:37:11 UTC
Cloning publications
Since many people want to clone a publication, create new doctypes and
customize
the layout and always ask the same questions, I thought it would make
sense if
we would offer the following setup within Lenya
pubs/default
and
pubs/my-default
where the publication to clone has a build.xml and corresponding XSLTs
in it,
e.g.
pubs/default/clone/build.xml
where the publication
pubs/my-default would contain certain patched files, e.g.
xslt/page2xhtml.xsl
and resources/shared/css/page.css
so people would have an example of a cloned publication.
Makes sense?
Michi
--
Michael Wechner
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://cocoon.apache.org/lenya/
michael.wechner@wyona.com michi@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
Re: Cloning publications
Posted by Michael Wechner <mi...@wyona.com>.
Gregor J. Rothfuss wrote:
> we need to solve the sitemap lookup issues before cloning makes sense.
> basically, if you load a sitemap from a different location all paths
> defined in that sitemap are relative to that sitemap (of course).
> there may be ways around it. otherwise you have to basically copy over
> most of the files to your clone which defeats the purpose.
the way I currently do it, is to copy all files from source into the
build directory:
src/webapp/lenya/pubs/default -->
build/lenya/webapp/lenya/pubs/my-default
and at the same time do a search and replace:
default --> my-default
which is being done by
ect
ant -f src/webapp/lenya/pubs/default/clone/build.xml
then you can do a regular ant, whereas the files from
src/webapp/lenya/pubs/my-default
will overwrite the other files.
I know it's not perfect, but it does the trick for the moment and I
believe is
better then just overwriting the default or whatever publication.
We only would have to add very few additional files to show people how this
can be accomplished.
It would certainly be better to have something like Mozilla is doing
with overlays
or whatsoever.
WDYT?
Michi
--
Michael Wechner
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://cocoon.apache.org/lenya/
michael.wechner@wyona.com michi@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
Re: Cloning publications
Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
we need to solve the sitemap lookup issues before cloning makes sense.
basically, if you load a sitemap from a different location all paths
defined in that sitemap are relative to that sitemap (of course). there
may be ways around it. otherwise you have to basically copy over most of
the files to your clone which defeats the purpose.
--
Gregor J. Rothfuss
Wyona Inc. - Open Source Content Management - Apache Lenya
http://wyona.com http://cocoon.apache.org/lenya
gregor.rothfuss@wyona.com gregor@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
Re: Cloning publications
Posted by Rolf Kulemann <ro...@apache.org>.
On Tue, 2004-03-02 at 17:37, Michael Wechner wrote:
> Since many people want to clone a publication, create new doctypes and
> customize
> the layout and always ask the same questions, I thought it would make
> sense if
> we would offer the following setup within Lenya
>
>
> pubs/default
>
> and
>
> pubs/my-default
>
> where the publication to clone has a build.xml and corresponding XSLTs
> in it,
> e.g.
>
> pubs/default/clone/build.xml
>
> where the publication
>
>
> pubs/my-default would contain certain patched files, e.g.
> xslt/page2xhtml.xsl
>
> and resources/shared/css/page.css
>
>
> so people would have an example of a cloned publication.
>
> Makes sense?
+1
Seems to be a simple and effective approach. It will be really useful
for users. Maybe we could provide html uis later to edit cloning params
for the users special needs and to trigger cloning?
--
Regards,
Rolf Kulemann
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org