I don't think there's too much documentation, it's just not organized as
best it could be. Most software like this would have a Reference
manual, a Users Guide, a Tutorial, and an install document. And then a
searchable knowledge base for support. Some of the stuff in the docs
dir would fit into those different documents....but then someone would
have to organize it and add to it.
-Nissim
Travis Low wrote:
>
> Actually, I think there's TOO MUCH documentation. It's a bit
> overwhelming. It turns out that configuration is very simple, but
> discovering that fact was not easy.
>
> I think a post-install-configure script would be better than more
> documentation. It would certainly reduce mailing list traffic. In
> each configuration file, you could turn the comments into questions,
> and add the appropriate checking. For example:
>
> ##
> ## You should set the foobar.path to a foobar directory
> foobar.path=/home/user/foobar
>
> Would become (please forgive my rusty perl):
>
> while()
> { print "Please specify the path to your foobar directory: ";
> $foobar = <STDIN>;
> chomp( $foobar );
> if( ! -d $foobar )
> { print "Sorry, $foobar doesn't exist!\n";
> }
> else
> { print "Using '$foobar' as your foobar directory.";
> last;
> }
> }
>
> I've been toying with the idea of doing this for JServ, but I'm really
> short on time and I'm not confident that I know JServ well enough to
> produce an accurate script. I'm new to Turbine so I'm certainly not
> ready to do one for Turbine.
>
> -- Travis Low
> [EMAIL PROTECTED]
> 1-301-592-6305 (direct)
>
> Brevsville Administrator wrote:
> >
> > Excuse me if I am talking out of turn, but I am a fan of Apache and a fan
> > of JServ, but myself and my colleagues found Turbine a bitch to get
> > running.
> >
> > This is not a criticism of Turbine, but rather the fact that there are
> > differing marketplaces for such products and one is not being addressed.
> > As an example, I was recently asked which servlet runner to use by a
> > moderately experienced part time programmer. As much as I like JServ I
> > just couldn't recommend it as it is much more complex to configure that
> > JavaWebserver.
> >
> > Now don't assume for one second I am a fan of JWS (we used it for 2
> > years), JServ and it simply do not compare.. for so many reasons. My
> > point is that as good as all the Apache products are, there is a real need
> > for ABC instructions for getting a very basic install running.
> >
> > Before everyone flames me, I know many of you will say "how simple can the
> > instructions get!!" a quick read of the java.apache archives show a large
> > group of users who may be forever lost to apache since they cannot follow
> > the current docs. That is not a criticism of the current documenters, but
> > i do think there is a void not being filled for inexperienced programmers.
> >
> > Anyway , I just wanted to express my views, for what they are worth, and
> > presently I am trying to find some time to put some totally dumb setup
> > instructions for JServ on Win32 and then Linux. Then you can flame me for
> > the poor job I maybe do.
> >
> > Anyway .. that's my 2c.. q flames..
> >
> > Chris
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
