RE: [Arianne-devel] Wiki

[Miguel A. B. L. <mig...@ho...>]

>Thanks for the quick reply.
>I tried to use the link but it didn't work. It
>downloaded the file but then wasn't openable by
>WinZip. Have you tried this? Perhaps it's because I'm
>not the administrator and haven't loged in as such?

No, it is another nice feature of our Wiki.
Give it a few tries until it load correctly... as you should know our Wiki 
is a bit "special". :)
BTW there is no administrator at all.

>Keeping the wiki online is great for the original and
>the edits but there are times when people need an
>offline version for review. People with slow internet
>connections will find always having to be online just
>to read the documentation frustrating. I my self do my
>development on my laptop often from the road. I'll
>need an offline version for review. My thoughts were
>to just include a snapshot of the wiki with each
>release.

We are going to point people either to the Zip file or the online Wiki.
Duplicated information means duplicated problems.

>This way we can remove some of the
>documentation from the readme and include it all in
>the wiki. After my last updates to the reame I noticed
>that documention on the wiki had been copied from what
>was previously in the readme. Now it's out of date. We
>have to limit documentation to one source.

CVS README is the latest.
People is .... ummm.... how to say....
People dislike to read. Readme MUST be as clear and obvious as possible, in 
fact the compiled version of Arianne requiere that you configure the MySQL 
stuff and just that... the rest is handled automatically. It should be 
improved anyway.

>Please don't fill Bugs and Authors. Bugs is already on
>sourcforge. Authors should be in the javadocs. When
>ever you have documentation in two places one will be
>out of date. At the very least this information should
>be in the wiki (and already is). Why repeat it?

OK.

>The .txt issue. Arianne is a multiplatform
>application. I myself want to run a server on FreeBSD.
>However, why alienate windows users? Adding the .txt
>extension won't break anything for the other OSs but
>windows has no idea what the file type is without an
>extension. I know how to open the file but not
>everyone will. Besides with out the extension I can't
>just double click to open the file. A lack of an
>extension is just one more piece of confusion to add
>to things. Since this doesn't break anything for
>others I don't see what the problem is.

The point is that Marauroa ( we are talking about Marauroa, isn't it? ) is 
the server side. If you don't know how to open a text file you should 
perhaps not be playing with a MySQL database, a Jython installation from a 
java class file or running a service on your computer, don't you?

I prefer README to keep in conformance with what is expected to find in a 
Linux installation, that is because some files are ( still ) empty, just to 
follow the automake --gnu way :)

I will change extension anyway.

_________________________________________________________________
MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. 
http://join.msn.com/?page=features/virus