[Koha-devel] web installer committed

[Henri-Damien LAURENT]

Web installer is committed in installer directory.
I would have rather use install dir. But I couldnot (I don't know why).
The commit concerns :

+ Adding a script to list ALL modules used in Koha Scripts and provide user 
with a list of the scripts using these modules.
+ kohastructure.sql is the structure of my database for koha3.0 (could be used 
as a ground before update.)
+ list of language as ISO-639-2
+ Adding a new InstallAuth.pm which should only be used for install. Since I 
could not suppose that there was a database, this authentication could not 
match with a borrower. It still relies on cookies but Only super superlibrarian 
(the one described in koha.xml) can acheive this.
+ Adding Web Installer 3 steps :
step 1: checking database exists and access (table creation insert....)
Step 2: checking database structure and updating database if need be.
Step 3: importing datasets which are supposed to be in 
misc/sql-datas/<language>/<level>
where <language> is international abbreviation of a language.
and <level> is to qualify the criticity of the import :
required : necessary for Koha to work.
recommended : very helpful.
additionals : would be to "ease the pain" in configuring Koha.
each <level> directory contains a list of sql files which have meaningful 
names. and the same list txt files which contains a little description in the 
<language> to explain what sql file is aimed at.
This can be VERY helpfull if we put there some normalised data such as position 
authorised values, code5 authorised value, frameworks, language authorised 
value list, CDU or CDD description, depending on which one is "free"... 
We still can go further :
- We could allow people to get only subsets of international normalised set of 
datas.
- this installer doesnot help people in creating their zebra configuration 
files. But this would be a BIG tricky part.


There is on refresh on a selection list change. MJ Ray told me not to do
it but I can't figure out how to do otherwise.
frameworks could be XML files containing descriptions for zebra,
output(s) format, input wizard or type, tabs, default values +
eventually some correspondances.
There is still some "pretty"fication work to use css classes.
But this is the spirit.

-- 
Henri-Damien LAURENT