[Ginp-developers] Status report and outstanding issues

[Brian B. <br...@Pi...>]

Doug, I hope you can spare a few minutes to deal with this list of loose 
ends for me...

1. I have updated the "manual". I've made a few cosmetic changes and 
fixed some typos, but mainly I've re-organised and expanded the initial 
"Getting Started" section. In particular, I've described how to work 
around a failure in the configuration wizard. I've worded it so when we 
get round to fixing the problem, the manual will still make some sort of 
sense.

I intend to do some work on the next section "How to build the ginp into 
your site" fairly soon, but I've got to try doing it myself first.


2. If you are happy with this latest change, would you mind updating the 
public site on SourceForge? I noticed my last significant change - the 
"new" GetFolderInfo.java module hasn't turned up on the CVS change log yet.

Without this module, the non-basic demo styles will continue to crash as 
soon as they are selected.


3. Incidentally, the latest download shown on 
http://sourceforge.net/project/showfiles.php?group_id=105663
is labelled v0.23 and dated nearly TWO YEARS AGO! Is this correct?


4. While working on manual.xml, I couldn't check it properly on my own 
web site. This is because the demo index page links to 
/src/main/webapp/manual.jsp, but the jsp tries to present a non-existent 
file called /docs/manual.html to the browser. Anyway, manual.xml is not 
even shipped in ginp.war at the moment.

This is obviously a hangover from the pre-maven days, but I'm not sure 
how best to tidy it up. Do you have any suggestions? It would make 
future updates to the manual easier to test if it were deployed properly.


5. I keep getting pangs of conscience when working on the source. The 
code looks very messy when viewed with my netbeans ide. It is full of 
tab characters, but they are presumably rendered differently to your 
development system.

Several years ago, I had a change rejected from a mature open source 
project because of my embedded tab characters. I was sternly told the 
project had coding style rules that must be adhered to. Since that time, 
I've worked on several open source projects that have different style 
rules, BUT ALL BAN TAB CHARACTERS. These days I simply leave both 
netbeans and eclipse to their default settings - to replace local tabs 
with 4 space characters and indent continuations with 8 spaces. This 
standard seems to be widely implemented.

So, I'm basically apologising for messing up the appearance of your code 
whenever I touch a line... when I save the file each line that I've 
modified has its tabs replaced with spaces. I hope this isn't causing 
too much confusion and irritation.