Geertjan's Blog

  • August 11, 2010

NetBeans Platform 6.9 Developer's Guide is Available

Geertjan Wielenga
Product Manager
It is alive! I downloaded the eBook, which is now available, and the actual book itself will now also be shipped to you:

Go here to buy yours and attain a step-by-step guide to creating a new modular Swing application on the NetBeans Platform.

Join the discussion

Comments ( 11 )
  • Chris Wednesday, August 11, 2010

    Is this available in the U.S. yet? My packt account is not showing it available for download.

  • RS Wednesday, August 11, 2010

    The site's URL and text both reference 6.8, but the cover is for 6.9. They should probably fix that...

  • Steven Wednesday, August 11, 2010


    But... my order still shows as per-order. NOOO!!!

    Guess I'll have to contact packt. :)

  • Kenneth Wednesday, August 11, 2010

    Thanks for the information but unfortunately Packt mess up my pre-order and I'm still fighting for my copy.

  • Geertjan Wielenga Wednesday, August 11, 2010

    OK, will pass these messages on to Packt. Just please be patient, will be fixed soon.

  • Henry Kleynhans Thursday, August 12, 2010

    My pre-order just went through. Busy downloading the e-book.

    Congrats to all involved in getting this out the door!

  • Geertjan Wielenga Thursday, August 12, 2010

    Hi all. From Packt I hear that all the eBooks should now be available for download. Thanks for your patience.

  • Robert S. Thursday, August 12, 2010

    Did you exchange your Ubuntu notebook for a Macbook?

  • Geertjan Wielenga Thursday, August 12, 2010

    No... :-) That was a screenshot taken on my girlfriend's computer.

  • Eric K. Friday, August 20, 2010

    The book is well layed out, easy to follow and overall an excellent read. Thanks to all involved on the translation team and to Jurgen for writing it! However, I seem to be having a problem with the examples:

    Most of the examples advocate creating an "api subpackage" (ex. com.netbeansrcp.taskmodel.api) for interfaces and creating the implementation classes in the package above the api package (ex. com.netbeansrcp.taskmodel).

    Then the .api package is exposed as the "public interface" for the module. However, other modules that need to use the concrete classes (like the TaskEditor module -- specifically the TaskEditorPanel needs to instantiate a TaskImpl object) don't seem to be able to unless the implementation package (ex. com.netbeansrcp.taskmodel) is exposed as well. Am I missing something?

  • Geertjan Wielenga Saturday, August 21, 2010

    You're absolutely right, Eric. I will make an erratum about that, to be published in the coming weeks. Also apologies for the appendices and code not beign available yet, watch this space, coming soon. Thanks a lot for your nice comments about the book.

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