Insert Witty Irony Here

Tuesday December 27, 2005

Start writing apps for Tivo in NetBeans; updates for HME 1.4 I gave my wife a Tivo box Christmas. And I got a new toy to play with....

One of the first things I did was look for how to hac... create applications for... it. And there was a ton of resources about it.

Some of the folks associated with NetBeans have an article about developing Tivo application using NetBeans. Unfortunately, it seems like the Tivo HME team is a bit more liberal about API evolution than the NetBeans team.

I had to use the following code to create the app that Tim Boudreau blogged back in February, 2005.

package tivotest;
import com.tivo.hme.sdk.Application;
import com.tivo.hme.interfaces.IContext;
import com.tivo.hme.sim.Simulator;
import java.awt.Color;

public class Main extends Application {

    public static void main(String[] args) {
        try {
            Simulator.main(new String[] {Main.class.getName()});
        } catch (Exception ex) {
            System.out.println("I don't know what to do!!!");
        }
    }

     public void init(IContext context) {
         getRoot().setResource(createText("default-36-bold.font",
            Color.white, "Hello from an application!"));
    }

}

The bigggest changes between Tim's code and this:

1. import of IContext.
2. catch the Exception in main().
3. use of getRoot() instead of a direct reference to root (which became a private member of Application).

What about Eclipse.... Though some of my co-workers may call me a traitor, I saw this article on developing EJB 3.0 using GlassFish with Eclipse.

As further evidence of Java EE 5's "ease of development", I don't think Filippo Diotalevi is using Eclipse's WTP. (2005-12-27 17:57:27.0) Permalink Comments [2]

Java Web Start fast and easy... I wrote my entry about creating a Java Web Start-able application client, without really knowing much about Java Web Start. So, I read through the white paper that Eduardo cited on The Aquarium to learn more about it.

After I read through the paper, I realized how much work NetBeans 5 and the GlassFish Project's is doing for the developer...

• Package the app in a jar...Covered
• Deploying a JWS App... Covered
• Setting up the Web Server... Covered
• Creating the JNLP File... Covered
• Placing the Application on the Web Server... Covered
• Creating the Web Page... Almost

Then I got to thinking, does an application client need to access resources from the server? The answer is no. It might, but doesn't have to. That means that a developer could create a "plain old java application", wrap it up in an Enterprise Application and let the GlassFish Project's deployment mechanism do the tedious housekeepinng. Their app would be JWS enabled with hardly any effort.

Sweet! (2005-12-27 12:07:23.0) Permalink Comments [2]