Re: FOP website, release preparations: refactoring necessary
Patrick, I'm glad you took the time to finish the changes all the same. I'd simply put the SVN diff file in a Bugzilla issue and I'll deal with everything so that history is preserved. If there are any problems applying your patch, I can always get back to you. If you renamed any files while moving them, please indicate those as they are probably not easily recognizable in the patch. Thanks for doing that for us! That's one of the most important preconditions to get the first release out. PS: Some might have seen that I've changed my mail address for posting to mailing lists. The ISP for that old address has recently moved to M$ Exchange for mail infrastructure and since then I've had to deal with a lot of annoyances. On Friday, I finally migrated my 30+ list subscriptions. Phew. On 11.09.2005 05:22:30 Patrick Paul wrote: I apologize for not responding sooner, but I've been very busy lately. Anyways, I've finally found some time to get working on the website. I think I got everything right, now I just need to work on some broken links. Also, I am wondering if the svn diff will show everything (I moved some files around, for example the ones listed below are now in a directory called 0.20.5). I hope this is not a big issue. Cheers, Patrick Paul Jeremias Maerki wrote: Ok, so let's try to come up with a list. I see: The whole Using FOP section - compiling.xml - configuration.xml - running.xml - embedding.xml - servlets.xml - anttask.xml then most of Features: - output.xml - pdfencryption.xml - graphics.xml - fonts.xml - hyphenation.xml - extensions.xml The only item left out is this last section was compliance.xml which contains information for both versions. I'm not sure what to do with it. On 29.08.2005 00:10:31 Patrick Paul wrote: Now I have to determine what goes in the 2 newly created tabs. ;-) Jeremias Maerki Jeremias Maerki
Re: FOP website, release preparations: refactoring necessary
I apologize for not responding sooner, but I've been very busy lately. Anyways, I've finally found some time to get working on the website. I think I got everything right, now I just need to work on some broken links. Also, I am wondering if the svn diff will show everything (I moved some files around, for example the ones listed below are now in a directory called 0.20.5). I hope this is not a big issue. Cheers, Patrick Paul Jeremias Maerki wrote: Ok, so let's try to come up with a list. I see: The whole Using FOP section - compiling.xml - configuration.xml - running.xml - embedding.xml - servlets.xml - anttask.xml then most of Features: - output.xml - pdfencryption.xml - graphics.xml - fonts.xml - hyphenation.xml - extensions.xml The only item left out is this last section was compliance.xml which contains information for both versions. I'm not sure what to do with it. On 29.08.2005 00:10:31 Patrick Paul wrote: Now I have to determine what goes in the 2 newly created tabs. ;-) Jeremias Maerki
Re: FOP website, release preparations: refactoring necessary
Just an update to let you know I should have something ready to show you this week-end. Patrick Paul Jeremias Maerki wrote: Ok, so let's try to come up with a list. I see: The whole Using FOP section - compiling.xml - configuration.xml - running.xml - embedding.xml - servlets.xml - anttask.xml then most of Features: - output.xml - pdfencryption.xml - graphics.xml - fonts.xml - hyphenation.xml - extensions.xml The only item left out is this last section was compliance.xml which contains information for both versions. I'm not sure what to do with it. On 29.08.2005 00:10:31 Patrick Paul wrote: Now I have to determine what goes in the 2 newly created tabs. ;-) Jeremias Maerki
Re: FOP website, release preparations: refactoring necessary
Jeremias Maerki wrote: (It's probably best to collapse Development and Design into one tab. Too many tabs are not ideal. I second that. J.Pietschmann
Re: FOP website, release preparations: refactoring necessary
Have you seen this page? http://xmlgraphics.apache.org/fop/dev/doc.html This should give you everything you need to build the docs. But you will need to ignore the section about ForrestBot since that only works for committers. Just use local Forrest by calling forrest run after you've unpacked Forrest 0.7 and set up the environment variables. You can then simply point your browser to http://localhost: and check the changed website. I'd like the changes as SVN diffs (svn diff mypatch.diff) attached to a Bugzilla issue. http://xmlgraphics.apache.org/fop/dev/index.html#patches http://xmlgraphics.apache.org/fop/dev/tools.html#patches Thanks a lot for diving into this. On 27.08.2005 06:08:14 Patrick Paul wrote: I have figured out how the documentation files work and how to edit them. I still have to figure out how to get the site to build on my local machine and then I will be in business. What way you suggest I send the changes to you ? Thanks, Patrick Paul Jeremias Maerki wrote: Very cool! Thanks a lot! If you need any help, just yell. On 23.08.2005 14:37:38 Patrick Paul wrote: I would like to take care of that. I should have some free time in the next few weeks, so I will start doing a little bit everyday starting Wednesday. Patrick Jeremias Maerki wrote: While we're at it: In preparation for the first release we need to start thinking about a refactoring of our website. Since FOP 0.20.5 will probably stay the preferred productive version for some time and FOP Trunk is substantially different, I'd like to propose doing a version split like Forrest [1] have done. That would involve factoring out the version-dependent docs into a separate tab (or something like that), so we can have info for both versions side-by-side for the time being. I think stuff like embedding info would become too complicated and unreadable if we tried to put everything in the same place. If anyone would like to take the lead here, I'd be grateful. Otherwise, I will squeeze it in somewhere. [1] http://forrest.apache.org Jeremias Maerki Jeremias Maerki Jeremias Maerki
Re: FOP website, release preparations: refactoring necessary
Patrick, assuming you have forrest installed you build by simply typing forrest in the directory you checked the sources out from subversion, that is the directory where the forrest.properties file is in. The generated site is then in build/site. For delivering changes the following procedure is often followed: For changes to existing files. Use the subversion diff command and capture its output, e.g. svn diff mychanges.patch For new files jar or zip them up unless its only very few. Then create a BugZilla entry with the title starting with '[PATCH] ...' and attach the patch file and if applicable the jar/zip file or the few new files individually. Usually one of the committers will then take care of the rest. Manuel On Sat, 27 Aug 2005 12:08 pm, Patrick Paul wrote: I have figured out how the documentation files work and how to edit them. I still have to figure out how to get the site to build on my local machine and then I will be in business. What way you suggest I send the changes to you ? Thanks, Patrick Paul Jeremias Maerki wrote: Very cool! Thanks a lot! If you need any help, just yell. On 23.08.2005 14:37:38 Patrick Paul wrote: I would like to take care of that. I should have some free time in the next few weeks, so I will start doing a little bit everyday starting Wednesday. Patrick Jeremias Maerki wrote: While we're at it: In preparation for the first release we need to start thinking about a refactoring of our website. Since FOP 0.20.5 will probably stay the preferred productive version for some time and FOP Trunk is substantially different, I'd like to propose doing a version split like Forrest [1] have done. That would involve factoring out the version-dependent docs into a separate tab (or something like that), so we can have info for both versions side-by-side for the time being. I think stuff like embedding info would become too complicated and unreadable if we tried to put everything in the same place. If anyone would like to take the lead here, I'd be grateful. Otherwise, I will squeeze it in somewhere. [1] http://forrest.apache.org Jeremias Maerki Jeremias Maerki
Re: FOP website, release preparations: refactoring necessary
I was talking about their website (with the two tabs for the different versions) , not their product. Patrick Jeremias Maerki wrote: Uh, oh. Sorry, but I don't think we'll do that. We don't even have the infrastructure for a Lenya installation and I wouldn't want to rewrite our whole website just now. That would distract me too much at this stage of development. Even the Lenya project uses Forrest for their website. :-) On 27.08.2005 04:31:55 Patrick Paul wrote: Ok, so from what I understand you want to do, I think that what the Lenya project did looks good. http://lenya.apache.org/ What do you think ? Patrick Paul Jeremias Maerki wrote: While we're at it: In preparation for the first release we need to start thinking about a refactoring of our website. Since FOP 0.20.5 will probably stay the preferred productive version for some time and FOP Trunk is substantially different, I'd like to propose doing a version split like Forrest [1] have done. That would involve factoring out the version-dependent docs into a separate tab (or something like that), so we can have info for both versions side-by-side for the time being. I think stuff like embedding info would become too complicated and unreadable if we tried to put everything in the same place. If anyone would like to take the lead here, I'd be grateful. Otherwise, I will squeeze it in somewhere. [1] http://forrest.apache.org Jeremias Maerki Jeremias Maerki
Re: FOP website, release preparations: refactoring necessary
Sorry, I got the wrong impression. Since it's a CMS I thought you suggested we use that. But you're right. The tab structure like Lenya has it is exactly what we need. I think we'll end up with the following tabs: - Home - 0.20.5 - 1.0dev - Development (It's probably best to collapse Development and Design into one tab. Too many tabs are not ideal. If anyone has better ideas, please bring'em up. On 27.08.2005 15:57:02 Patrick Paul wrote: I was talking about their website (with the two tabs for the different versions) , not their product. Patrick Jeremias Maerki wrote: Uh, oh. Sorry, but I don't think we'll do that. We don't even have the infrastructure for a Lenya installation and I wouldn't want to rewrite our whole website just now. That would distract me too much at this stage of development. Even the Lenya project uses Forrest for their website. :-) On 27.08.2005 04:31:55 Patrick Paul wrote: Ok, so from what I understand you want to do, I think that what the Lenya project did looks good. http://lenya.apache.org/ What do you think ? Patrick Paul Jeremias Maerki wrote: While we're at it: In preparation for the first release we need to start thinking about a refactoring of our website. Since FOP 0.20.5 will probably stay the preferred productive version for some time and FOP Trunk is substantially different, I'd like to propose doing a version split like Forrest [1] have done. That would involve factoring out the version-dependent docs into a separate tab (or something like that), so we can have info for both versions side-by-side for the time being. I think stuff like embedding info would become too complicated and unreadable if we tried to put everything in the same place. If anyone would like to take the lead here, I'd be grateful. Otherwise, I will squeeze it in somewhere. [1] http://forrest.apache.org Jeremias Maerki Jeremias Maerki Jeremias Maerki
Re: FOP website, release preparations: refactoring necessary
Perfect, I will be working towards something like that. Patrick Paul Jeremias Maerki wrote: Sorry, I got the wrong impression. Since it's a CMS I thought you suggested we use that. But you're right. The tab structure like Lenya has it is exactly what we need. I think we'll end up with the following tabs: - Home - 0.20.5 - 1.0dev - Development (It's probably best to collapse Development and Design into one tab. Too many tabs are not ideal. If anyone has better ideas, please bring'em up. On 27.08.2005 15:57:02 Patrick Paul wrote: I was talking about their website (with the two tabs for the different versions) , not their product. Patrick Jeremias Maerki wrote: Uh, oh. Sorry, but I don't think we'll do that. We don't even have the infrastructure for a Lenya installation and I wouldn't want to rewrite our whole website just now. That would distract me too much at this stage of development. Even the Lenya project uses Forrest for their website. :-) On 27.08.2005 04:31:55 Patrick Paul wrote: Ok, so from what I understand you want to do, I think that what the Lenya project did looks good. http://lenya.apache.org/ What do you think ? Patrick Paul Jeremias Maerki wrote: While we're at it: In preparation for the first release we need to start thinking about a refactoring of our website. Since FOP 0.20.5 will probably stay the preferred productive version for some time and FOP Trunk is substantially different, I'd like to propose doing a version split like Forrest [1] have done. That would involve factoring out the version-dependent docs into a separate tab (or something like that), so we can have info for both versions side-by-side for the time being. I think stuff like embedding info would become too complicated and unreadable if we tried to put everything in the same place. If anyone would like to take the lead here, I'd be grateful. Otherwise, I will squeeze it in somewhere. [1] http://forrest.apache.org Jeremias Maerki Jeremias Maerki Jeremias Maerki
Re: FOP website, release preparations: refactoring necessary
Ok, so from what I understand you want to do, I think that what the Lenya project did looks good. http://lenya.apache.org/ What do you think ? Patrick Paul Jeremias Maerki wrote: While we're at it: In preparation for the first release we need to start thinking about a refactoring of our website. Since FOP 0.20.5 will probably stay the preferred productive version for some time and FOP Trunk is substantially different, I'd like to propose doing a version split like Forrest [1] have done. That would involve factoring out the version-dependent docs into a separate tab (or something like that), so we can have info for both versions side-by-side for the time being. I think stuff like embedding info would become too complicated and unreadable if we tried to put everything in the same place. If anyone would like to take the lead here, I'd be grateful. Otherwise, I will squeeze it in somewhere. [1] http://forrest.apache.org Jeremias Maerki
Re: FOP website, release preparations: refactoring necessary
I have figured out how the documentation files work and how to edit them. I still have to figure out how to get the site to build on my local machine and then I will be in business. What way you suggest I send the changes to you ? Thanks, Patrick Paul Jeremias Maerki wrote: Very cool! Thanks a lot! If you need any help, just yell. On 23.08.2005 14:37:38 Patrick Paul wrote: I would like to take care of that. I should have some free time in the next few weeks, so I will start doing a little bit everyday starting Wednesday. Patrick Jeremias Maerki wrote: While we're at it: In preparation for the first release we need to start thinking about a refactoring of our website. Since FOP 0.20.5 will probably stay the preferred productive version for some time and FOP Trunk is substantially different, I'd like to propose doing a version split like Forrest [1] have done. That would involve factoring out the version-dependent docs into a separate tab (or something like that), so we can have info for both versions side-by-side for the time being. I think stuff like embedding info would become too complicated and unreadable if we tried to put everything in the same place. If anyone would like to take the lead here, I'd be grateful. Otherwise, I will squeeze it in somewhere. [1] http://forrest.apache.org Jeremias Maerki Jeremias Maerki
FOP website, release preparations: refactoring necessary
While we're at it: In preparation for the first release we need to start thinking about a refactoring of our website. Since FOP 0.20.5 will probably stay the preferred productive version for some time and FOP Trunk is substantially different, I'd like to propose doing a version split like Forrest [1] have done. That would involve factoring out the version-dependent docs into a separate tab (or something like that), so we can have info for both versions side-by-side for the time being. I think stuff like embedding info would become too complicated and unreadable if we tried to put everything in the same place. If anyone would like to take the lead here, I'd be grateful. Otherwise, I will squeeze it in somewhere. [1] http://forrest.apache.org Jeremias Maerki
Re: FOP website, release preparations: refactoring necessary
I would like to take care of that. I should have some free time in the next few weeks, so I will start doing a little bit everyday starting Wednesday. Patrick Jeremias Maerki wrote: While we're at it: In preparation for the first release we need to start thinking about a refactoring of our website. Since FOP 0.20.5 will probably stay the preferred productive version for some time and FOP Trunk is substantially different, I'd like to propose doing a version split like Forrest [1] have done. That would involve factoring out the version-dependent docs into a separate tab (or something like that), so we can have info for both versions side-by-side for the time being. I think stuff like embedding info would become too complicated and unreadable if we tried to put everything in the same place. If anyone would like to take the lead here, I'd be grateful. Otherwise, I will squeeze it in somewhere. [1] http://forrest.apache.org Jeremias Maerki
Re: FOP website, release preparations: refactoring necessary
I would be willing to help in any way I can... One thing I've noticed, is that Forrest 0.7 appears to have created separate versions of their documentation. It may make sense to follow their example: http://forrest.apache.org/versions/index.html Web Maestro Clay On Aug 23, 2005, at 5:41 AM, Jeremias Maerki wrote: Very cool! Thanks a lot! If you need any help, just yell. On 23.08.2005 14:37:38 Patrick Paul wrote: I would like to take care of that. I should have some free time in the next few weeks, so I will start doing a little bit everyday starting Wednesday. Patrick Jeremias Maerki wrote: Regards, Web Maestro Clay -- [EMAIL PROTECTED] - http://homepage.mac.com/webmaestro/ My religion is simple. My religion is kindness. - HH The 14th Dalai Lama of Tibet
