You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Reinhard Poetz <re...@apache.org> on 2007/05/10 09:33:21 UTC

Upgrading Daisy

[moving over a discussion from daisy@cocoondev to dev@cocoon]

Bruno Dumon wrote:
> Which also makes me think of it: the Cocoon zone is still running Daisy
> 1.5. I could do the upgrade, but I'm not sure on the impact this might
> have. The maven plugin should be easy to upgrade, but I think the
> forrest plugin is also still in use? It could be that it works without
> changes but I'm not sure.

I was thinking about an upgrade too but I'd prefer to wait until we have 
published the new documentation because I want to concentrate on that first.

WDYT?

-- 
Reinhard Pötz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------

Re: Upgrading Daisy

Posted by Reinhard Poetz <re...@apache.org>.
Marc Portier wrote:
> one less argument not to update

I haven't had enough time to have a deeper look on what has to be done to 
upgrade the Daisy plugin and the Daisy Java adapter 
(http://svn.cocoondev.org/repos/daisy/contrib/daisy-client-apps/trunk/daisy-java-adapter/). 
I'm sorry.

My priorities now are getting the RC1 release done and publish our new website. 
Then the upgrade of the two modules will follow. If anyone else wants the 
upgrade being done faster than this, I will help as much as I can but I'm 
against an upgrade without having both modules because we wouldn't be able to 
publish our docs anymore.

-- 
Reinhard Pötz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------

Re: Upgrading Daisy

Posted by Reinhard Poetz <re...@apache.org>.
Marc Portier wrote:
> we need to decide on a namespace though, 'cdoc' for 'cocoon docs' is my 
> naive first proposal.

fine for me.

-- 
Reinhard Pötz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------

Re: Upgrading Daisy

Posted by Marc Portier <mp...@outerthought.org>.

Reinhard Poetz wrote:
> hepabolu wrote:
>>> I don't see a reason why we need the namespace in our published URLs 
>>> at all. The Daisy plugin could cut them off.
>>
>> Sure, and I'm all for cutting it off, but in Daisy the namespace is 
>> there so backlink from the published page should go to the namespaced 
>> version.
>>
>> Now:
>>
>> Daisy: .../1.html
>> Published: ../1.html (<div id="EditUrl"><a href="zones.../1.html">.....)
>>
>> After upgrading Daisy 2.0:
>>
>> Daisy: .../1-NS.html
>> Published: ../1.html (<div id="EditUrl"><a href="zones.../1.html">.....)
>> ----This is where it goes wrong ------------>             ^^^^^^
> 

no it doesn't

document-id's without namespace-suffixes are assumed to be in the 
default namespace of the site


see e.g. this link;

http://cocoondev.org/daisydocs-2_0/301-cd/343-cd.html

still works in the old style referencing:

http://cocoondev.org/daisydocs-2_0/301/343
http://cocoondev.org/daisydocs-2_0/343

or even as:

http://cocoondev.org/daisy/343



this was precisely to allow people to upgrade without need to worry 
about elder links (e.g in bookmarks and emails) no longer working

> adding the namespace there shouldn't be that difficult ;-)
> 
> I will introduce a Daisy plugin parameter "namespace" which will be cut 
> off from document ids and added to edit urls.
> 


one less argument not to update


we need to decide on a namespace though, 'cdoc' for 'cocoon docs' is my 
naive first proposal.


regards,
-marc=

Re: Upgrading Daisy

Posted by Reinhard Poetz <re...@apache.org>.
hepabolu wrote:
>> I don't see a reason why we need the namespace in our published URLs 
>> at all. The Daisy plugin could cut them off.
> 
> Sure, and I'm all for cutting it off, but in Daisy the namespace is 
> there so backlink from the published page should go to the namespaced 
> version.
> 
> Now:
> 
> Daisy: .../1.html
> Published: ../1.html (<div id="EditUrl"><a href="zones.../1.html">.....)
> 
> After upgrading Daisy 2.0:
> 
> Daisy: .../1-NS.html
> Published: ../1.html (<div id="EditUrl"><a href="zones.../1.html">.....)
> ----This is where it goes wrong ------------>             ^^^^^^

adding the namespace there shouldn't be that difficult ;-)

I will introduce a Daisy plugin parameter "namespace" which will be cut off from 
document ids and added to edit urls.

-- 
Reinhard Pötz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------

Re: Upgrading Daisy

Posted by hepabolu <he...@gmail.com>.
Reinhard Poetz said the following on 10/5/07 14:51:
>> Daisy 2.0.X changes the name of the document in the url (1.html -> 
>> 1-NS.html with NS = a namespacecode), which means you have to redo the 
>> publishing all over again because the link to the Daisy page breaks 
>> after the upgrade.
> 
> I don't see a reason why we need the namespace in our published URLs at 
> all. The Daisy plugin could cut them off.

Sure, and I'm all for cutting it off, but in Daisy the namespace is 
there so backlink from the published page should go to the namespaced 
version.

Now:

Daisy: .../1.html
Published: ../1.html (<div id="EditUrl"><a href="zones.../1.html">.....)

After upgrading Daisy 2.0:

Daisy: .../1-NS.html
Published: ../1.html (<div id="EditUrl"><a href="zones.../1.html">.....)
----This is where it goes wrong ------------>             ^^^^^^


> Basically I'm not against the upgrade but I would like to invest my time 
> rather in cleaning up and adding docs instead of upgrading the Daisy 

So true, but you need to realise that the above situation will occur 
when Daisy is upgraded and the publication has not been redone.

> plugin. In theory the upgrade shouldn't cause any problems but I learned 
> by experience that upgrades aren't that smooth as expected most of the 
> time.

:-)

> Anyway, maybe I find some time over the weekend but I can't promise it ...


ok.

Bye, Helma

Re: Upgrading Daisy

Posted by Reinhard Poetz <re...@apache.org>.
hepabolu wrote:
> Reinhard Poetz said the following on 10/5/07 09:33:
>> [moving over a discussion from daisy@cocoondev to dev@cocoon]
>>
>> Bruno Dumon wrote:
>>> Which also makes me think of it: the Cocoon zone is still running Daisy
>>> 1.5. I could do the upgrade, but I'm not sure on the impact this might
>>> have. The maven plugin should be easy to upgrade, but I think the
>>> forrest plugin is also still in use? It could be that it works without
>>> changes but I'm not sure.
>>
>> I was thinking about an upgrade too but I'd prefer to wait until we 
>> have published the new documentation because I want to concentrate on 
>> that first.
>>
>> WDYT?
> 
> IMO: Best to do the upgrade now. I've done it here with a small site and 
> it was done in 3 hours (including figuring out the best way to upgrade a 
> Suse machine to java 1.5).
> 
> Daisy 2.0.X changes the name of the document in the url (1.html -> 
> 1-NS.html with NS = a namespacecode), which means you have to redo the 
> publishing all over again because the link to the Daisy page breaks 
> after the upgrade.

I don't see a reason why we need the namespace in our published URLs at all. The 
Daisy plugin could cut them off.

Basically I'm not against the upgrade but I would like to invest my time rather 
in cleaning up and adding docs instead of upgrading the Daisy plugin. In theory 
the upgrade shouldn't cause any problems but I learned by experience that 
upgrades aren't that smooth as expected most of the time.

Anyway, maybe I find some time over the weekend but I can't promise it ...

-- 
Reinhard Pötz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------

Re: Upgrading Daisy

Posted by Grzegorz Kossakowski <gk...@apache.org>.
hepabolu napisał(a):
> Reinhard Poetz said the following on 10/5/07 09:33:
>> [moving over a discussion from daisy@cocoondev to dev@cocoon]
>>
>> Bruno Dumon wrote:
>>> Which also makes me think of it: the Cocoon zone is still running Daisy
>>> 1.5. I could do the upgrade, but I'm not sure on the impact this might
>>> have. The maven plugin should be easy to upgrade, but I think the
>>> forrest plugin is also still in use? It could be that it works without
>>> changes but I'm not sure.
>>
>> I was thinking about an upgrade too but I'd prefer to wait until we 
>> have published the new documentation because I want to concentrate on 
>> that first.
>>
>> WDYT?
> 
> IMO: Best to do the upgrade now. I've done it here with a small site and 
> it was done in 3 hours (including figuring out the best way to upgrade a 
> Suse machine to java 1.5).
> 
> Daisy 2.0.X changes the name of the document in the url (1.html -> 
> 1-NS.html with NS = a namespacecode), which means you have to redo the 
> publishing all over again because the link to the Daisy page breaks 
> after the upgrade.

I agree with Helma.


-- 
Grzegorz Kossakowski

Re: Upgrading Daisy

Posted by hepabolu <he...@gmail.com>.
Reinhard Poetz said the following on 10/5/07 09:33:
> [moving over a discussion from daisy@cocoondev to dev@cocoon]
> 
> Bruno Dumon wrote:
>> Which also makes me think of it: the Cocoon zone is still running Daisy
>> 1.5. I could do the upgrade, but I'm not sure on the impact this might
>> have. The maven plugin should be easy to upgrade, but I think the
>> forrest plugin is also still in use? It could be that it works without
>> changes but I'm not sure.
> 
> I was thinking about an upgrade too but I'd prefer to wait until we have 
> published the new documentation because I want to concentrate on that 
> first.
> 
> WDYT?

IMO: Best to do the upgrade now. I've done it here with a small site and 
it was done in 3 hours (including figuring out the best way to upgrade a 
Suse machine to java 1.5).

Daisy 2.0.X changes the name of the document in the url (1.html -> 
1-NS.html with NS = a namespacecode), which means you have to redo the 
publishing all over again because the link to the Daisy page breaks 
after the upgrade.

Bye, Helma