Re: [Ginp-developers] Status report and outstanding issues

[Doug C. <do...@cu...>]

Brian Burch wrote:
> 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.
>   
Will try to update the public site for you now.  Check the last
published date on each page.
> 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?
>   
Yes.  As mentioned earlier a release is long overdue but the code has
not got to release stage for it to happen.
>
> 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 an error there should be no JSP pages in the website they are
all HTML now.  Do a
> mvn site
this generates the public website in your target/site folder.  You can
check it there.
> 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.
>   
Not sue how to do this either.  Link to the public website would be easiest.
>
> 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.
>   
Code formatters cause problems with managing changes in source code.  I
can build jalopy and checkstyle into the Maven build to automatically
format and report on code format errors if you like.  This is a question
of taste but I think the this is the best method of coping with code
formatting.   Do you want this?  The alternative is setting up your
IDE.  Either way it is your call on how to do this but I can offer you
what I think is a cool Maven solution.
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Ginp-developers mailing list
> Gin...@li...
> https://lists.sourceforge.net/lists/listinfo/ginp-developers
>