You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Stefano Mazzocchi <st...@apache.org> on 2001/12/05 12:51:26 UTC
[Vote] Improving Cocoon Site
We have released Cocoon and this is a great thing.
Now we have to improve the web site a little bit.
1) location of Cocoon 1.x documentation:
I propose to move
http://xml.apache.org/cocoon1
into
http://xml.apache.org/cocoon/old/
which I believe it's better because the URI is version-free and
future-compatible: this means this location identified "the previous
generation of Cocoon, now considered obsolete, but still used by many".
2) graphic look:
I propose to update the site skin using the new xml.apache.org look
proposed over at general@xml.apache.org. Ted, what's the status of this?
where can we find the stylesheets you came up with?
This mainly because the site is simply too heavy: it's ok to show off
the power of generating raster images out of SVG files, but this is
clearly too much.
3) Clean up documentation: there is a lot to do, but here are things
that bug me:
a) there is no visual difference between sections (i.e. User) and pages
(Who We Are).
b) there is very little meaning associated with the sections (how in
hell are readers supposed to know what CTWIG is?)
c) we should have a "community" section.
4) enhance site functionality:
a) searching: we must come up with a way to search content, even
forwarding to Google is better than nothing.
b) community information:
- graphs of people subscribed on the mail lists
- graphs of messages on the mail lists
- graphs of downloads
I see much more valuable to use the SVG rasterizer for such graphs
rather than "waste" it to generate the sitebar text. In order to do
this, though, we need to gather this information.
My idea is to have a perl script (or equivalent) run every week that
comes up with this information and places it on a specific location
(this should be done for every xml.apache project).
Unfortunately, the mail list subscription information is reserved by
root, so we need a high level of access in order to do this (Sam, do you
have that kind of access level?). The compressed MBOX files can be found
over at:
/www/xml.apache.org/mail/cocoon-(users|dev)
while the web site logs are in
/x2/logarchive/www/2001
The ideal solution would be to have this processed information already
XML-ized, but it's probably easier to "append" a line than to add an
element to an XML file. We could use CSV and do the XML-ization at
Generation level.
Something like this would be great:
cocoon.list.cocoon-dev:
cocoon.list.cocoon-users:
year,week,subscribers,messages
2001,01,348,983
2001,02,358,839
2001,03,334,1093
2001,03,343,1293
...
which could XML-ized as
<list>
<item year="2001" week="01" subscribers="348" messages="983"/>
<item year="2001" week="02" subscribers="358" messages="839"/>
...
</list>
or
<list>
<item>
<year>2001</year>
<week>01</week>
<subscribers>348</subscribers>
<messages>983</messages>
</item>
...
</list>
which is more verbose, but could be easier to create using SAX events
and easier to process with XSLT stylesheets (why attributes are so
neglected in the XML world? bah, I love them so much)
Then we could easily transform this into SVG with an XSLT stylesheet and
have the raster graph generated automatically without human
intervention. Again, note that XML-ization of the CSV file can be done
by a CSVGenerator which is piece of cake to write (I volunteer to do it
if this is accepted)
Also,
cocoon.downloads
year,week,downloads
2001,01,294
2001,02,384
I'm not very good at UNIX administration, so I'd be more than happy if
somebody else provides the scripts and installs them on apache.org :)
Ok, enough for now.
Please, place your votes or indicate your
comments/suggestions/criticism.
Thanks.
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [Vote] Improving Cocoon Site
Posted by David Crossley <cr...@indexgeo.com.au>.
Giacomo Pati wrote:
> Quoting David Crossley <cr...@indexgeo.com.au>:
> > Stefano Mazzocchi wrote:
>
> <snip/>
>
> > > My idea is to have a perl script (or equivalent) run every
> > > week that comes up with this information and places it on
> > > a specific location
> > > (this should be done for every xml.apache project).
> >
> > I do not understand how the graphs would get regularly updated
> > on the website for everyone see. At the moment the site
> > documentation is only updated on an occasional basis.
>
> We can use cocoon-cli running regularly via cron jobs.
> Giacomo
Yes, great - i love the cli capability. However, where does
Cocoon run so as to do this job? How do the results get back
to xml.apache.org/cocoon/ static website. Hence the discussion
in the other part of this thread about a Cocoon demo server.
--David
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [Vote] Improving Cocoon Site
Posted by Giacomo Pati <gi...@apache.org>.
Quoting David Crossley <cr...@indexgeo.com.au>:
> Stefano Mazzocchi wrote:
<snip/>
> > My idea is to have a perl script (or equivalent) run every week that
> > comes up with this information and places it on a specific location
> > (this should be done for every xml.apache project).
>
> I do not understand how the graphs would get regularly updated
> on the website for everyone see. At the moment the site
> documentation is only updated on an occasional basis.
We can use cocoon-cli running regularly via cron jobs.
Giacomo
<snip/>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [Vote] Improving Cocoon Site
Posted by David Crossley <cr...@indexgeo.com.au>.
"Robert Koberg" <ro...@koberg.com> wrote:
> > David Crossley wrote:
> > > +1 ... However, it is hard to have interactive search on
> > > a static website. Again, if only Cocoon was running on
> > > the server, we
> > > could use the new Cocoon-Lucene functionality.
> > >
> > > Sure, links to Google might help. However, Google's content
> > > is at least one month out-of-date ... a bit useful, nevertheless.
>
> ---
> wouldn't it be easier to have an interactive (not sure what that is...)
> search on a static site? If you know the content you need to
> search then you can prepare.
As discussed elsewhere in this thread, the problem is that
we cannot run any services on the xml.apache.org machine.
Yes, the search system could operate on the collection of
static Cocoon 2 documents.
Robert Koberg continued:
> Stefano Mazzocchi wrote:
> > Oh, I'd love to have Cocoon serve its own pages, believe me, but apache
> > machines are simply too loaded for that (and I don't personally have the
> > access level to be able to run this, nor I want that responsability on
> > such an important servers since I'm no system adminitrator of any sort!)
> >
> > Maybe we could use Nagoya (Sun E4500, *big* beast!) for that and
> > redirect: Sam, you have access to that machine, right?
>
> ---
> Are you guys saying that the cocoon site site should be dynamic?
> Isn't that a waste of resources for a few weekly graphs?
> best,
> -Rob
It would be used for many things. Live demos of the distributed
samples is one other thing that is sadly missing.
--David
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [Vote] Improving Cocoon Site
Posted by Stefano Mazzocchi <st...@apache.org>.
Robert Koberg wrote:
>
> > > +1 ... However, it is hard to have interactive search on a static
> > > website. Again, if only Cocoon was running on the server, we
> > > could use the new Cocoon-Lucene functionality.
> > >
> > > Sure, links to Google might help. However, Google's content
> > > is at least one month out-of-date ... a bit useful, nevertheless.
>
> ---
> wouldn't it be easier to have an interactive (not sure what that is...)
> search on a static site? If you know the content you need to search then you
> can prepare.
Yes, we could use things like HtDIG or a servlet that connects to
Lucene.
> >
> > Oh, I'd love to have Cocoon serve its own pages, believe me, but apache
> > machines are simply too loaded for that (and I don't personally have the
> > access level to be able to run this, nor I want that responsability on
> > such an important servers since I'm no system adminitrator of any sort!)
> >
> > Maybe we could use Nagoya (Sun E4500, *big* beast!) for that and
> > redirect: Sam, you have access to that machine, right?
> >
>
> ---
> Are you guys saying that the cocoon site site should be dynamic? Isn't that
> a waste of resources for a few weekly graphs?
Yes, good point.
At the same time, having Cocoon dynamism present we could clearly
improve the browsing experience with more interactive things. I find
myself constrained by staticity and by lack of access on the serving
infrastructure of xml.apache.org :/
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [Vote] Improving Cocoon Site
Posted by Robert Koberg <ro...@koberg.com>.
> > +1 ... However, it is hard to have interactive search on a static
> > website. Again, if only Cocoon was running on the server, we
> > could use the new Cocoon-Lucene functionality.
> >
> > Sure, links to Google might help. However, Google's content
> > is at least one month out-of-date ... a bit useful, nevertheless.
---
wouldn't it be easier to have an interactive (not sure what that is...)
search on a static site? If you know the content you need to search then you
can prepare.
>
> Oh, I'd love to have Cocoon serve its own pages, believe me, but apache
> machines are simply too loaded for that (and I don't personally have the
> access level to be able to run this, nor I want that responsability on
> such an important servers since I'm no system adminitrator of any sort!)
>
> Maybe we could use Nagoya (Sun E4500, *big* beast!) for that and
> redirect: Sam, you have access to that machine, right?
>
---
Are you guys saying that the cocoon site site should be dynamic? Isn't that
a waste of resources for a few weekly graphs?
best,
-Rob
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [Vote] Improving Cocoon Site
Posted by David Crossley <cr...@indexgeo.com.au>.
Stefano Mazzocchi wrote:
> David Crossley wrote:
> > Stefano Mazzocchi wrote:
> > > We have released Cocoon and this is a great thing.
> > >
> > > Now we have to improve the web site a little bit.
<snip/>
> > > 4) enhance site functionality:
> > >
> > > a) searching: we must come up with a way to search content,
> > > even forwarding to Google is better than nothing.
> >
> > +1 ... However, it is hard to have interactive search on a static
> > website. Again, if only Cocoon was running on the server, we
> > could use the new Cocoon-Lucene functionality.
> >
> > Sure, links to Google might help. However, Google's content
> > is at least one month out-of-date ... a bit useful, nevertheless.
>
> Oh, I'd love to have Cocoon serve its own pages, believe me, but apache
> machines are simply too loaded for that (and I don't personally have the
> access level to be able to run this, nor I want that responsability on
> such an important servers since I'm no system adminitrator of any sort!)
>
> Maybe we could use Nagoya (Sun E4500, *big* beast!) for that and
> redirect: Sam, you have access to that machine, right?
If that does not pan out, then how about someone else run
an "official" Cocoon demonstration server, which could get
its content from xml.apache.org (xdocs from cvs, log summaries)
The remote server could easily regularly get the data via
cvs update over ssh2.
Whatever happens, i believe that we *must* have a Cocoon
demonstration server somewhere.
This i could never understand when i started to explore Cocoon.
Cocoon seemed so wonderful, yet the website was a klutz.
Then i figured out that it was a static website ... relief.
However, the first impression was not good.
--David
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [Vote] Improving Cocoon Site
Posted by Stefano Mazzocchi <st...@apache.org>.
David Crossley wrote:
>
> Stefano Mazzocchi wrote:
> > We have released Cocoon and this is a great thing.
> >
> > Now we have to improve the web site a little bit.
> >
> > 1) location of Cocoon 1.x documentation:
> >
> > I propose to move
> >
> > http://xml.apache.org/cocoon1
> >
> > into
> >
> > http://xml.apache.org/cocoon/old/
> >
> > which I believe it's better because the URI is version-free and
> > future-compatible: this means this location identified "the previous
> > generation of Cocoon, now considered obsolete, but still used by many".
>
> +0 ... I abstain because i do not yet understand the issues.
> I gather that you intend that there will never be another major
> version of Cocoon. Otherwise, we will need cocoon/very-old/
> as well as cocoon/old/
No, I indend that will never be more than two incompatible versions
supported, the current and the old.
> > 2) graphic look:
> >
> > I propose to update the site skin using the new xml.apache.org look
> > proposed over at general@xml.apache.org. Ted, what's the status
> > of this?
> > where can we find the stylesheets you came up with?
> >
> > This mainly because the site is simply too heavy: it's ok to show off
> > the power of generating raster images out of SVG files, but this is
> > clearly too much.
>
> +1 ... the current website is a huge turn-off. Even local build docs
> is very frustrating. I wish for a nice clean look-and-feel like the
> Avalon website.
Ok, will do it.
> > 3) Clean up documentation: there is a lot to do, but here are things
> > that bug me:
> >
> > a) there is no visual difference between sections (i.e. User) and pages
> > (Who We Are).
> >
> > b) there is very little meaning associated with the sections (how in
> > hell are readers supposed to know what CTWIG is?)
> >
> > c) we should have a "community" section.
> >
> > 4) enhance site functionality:
> >
> > a) searching: we must come up with a way to search content, even
> > forwarding to Google is better than nothing.
>
> +1 ... However, it is hard to have interactive search on a static
> website. Again, if only Cocoon was running on the server, we
> could use the new Cocoon-Lucene functionality.
>
> Sure, links to Google might help. However, Google's content
> is at least one month out-of-date ... a bit useful, nevertheless.
Oh, I'd love to have Cocoon serve its own pages, believe me, but apache
machines are simply too loaded for that (and I don't personally have the
access level to be able to run this, nor I want that responsability on
such an important servers since I'm no system adminitrator of any sort!)
Maybe we could use Nagoya (Sun E4500, *big* beast!) for that and
redirect: Sam, you have access to that machine, right?
> > b) community information:
> >
> > - graphs of people subscribed on the mail lists
> > - graphs of messages on the mail lists
> > - graphs of downloads
> >
> > I see much more valuable to use the SVG rasterizer for such graphs
> > rather than "waste" it to generate the sitebar text. In order to do
> > this, though, we need to gather this information.
>
> +1 ... this would be great for us all to see. Yes a far better way
> to show off SVG.
>
> > My idea is to have a perl script (or equivalent) run every week that
> > comes up with this information and places it on a specific location
> > (this should be done for every xml.apache project).
>
> I do not understand how the graphs would get regularly updated
> on the website for everyone see. At the moment the site
> documentation is only updated on an occasional basis.
>
> Oh, how we wish for a site that was actually running Cocoon
> rather than a static web site.
What about moving over to nagoya? it's solaris machine so java support
rocks, plus it has more RAM than we need :) It could also be a wonderful
load test.
> > Unfortunately, the mail list subscription information is reserved by
> > root, so we need a high level of access in order to do this (Sam, do you
> > have that kind of access level?). The compressed MBOX files can be found
> > over at:
> >
> > /www/xml.apache.org/mail/cocoon-(users|dev)
> >
> > while the web site logs are in
> >
> > /x2/logarchive/www/2001
> >
> > The ideal solution would be to have this processed information already
> > XML-ized, but it's probably easier to "append" a line than to add an
> > element to an XML file. We could use CSV and do the XML-ization at
> > Generation level.
> >
> > Something like this would be great:
> >
> > cocoon.list.cocoon-dev:
> > cocoon.list.cocoon-users:
> >
> > year,week,subscribers,messages
> > 2001,01,348,983
> > 2001,02,358,839
> > 2001,03,334,1093
> > 2001,03,343,1293
> > ...
> >
> > which could XML-ized as
> >
> > <list>
> > <item year="2001" week="01" subscribers="348" messages="983"/>
> > <item year="2001" week="02" subscribers="358" messages="839"/>
> > ...
> > </list>
> >
> > or
> >
> > <list>
> > <item>
> > <year>2001</year>
> > <week>01</week>
> > <subscribers>348</subscribers>
> > <messages>983</messages>
> > </item>
> > ...
> > </list>
> >
> > which is more verbose, but could be easier to create using SAX events
> > and easier to process with XSLT stylesheets (why attributes are so
> > neglected in the XML world? bah, I love them so much)
>
> http://xml.coverpages.org/topics.html#elementsAndAttrs
> has arguments for and against each. I am still unclear, but
> think that i lean towards structured data as elements rather
> than attributes.
My personal design pattern is: if it's only one and doesn't require
nesting, should be an attribute.
This results, IMO, in increased readability and reduced verbosity
without any degradation in expressivity.
But that's my personal opinion only.
> > Then we could easily transform this into SVG with an XSLT stylesheet and
> > have the raster graph generated automatically without human
> > intervention. Again, note that XML-ization of the CSV file can be done
> > by a CSVGenerator which is piece of cake to write (I volunteer to do it
> > if this is accepted)
>
> Excellent, Cocoon needs a default CSVGenerator anyway.
Shouldn't take long to write.
You guys come up with the CSV files and I write the generator, ok? :)
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [Vote] Improving Cocoon Site
Posted by David Crossley <cr...@indexgeo.com.au>.
Stefano Mazzocchi wrote:
> We have released Cocoon and this is a great thing.
>
> Now we have to improve the web site a little bit.
>
> 1) location of Cocoon 1.x documentation:
>
> I propose to move
>
> http://xml.apache.org/cocoon1
>
> into
>
> http://xml.apache.org/cocoon/old/
>
> which I believe it's better because the URI is version-free and
> future-compatible: this means this location identified "the previous
> generation of Cocoon, now considered obsolete, but still used by many".
+0 ... I abstain because i do not yet understand the issues.
I gather that you intend that there will never be another major
version of Cocoon. Otherwise, we will need cocoon/very-old/
as well as cocoon/old/
> 2) graphic look:
>
> I propose to update the site skin using the new xml.apache.org look
> proposed over at general@xml.apache.org. Ted, what's the status
> of this?
> where can we find the stylesheets you came up with?
>
> This mainly because the site is simply too heavy: it's ok to show off
> the power of generating raster images out of SVG files, but this is
> clearly too much.
+1 ... the current website is a huge turn-off. Even local build docs
is very frustrating. I wish for a nice clean look-and-feel like the
Avalon website.
> 3) Clean up documentation: there is a lot to do, but here are things
> that bug me:
>
> a) there is no visual difference between sections (i.e. User) and pages
> (Who We Are).
>
> b) there is very little meaning associated with the sections (how in
> hell are readers supposed to know what CTWIG is?)
>
> c) we should have a "community" section.
>
> 4) enhance site functionality:
>
> a) searching: we must come up with a way to search content, even
> forwarding to Google is better than nothing.
+1 ... However, it is hard to have interactive search on a static
website. Again, if only Cocoon was running on the server, we
could use the new Cocoon-Lucene functionality.
Sure, links to Google might help. However, Google's content
is at least one month out-of-date ... a bit useful, nevertheless.
> b) community information:
>
> - graphs of people subscribed on the mail lists
> - graphs of messages on the mail lists
> - graphs of downloads
>
> I see much more valuable to use the SVG rasterizer for such graphs
> rather than "waste" it to generate the sitebar text. In order to do
> this, though, we need to gather this information.
+1 ... this would be great for us all to see. Yes a far better way
to show off SVG.
> My idea is to have a perl script (or equivalent) run every week that
> comes up with this information and places it on a specific location
> (this should be done for every xml.apache project).
I do not understand how the graphs would get regularly updated
on the website for everyone see. At the moment the site
documentation is only updated on an occasional basis.
Oh, how we wish for a site that was actually running Cocoon
rather than a static web site.
> Unfortunately, the mail list subscription information is reserved by
> root, so we need a high level of access in order to do this (Sam, do you
> have that kind of access level?). The compressed MBOX files can be found
> over at:
>
> /www/xml.apache.org/mail/cocoon-(users|dev)
>
> while the web site logs are in
>
> /x2/logarchive/www/2001
>
> The ideal solution would be to have this processed information already
> XML-ized, but it's probably easier to "append" a line than to add an
> element to an XML file. We could use CSV and do the XML-ization at
> Generation level.
>
> Something like this would be great:
>
> cocoon.list.cocoon-dev:
> cocoon.list.cocoon-users:
>
> year,week,subscribers,messages
> 2001,01,348,983
> 2001,02,358,839
> 2001,03,334,1093
> 2001,03,343,1293
> ...
>
> which could XML-ized as
>
> <list>
> <item year="2001" week="01" subscribers="348" messages="983"/>
> <item year="2001" week="02" subscribers="358" messages="839"/>
> ...
> </list>
>
> or
>
> <list>
> <item>
> <year>2001</year>
> <week>01</week>
> <subscribers>348</subscribers>
> <messages>983</messages>
> </item>
> ...
> </list>
>
> which is more verbose, but could be easier to create using SAX events
> and easier to process with XSLT stylesheets (why attributes are so
> neglected in the XML world? bah, I love them so much)
http://xml.coverpages.org/topics.html#elementsAndAttrs
has arguments for and against each. I am still unclear, but
think that i lean towards structured data as elements rather
than attributes.
> Then we could easily transform this into SVG with an XSLT stylesheet and
> have the raster graph generated automatically without human
> intervention. Again, note that XML-ization of the CSV file can be done
> by a CSVGenerator which is piece of cake to write (I volunteer to do it
> if this is accepted)
Excellent, Cocoon needs a default CSVGenerator anyway.
--David Crossley
> Also,
>
> cocoon.downloads
>
> year,week,downloads
> 2001,01,294
> 2001,02,384
>
> I'm not very good at UNIX administration, so I'd be more than happy if
> somebody else provides the scripts and installs them on apache.org :)
>
> Ok, enough for now.
>
> Please, place your votes or indicate your
> comments/suggestions/criticism.
>
> Thanks.
>
> --
> Stefano Mazzocchi One must still have chaos in oneself to be
> able to give birth to a dancing star.
> <st...@apache.org> Friedrich Nietzsche
> --------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [Vote] Improving Cocoon Site
Posted by Frans Thamura <ft...@yahoo.com>.
+ 1 for documentation, and may be add beginner guide for cocoon 2.
+1 for compressed mail.. even this is not a high..
----- Original Message -----
From: "Stefano Mazzocchi" <st...@apache.org>
To: "Apache Cocoon" <co...@xml.apache.org>
Cc: "Ted Leung" <tw...@sauria.com>
Sent: Wednesday, December 05, 2001 6:51 AM
Subject: [Vote] Improving Cocoon Site
> We have released Cocoon and this is a great thing.
>
> Now we have to improve the web site a little bit.
>
> 1) location of Cocoon 1.x documentation:
>
> I propose to move
>
> http://xml.apache.org/cocoon1
>
> into
>
> http://xml.apache.org/cocoon/old/
>
> which I believe it's better because the URI is version-free and
> future-compatible: this means this location identified "the previous
> generation of Cocoon, now considered obsolete, but still used by many".
>
> 2) graphic look:
>
> I propose to update the site skin using the new xml.apache.org look
> proposed over at general@xml.apache.org. Ted, what's the status of this?
> where can we find the stylesheets you came up with?
>
> This mainly because the site is simply too heavy: it's ok to show off
> the power of generating raster images out of SVG files, but this is
> clearly too much.
>
> 3) Clean up documentation: there is a lot to do, but here are things
> that bug me:
>
> a) there is no visual difference between sections (i.e. User) and pages
> (Who We Are).
>
> b) there is very little meaning associated with the sections (how in
> hell are readers supposed to know what CTWIG is?)
>
> c) we should have a "community" section.
>
> 4) enhance site functionality:
>
> a) searching: we must come up with a way to search content, even
> forwarding to Google is better than nothing.
>
> b) community information:
>
> - graphs of people subscribed on the mail lists
> - graphs of messages on the mail lists
> - graphs of downloads
>
> I see much more valuable to use the SVG rasterizer for such graphs
> rather than "waste" it to generate the sitebar text. In order to do
> this, though, we need to gather this information.
>
> My idea is to have a perl script (or equivalent) run every week that
> comes up with this information and places it on a specific location
> (this should be done for every xml.apache project).
>
> Unfortunately, the mail list subscription information is reserved by
> root, so we need a high level of access in order to do this (Sam, do you
> have that kind of access level?). The compressed MBOX files can be found
> over at:
>
> /www/xml.apache.org/mail/cocoon-(users|dev)
>
> while the web site logs are in
>
> /x2/logarchive/www/2001
>
> The ideal solution would be to have this processed information already
> XML-ized, but it's probably easier to "append" a line than to add an
> element to an XML file. We could use CSV and do the XML-ization at
> Generation level.
>
> Something like this would be great:
>
> cocoon.list.cocoon-dev:
> cocoon.list.cocoon-users:
>
> year,week,subscribers,messages
> 2001,01,348,983
> 2001,02,358,839
> 2001,03,334,1093
> 2001,03,343,1293
> ...
>
> which could XML-ized as
>
> <list>
> <item year="2001" week="01" subscribers="348" messages="983"/>
> <item year="2001" week="02" subscribers="358" messages="839"/>
> ...
> </list>
>
> or
>
> <list>
> <item>
> <year>2001</year>
> <week>01</week>
> <subscribers>348</subscribers>
> <messages>983</messages>
> </item>
> ...
> </list>
>
> which is more verbose, but could be easier to create using SAX events
> and easier to process with XSLT stylesheets (why attributes are so
> neglected in the XML world? bah, I love them so much)
>
> Then we could easily transform this into SVG with an XSLT stylesheet and
> have the raster graph generated automatically without human
> intervention. Again, note that XML-ization of the CSV file can be done
> by a CSVGenerator which is piece of cake to write (I volunteer to do it
> if this is accepted)
>
> Also,
>
> cocoon.downloads
>
> year,week,downloads
> 2001,01,294
> 2001,02,384
>
> I'm not very good at UNIX administration, so I'd be more than happy if
> somebody else provides the scripts and installs them on apache.org :)
>
> Ok, enough for now.
>
> Please, place your votes or indicate your
> comments/suggestions/criticism.
>
> Thanks.
>
> --
> Stefano Mazzocchi One must still have chaos in oneself to be
> able to give birth to a dancing star.
> <st...@apache.org> Friedrich Nietzsche
> --------------------------------------------------------------------
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [Vote] Improving Cocoon Site
Posted by Stefano Mazzocchi <st...@apache.org>.
John Morrison wrote:
> > b) community information:
> >
> > - graphs of people subscribed on the mail lists
> > - graphs of messages on the mail lists
> > - graphs of downloads
> >
> > I see much more valuable to use the SVG rasterizer for such graphs
> > rather than "waste" it to generate the sitebar text. In order to do
> > this, though, we need to gather this information.
>
> When you've got the data theres a couple of xslt's which generate bar,
> column, line and pie charts in the Batik source. I donated them _ages_ ago
> after playing with Cocoon2 for the first time with svg. They have some
> errors (I was wanting to start a project at work to improve them - but it's
> not happened yet) but I'm sure the Batik team would appreciate them being
> improved. Even if we don't use them, they might give us a start...
Awesome. Where are they? included in batik?
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [Vote] Improving Cocoon Site
Posted by Judson Lester <ju...@irev2.com>.
I'm violating ettiquette a little here (haveonly been reading list for a week
or two, and am not an active Cocoon developer. However, I wanted to mention
that the Cocoon2 site is the only one I've found that consistently crashes
Konqueror. If the improvement involved avoiding this, I'd be thrilled.
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: [Vote] Improving Cocoon Site
Posted by John Morrison <jo...@ntlworld.com>.
> -----Original Message-----
> From: Stefano Mazzocchi [mailto:stefano@apache.org]
> Sent: Wednesday, 05 December 2001 11:51 am
> To: Apache Cocoon
> Cc: Ted Leung
> Subject: [Vote] Improving Cocoon Site
>
>
> We have released Cocoon and this is a great thing.
>
> Now we have to improve the web site a little bit.
>
> 1) location of Cocoon 1.x documentation:
>
> I propose to move
>
> http://xml.apache.org/cocoon1
>
> into
>
> http://xml.apache.org/cocoon/old/
>
> which I believe it's better because the URI is version-free and
> future-compatible: this means this location identified "the previous
> generation of Cocoon, now considered obsolete, but still used by many".
+0
> 2) graphic look:
>
> I propose to update the site skin using the new xml.apache.org look
> proposed over at general@xml.apache.org. Ted, what's the status of this?
> where can we find the stylesheets you came up with?
>
> This mainly because the site is simply too heavy: it's ok to show off
> the power of generating raster images out of SVG files, but this is
> clearly too much.
+1 Definately want this.
> 3) Clean up documentation: there is a lot to do, but here are things
> that bug me:
>
> a) there is no visual difference between sections (i.e. User) and pages
> (Who We Are).
>
> b) there is very little meaning associated with the sections (how in
> hell are readers supposed to know what CTWIG is?)
>
> c) we should have a "community" section.
>
> 4) enhance site functionality:
>
> a) searching: we must come up with a way to search content, even
> forwarding to Google is better than nothing.
>
> b) community information:
>
> - graphs of people subscribed on the mail lists
> - graphs of messages on the mail lists
> - graphs of downloads
>
> I see much more valuable to use the SVG rasterizer for such graphs
> rather than "waste" it to generate the sitebar text. In order to do
> this, though, we need to gather this information.
When you've got the data theres a couple of xslt's which generate bar,
column, line and pie charts in the Batik source. I donated them _ages_ ago
after playing with Cocoon2 for the first time with svg. They have some
errors (I was wanting to start a project at work to improve them - but it's
not happened yet) but I'm sure the Batik team would appreciate them being
improved. Even if we don't use them, they might give us a start...
> My idea is to have a perl script (or equivalent) run every week that
> comes up with this information and places it on a specific location
> (this should be done for every xml.apache project).
>
> Unfortunately, the mail list subscription information is reserved by
> root, so we need a high level of access in order to do this (Sam, do you
> have that kind of access level?). The compressed MBOX files can be found
> over at:
>
> /www/xml.apache.org/mail/cocoon-(users|dev)
>
> while the web site logs are in
>
> /x2/logarchive/www/2001
>
> The ideal solution would be to have this processed information already
> XML-ized, but it's probably easier to "append" a line than to add an
> element to an XML file. We could use CSV and do the XML-ization at
> Generation level.
>
> Something like this would be great:
>
> cocoon.list.cocoon-dev:
> cocoon.list.cocoon-users:
>
> year,week,subscribers,messages
> 2001,01,348,983
> 2001,02,358,839
> 2001,03,334,1093
> 2001,03,343,1293
> ...
>
> which could XML-ized as
>
> <list>
> <item year="2001" week="01" subscribers="348" messages="983"/>
> <item year="2001" week="02" subscribers="358" messages="839"/>
> ...
> </list>
>
> or
>
> <list>
> <item>
> <year>2001</year>
> <week>01</week>
> <subscribers>348</subscribers>
> <messages>983</messages>
> </item>
> ...
> </list>
>
> which is more verbose, but could be easier to create using SAX events
> and easier to process with XSLT stylesheets (why attributes are so
> neglected in the XML world? bah, I love them so much)
>
> Then we could easily transform this into SVG with an XSLT stylesheet and
> have the raster graph generated automatically without human
> intervention. Again, note that XML-ization of the CSV file can be done
> by a CSVGenerator which is piece of cake to write (I volunteer to do it
> if this is accepted)
>
> Also,
>
> cocoon.downloads
>
> year,week,downloads
> 2001,01,294
> 2001,02,384
>
> I'm not very good at UNIX administration, so I'd be more than happy if
> somebody else provides the scripts and installs them on apache.org :)
>
> Ok, enough for now.
>
> Please, place your votes or indicate your
> comments/suggestions/criticism.
>
> Thanks.
>
> --
> Stefano Mazzocchi One must still have chaos in oneself to be
> able to give birth to a dancing star.
> <st...@apache.org> Friedrich Nietzsche
> --------------------------------------------------------------------
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [Vote] Improving Cocoon Site
Posted by Peter Royal <pr...@managingpartners.com>.
On Wednesday 05 December 2001 07:20 pm, Stefano Mazzocchi wrote:
> > > I'm not very good at UNIX administration, so I'd be more than happy if
> > > somebody else provides the scripts and installs them on apache.org :)
>
> Yep. Any Perl/sed guru around? :)
I'm no guru, but I can write perl. If you can get me copies of the raw data
files I'll write the scripts.
-pete
--
peter royal -> proyal@managingpartners.com
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [Vote] Improving Cocoon Site
Posted by giacomo <gi...@apache.org>.
On Thu, 6 Dec 2001, Piroumian, Konstantin wrote:
> > >
> > > Oh, gosh, no need to be a javascript guru for that
> > >
> > > <input type=submit onsubmit="q.value += 'site:xml.apache.org'">
> > >
> > > might do it. (you might need to add id=q to the text field) I can
> > > investigate this more if we are going in this direction.
> >
> > This is why I asked for a guru 'cause it's not going to work with your way
> ;) i
> > already checked that out yesterday.
> >
>
> 'onsubmit' is allowed only for a form tag and not an input. I've tried this
> and it worked:
>
> <!-- Search Google -->
> <form method="GET" action="http://www.google.com/search"
> onsubmit="q.value += ' site:xml.apache.org'">
> <input type=text name=q size=31 maxlength=255 value="">
> <input type=submit name=btnG value="Google Search">
> </form>
> > <!-- Search Google -->
Cool, that's what I was looking for.
Giacomo
>
> Regards,
> Konstantin Piroumian
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [Vote] Improving Cocoon Site
Posted by "Piroumian, Konstantin" <KP...@flagship.ru>.
> >
> > Oh, gosh, no need to be a javascript guru for that
> >
> > <input type=submit onsubmit="q.value += 'site:xml.apache.org'">
> >
> > might do it. (you might need to add id=q to the text field) I can
> > investigate this more if we are going in this direction.
>
> This is why I asked for a guru 'cause it's not going to work with your way
;) i
> already checked that out yesterday.
>
'onsubmit' is allowed only for a form tag and not an input. I've tried this
and it worked:
<!-- Search Google -->
<form method="GET" action="http://www.google.com/search"
onsubmit="q.value += ' site:xml.apache.org'">
<input type=text name=q size=31 maxlength=255 value="">
<input type=submit name=btnG value="Google Search">
</form>
> <!-- Search Google -->
Regards,
Konstantin Piroumian
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [Vote] Improving Cocoon Site
Posted by Giacomo Pati <gi...@apache.org>.
Quoting Stefano Mazzocchi <st...@apache.org>:
> giacomo wrote:
> >
> > On Wed, 5 Dec 2001, Stefano Mazzocchi wrote:
> >
> > > We have released Cocoon and this is a great thing.
> > >
> > > Now we have to improve the web site a little bit.
> > >
> > > 1) location of Cocoon 1.x documentation:
> > >
> > > I propose to move
> > >
> > > http://xml.apache.org/cocoon1
> > >
> > > into
> > >
> > > http://xml.apache.org/cocoon/old/
> >
> > +1 for me.
> >
> > > which I believe it's better because the URI is version-free and
> > > future-compatible: this means this location identified "the previous
> > > generation of Cocoon, now considered obsolete, but still used by
> many".
> > >
> > > 2) graphic look:
> > >
> > > I propose to update the site skin using the new xml.apache.org look
> > > proposed over at general@xml.apache.org. Ted, what's the status of
> this?
> > > where can we find the stylesheets you came up with?
> > >
> > > This mainly because the site is simply too heavy: it's ok to show
> off
> > > the power of generating raster images out of SVG files, but this is
> > > clearly too much.
> >
> > +100
> >
> > > 3) Clean up documentation: there is a lot to do, but here are things
> > > that bug me:
> >
> > We once had a thread on how a TOC should look like.
>
> Ok, let's postpone this on another thread.
>
> > > a) there is no visual difference between sections (i.e. User) and
> pages
> > > (Who We Are).
> > >
> > > b) there is very little meaning associated with the sections (how in
> > > hell are readers supposed to know what CTWIG is?)
> >
> > Yes, I always forgot to bring that up since weeks.
> >
> > > c) we should have a "community" section.
> >
> > What do you think should be in there?
>
> well, the current site TOC is very unbalanced: the community section
> should have everything ranging from "who we are" to "how to help/join"
> from "community info" (the one outlined below) to "sites powered by
> Cocoon".
>
> This should balance the sitebar in the home page between sections and
> pages [which will still need visual differences]
>
> > > 4) enhance site functionality:
> > >
> > > a) searching: we must come up with a way to search content, even
> > > forwarding to Google is better than nothing.
> >
> > Google offers search functionality restricted to a domain. If one can
> > manage to have browsers point to the following URL you'll get the
> search
> > results for keywords QUERY withing xml.apache.org only:
> >
> > http://www.google.com/search?q=QUERY+site:xml.apache.org
> >
> > On the Google site one finds html snippets like below to include
> > in a pages:
> >
> > <!-- Search Google -->
> > <center>
> > <form method="GET" action="http://www.google.com/search">
> > <table bgcolor="#FFFFFF">
> > <tr>
> > <td>
> > <a href="http://www.google.com">
> > <img src="http://www.google.com/logos/Logo_40wht.gif"
> > border="0" alt="Google" align="absmiddle">
> > </a>
> > <input type=text name=q size=31 maxlength=255 value="">
> > <input type=submit name=btnG value="Google Search">
> > </td>
> > </tr>
> > </table>
> > </form>
> > </center>
> > <!-- Search Google -->
> >
> > The trick is that you should add ' site:xml.apache.org' to the input
> > field q to restrict the search on the domain xml.apache.org. Maybe
> some
> > html and javascript guru knows how to do that
>
> Oh, gosh, no need to be a javascript guru for that
>
> <input type=submit onsubmit="q.value += 'site:xml.apache.org'">
>
> might do it. (you might need to add id=q to the text field) I can
> investigate this more if we are going in this direction.
This is why I asked for a guru 'cause it's not going to work with your way ;) i
already checked that out yesterday.
>
> > > b) community information:
> > >
> > > - graphs of people subscribed on the mail lists
> > > - graphs of messages on the mail lists
> > > - graphs of downloads
> >
> > would be cool.
> >
> > > I see much more valuable to use the SVG rasterizer for such graphs
> > > rather than "waste" it to generate the sitebar text. In order to do
> > > this, though, we need to gather this information.
> > >
> > > My idea is to have a perl script (or equivalent) run every week that
> > > comes up with this information and places it on a specific location
> > > (this should be done for every xml.apache project).
> > >
> > > Unfortunately, the mail list subscription information is reserved by
> > > root, so we need a high level of access in order to do this (Sam, do
> you
> > > have that kind of access level?). The compressed MBOX files can be
> found
> > > over at:
> > >
> > > /www/xml.apache.org/mail/cocoon-(users|dev)
> > >
> > > while the web site logs are in
> > >
> > > /x2/logarchive/www/2001
> > >
> > > The ideal solution would be to have this processed information
> already
> > > XML-ized, but it's probably easier to "append" a line than to add an
> > > element to an XML file. We could use CSV and do the XML-ization at
> > > Generation level.
> > >
> > > Something like this would be great:
> > >
> > > cocoon.list.cocoon-dev:
> > > cocoon.list.cocoon-users:
> > >
> > > year,week,subscribers,messages
> > > 2001,01,348,983
> > > 2001,02,358,839
> > > 2001,03,334,1093
> > > 2001,03,343,1293
> > > ...
> > >
> > > which could XML-ized as
> > >
> > > <list>
> > > <item year="2001" week="01" subscribers="348" messages="983"/>
> > > <item year="2001" week="02" subscribers="358" messages="839"/>
> > > ...
> > > </list>
> > >
> > > or
> > >
> > > <list>
> > > <item>
> > > <year>2001</year>
> > > <week>01</week>
> > > <subscribers>348</subscribers>
> > > <messages>983</messages>
> > > </item>
> > > ...
> > > </list>
> > >
> > > which is more verbose, but could be easier to create using SAX
> events
> > > and easier to process with XSLT stylesheets (why attributes are so
> > > neglected in the XML world? bah, I love them so much)
> > >
> > > Then we could easily transform this into SVG with an XSLT stylesheet
> and
> > > have the raster graph generated automatically without human
> > > intervention. Again, note that XML-ization of the CSV file can be
> done
> > > by a CSVGenerator which is piece of cake to write (I volunteer to do
> it
> > > if this is accepted)
> >
> > +1
> >
> > >
> > > Also,
> > >
> > > cocoon.downloads
> > >
> > > year,week,downloads
> > > 2001,01,294
> > > 2001,02,384
> > >
> > > I'm not very good at UNIX administration, so I'd be more than happy
> if
> > > somebody else provides the scripts and installs them on apache.org
> :)
> > >
> > > Ok, enough for now.
> > >
> > > Please, place your votes or indicate your
> > > comments/suggestions/criticism.
> >
> > All this information would give alot more attention on the Cocoon
> > project to everybody (not only newer people).
>
> Yep. Any Perl/sed guru around? :)
I can write the scripts if we come to a conclusion on the format of the output.
Giacomo
>
> --
> Stefano Mazzocchi One must still have chaos in oneself to be
> able to give birth to a dancing star.
> <st...@apache.org> Friedrich Nietzsche
> --------------------------------------------------------------------
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [Vote] Improving Cocoon Site
Posted by Stefano Mazzocchi <st...@apache.org>.
giacomo wrote:
>
> On Wed, 5 Dec 2001, Stefano Mazzocchi wrote:
>
> > We have released Cocoon and this is a great thing.
> >
> > Now we have to improve the web site a little bit.
> >
> > 1) location of Cocoon 1.x documentation:
> >
> > I propose to move
> >
> > http://xml.apache.org/cocoon1
> >
> > into
> >
> > http://xml.apache.org/cocoon/old/
>
> +1 for me.
>
> > which I believe it's better because the URI is version-free and
> > future-compatible: this means this location identified "the previous
> > generation of Cocoon, now considered obsolete, but still used by many".
> >
> > 2) graphic look:
> >
> > I propose to update the site skin using the new xml.apache.org look
> > proposed over at general@xml.apache.org. Ted, what's the status of this?
> > where can we find the stylesheets you came up with?
> >
> > This mainly because the site is simply too heavy: it's ok to show off
> > the power of generating raster images out of SVG files, but this is
> > clearly too much.
>
> +100
>
> > 3) Clean up documentation: there is a lot to do, but here are things
> > that bug me:
>
> We once had a thread on how a TOC should look like.
Ok, let's postpone this on another thread.
> > a) there is no visual difference between sections (i.e. User) and pages
> > (Who We Are).
> >
> > b) there is very little meaning associated with the sections (how in
> > hell are readers supposed to know what CTWIG is?)
>
> Yes, I always forgot to bring that up since weeks.
>
> > c) we should have a "community" section.
>
> What do you think should be in there?
well, the current site TOC is very unbalanced: the community section
should have everything ranging from "who we are" to "how to help/join"
from "community info" (the one outlined below) to "sites powered by
Cocoon".
This should balance the sitebar in the home page between sections and
pages [which will still need visual differences]
> > 4) enhance site functionality:
> >
> > a) searching: we must come up with a way to search content, even
> > forwarding to Google is better than nothing.
>
> Google offers search functionality restricted to a domain. If one can
> manage to have browsers point to the following URL you'll get the search
> results for keywords QUERY withing xml.apache.org only:
>
> http://www.google.com/search?q=QUERY+site:xml.apache.org
>
> On the Google site one finds html snippets like below to include
> in a pages:
>
> <!-- Search Google -->
> <center>
> <form method="GET" action="http://www.google.com/search">
> <table bgcolor="#FFFFFF">
> <tr>
> <td>
> <a href="http://www.google.com">
> <img src="http://www.google.com/logos/Logo_40wht.gif"
> border="0" alt="Google" align="absmiddle">
> </a>
> <input type=text name=q size=31 maxlength=255 value="">
> <input type=submit name=btnG value="Google Search">
> </td>
> </tr>
> </table>
> </form>
> </center>
> <!-- Search Google -->
>
> The trick is that you should add ' site:xml.apache.org' to the input
> field q to restrict the search on the domain xml.apache.org. Maybe some
> html and javascript guru knows how to do that
Oh, gosh, no need to be a javascript guru for that
<input type=submit onsubmit="q.value += 'site:xml.apache.org'">
might do it. (you might need to add id=q to the text field) I can
investigate this more if we are going in this direction.
> > b) community information:
> >
> > - graphs of people subscribed on the mail lists
> > - graphs of messages on the mail lists
> > - graphs of downloads
>
> would be cool.
>
> > I see much more valuable to use the SVG rasterizer for such graphs
> > rather than "waste" it to generate the sitebar text. In order to do
> > this, though, we need to gather this information.
> >
> > My idea is to have a perl script (or equivalent) run every week that
> > comes up with this information and places it on a specific location
> > (this should be done for every xml.apache project).
> >
> > Unfortunately, the mail list subscription information is reserved by
> > root, so we need a high level of access in order to do this (Sam, do you
> > have that kind of access level?). The compressed MBOX files can be found
> > over at:
> >
> > /www/xml.apache.org/mail/cocoon-(users|dev)
> >
> > while the web site logs are in
> >
> > /x2/logarchive/www/2001
> >
> > The ideal solution would be to have this processed information already
> > XML-ized, but it's probably easier to "append" a line than to add an
> > element to an XML file. We could use CSV and do the XML-ization at
> > Generation level.
> >
> > Something like this would be great:
> >
> > cocoon.list.cocoon-dev:
> > cocoon.list.cocoon-users:
> >
> > year,week,subscribers,messages
> > 2001,01,348,983
> > 2001,02,358,839
> > 2001,03,334,1093
> > 2001,03,343,1293
> > ...
> >
> > which could XML-ized as
> >
> > <list>
> > <item year="2001" week="01" subscribers="348" messages="983"/>
> > <item year="2001" week="02" subscribers="358" messages="839"/>
> > ...
> > </list>
> >
> > or
> >
> > <list>
> > <item>
> > <year>2001</year>
> > <week>01</week>
> > <subscribers>348</subscribers>
> > <messages>983</messages>
> > </item>
> > ...
> > </list>
> >
> > which is more verbose, but could be easier to create using SAX events
> > and easier to process with XSLT stylesheets (why attributes are so
> > neglected in the XML world? bah, I love them so much)
> >
> > Then we could easily transform this into SVG with an XSLT stylesheet and
> > have the raster graph generated automatically without human
> > intervention. Again, note that XML-ization of the CSV file can be done
> > by a CSVGenerator which is piece of cake to write (I volunteer to do it
> > if this is accepted)
>
> +1
>
> >
> > Also,
> >
> > cocoon.downloads
> >
> > year,week,downloads
> > 2001,01,294
> > 2001,02,384
> >
> > I'm not very good at UNIX administration, so I'd be more than happy if
> > somebody else provides the scripts and installs them on apache.org :)
> >
> > Ok, enough for now.
> >
> > Please, place your votes or indicate your
> > comments/suggestions/criticism.
>
> All this information would give alot more attention on the Cocoon
> project to everybody (not only newer people).
Yep. Any Perl/sed guru around? :)
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [Vote] Improving Cocoon Site
Posted by Stefano Mazzocchi <st...@apache.org>.
Jeremy Aston wrote:
>
> In conversation...
>
> ... snippity snip...
>
> > b) there is very little meaning associated with the sections (how in
> > hell are readers supposed to know what CTWIG is?)
>
> Yes, I always forgot to bring that up since weeks.
>
> ...end snippity snip...
>
> Funny you say that 'cos I've been thinking for a while that it's probably
> worth going to a plain vanilla "Idiot's Guide" title.
Big +1
> In fact, perhaps the stuff in there should be incorporated into the
> main doc stuff.
Even better!
> I am about
> to present some extra stuff on actions and db access so perhaps this should
> be revisitied then?
You'll make me happy if you do :)
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: [Vote] Improving Cocoon Site
Posted by Jeremy Aston <je...@yahoo.co.uk>.
In conversation...
... snippity snip...
> b) there is very little meaning associated with the sections (how in
> hell are readers supposed to know what CTWIG is?)
Yes, I always forgot to bring that up since weeks.
...end snippity snip...
Funny you say that 'cos I've been thinking for a while that it's probably
worth going to a plain vanilla "Idiot's Guide" title. In fact, perhaps the
stuff in there should be incorporated into the main doc stuff. I am about
to present some extra stuff on actions and db access so perhaps this should
be revisitied then?
Jez
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [Vote] Improving Cocoon Site
Posted by giacomo <gi...@apache.org>.
On Wed, 5 Dec 2001, Stefano Mazzocchi wrote:
> We have released Cocoon and this is a great thing.
>
> Now we have to improve the web site a little bit.
>
> 1) location of Cocoon 1.x documentation:
>
> I propose to move
>
> http://xml.apache.org/cocoon1
>
> into
>
> http://xml.apache.org/cocoon/old/
+1 for me.
> which I believe it's better because the URI is version-free and
> future-compatible: this means this location identified "the previous
> generation of Cocoon, now considered obsolete, but still used by many".
>
> 2) graphic look:
>
> I propose to update the site skin using the new xml.apache.org look
> proposed over at general@xml.apache.org. Ted, what's the status of this?
> where can we find the stylesheets you came up with?
>
> This mainly because the site is simply too heavy: it's ok to show off
> the power of generating raster images out of SVG files, but this is
> clearly too much.
+100
> 3) Clean up documentation: there is a lot to do, but here are things
> that bug me:
We once had a thread on how a TOC should look like.
> a) there is no visual difference between sections (i.e. User) and pages
> (Who We Are).
>
> b) there is very little meaning associated with the sections (how in
> hell are readers supposed to know what CTWIG is?)
Yes, I always forgot to bring that up since weeks.
> c) we should have a "community" section.
What do you think should be in there?
> 4) enhance site functionality:
>
> a) searching: we must come up with a way to search content, even
> forwarding to Google is better than nothing.
Google offers search functionality restricted to a domain. If one can
manage to have browsers point to the following URL you'll get the search
results for keywords QUERY withing xml.apache.org only:
http://www.google.com/search?q=QUERY+site:xml.apache.org
On the Google site one finds html snippets like below to include
in a pages:
<!-- Search Google -->
<center>
<form method="GET" action="http://www.google.com/search">
<table bgcolor="#FFFFFF">
<tr>
<td>
<a href="http://www.google.com">
<img src="http://www.google.com/logos/Logo_40wht.gif"
border="0" alt="Google" align="absmiddle">
</a>
<input type=text name=q size=31 maxlength=255 value="">
<input type=submit name=btnG value="Google Search">
</td>
</tr>
</table>
</form>
</center>
<!-- Search Google -->
The trick is that you should add ' site:xml.apache.org' to the input
field q to restrict the search on the domain xml.apache.org. Maybe some
html and javascript guru knows how to do that
> b) community information:
>
> - graphs of people subscribed on the mail lists
> - graphs of messages on the mail lists
> - graphs of downloads
would be cool.
> I see much more valuable to use the SVG rasterizer for such graphs
> rather than "waste" it to generate the sitebar text. In order to do
> this, though, we need to gather this information.
>
> My idea is to have a perl script (or equivalent) run every week that
> comes up with this information and places it on a specific location
> (this should be done for every xml.apache project).
>
> Unfortunately, the mail list subscription information is reserved by
> root, so we need a high level of access in order to do this (Sam, do you
> have that kind of access level?). The compressed MBOX files can be found
> over at:
>
> /www/xml.apache.org/mail/cocoon-(users|dev)
>
> while the web site logs are in
>
> /x2/logarchive/www/2001
>
> The ideal solution would be to have this processed information already
> XML-ized, but it's probably easier to "append" a line than to add an
> element to an XML file. We could use CSV and do the XML-ization at
> Generation level.
>
> Something like this would be great:
>
> cocoon.list.cocoon-dev:
> cocoon.list.cocoon-users:
>
> year,week,subscribers,messages
> 2001,01,348,983
> 2001,02,358,839
> 2001,03,334,1093
> 2001,03,343,1293
> ...
>
> which could XML-ized as
>
> <list>
> <item year="2001" week="01" subscribers="348" messages="983"/>
> <item year="2001" week="02" subscribers="358" messages="839"/>
> ...
> </list>
>
> or
>
> <list>
> <item>
> <year>2001</year>
> <week>01</week>
> <subscribers>348</subscribers>
> <messages>983</messages>
> </item>
> ...
> </list>
>
> which is more verbose, but could be easier to create using SAX events
> and easier to process with XSLT stylesheets (why attributes are so
> neglected in the XML world? bah, I love them so much)
>
> Then we could easily transform this into SVG with an XSLT stylesheet and
> have the raster graph generated automatically without human
> intervention. Again, note that XML-ization of the CSV file can be done
> by a CSVGenerator which is piece of cake to write (I volunteer to do it
> if this is accepted)
+1
>
> Also,
>
> cocoon.downloads
>
> year,week,downloads
> 2001,01,294
> 2001,02,384
>
> I'm not very good at UNIX administration, so I'd be more than happy if
> somebody else provides the scripts and installs them on apache.org :)
>
> Ok, enough for now.
>
> Please, place your votes or indicate your
> comments/suggestions/criticism.
All this information would give alot more attention on the Cocoon
project to everybody (not only newer people).
Giacomo
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org