On Tue, Apr 04, 2000 at 01:07:45PM -0700, Kevin A. Burton wrote:

> David Leal wrote:
> > 
> > Hi,
> > 
> > I finally managed to install jetspeed (though not fully; cocoon and
> > user administration aren't working yet). I don't know what will happen,
> > but it seems that jetspeed will be an important part of my work in the
> > near future. However, I find the installation part unnecessarily
> > difficult, due to the fact that there isn't enough documentation and
> > some confusion in the configuration files. So, I have a few doubts:
> 
> 1.0 or 1.1?  If you don't like something then post a .diff.  

   No, I'm talking 1.1. I wanted to know if something is already 
happening because, if I'll do it, I don't want to be duplicating work.
 
> >    Is there any project to improve the documentation? It seems to me
> > that one of the things that could be done shortly is a kind of
> > "templating" of the config files. Some
> > 
> >    file://<your_docroot_path>/content/etc
> > 
> > strategically placed would help a little, so people would know what
> > to change more easily. If no one is doing that, I can, with some help,
> > do it. A good thing would be providing examples and commenting on the
> > effects each documentation parameter would have (ex: increasing
> > this_par to 20 will cause things to be faster but more memory will be
> > used).
>
> Example?

   Well, what I mean is this: Say, for example the option

   contentfeeds.maxthreads

   Suppose I don't understand anything of this (which I don't :), and I 
look at this option. What does it do? How will it influence my 
application if I change its value? I think a nice explanation like

   "This option does so and so [already explained]. Increasing its
value will cause the cache to be populated faster--since more
connections will be established--but more bandwidth will be used." [I 
think this is right, right?]

   would improve my understanding of the app without making me have to
know its internal workings (we are trying to maximize usability here).
 
> Also if you notice any problems with documentation just send a diff.  

   A little disclaimer here. I read your post about what the
documentation lacks, and I think it was very well put. I'm a newbie to 
much of this stuff, and so I feel a little like I'm drifting in limbo. 
I read some documentation (turbine related stuff) and browsed a little 
through the source code but I'm somewhat uneasy to propose ideas on 
something which I'm not very sure about how it works. I'll try to learn
and I'll try to post some diffs to the config files first. Then I'll 
see what I can do next.
   One other thing: I noticed that the content that gets sent to the
browser is just plain html. Wouldn't it be better if we used xmHtml
instead? I understand this means changing ECS, but wouldn't it be
advisable to do it sooner than later?

   Cheers,

   David


--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Archives and Other:  <http://java.apache.org/main/mail.html>
Problems?:           [EMAIL PROTECTED]

Reply via email to