Reinier Zwitserloot wrote: > /Applications/Netbeans/Netbeans.app is strange in that a properly > deployed app would be /Applications/Netbeans.app. > First question: is this explicitly coded by Apple's guidelines? Second point:
[Mistral:/Applications] fritz% find . -depth 1 -type d | grep -v app find: ./Adobe Bridge CS3 ./AppleScript ./DivX ./Flip4Mac ./iWork '09 ./JavaFX Production Suite ./MacPython 2.5 ./Mark:Space ./Missing Sync for Windows Mobile ./Mobile Partner ./NetBeans ./Pantone ./PostgreSQL 8.3 ./Snapz Pro X As you can see there's plenty of applications installing in a sub-directory of /Applications... iWork included! That probably answers to my first question :-) > The way the eclipse distro is set up, you're essentially stuck with > the same schema (/Applications/eclipse/Eclipse.app and not / > Applications/Eclipse.app) but at least eclipse is deployed properly, > mostly (as a zip file - the optimum distro for mac apps is a dmg file, > but I can live with this. The mpkg that netbeans offers is much more > annoying and makes me wonder what the heck that installer is doing). > NetBeans also installs Tomcat and Glassfish. Frankly all this seems pretty nitpicking to me, considering that Adobe's graphical products all install themselves with wizards, not with drag&drop, and they can be seen as similar complexity production tools. Given that, I think that NetBeans should do the possible to revert its installation to a simple drag&drop on MAc OS X (it's one of the first things I've done for my NB Platform - based products), but this is not certainly a high priority. > How do I make one project dependent on another? What the heck is this > 'primary project' thing? How do I set a given class as the main class > to run? Where do I configure parameters and the like for this stuff? > Where do I configure things? Eclipse's configuration screen has a > bazillion options, but at least everything is there, and it has > fantastic UX - there's a very useful search box with instant response. > Netbeans preferences dialog has just about nothing. > Well, everything is subjective, but it sounds as you didn't spend more than ten seconds to try almost half of the above stuff... you can make dependent projects, set the main class and configure parameters in a few mouse clicks. On the contrary, not only myself, but I constantly see those customers of mine who still use Eclipse waste minutes to find out where to configure stuff. The last one took ten minutes to figure out where to place stuff in a web application and the bazillion options is the classic "no no" of UI usability. Since we were talking about Apple, who's the master of usability, have a look at the UIs of complex tools such as Aperture and see how different it is from the Eclipse approach. The time-consuming problem and other random UI blocks of 6.7, while fortunately they don't happen always and to everybody, are a real problem and they are fixing that. It's indeed a shame these troubles take so long to be fixed, but nobody is perfect :-) -- Fabrizio Giudici - Java Architect, Project Manager Tidalwave s.a.s. - "We make Java work. Everywhere." weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/blog [email protected] - mobile: +39 348.150.6941 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
