I've been using NEdit (a simple GNU text editor for X) and Ant scripts since the dawn of time and I haven't had any of those issues. Just thought I'd share. Carry on... :)
Alexey 2001 Honda CBR600F4i (CCS) 1992 Kawasaki EX500 http://azinger.blogspot.com http://bsheet.sourceforge.net http://wcollage.sourceforge.net ________________________________ From: Michael Kimsal <[email protected]> To: [email protected] Sent: Wednesday, August 12, 2009 1:42:47 PM Subject: [The Java Posse] Re: jdk versions (netbeans) I have the complete opposite experiences with Eclipse. I somehow manage to hit some keystroke or press some button that makes panels (which I don't know the names of) disappear, with no indication of how to get them back. I guess if I was totally focused on the screen 100% of the time I could be watching the snazzy animations and get an idea of where something 'disappeared' to, but I don't. I'm generally typing or moving my mouse and causing these things to happen without noticing what I've done until it's too late. I'm sure if you already *know* Eclipse, it's great. Much like Java - once you're used to the boilerplate, it all makes sense, and you perhaps have an idea of what to visually skip over. When you don't know it, it's overwhelming. On Wed, Aug 12, 2009 at 1:33 PM, Reinier Zwitserloot <[email protected]> wrote: >>/Applications/Netbeans/Netbeans.app is strange in that a properly >>deployed app would be /Applications/Netbeans.app. > >>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). > > >>I had the opposite experience: I have a lot of trouble getting into >>netbeans, whereas I managed to get my bearings in eclipse almost >>immediately, if memory serves correctly. Create project, create class, >>go type. The rest of the many many features you pick up as you go, >>except for the debugger, which, at least for the basics (set >>breakpoints. pause threads on demand, see live stack traces, as well >>as values of the variables on the stack) is entirely natural. The >>netbeans debugger is similar in UX, but its the basics that annoy me >>on netbeans: > >>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. > >>On Aug 12, 1:53 pm, Michael Kimsal <[email protected]> wrote: >>> On Tue, Aug 11, 2009 at 6:49 PM, Reinier Zwitserloot >>> <[email protected]>wrote: >>> >>> >>> >>> > Jess, that doesn't really make sense to me. >>> >>> > On to netbeans. On macs, it's.... an unusable horrid mess of crap. As >>> > nice as netbeans is, the basic usability problems on macs are thrown >>> > in your face even before you run it - it is deployed as an installer >>> > script which no mac app is ever distributed as - only drivers and >>> > crazy apps like Parallels. This installer will also put netbeans in a >>> > strange place, and if you manually move it, stuff breaks. Yich. >>> >>> "Strange place"? /Applications/Netbeans/ ? That's where it's installed for >>> me since the 6.x days - I can't recall before then, but that's been a while. >>> >>> > You then start up netbeans, and it asks you to register it. Okay, but, >>> > it never remembers. You can pick 'never', or you can actually >>> > register, it doesn't matter, you'll have to click 'never register' >>> > every single time you turn netbeans on. >>> >>> Never had this problem. Sounds like a local configuration issue someplace. >>> >>> >>> >>> > In fact, other than a number of obscure but worrying problems, what, >>> > exactly, is everybody's problem with eclipse? >>> >>> It's a huge beast to even begin to decipher for beginners. That's my >>> problem. Sometimes I just want a drink, I don't want to go swimming. >>> >>> I find it to be slow, but NB isn't massively faster. Java apps tend to be >>> slow, and that slowness is magnified on Macs. It's my direct experience, >>> and that of watching others using both Eclipse and other Java apps on their >>> Macs. Strangely, they don't seem to consider the apps 'slow', but that's a >>> matter of perspective. Apparently I'm just an impatient person. >>> >>> -- >>> Michael Kimsalhttp://jsmag.com- for javascript >>> developershttp://groovymag.com- for groovy developers >>> 919.827.4724 > > -- Michael Kimsal http://jsmag.com - for javascript developers http://groovymag.com - for groovy developers 919.827.4724 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
