Pulpcore and JavaDoc

One of the major personal love for Java is its JavaDoc description, it is extremely handy when you are coding something and is on a quest for the proper method to resolve your problems, especially when you are not extremely familiar with the library that you are using. However, upto the latest post I wrote on Pulpcore, we are still getting a screen that looks like this when we attempt to read the documentations within Netbeans.

Annoying isn’t it? We know there’s JavaDoc with Pulpcore, in fact, we can easily access it online! Don’t believe me? Click here for the Pulpcore 0.11.5 JavaDoc API!

So, how do we go about doing this? According to the original authors of the NetBeans Module, you need to add some jar files and a brunch of doc files to get this up and running, I’ve found a more simple and reasonable approach.

Code Assist JavaDocs from what I recall back from Java 1.4 is actually source code related. If you have your source code there, the engine will first attempt to look for the method or variables and display the JavaDoc style comments you have included with that method or variable.

Luckily, Pulpcore is released with Source, we can easily take advantage of this.

1. Navigate to your Pulpcore 0.11.5 folder and look for a zip file called ‘src.zip’ extract it to a sub folder called src.
2. At this point, if your Pulpcore 0.11.5 files are in C:\pulp, then you should have a sub folder called C:\pulp\src\.
3. Within C:\pulp\src, is a folder called src, and within this folder is a folder called pulpcore.
   
   You should have a file structure like C:\pulp\src\src\pulpcore\, if you don’t just look for the plupcore folder, the name of the parent folder of pulpcore is the one that you need to remember. For my example, it is C:\pulp\src\src.
4. Go back to Netbeans and navigate to the project properties.
   
5. Navigate to Java source Classpath
   
6. click on
   
7. Type in C:\pulp\src\src and click on open.
8. Click OK to save the Project Properties.
9. Test the Code assistant again.
   

You are done

Now, you are not only getting the live documentations from the Java code of Pulpcore 0.11.5, when you are running into problems during debugging, you can easily access the source code of the Pulpcore to find out whether you are using a method properly or not.

Tags: java, JavaDoc, JavaDoc description, JavaDoc style, Navigate, Netbeans, proper method, pulp, sub, zip

Netbeans IDE

My first time using NetBeans, it was barely an IDE. Actually, it was just a platform that allows Java Developers to test their JavaBeans on. Running on Java 1.3.

So, since 1.3 to the end of Java 1.4, I have been using a simple IDE called Gel. Gel’s developers have stopped development since the launch of Java 1.5, and actually becomes non-usable since Generics was released. So I have been on the search for another IDE. At one point, I tried the famous Eclipse IDE however was extremely disappointed at the slow responses Eclipse have. JDeveloper was not a bad solution, however I personally am not very comfortable with using something that is branded with Oracle with MySQL or PostgreSQL.

After jumping into bed with several Java IDEs, I’ve decided to give NetBeans 6.5.1 another try. This time, I think I am set for my Java Development. It not only have a decent speed while loading up, it supports two other languages that I use all the time, C++ and PHP.

I personally think NetBeans have come a long way, one of the most amazing tool is the GUI interface. I recall that back in the days of Java 1.4, to create a typical Java GUI, I must code the the GUI piece by piece in code. However with the GUI interface editor, drag and drop with double clicking to code. This made GUI design and GUI coding A LOT easier then when I was learning Java.

To obtain the Netbean IDE please go to http://netbeans.org/. and download the version that fits your developmental system.

Tags: development, Eclipse, Eclipse IDE, Gel, Generics, java, Java Developers, Netbeans IDE, platform

Pulpcore

Recently I came across an OpenSource project designed to make java more updated with simple 2D game programming. Flash, Silverlight and other secondary tools have long since dominate this client side, interactive coding portion of the web. HTML 5 is still in its infancy, and ultimately painful to implement. Of course, to some, Java is as painful to learn. But for most people who have been taking advantage of Java’s server side power, it would be relatively fun to go back to GUI programming.

Pulpcore is really not a brand new idea. Java’s applet attempts back in the mid ninties was a complete failure, yet super foresight on Sun’s part. Java Applet’s failure is actually due to the limitation in computing power back in the 90s. The Java VM is not light to load and run, yet most computers back then would have been under 100 mhz! That is like a joke compared to today’s cpu speed, measured in GHz instead!

So if there is a way to load the applet code without all the annoying java protection, java can actually be more efficient then flash!

Click here to take a look at Pulpcore’s main page!

Tags: games, java, pulpcore