I've somewhat got a grasp on what needs to be done. This brings me to a new question though.
Is it possible to call AbstractApplication.start() from another AbstractApplication? I'm getting exceptions in ULC. Then call the stop function when I want it to go away? Or is it better to just include the start function in the constructor? ----- Original Message ---- From: Joe L <[EMAIL PROTECTED]> To: [email protected] Sent: Tuesday, December 5, 2006 1:28:30 PM Subject: [ULC-developer] Different Application Components I'm developing an application where it's going to have several different parts, or components. The components are going to be ULC pieces, and the backend running everything is going to be pretty much straight java. Now usually I'd just create a jar of the component, and use that. With a jar, I wouldn't be able to display the ULC piece in an applet launched ULCFrame though, would I? I guess I'm looking for the correct way to compile a component, and then to link to it from the larger application. I want to be able to send information to it from the larger application though. I might next to execute commands in the component also. These events will most likely be time based. Let's say for example, I have a news reader. It runs standalone as a news reader and works fine. I want to expose the calls to be able to show specific news items at specific times to the user. What's the best way to package that? I'm not very familiar with applets. Joe Everyone is raving about the all-new Yahoo! Mail beta. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
