POI Website
As the project as matured the POI web site has grown organically to accommodate that growth. Unfortunately I think we're now at the stage were things are a bit messy and it's not holding together as well as it once may have. I'd like to open up discussions as to what you think the main problems are and some idea's how we might fix them without having to invest huge amounts of time in complete rewrites. I'll kick it off with a few things I can see: Problem) Some of the content is out of date. Potential Solution) Identify out of date content and rewrite it. Problem) The navigation system is kind of awkward. Potential Solution) Tabs for each project? Potential Solution) More clearly defining user oriented content and developer oriented content. Potential Solution) Maybe using forrest sitemaps will give us better control. Problem) How do we keep the translations up to date? For instance I just noticed that the german translations still point to the old download location. Potential Solution) Need owner for each translation who is willing to watch for changes as they come through. Regards, Glen Stampoultzis [EMAIL PROTECTED] http://members.iinet.net.au/~gstamp/glen/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: POI Website
Something that is kind of along the same lines, especially with the upcoming release, is that we need javadocs to hang off the site for the released version. The javadocs for the development version can still be on the page but possibly in a sub menu (tab?) on development. This would avoid some confusion with uses who see a certain feature available in the javadocs but does not work because they have the most current release and not the head. I do realize that this is still in on going development but we are starting to getting a good enough release and large enough base that many want need/want to use the development head. Shawn -Original Message- From: Glen Stampoultzis [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 03, 2003 6:08 AM To: [EMAIL PROTECTED] Subject: POI Website As the project as matured the POI web site has grown organically to accommodate that growth. Unfortunately I think we're now at the stage were things are a bit messy and it's not holding together as well as it once may have. I'd like to open up discussions as to what you think the main problems are and some idea's how we might fix them without having to invest huge amounts of time in complete rewrites. I'll kick it off with a few things I can see: Problem) Some of the content is out of date. Potential Solution) Identify out of date content and rewrite it. Problem) The navigation system is kind of awkward. Potential Solution) Tabs for each project? Potential Solution) More clearly defining user oriented content and developer oriented content. Potential Solution) Maybe using forrest sitemaps will give us better control. Problem) How do we keep the translations up to date? For instance I just noticed that the german translations still point to the old download location. Potential Solution) Need owner for each translation who is willing to watch for changes as they come through. Regards, Glen Stampoultzis [EMAIL PROTECTED] http://members.iinet.net.au/~gstamp/glen/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: POI Website
Yeah... it probably wouldn't hurt to show released documentation and the current HEAD documentation. I'll have to keep that in mind when the 2.0 release comes around. -- Glen At 11:56 PM 3/09/2003, you wrote: Something that is kind of along the same lines, especially with the upcoming release, is that we need javadocs to hang off the site for the released version. The javadocs for the development version can still be on the page but possibly in a sub menu (tab?) on development. This would avoid some confusion with uses who see a certain feature available in the javadocs but does not work because they have the most current release and not the head. I do realize that this is still in on going development but we are starting to getting a good enough release and large enough base that many want need/want to use the development head. Shawn -Original Message- From: Glen Stampoultzis [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 03, 2003 6:08 AM To: [EMAIL PROTECTED] Subject: POI Website As the project as matured the POI web site has grown organically to accommodate that growth. Unfortunately I think we're now at the stage were things are a bit messy and it's not holding together as well as it once may have. I'd like to open up discussions as to what you think the main problems are and some idea's how we might fix them without having to invest huge amounts of time in complete rewrites. I'll kick it off with a few things I can see: Problem) Some of the content is out of date. Potential Solution) Identify out of date content and rewrite it. Problem) The navigation system is kind of awkward. Potential Solution) Tabs for each project? Potential Solution) More clearly defining user oriented content and developer oriented content. Potential Solution) Maybe using forrest sitemaps will give us better control. Problem) How do we keep the translations up to date? For instance I just noticed that the german translations still point to the old download location. Potential Solution) Need owner for each translation who is willing to watch for changes as they come through. Regards, Glen Stampoultzis [EMAIL PROTECTED] http://members.iinet.net.au/~gstamp/glen/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Glen Stampoultzis [EMAIL PROTECTED] http://members.iinet.net.au/~gstamp/glen/
Re: POI Website
The site should always show the development version. The goal of the site is to get people involved. People who want to use the releases have the release docs. On 9/3/03 8:15 PM, "Glen Stampoultzis" <[EMAIL PROTECTED]> wrote: > > Yeah... it probably wouldn't hurt to show released documentation and the > current HEAD documentation. I'll have to keep that in mind when the 2.0 > release comes around. > > -- Glen > > At 11:56 PM 3/09/2003, you wrote: >> Something that is kind of along the same lines, especially with the upcoming >> release, is that we need javadocs to hang off the site for the released >> version. The javadocs for the development version can still be on the page >> but possibly in a sub menu (tab?) on development. This would avoid some >> confusion with uses who see a certain feature available in the javadocs but >> does not work because they have the most current release and not the head. >> >> I do realize that this is still in on going development but we are starting >> to getting a good enough release and large enough base that many want >> need/want to use the development head. >> >> Shawn >> >> -Original Message- >> From: Glen Stampoultzis [mailto:[EMAIL PROTECTED] >> Sent: Wednesday, September 03, 2003 6:08 AM >> To: [EMAIL PROTECTED] >> Subject: POI Website >> >> >> >> As the project as matured the POI web site has grown organically to >> accommodate that growth. Unfortunately I think we're now at the stage were >> things are a bit messy and it's not holding together as well as it once may >> have. >> >> I'd like to open up discussions as to what you think the main problems are >> and some idea's how we might fix them without having to invest huge amounts >> of time in complete rewrites. >> >> I'll kick it off with a few things I can see: >> >> Problem) Some of the content is out of date. >> Potential Solution) Identify out of date content and rewrite it. >> >> Problem) The navigation system is kind of awkward. >> Potential Solution) Tabs for each project? >> Potential Solution) More clearly defining user oriented content and >> developer oriented content. >> Potential Solution) Maybe using forrest sitemaps will give us better >> control. >> >> Problem) How do we keep the translations up to date? For instance I just >> noticed that the german translations still point to the old download >> location. >> Potential Solution) Need owner for each translation who is willing to >> watch for changes as they come through. >> >> >> Regards, >> >> >> Glen Stampoultzis >> [EMAIL PROTECTED] >> http://members.iinet.net.au/~gstamp/glen/ >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] > > > Glen Stampoultzis > [EMAIL PROTECTED] > http://members.iinet.net.au/~gstamp/glen/ > -- Andrew C. Oliver http://www.superlinksoftware.com/poi.jsp Custom enhancements and Commercial Implementation for Jakarta POI http://jakarta.apache.org/poi For Java and Excel, Got POI? The views expressed in this email are those of the author and are almost definitely not shared by the Apache Software Foundation, its board or its general membership. In fact they probably most definitively disagree with everything espoused in the above email. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: POI Website
I agree that the main site should show the development version but surely there's no harm in providing a link to the released version docs on-line as well? Regards, Glen At 11:14 AM 4/09/2003, you wrote: The site should always show the development version. The goal of the site is to get people involved. People who want to use the releases have the release docs. On 9/3/03 8:15 PM, "Glen Stampoultzis" <[EMAIL PROTECTED]> wrote: > > Yeah... it probably wouldn't hurt to show released documentation and the > current HEAD documentation. I'll have to keep that in mind when the 2.0 > release comes around. > > -- Glen > > At 11:56 PM 3/09/2003, you wrote: >> Something that is kind of along the same lines, especially with the upcoming >> release, is that we need javadocs to hang off the site for the released >> version. The javadocs for the development version can still be on the page >> but possibly in a sub menu (tab?) on development. This would avoid some >> confusion with uses who see a certain feature available in the javadocs but >> does not work because they have the most current release and not the head. >> >> I do realize that this is still in on going development but we are starting >> to getting a good enough release and large enough base that many want >> need/want to use the development head. >> >> Shawn >> >> -Original Message- >> From: Glen Stampoultzis [mailto:[EMAIL PROTECTED] >> Sent: Wednesday, September 03, 2003 6:08 AM >> To: [EMAIL PROTECTED] >> Subject: POI Website >> >> >> >> As the project as matured the POI web site has grown organically to >> accommodate that growth. Unfortunately I think we're now at the stage were >> things are a bit messy and it's not holding together as well as it once may >> have. >> >> I'd like to open up discussions as to what you think the main problems are >> and some idea's how we might fix them without having to invest huge amounts >> of time in complete rewrites. >> >> I'll kick it off with a few things I can see: >> >> Problem) Some of the content is out of date. >> Potential Solution) Identify out of date content and rewrite it. >> >> Problem) The navigation system is kind of awkward. >> Potential Solution) Tabs for each project? >> Potential Solution) More clearly defining user oriented content and >> developer oriented content. >> Potential Solution) Maybe using forrest sitemaps will give us better >> control. >> >> Problem) How do we keep the translations up to date? For instance I just >> noticed that the german translations still point to the old download >> location. >> Potential Solution) Need owner for each translation who is willing to >> watch for changes as they come through. >> >> >> Regards, >> >> >> Glen Stampoultzis >> [EMAIL PROTECTED] >> http://members.iinet.net.au/~gstamp/glen/ >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] > > > Glen Stampoultzis > [EMAIL PROTECTED] > http://members.iinet.net.au/~gstamp/glen/ > -- Andrew C. Oliver http://www.superlinksoftware.com/poi.jsp Custom enhancements and Commercial Implementation for Jakarta POI http://jakarta.apache.org/poi For Java and Excel, Got POI? The views expressed in this email are those of the author and are almost definitely not shared by the Apache Software Foundation, its board or its general membership. In fact they probably most definitively disagree with everything espoused in the above email. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Glen Stampoultzis [EMAIL PROTECTED] http://members.iinet.net.au/~gstamp/glen/
Re: POI Website
yeah, i think that should be nice, tho properly labelled to avoid confusion. My biggest currently is the skin.. if i get a momentoh well... :) On Thu, 2003-09-04 at 07:05, Glen Stampoultzis wrote: > I agree that the main site should show the development version but surely > there's no harm in providing a link to the released version docs on-line as > well? > > Regards, > > Glen > > At 11:14 AM 4/09/2003, you wrote: > >The site should always show the development version. The goal of the site > >is to get people involved. People who want to use the releases have the > >release docs. > > > >On 9/3/03 8:15 PM, "Glen Stampoultzis" <[EMAIL PROTECTED]> wrote: > > > > > > > > Yeah... it probably wouldn't hurt to show released documentation and the > > > current HEAD documentation. I'll have to keep that in mind when the 2.0 > > > release comes around. > > > > > > -- Glen > > > > > > At 11:56 PM 3/09/2003, you wrote: > > >> Something that is kind of along the same lines, especially with the > > upcoming > > >> release, is that we need javadocs to hang off the site for the released > > >> version. The javadocs for the development version can still be on the > > page > > >> but possibly in a sub menu (tab?) on development. This would avoid some > > >> confusion with uses who see a certain feature available in the > > javadocs but > > >> does not work because they have the most current release and not the head. > > >> > > >> I do realize that this is still in on going development but we are > > starting > > >> to getting a good enough release and large enough base that many want > > >> need/want to use the development head. > > >> > > >> Shawn > > >> > > >> -Original Message- > > >> From: Glen Stampoultzis [mailto:[EMAIL PROTECTED] > > >> Sent: Wednesday, September 03, 2003 6:08 AM > > >> To: [EMAIL PROTECTED] > > >> Subject: POI Website > > >> > > >> > > >> > > >> As the project as matured the POI web site has grown organically to > > >> accommodate that growth. Unfortunately I think we're now at the stage > > were > > >> things are a bit messy and it's not holding together as well as it > > once may > > >> have. > > >> > > >> I'd like to open up discussions as to what you think the main problems are > > >> and some idea's how we might fix them without having to invest huge > > amounts > > >> of time in complete rewrites. > > >> > > >> I'll kick it off with a few things I can see: > > >> > > >> Problem) Some of the content is out of date. > > >> Potential Solution) Identify out of date content and rewrite it. > > >> > > >> Problem) The navigation system is kind of awkward. > > >> Potential Solution) Tabs for each project? > > >> Potential Solution) More clearly defining user oriented content and > > >> developer oriented content. > > >> Potential Solution) Maybe using forrest sitemaps will give us better > > >> control. > > >> > > >> Problem) How do we keep the translations up to date? For instance I just > > >> noticed that the german translations still point to the old download > > >> location. > > >> Potential Solution) Need owner for each translation who is willing to > > >> watch for changes as they come through. > > >> > > >> > > >> Regards, > > >> > > >> > > >> Glen Stampoultzis > > >> [EMAIL PROTECTED] > > >> http://members.iinet.net.au/~gstamp/glen/ > > >> > > >> > > >> - > > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > > >> For additional commands, e-mail: [EMAIL PROTECTED] > > >> > > >> - > > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > > >> For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > Glen Stampoultzis > > > [EMAIL PROTECTED] > > > http://members.iinet.net.au/~gstamp/glen/ > > > > > > >-- > >Andrew C. Oliver > >http://www.superlinksoftware.com/poi.jsp > >Custom enhancements and Commercial Implementation for Jakarta POI > > > >http://jakarta.apache.org/poi > >For Java and Excel, Got POI? > > > >The views expressed in this email are those of the author and are almost > >definitely not shared by the Apache Software Foundation, its board or its > >general membership. In fact they probably most definitively disagree with > >everything espoused in the above email. > > > > > >- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > Glen Stampoultzis > [EMAIL PROTECTED] > http://members.iinet.net.au/~gstamp/glen/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: POI Website
On Thu, 04 Sep 2003 11:35:00 +1000 Glen Stampoultzis <[EMAIL PROTECTED]> wrote: > I agree that the main site should show the development version but surely > there's no harm in providing a link to the released version docs on-line as > well? Not at all. The reader should see a clear distinction between the developer and the stable releases. He should also see *what* the differences are. Best regards Rainer Klute Rainer Klute IT-Consulting GmbH Dipl.-Inform. Rainer Klute E-Mail: [EMAIL PROTECTED] Körner Grund 24 Telefon: +49 172 2324824 D-44143 Dortmund Telefax: +49 231 5349423 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: POI Website
What's your issue with the skin? I'm pretty happy with it aside from the logo which I think just doesn't work well against the blue background. -- Glen At 02:08 AM 5/09/2003, you wrote: yeah, i think that should be nice, tho properly labelled to avoid confusion. My biggest currently is the skin.. if i get a momentoh well... :) On Thu, 2003-09-04 at 07:05, Glen Stampoultzis wrote: > I agree that the main site should show the development version but surely > there's no harm in providing a link to the released version docs on-line as > well? > > Regards, > > Glen > > At 11:14 AM 4/09/2003, you wrote: > >The site should always show the development version. The goal of the site > >is to get people involved. People who want to use the releases have the > >release docs. > > > >On 9/3/03 8:15 PM, "Glen Stampoultzis" <[EMAIL PROTECTED]> wrote: > > > > > > > > Yeah... it probably wouldn't hurt to show released documentation and the > > > current HEAD documentation. I'll have to keep that in mind when the 2.0 > > > release comes around. > > > > > > -- Glen > > > > > > At 11:56 PM 3/09/2003, you wrote: > > >> Something that is kind of along the same lines, especially with the > > upcoming > > >> release, is that we need javadocs to hang off the site for the released > > >> version. The javadocs for the development version can still be on the > > page > > >> but possibly in a sub menu (tab?) on development. This would avoid some > > >> confusion with uses who see a certain feature available in the > > javadocs but > > >> does not work because they have the most current release and not the head. > > >> > > >> I do realize that this is still in on going development but we are > > starting > > >> to getting a good enough release and large enough base that many want > > >> need/want to use the development head. > > >> > > >> Shawn > > >> > > >> -Original Message- > > >> From: Glen Stampoultzis [mailto:[EMAIL PROTECTED] > > >> Sent: Wednesday, September 03, 2003 6:08 AM > > >> To: [EMAIL PROTECTED] > > >> Subject: POI Website > > >> > > >> > > >> > > >> As the project as matured the POI web site has grown organically to > > >> accommodate that growth. Unfortunately I think we're now at the stage > > were > > >> things are a bit messy and it's not holding together as well as it > > once may > > >> have. > > >> > > >> I'd like to open up discussions as to what you think the main problems are > > >> and some idea's how we might fix them without having to invest huge > > amounts > > >> of time in complete rewrites. > > >> > > >> I'll kick it off with a few things I can see: > > >> > > >> Problem) Some of the content is out of date. > > >> Potential Solution) Identify out of date content and rewrite it. > > >> > > >> Problem) The navigation system is kind of awkward. > > >> Potential Solution) Tabs for each project? > > >> Potential Solution) More clearly defining user oriented content and > > >> developer oriented content. > > >> Potential Solution) Maybe using forrest sitemaps will give us better > > >> control. > > >> > > >> Problem) How do we keep the translations up to date? For instance I just > > >> noticed that the german translations still point to the old download > > >> location. > > >> Potential Solution) Need owner for each translation who is willing to > > >> watch for changes as they come through. > > >> > > >> > > >> Regards, > > >> > > >> > > >> Glen Stampoultzis > > >> [EMAIL PROTECTED] > > >> http://members.iinet.net.au/~gstamp/glen/ > > >> > > >> > > >> - > > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > > >> For additional commands, e-mail: [EMAIL PROTECTED] > > >> > > >> - > > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > > >> For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > Glen Stampo
Re: POI Website
>What's your issue with the skin? I particularly dont like the color scheme.. I think its slightly depressing .. i would prefer something happier :) And, as you say, it doesnt play too well with the logo. The other thing i dont like is the side menu.. it doesnt size too well (becomes too big if text is too long) .. etc... However, whatever my opinions on this, i have a stronger view that its totally counter-productive to discuss subjective website look issues on lists such as this .. either i care enough to change it myself, or I am happy with it so long as it does its job On a more objective basis, I think our site has lots of info.. we probably need a way to categorize it better.. anyone with a library science degree? :) For example, see the menu on the left.. each of the items seem as important as another, however, most people probably want the FAQ and the Quick Start first.. so that should be most obvious.. maybe a big red arrow.. :) There is one thing i have always thought we should do, but i have been to lazy.. is that we should have an INSTALL page on the site.. even tho we dont have much to say.. people still look for it.. so it should be there to pander This needs more thought.. will give it some. On Fri, 2003-09-05 at 08:34, Glen Stampoultzis wrote: > What's your issue with the skin? I'm pretty happy with it aside from the > logo which I think just doesn't work well against the blue background. > > -- Glen > > At 02:08 AM 5/09/2003, you wrote: > >yeah, i think that should be nice, tho properly labelled to avoid > >confusion. My biggest currently is the skin.. if i get a momentoh > >well... :) > > > >On Thu, 2003-09-04 at 07:05, Glen Stampoultzis wrote: > > > I agree that the main site should show the development version but surely > > > there's no harm in providing a link to the released version docs > > on-line as > > > well? > > > > > > Regards, > > > > > > Glen > > > > > > At 11:14 AM 4/09/2003, you wrote: > > > >The site should always show the development version. The goal of the site > > > >is to get people involved. People who want to use the releases have the > > > >release docs. > > > > > > > >On 9/3/03 8:15 PM, "Glen Stampoultzis" <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > Yeah... it probably wouldn't hurt to show released documentation > > and the > > > > > current HEAD documentation. I'll have to keep that in mind when > > the 2.0 > > > > > release comes around. > > > > > > > > > > -- Glen > > > > > > > > > > At 11:56 PM 3/09/2003, you wrote: > > > > >> Something that is kind of along the same lines, especially with the > > > > upcoming > > > > >> release, is that we need javadocs to hang off the site for the > > released > > > > >> version. The javadocs for the development version can still be on > > the > > > > page > > > > >> but possibly in a sub menu (tab?) on development. This would > > avoid some > > > > >> confusion with uses who see a certain feature available in the > > > > javadocs but > > > > >> does not work because they have the most current release and not > > the head. > > > > >> > > > > >> I do realize that this is still in on going development but we are > > > > starting > > > > >> to getting a good enough release and large enough base that many want > > > > >> need/want to use the development head. > > > > >> > > > > >> Shawn > > > > >> > > > > >> -Original Message- > > > > >> From: Glen Stampoultzis [mailto:[EMAIL PROTECTED] > > > > >> Sent: Wednesday, September 03, 2003 6:08 AM > > > > >> To: [EMAIL PROTECTED] > > > > >> Subject: POI Website > > > > >> > > > > >> > > > > >> > > > > >> As the project as matured the POI web site has grown organically to > > > > >> accommodate that growth. Unfortunately I think we're now at the > > stage > > > > were > > > > >> things are a bit messy and it's not holding together as well as it > > > > once may > > > > >> have. > > > > >> > > > > >> I'd like to open up discussions as t
Re: POI Website
Skin.. you (we) can choose tigris-skin. To tell the truth, my company's website is now using Apache Forrest .. Yay! ;-) (http://www.terra-intl.com/) Will I build POI-website using tigris-skin and show you all? (There could be no need for discussion of the background color any more, I believe) -- Also, what about using the Cocoon-like (Release-Number based website management system) styled site? -- Tetsuya ([EMAIL PROTECTED]) On 05 Sep 2003 20:21:11 +0530 (Subject: Re: POI Website) Avik Sengupta <[EMAIL PROTECTED]> wrote: > >What's your issue with the skin? > I particularly dont like the color scheme.. I think its slightly > depressing .. i would prefer something happier :) And, as you say, it > doesnt play too well with the logo. The other thing i dont like is the > side menu.. it doesnt size too well (becomes too big if text is too > long) .. etc... > > However, whatever my opinions on this, i have a stronger view that its > totally counter-productive to discuss subjective website look issues on > lists such as this .. either i care enough to change it myself, or I am > happy with it so long as it does its job > > On a more objective basis, I think our site has lots of info.. we > probably need a way to categorize it better.. anyone with a library > science degree? :) > > For example, see the menu on the left.. each of the items seem as > important as another, however, most people probably want the FAQ and the > Quick Start first.. so that should be most obvious.. maybe a big red > arrow.. :) > > There is one thing i have always thought we should do, but i have been > to lazy.. is that we should have an INSTALL page on the site.. even tho > we dont have much to say.. people still look for it.. so it should be > there to pander > > This needs more thought.. will give it some. > > > > On Fri, 2003-09-05 at 08:34, Glen Stampoultzis wrote: > > What's your issue with the skin? I'm pretty happy with it aside from the > > logo which I think just doesn't work well against the blue background. > > > > -- Glen > > > > At 02:08 AM 5/09/2003, you wrote: > > >yeah, i think that should be nice, tho properly labelled to avoid > > >confusion. My biggest currently is the skin.. if i get a momentoh > > >well... :) > > > > > >On Thu, 2003-09-04 at 07:05, Glen Stampoultzis wrote: > > > > I agree that the main site should show the development version but surely > > > > there's no harm in providing a link to the released version docs > > > on-line as > > > > well? > > > > > > > > Regards, > > > > > > > > Glen > > > > > > > > At 11:14 AM 4/09/2003, you wrote: > > > > >The site should always show the development version. The goal of the site > > > > >is to get people involved. People who want to use the releases have the > > > > >release docs. > > > > > > > > > >On 9/3/03 8:15 PM, "Glen Stampoultzis" <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > > > Yeah... it probably wouldn't hurt to show released documentation > > > and the > > > > > > current HEAD documentation. I'll have to keep that in mind when > > > the 2.0 > > > > > > release comes around. > > > > > > > > > > > > -- Glen > > > > > > > > > > > > At 11:56 PM 3/09/2003, you wrote: > > > > > >> Something that is kind of along the same lines, especially with the > > > > > upcoming > > > > > >> release, is that we need javadocs to hang off the site for the > > > released > > > > > >> version. The javadocs for the development version can still be on > > > the > > > > > page > > > > > >> but possibly in a sub menu (tab?) on development. This would > > > avoid some > > > > > >> confusion with uses who see a certain feature available in the > > > > > javadocs but > > > > > >> does not work because they have the most current release and not > > > the head. > > > > > >> > > > > > >> I do realize that this is still in on going development but we are > > > > > starting > > > > > >> to getting a good enough release and large enough base that many want > > > > > >> need/want to use the development head. > > > >
Re: POI Website
> However, whatever my opinions on this, i have a stronger view that its > totally counter-productive to discuss subjective website look issues on > lists such as this .. either i care enough to change it myself, or I am > happy with it so long as it does its job > +1 -- Andrew C. Oliver http://www.superlinksoftware.com/poi.jsp Custom enhancements and Commercial Implementation for Jakarta POI http://jakarta.apache.org/poi For Java and Excel, Got POI? The views expressed in this email are those of the author and are almost definitely not shared by the Apache Software Foundation, its board or its general membership. In fact they probably most definitively disagree with everything espoused in the above email. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: POI Website
At 02:18 AM 6/09/2003, you wrote: > However, whatever my opinions on this, i have a stronger view that its > totally counter-productive to discuss subjective website look issues on > lists such as this .. either i care enough to change it myself, or I am > happy with it so long as it does its job > +1 Just curious. I really was more interested more substantial issues that do effect our users rather than L&F. Just after some practical idea's on how we might improve that their experience. -- Glen
