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:

   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).
   Another thing (better) would be a servlet to get the parameters and
write the files instead of making people actually go through them to
configure the application. Again, my knowledge of java is somewhat
limited, but, hey, it will help me learn the servlet api anyway, and 
with enough time and patience I think I can do it too.
   The other problem is actualy developing for and customizing it to suit
each other's needs. For example, it may be my fault, but the only way I
found to customize the navigation bars would be to actually rewrite the
build () functions in 
   
   jetspeed/turbine/navigation/Jetspeed*Navigation.java

... Which seems a little strange. 

   So, my questions are: Can I help? What can I do to help? Where do I
start?

   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