Re: DO NOT REPLY [Bug 34283] - Tutorial: Write a Custom Generator

[Geoff Howard <ge...@gmail.com>]

Upayavira,

As I've only been able to marginally follow the new 2.2 docs strategy
(especially because there have been several I think over time!) :)  I
wasn't sure what to do with this doc in 2.2.  I also am not clear how
much of it will be accurate in 2.2.

I'll try to take a look at some point and come up with a logical place
for it.  I have the link to the new docs on brutus, but poking around,
things seem pretty rough still.  Where is the current authoritative
menu structure?

Geoff

On 5/2/05, bugzilla@apache.org <bu...@apache.org> wrote:
> DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
> RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
> <http://issues.apache.org/bugzilla/show_bug.cgi?id=34283>.
> ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
> INSERTED IN THE BUG DATABASE.
> 
> http://issues.apache.org/bugzilla/show_bug.cgi?id=34283
> 
> ------- Additional Comments From uv@upaya.co.uk  2005-05-02 08:11 -------
> Geoff -
> 
> Please consider committing it to 2.2 too. The doc structure there is very
> different, and at an early stage. Either commit it as a c21-custom-generator
> page (as this is an as-yet-unconverted page), or if you wish, find the place in
> the menu structure for your page.
> 
> Thanks, Upayavira
> 
> --
> Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are the assignee for the bug, or are watching the assignee.
>

Re: DO NOT REPLY [Bug 34283] - Tutorial: Write a Custom Generator

[Upayavira <uv...@upaya.co.uk>]

Geoff Howard wrote:
> Upayavira,
> 
> As I've only been able to marginally follow the new 2.2 docs strategy
> (especially because there have been several I think over time!) :)  I
> wasn't sure what to do with this doc in 2.2.  I also am not clear how
> much of it will be accurate in 2.2.
> 
> I'll try to take a look at some point and come up with a logical place
> for it.  I have the link to the new docs on brutus, but poking around,
> things seem pretty rough still.  Where is the current authoritative
> menu structure?

Well, the simplest thing to do is to create a folder in 
trunk/src/documentation/src/content/xdocs, say, called 
c21-custom-installer. Copy the meta-meta.xml and comments_en.xml from 
any other folder (change the legacy filename in meta), and add your own 
content_en.html file for the content of your page.

Basically, if you create a page prefixed with c21, that says that the 
page has not yet been converted from Cocoon 2.1, and needs to be 
verified and confirmed in terms of functionality with Cocoon 2.2. Which 
means it is _perfectly_ safe to copy your page (as HTML, preferably, 
although content_en.xml should still work) into the 2.2 repos without 
worrying whether it will work or not on 2.2. Worrying about that will be 
someone else's job!

Thanks,

Regards, Upayavira

Re: DO NOT REPLY [Bug 34283] - Tutorial: Write a Custom Generator

[Upayavira <uv...@odoko.co.uk>]

Geoff Howard wrote:
> Upayavira,
> 
> As I've only been able to marginally follow the new 2.2 docs strategy
> (especially because there have been several I think over time!) :)  I
> wasn't sure what to do with this doc in 2.2.  I also am not clear how
> much of it will be accurate in 2.2.
> 
> I'll try to take a look at some point and come up with a logical place
> for it.  I have the link to the new docs on brutus, but poking around,
> things seem pretty rough still.  Where is the current authoritative
> menu structure?

Well, the simplest thing to do is to create a folder in 
trunk/src/documentation/src/content/xdocs, say, called 
c21-custom-installer. Copy the meta-meta.xml and comments_en.xml from 
any other folder (change the legacy filename in meta), and add your own 
content_en.html file for the content of your page.

Basically, if you create a page prefixed with c21, that says that the 
page has not yet been converted from Cocoon 2.1, and needs to be 
verified and confirmed in terms of functionality with Cocoon 2.2. Which 
means it is _perfectly_ safe to copy your page (as HTML, preferably, 
although content_en.xml should still work) into the 2.2 repos without 
worrying whether it will work or not on 2.2. Worrying about that will be 
someone else's job!

Thanks,

Regards, Upayavira