You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by Vincent Hennebert <vi...@anyware-tech.com> on 2007/07/27 09:57:25 UTC
Help Refactoring the Website
Hi all,
The 0.94 version of FOP is basically ready to be released. The poll on
fop-user gave interesting results, although not applicable to the next
release. What about creating a wiki page summarizing those user wishes?
Users could then maintain it by themselves. Andreas, would you be
willing to take care of this?
As Chris pointed out a few days ago [1], it would be good to refactor
the website before the release and, in particular, remove the 0.20.5
tab. I'd like to call for help on this, as this is not a small task.
I'll try to do as much as possible on the WE, but that would be great if
we could share the work. Any volunteers?
Some tasks I can think of right now:
- update the introduction page (latest stable release, version of the
recommendation implemented...)
- add a small news section on the home page? this would make the site
look more live. It could simply list the latest versions released.
- correct/update/simplify other pages
So, in short: HEEELP! ;-)
Thanks,
Vincent
[1]
http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-dev/200707.mbox/%3cBAY117-DAV1722B3C005CF3B033EFDFFB040@phx.gbl%3e
Re: Help Refactoring the Website
Posted by The Web Maestro <th...@gmail.com>.
BTW, I added a table column for 0.94 to the Compliance page. I did
*not* remove the 0.20.5 or 0.93 columns. Those can be removed fairly
easily, if decided, but I figured we might want to keep those (but add
a note that fop-0.20.5 is unsupported).
Web Maestro Clay
--
Regards,
The Web Maestro
--
<th...@gmail.com> - <http://homepage.mac.com/webmaestro/>
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet
Re: Help Refactoring the Website
Posted by The Web Maestro <th...@gmail.com>.
On 8/2/07, Vincent Hennebert <vi...@anyware-tech.com> wrote:
> >> Strangely enough when I run Forrest on my local copy I get different
> >> (smaller) font sizes than on the website for all the other elements but
> >> the main text (without the above change). The screen.css style sheets
> >> are exactly the same though. I wonder what might be happening?
> >
> > Can you upload the `forrest` output to your web space, so we can take
> > a look? Here's the result of mine from last night (without the
> > #content changes):
> >
> > http://people.apache.org/~clay/fop-0.94/
>
> Here it is:
> http://people.apache.org/~vhennebert/fop-0.94/
The content appears to be *exactly* the same size, but the font-size
for the tabs appears to be smaller in our versions.
> <snip/>
> > I wonder if it has to do with your browser setup (what are you
> > using--browser/version, OS/version w service packs, build etc.)? Have
> > you tried on another machine? Maybe Forrest needs to have a support
> > ticket put in about the font resize buttons (and if you prefer the
> > font-size as well).
>
> Firefox 2.0.0.5
> Ubuntu Feisty
> Revision 556027 of Forrest 0.7 but no CSS file got modified when
> I updated my copy (only Java code).
>
> I think I'm becoming crazy. On your version the main text is smaller
> than on mine (without applying the CSS change), which now has normal
> size. For all other text objects (menu, etc.), sizes are the same.
If I were feeling 'feisty' I might say something pithy, like 'You
probably are going crazy...' but I'm not so I'll tell you that the
reason our sites didn't have the font-size adjust buttons was because
they weren't enabled in 'src/documentation/skinconf.xml'. I just
enabled it, as well as:
- compliance links (shows HTML & CSS compliance badges)
- external-link-image (indicates off-site links with mini-image icon)
- and XML file availability (enables re-purposing of content via XML)
> Trying with Konqueror the main text is larger on my version, but also
> the tab titles (Home, Version 0.93, etc.).
>
> I have no font-size button on any version, with any browser. Note that
> I have them on the XML Graphics site.
Mentioning that it was on the XML Graphics site gave me the clue it
was a preference setting.
> !?!??
> Thanks for looking into this,
> Vincent
Glad I could help... It's been a while since I've delved into Forrest.
In fact, they just released Forrest 0.8, so someone may want to look
into identifying if there's a compelling reason to 'upgrade'. ;-)
--
Regards,
The Web Maestro
--
<th...@gmail.com> - <http://homepage.mac.com/webmaestro/>
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet
Re: Help Refactoring the Website
Posted by Vincent Hennebert <vi...@anyware-tech.com>.
Hi Clay,
The Web Maestro a écrit :
> Hi Vincent,
>
> On 8/2/07, Vincent Hennebert wrote:
<snip/>
>> Thanks for the pointers. By adding the following in skinconf.xml:
>> #content { font-size: 100% }
>> I managed to get normal size for the main text. I didn't commit the
>> change because I wasn't sure this was the right place to do that.
>
> That's perfect. Go ahead and commit...
Ok, I’ll do.
>> Strangely enough when I run Forrest on my local copy I get different
>> (smaller) font sizes than on the website for all the other elements but
>> the main text (without the above change). The screen.css style sheets
>> are exactly the same though. I wonder what might be happening?
>
> Can you upload the `forrest` output to your web space, so we can take
> a look? Here's the result of mine from last night (without the
> #content changes):
>
> http://people.apache.org/~clay/fop-0.94/
Here it is:
http://people.apache.org/~vhennebert/fop-0.94/
<snip/>
> I wonder if it has to do with your browser setup (what are you
> using--browser/version, OS/version w service packs, build etc.)? Have
> you tried on another machine? Maybe Forrest needs to have a support
> ticket put in about the font resize buttons (and if you prefer the
> font-size as well).
Firefox 2.0.0.5
Ubuntu Feisty
Revision 556027 of Forrest 0.7 but no CSS file got modified when
I updated my copy (only Java code).
I think I’m becoming crazy. On your version the main text is smaller
than on mine (without applying the CSS change), which now has normal
size. For all other text objects (menu, etc.), sizes are the same.
Trying with Konqueror the main text is larger on my version, but also
the tab titles (Home, Version 0.93, etc.).
I have no font-size button on any version, with any browser. Note that
I have them on the XML Graphics site.
!?!??
Thanks for looking into this,
Vincent
Re: Help Refactoring the Website
Posted by The Web Maestro <th...@gmail.com>.
Hi Vincent,
On 8/2/07, Vincent Hennebert <vi...@anyware-tech.com> wrote:
> The Web Maestro a écrit :
> > On 7/31/07, Vincent Hennebert wrote:
> >> As I said I already did it, but if you wanna double-check all the
> >> better. Also, one thing that would be great if you could have a look at,
> >> is improving the stylesheet a bit. For example the main content is set
> >> to be displayed at 80% of its size. That should really not be the case
> >> as the setting for the main text's size should be left to the user's
> >> choice (I'm ok with reducing the size of e.g. the menu, however). I'm
> >> not really sure where to change that as the CSS stylesheets seem to
> >> directly come from the Forrest distribution.
> >
> > I haven't had a chance to work on the font-size yet, but here're a
> > couple of links to get started on it if I can't get to it in time:
> >
> > http://forrest.apache.org/docs_0_70/your-project.html#skins
> >
> > http://forrest.apache.org/docs_0_70/skin-package.html
> >
> > FWIW, I tried modifying the
> > 'branches/fop-0_94/src/documentation/skinconf.xml' file, but it didn't
> > work. I added the 'p, td, li' declaration to adjust it and make it
> > larger. I didn't commit my change.
>
> Thanks for the pointers. By adding the following in skinconf.xml:
> #content { font-size: 100% }
> I managed to get normal size for the main text. I didn't commit the
> change because I wasn't sure this was the right place to do that.
That's perfect. Go ahead and commit...
> Strangely enough when I run Forrest on my local copy I get different
> (smaller) font sizes than on the website for all the other elements but
> the main text (without the above change). The screen.css style sheets
> are exactly the same though. I wonder what might be happening?
Can you upload the `forrest` output to your web space, so we can take
a look? Here's the result of mine from last night (without the
#content changes):
http://people.apache.org/~clay/fop-0.94/
> > Here are a few locations for the Forrest skin files if you want to
> > modify them (although the CSS change may be overwritten if someone
> > else changes it (hence it'd be better to find a 'skinconf.xml'
> > solution):
> >
> > apache-forrest-0.7/main/webapp/skins/pelt/css/profile.css.xslt
> > fop/trunk/build/site/skin/profile.css
> > fop/trunk/build/site/skin/profile.css.xslt
> >
> > However, I think it's somewhat of a 'moot' point, as in the upper
> > right of the page, there are increase and decrease font-size widget
> > buttons, and the settings appear to follow you from page to page...
>
> Still, the user shouldn't have to do anything to retrieve their favorite
> text size. That's a basic accessibility rule IMHO.
> Moreover, I don't get any font-size widget button, again both on my
> local copy and the website!? FWIW I'm using the Trunk of the 0.7 branch.
I wonder if it has to do with your browser setup (what are you
using--browser/version, OS/version w service packs, build etc.)? Have
you tried on another machine? Maybe Forrest needs to have a support
ticket put in about the font resize buttons (and if you prefer the
font-size as well).
> <snip/>
>
> Vincent
--
Regards,
The Web Maestro
--
<th...@gmail.com> - <http://homepage.mac.com/webmaestro/>
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet
Re: Help Refactoring the Website
Posted by Vincent Hennebert <vi...@anyware-tech.com>.
Hi Clay,
The Web Maestro a écrit :
> On 7/31/07, Vincent Hennebert wrote:
>
> I've committed my changes, so the site should be re-factored. There is
> likely a bunch of content in the '0.94' realm that needs updating so
> it's more relevant to the current release. In addition, there may be
> some pages, which will need some attention (like
> 'branches/fop-0_94/build/site/0.94/releaseNotes_0.94.html',
> 'branches/fop-0_94/build/site/0.94/changes_0.94.html' and
> 'branches/fop-0_94/build/site/0.94/knownissues_overview.html').
That sounds great, thanks! I’ll have a closer look on the WE and
complete if necessary.
>> As I said I already did it, but if you wanna double-check all the
>> better. Also, one thing that would be great if you could have a look at,
>> is improving the stylesheet a bit. For example the main content is set
>> to be displayed at 80% of its size. That should really not be the case
>> as the setting for the main text's size should be left to the user's
>> choice (I'm ok with reducing the size of e.g. the menu, however). I'm
>> not really sure where to change that as the CSS stylesheets seem to
>> directly come from the Forrest distribution.
>
> I haven't had a chance to work on the font-size yet, but here're a
> couple of links to get started on it if I can't get to it in time:
>
> http://forrest.apache.org/docs_0_70/your-project.html#skins
>
> http://forrest.apache.org/docs_0_70/skin-package.html
>
> FWIW, I tried modifying the
> 'branches/fop-0_94/src/documentation/skinconf.xml' file, but it didn't
> work. I added the 'p, td, li' declaration to adjust it and make it
> larger. I didn't commit my change.
Thanks for the pointers. By adding the following in skinconf.xml:
#content { font-size: 100% }
I managed to get normal size for the main text. I didn’t commit the
change because I wasn’t sure this was the right place to do that.
Strangely enough when I run Forrest on my local copy I get different
(smaller) font sizes than on the website for all the other elements but
the main text (without the above change). The screen.css style sheets
are exactly the same though. I wonder what might be happening?
> Here are a few locations for the Forrest skin files if you want to
> modify them (although the CSS change may be overwritten if someone
> else changes it (hence it'd be better to find a 'skinconf.xml'
> solution):
>
> apache-forrest-0.7/main/webapp/skins/pelt/css/profile.css.xslt
> fop/trunk/build/site/skin/profile.css
> fop/trunk/build/site/skin/profile.css.xslt
>
> However, I think it's somewhat of a 'moot' point, as in the upper
> right of the page, there are increase and decrease font-size widget
> buttons, and the settings appear to follow you from page to page...
Still, the user shouldn’t have to do anything to retrieve their favorite
text size. That’s a basic accessibility rule IMHO.
Moreover, I don’t get any font-size widget button, again both on my
local copy and the website!? FWIW I’m using the Trunk of the 0.7 branch.
<snip/>
Vincent
Re: Help Refactoring the Website
Posted by The Web Maestro <th...@gmail.com>.
On 7/31/07, Vincent Hennebert <vi...@anyware-tech.com> wrote:
> Hi Clay,
>
> Thanks for chiming in!
I've committed my changes, so the site should be re-factored. There is
likely a bunch of content in the '0.94' realm that needs updating so
it's more relevant to the current release. In addition, there may be
some pages, which will need some attention (like
'branches/fop-0_94/build/site/0.94/releaseNotes_0.94.html',
'branches/fop-0_94/build/site/0.94/changes_0.94.html' and
'branches/fop-0_94/build/site/0.94/knownissues_overview.html').
> > It didn't take too much to re-factor the site... Just had to adjust
> > the tabs.xml and site.xml documents (and remove the 0.20.5 documents).
> > I'll need to do a `svn delete` for the 0.20.5/ and 0.93/ directories,
> > so let me know if I should do that NOW, or we need to wait until we're
> > more ready for the release.
>
> As I said I already did it, but if you wanna double-check all the
> better. Also, one thing that would be great if you could have a look at,
> is improving the stylesheet a bit. For example the main content is set
> to be displayed at 80% of its size. That should really not be the case
> as the setting for the main text's size should be left to the user's
> choice (I'm ok with reducing the size of e.g. the menu, however). I'm
> not really sure where to change that as the CSS stylesheets seem to
> directly come from the Forrest distribution.
I haven't had a chance to work on the font-size yet, but here're a
couple of links to get started on it if I can't get to it in time:
http://forrest.apache.org/docs_0_70/your-project.html#skins
http://forrest.apache.org/docs_0_70/skin-package.html
FWIW, I tried modifying the
'branches/fop-0_94/src/documentation/skinconf.xml' file, but it didn't
work. I added the 'p, td, li' declaration to adjust it and make it
larger. I didn't commit my change.
Here are a few locations for the Forrest skin files if you want to
modify them (although the CSS change may be overwritten if someone
else changes it (hence it'd be better to find a 'skinconf.xml'
solution):
apache-forrest-0.7/main/webapp/skins/pelt/css/profile.css.xslt
fop/trunk/build/site/skin/profile.css
fop/trunk/build/site/skin/profile.css.xslt
However, I think it's somewhat of a 'moot' point, as in the upper
right of the page, there are increase and decrease font-size widget
buttons, and the settings appear to follow you from page to page...
Here's the snippet,
<!--
extra-css - here you can define custom css-elements that are
a. overriding the fallback elements or
b. adding the css definition from new elements that you may have
used in your documentation.
-->
<extra-css>
<!--Example of b.
To define the css definition of a new element that you may have used
in the class attribute of a <p> node.
e.g. <p class="quote"/>
-->
p, td, li {
font-size: 94%;
}
p.quote {
margin-left: 2em;
padding: .5em;
background-color: #f0f0f0;
font-family: monospace;
}
.yes { background-color: #99FF99; }
.no { background-color: #FF9999; }
.partial { background-color: #FFFFCC; }
.ForrestTable td.basic { text-align: center; }
.ForrestTable td.extended { text-align: center; }
.ForrestTable td.complete { text-align: center; }
.ForrestTable td.na { text-align: center; }
.ForrestTable td.yes { background-color: #99FF99;
text-align: center; }
.ForrestTable td.no { background-color: #FF9999;
text-align: center; }
.ForrestTable td.partial { background-color: #FFFFCC;
text-align: center; }
.ForrestTable td.category { /*background-color: #CFDCED;*/
font-size: 1.2em }
</extra-css>
Web Maestro Clay
--
Regards,
The Web Maestro
--
<th...@gmail.com> - <http://homepage.mac.com/webmaestro/>
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet
Re: Help Refactoring the Website
Posted by Vincent Hennebert <vi...@anyware-tech.com>.
Hi Clay,
Thanks for chiming in!
It seems we are somewhat duplicating our efforts here. I already removed
the 0.20.5 tab and added a new one for 0.94. Look at the 0.94 branch of
the svn repository. I prefer to work in the branch so that the trunk
stil reflects the current site, and we can re-generate it if ever
needed.
(More below.)
The Web Maestro a écrit :
> On 7/30/07, The Web Maestro <th...@gmail.com> wrote:
>> Thanks Chris! I'll look into what I can to help re-factor the site to
>> remove the 0.20.5 references. I agree, that with 0.93 & 0.94, the 0.20
>> branch information is no longer necessary.
>
> I was able to factor out the 0.20.5 stuff but there are a couple of
> relatively minor issues:
>
> 1. I am planning to remove 0.93, but want to confirm this should be
> removed so we have only 0.94 and trunk ( as well as Trunk, etc.)
No, I think the 0.93 section should remain, for those who don’t want to
immediately upgrade. There will be slight config changes between the two
versions so it’s best that each one have its dedicated tab.
> 2. To create the '0.94' section, I copied the 'Trunk' area, but there
So did I, which is an indication to me that that was the way to do ;-)
> are numerous areas in the documentation which are likely outdated.
> Should I commit my changes and let others adjust the documentation to
> reflect the recent changes to the code?
Yes, I thought of that afterwards. It may make sense to update the
content /before/ creating the 0.94 tab, in order to avoid duplicating
changes or managing svn merges. I’ve already updated most of the Home
tab and I’ll try to work on the Trunk one ASAP.
> 3. There are a few places where a 'date' will be required to identify
> when 0.94 is released, but I'm not sure what that date is yet.
The best IMO is to put an “XX August 20007” everywhere and replace the
“XX” with the actual date once it is known. That is, once the vote is
done, when I upload the artifacts, I’ll do the change and update the
website in the same time.
> It didn't take too much to re-factor the site... Just had to adjust
> the tabs.xml and site.xml documents (and remove the 0.20.5 documents).
> I'll need to do a `svn delete` for the 0.20.5/ and 0.93/ directories,
> so let me know if I should do that NOW, or we need to wait until we're
> more ready for the release.
As I said I already did it, but if you wanna double-check all the
better. Also, one thing that would be great if you could have a look at,
is improving the stylesheet a bit. For example the main content is set
to be displayed at 80% of its size. That should really not be the case
as the setting for the main text’s size should be left to the user’s
choice (I’m ok with reducing the size of e.g. the menu, however). I’m
not really sure where to change that as the CSS stylesheets seem to
directly come from the Forrest distribution.
Thanks,
Vincent
Re: Help Refactoring the Website
Posted by The Web Maestro <th...@gmail.com>.
On 7/30/07, The Web Maestro <th...@gmail.com> wrote:
> Thanks Chris! I'll look into what I can to help re-factor the site to
> remove the 0.20.5 references. I agree, that with 0.93 & 0.94, the 0.20
> branch information is no longer necessary.
I was able to factor out the 0.20.5 stuff but there are a couple of
relatively minor issues:
1. I am planning to remove 0.93, but want to confirm this should be
removed so we have only 0.94 and trunk ( as well as Trunk, etc.)
2. To create the '0.94' section, I copied the 'Trunk' area, but there
are numerous areas in the documentation which are likely outdated.
Should I commit my changes and let others adjust the documentation to
reflect the recent changes to the code?
3. There are a few places where a 'date' will be required to identify
when 0.94 is released, but I'm not sure what that date is yet.
It didn't take too much to re-factor the site... Just had to adjust
the tabs.xml and site.xml documents (and remove the 0.20.5 documents).
I'll need to do a `svn delete` for the 0.20.5/ and 0.93/ directories,
so let me know if I should do that NOW, or we need to wait until we're
more ready for the release.
Web Maestro Clay
--
Regards,
The Web Maestro
--
<th...@gmail.com> - <http://homepage.mac.com/webmaestro/>
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet
Re: Help Refactoring the Website
Posted by The Web Maestro <th...@gmail.com>.
On 7/30/07, Chris Bowditch <bo...@hotmail.com> wrote:
> Hi Clay,
>
> 0.93 and 0.94 are still compatible with Java 1.3 so AIX 4.1 users will
> still be able to use it. We have clients running AIX who use Java 1.4,
> so I didn't realise AIX couldn't run 1.4. Maybe its down to exact o/s
> version. In either case, we decided to drop support for 1.3 after 0.94.
> So if 1.3 is still needed in the future users can download 0.94. And I
> think the website should reflect this.
>
> The reason why 0.20.5 should be removed from the website is that
> fop-users is still receiving several posts per week relating to it.
> There is now very little knowledge of it within our development team, so
> supporting it is not something we would like to continue. Therefore,
> users should be actively discouraged from downloading it. Looking at the
> website today, I get the impression that 0.20.5 and 0.94 are two
> separate development streams which both receive active maintenance.
> However, we all know that is not the case. 0.9x is a direct replacement
> for the 0.20.x series.
>
> It made sense to keep 0.20.5 on the website for a couple of years after
> the initial 0.9x release to give folk a chance to upgrade. But 0.9x has
> been around for a couple of years and now I believe it is time to start
> encouraging users to switch over.
>
> Chris
Thanks Chris! I'll look into what I can to help re-factor the site to
remove the 0.20.5 references. I agree, that with 0.93 & 0.94, the 0.20
branch information is no longer necessary.
Web Maestro Clay
--
Regards,
The Web Maestro
--
<th...@gmail.com> - <http://homepage.mac.com/webmaestro/>
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet
Re: Help Refactoring the Website
Posted by Chris Bowditch <bo...@hotmail.com>.
The Web Maestro wrote:
> On 7/29/07, Andreas L Delmelle <a_...@pandora.be> wrote:
>
>>On Jul 27, 2007, at 18:36, Andreas L Delmelle wrote:
>>
>>>>it would be good to refactor
>>>>the website before the release and, in particular, remove the 0.20.5
>>>>tab.
>>
>>This could maybe still be done before the release, but I started
>>wondering...
>>
>>
>>>>I'd like to call for help on this, as this is not a small task.
>>>>I'll try to do as much as possible on the WE, but that would be
>>>>great if
>>>>we could share the work. Any volunteers?
>>>>Some tasks I can think of right now:
>>>>- update the introduction page (latest stable release, version of the
>>>> recommendation implemented...)
>>>>- add a small news section on the home page? this would make the site
>>>> look more live. It could simply list the latest versions released.
>>>>- correct/update/simplify other pages
>>
>>Wouldn't it be better, FTM, to focus on making the site 0.94-ready,
>>and do any serious restyling afterwards? It's just that a release by
>>itself already takes some work and preparation... Just a thought.
>
>
> I'll spend some time looking into what it'll take to refactor,
> although I agree with Andreas that it would be better to focus on
> getting 0.94 ready and do any necessary 'purging' of fop-0.20.5 after
> that, if that's what's deemed best.
>
> I'm not actually convinced eradicating it from the FOP site is the
> best route, as there will be some who can't upgrade (namely users of
> AIX 4.1 and/or others who can't upgrade to a Java Run-time Environment
> newer than 1.3)... I would think the fop-0.20.5 information should
> remain accessible somewhere other than on <http://archive.org/>. The
> good part is, that the content will likely never change and would
> exist on a separate TAB, out of the way. That's not to say I'm firmly
> in the trench of keeping the content, but I don't see how it'd hurt to
> retain it.
>
Hi Clay,
0.93 and 0.94 are still compatible with Java 1.3 so AIX 4.1 users will
still be able to use it. We have clients running AIX who use Java 1.4,
so I didn't realise AIX couldn't run 1.4. Maybe its down to exact o/s
version. In either case, we decided to drop support for 1.3 after 0.94.
So if 1.3 is still needed in the future users can download 0.94. And I
think the website should reflect this.
The reason why 0.20.5 should be removed from the website is that
fop-users is still receiving several posts per week relating to it.
There is now very little knowledge of it within our development team, so
supporting it is not something we would like to continue. Therefore,
users should be actively discouraged from downloading it. Looking at the
website today, I get the impression that 0.20.5 and 0.94 are two
separate development streams which both receive active maintenance.
However, we all know that is not the case. 0.9x is a direct replacement
for the 0.20.x series.
It made sense to keep 0.20.5 on the website for a couple of years after
the initial 0.9x release to give folk a chance to upgrade. But 0.9x has
been around for a couple of years and now I believe it is time to start
encouraging users to switch over.
Chris
Re: Help Refactoring the Website
Posted by The Web Maestro <th...@gmail.com>.
On 7/29/07, Andreas L Delmelle <a_...@pandora.be> wrote:
> On Jul 27, 2007, at 18:36, Andreas L Delmelle wrote:
> >> it would be good to refactor
> >> the website before the release and, in particular, remove the 0.20.5
> >> tab.
>
> This could maybe still be done before the release, but I started
> wondering...
>
> >> I'd like to call for help on this, as this is not a small task.
> >> I'll try to do as much as possible on the WE, but that would be
> >> great if
> >> we could share the work. Any volunteers?
> >> Some tasks I can think of right now:
> >> - update the introduction page (latest stable release, version of the
> >> recommendation implemented...)
> >> - add a small news section on the home page? this would make the site
> >> look more live. It could simply list the latest versions released.
> >> - correct/update/simplify other pages
>
> Wouldn't it be better, FTM, to focus on making the site 0.94-ready,
> and do any serious restyling afterwards? It's just that a release by
> itself already takes some work and preparation... Just a thought.
I'll spend some time looking into what it'll take to refactor,
although I agree with Andreas that it would be better to focus on
getting 0.94 ready and do any necessary 'purging' of fop-0.20.5 after
that, if that's what's deemed best.
I'm not actually convinced eradicating it from the FOP site is the
best route, as there will be some who can't upgrade (namely users of
AIX 4.1 and/or others who can't upgrade to a Java Run-time Environment
newer than 1.3)... I would think the fop-0.20.5 information should
remain accessible somewhere other than on <http://archive.org/>. The
good part is, that the content will likely never change and would
exist on a separate TAB, out of the way. That's not to say I'm firmly
in the trench of keeping the content, but I don't see how it'd hurt to
retain it.
--
Regards,
The Web Maestro
--
<th...@gmail.com> - <http://homepage.mac.com/webmaestro/>
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet
Re: Help Refactoring the Website
Posted by Andreas L Delmelle <a_...@pandora.be>.
On Jul 27, 2007, at 18:36, Andreas L Delmelle wrote:
> On Jul 27, 2007, at 09:57, Vincent Hennebert wrote:
>
>> The 0.94 version of FOP is basically ready to be released. The
>> poll on
>> fop-user gave interesting results, although not applicable to the
>> next
>> release. What about creating a wiki page summarizing those user
>> wishes?
>> Users could then maintain it by themselves. Andreas, would you be
>> willing to take care of this?
>
> Sure.
Just did this. Probably due to the holidays, I presume, but there
were ultimately only very few explicit requests.
BTW:
>> As Chris pointed out a few days ago [1],
I'd hereby also like to apologize to Chris for not responding. Not
really my fault though, just re-checked my mails, and the referenced
post seems not to have made it into my mailbox... and I'm not in the
habit of checking for posts on the archives (until they're old history)
Anyway, the idea definitely looks OK to me. I'm all for.
>> it would be good to refactor
>> the website before the release and, in particular, remove the 0.20.5
>> tab.
This could maybe still be done before the release, but I started
wondering...
>> I'd like to call for help on this, as this is not a small task.
>> I'll try to do as much as possible on the WE, but that would be
>> great if
>> we could share the work. Any volunteers?
>> Some tasks I can think of right now:
>> - update the introduction page (latest stable release, version of the
>> recommendation implemented...)
>> - add a small news section on the home page? this would make the site
>> look more live. It could simply list the latest versions released.
>> - correct/update/simplify other pages
Wouldn't it be better, FTM, to focus on making the site 0.94-ready,
and do any serious restyling afterwards? It's just that a release by
itself already takes some work and preparation... Just a thought.
Cheers
Andreas
Re: Help Refactoring the Website
Posted by Andreas L Delmelle <a_...@pandora.be>.
On Jul 27, 2007, at 09:57, Vincent Hennebert wrote:
> The 0.94 version of FOP is basically ready to be released. The poll on
> fop-user gave interesting results, although not applicable to the next
> release. What about creating a wiki page summarizing those user
> wishes?
> Users could then maintain it by themselves. Andreas, would you be
> willing to take care of this?
Sure. I have one more important change I'd like to see in the
release, and which is just about finished. (concerns the
PropertyCache, more about that in a separate post later this evening)
> As Chris pointed out a few days ago [1], it would be good to refactor
> the website before the release and, in particular, remove the 0.20.5
> tab. I'd like to call for help on this, as this is not a small task.
> I'll try to do as much as possible on the WE, but that would be
> great if
> we could share the work. Any volunteers?
> Some tasks I can think of right now:
> - update the introduction page (latest stable release, version of the
> recommendation implemented...)
> - add a small news section on the home page? this would make the site
> look more live. It could simply list the latest versions released.
> - correct/update/simplify other pages
>
> So, in short: HEEELP! ;-)
Concerning the documentation, I'm actually limited in my
possibilities. I know just about enough to update the compliance page
every once in a while, but thorough restructuring is not something
I'd immediately take on. I'm afraid I'm of no immediate use there.
Sure hope our Web Maestro Clay chimes in to offer you useful hands.
Cheers
Andreas