Geertjan's Blog

  • March 27, 2009

Inside the Android SDK

Geertjan Wielenga
Product Manager
A colleague told me about this the other day and so I downloaded the Android SDK and saw for myself...

The NetBeans Platform Learning Trail has a section entitled "NetBeans APIs for Visualizing Data", which provides several tutorials covering the NetBeans Visual Library API, which is, simply put, a Java widget library. And some of those tutorials, like the Android SDK screenshot above, indicate that the NetBeans Platform isn't needed at all if you want to use the NetBeans Visual Library API. Only two JARs are all that you need... as you can see above.

As a result, you could use any IDE at all, such as shown here:

Note: The recently released part 9 of the Top 10 NetBeans APIs screencast series focuses specifically on the Visual Library API.

Join the discussion

Comments ( 3 )
  • Romain Guy Saturday, March 28, 2009

    Hi Geertjan,

    More specifically, I used these two libraries to build a tool called HierarchyViewer: http://developer.android.com/guide/developing/tools/hierarchy-viewer.html

    I actually first used these libraries for an internal tool that I'm using to track the performance of the drawing and layout operations of our UI toolkit: http://jext.free.fr/frameworkprofiler.png (that tool was originally built on top of NetBeans Platform but I then rewrote it on top of the Swing Application Framework to reduce the download size of the WebStart version.)

    I am however in the process of re-designing the entire tool and I'm not sure I'm going to use these libraries again. The design I'm aiming for does not require user interaction with the graph and I have very specific needs for the rendering.

  • Fabrizio Giudici Saturday, March 28, 2009

    Hello Romain.

    Unless the work you're doing for Android should be kept reserved, please consider telling us which kind of "special rendering" you need, and perhaps we could be able to fit it to the current Visual Library.

  • Geertjan Saturday, March 28, 2009

    Would be cool if Fabrizio's approach (i.e., somehow handling your rendering needs) works out, because then a library that originated in one of Android's competitors, i.e., from the tooling support for Java ME, continues being used in Android SDK. That interchange of JARs is kind of neat, undermining the public spin doctors and so on -- i.e., engineers use whatever they need and are not religious about things. But now I need to go back to introducing the NetBeans Platform to students in Warsaw.

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