Re: recommendations.html

cL wrote:
> you did mention something similar when you decided to fork the project 
> but the topic had been brought up on dev@projects prior:
> 
> http://projects.netbeans.org/servlets/ReadMsg?msgId=429557&listName=dev
> 
 > there are lots of places to get feedback and ideas from -we're always
 > happy for contributions and will certainly give credit when it is due.
 >

Good to see that it was on the radar (links/credits on NB4DEV pages were 
added, thanks for the catch!), but the UI documents were silent about 
the topic for _five months_ if I count well - that does not seem as an 
attended issue, actually.

As I read David's question you linked above, it seems to be centered on 
giving the user a convenient place to go for project settings (the exact 
issue that surfaced in usability study) - so my issue talking about 
inextensible UI was actually a second flaw in the Project Customizer's 
design - and it was ignored again for another four months.

By the way:
 > you did mention something similar when you decided to fork the project

I would prefer not to fork - if the design worked for daily encountered 
situations well. It does not, so I hope NB4DEV will eliminate at least 
some of the issues and I will be once more able to use it for 
_productive_ development instead of IntelliJ IDEA.

There was a number of options: comment the issues, use the analysis, 
work on the issues or show them irrelevant. None of that happened - and 
surprise -- the usability study seems to point at some of them, or ones 
quite similar (cluttered project view, no central place for settings).

Indeed, ignoring perceived problems or postponing their solution is a 
great way to create an usable product.

-Svata