NetBeans Podcast Episode #21

Guest Author

NetBeans Podcast episode #21 is out there in the world wild web:

NetBeans Podcast Episode #21 (28 min 27 sec, size: 20.4 MB)


Podcast feedback to: roman dot strobl at sun dot com.

To subscribe via iTunes or similar players, visit http://feeds.feedburner.com/netbeanspod.

Join the discussion

Comments ( 4 )
  • Ove Nordstrom Wednesday, January 3, 2007
    In this podcast you talked about that Netbeans now also support MS vista.
    What about Mac OS X and linux and Netbeans support?
    I thought I should buy me a new (developer)laptop and I would prefer not to run MS windowsXP or Vista.
    Is now everything in Netbeans working with Mac OS X or Linux?
  • Roumen Friday, January 5, 2007
    NetBeans obviously works pretty well on MacOSX and Linux as well. We pointed out Vista because it's a new operating system. NetBeans works well on any operating system where you can install the JDK. The only problem is with Mobility Pack, because the WTK emulators are not available on all platforms.
  • Ove Nordstrom Saturday, January 6, 2007
    Do you know the plan for what WTK emulators will supports in the future?
    Anyway I will go for Mac OS X or linux (Ubuntu) and also using VMware player (for SW that not working)for my new laptop.
    I have run Ubuntu on a old laptop (for testing) for a while and it is really great. The performance is huge if you compare with my 1,5 year old laptop from DELL (running MS WinXP) and I have also 2Gb ram memory.
    I think it would be great if Netbeans in the future support linux and Mac OS X better, because many people are really angry about that (not so much Netbeans anylonger perhaps), I have one example:
  • Daniel Sheppard Saturday, January 6, 2007
    A request for advice. I am a long-time NB user from 3.6 days and took part in NetCAT 4. I regularly listen to and enjoy your webcast. The wiki page for the new Java syntax highlighting asks for feedback, such as what other things should/could be highlighted, but doesn't say where feedback should be. Do you know? I have some ideas. What do you think?

    I have a couple of ideas. Personally I feel that types should be highlighted in their own colour, thus distinguishing them from local variables. It would mean that I can see all class that are being used at a glance. The highlighting of

    List<String> data = new ArrayList<String>();

    has always seemed strange to me. Yes, ArrayList is a constructor, which is some kind of method, but the important thing is that is is a type. The = sign, new keyword and () are sufficent to indicate that it is a constructor.

    Also with


    showing that MyProperties is a type makes it clear that have is a class that is being used.

    A second thing is that in javadoc highlighting, arguments could be highlighted and validated. So,

    @param name of argument

    name could be highlighted in the method argument colour. Once @param was typed, code completion could be used to get name for the list of the method arguments below. If name was not in the method argument list below, then it could be given a red squiggle indicating an error. Clicking on the @param could highlight those parameters that are not yet documented. The same could be done for exceptions.

    Code completion could also be used to ensure that class and method cross-references are inserted correctly. I'm never entirely sure if I have cross-reference syntax correct - I'm sure I'm not the only one.

    A further JavaDoc help would be if there was a keyboard/menu shortcut that set-up @param lines for all arguments, @throws for all exceptions and @return and stepped you through each entry in much the same way as happens with code templates.

    A final personal annoyance if the header comments given to most files. Duplicated changes need to be done to a fair number of files to change this (in common with other IDEs it has to be said). However, KDevelop takes a different approach. When creating a project you say which licence you want or enter your own. This is then used as the header comment for each file - no need to change class template, interface template, main class template, junit template etc. This also means that the same IDE can be used for projects under different licence, e.g. one project under GPL and another project under Apache.

    Oh, and one other thing. I have a free-form web app project. I created a separate project that supplied functionality to be used by this web app through a jar. However, it doesn't seem that free-form web app projects could associate with netbeans projects.

Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.