Hi Joe, Correct.
You should not keep in static vars ULCProxys like ULCButton, ULCTextArea, ULCLabel, ULCIcon, ULCPollingTimer etc. Thanks and regards, Janak -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Joe L Sent: Thursday, December 14, 2006 11:12 PM To: [EMAIL PROTECTED] Com Subject: Re: [ULC-developer] Different Application Components Janak, Just to be clear, when you say 'do not keep ULCProxys in static vars' you're talking about ULCButton, ULCTextArea, ULCLabel and stuff similar to that. Right? Thanks Joe ----- Original Message ---- From: Janak Mulani <[EMAIL PROTECTED]> To: Joe L <[EMAIL PROTECTED]>; "[EMAIL PROTECTED] Com" <[EMAIL PROTECTED]> Cc: [email protected] Sent: Thursday, December 14, 2006 7:27:58 AM Subject: RE: [ULC-developer] Different Application Components Hi Joe, static variables will be shared among ULC App sessions running on the server i.e., there will be only one instance. So you need to be careful about synchronization. Moreover, as I said earlier, do not keep ULCProxys in static vars. You could make use of ApplicationContext to store data that persists during the life of a session. Thanks and regards, Janak -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Joe L Sent: Thursday, December 14, 2006 12:23 AM To: [EMAIL PROTECTED] Com Subject: Re: [ULC-developer] Different Application Components I changed it from an abstractapplication to a ULCFrame and then just launch it from the parent application. I'll do that for the rest of the components in the suite. I got it all working and launching properly. The question about static variables is the only remaining question. If I have a static variable is it the same across all server sessions? If 2 people are using the same ULC application on a server, I was under the impression that both would have their own set of static variables. I just want to make sure that this is the case. Joe ----- Original Message ---- From: Janak Mulani <[EMAIL PROTECTED]> To: Joe L <[EMAIL PROTECTED]> Cc: [email protected] Sent: Friday, December 8, 2006 5:02:37 AM Subject: RE: [ULC-developer] Different Application Components Hi Joe, It is not clear what exactly you are trying to achieve. When you say that you have various components, does it mean different ULC composite widgets or ULC Applications? If you have ULC composite widget then it can be easily shown in a ULCAppletPane On the other hand, if you mean that your component is a ULC Application, then it is possible to start a ULC application from another. Please refer to http://lists.canoo.com/mailman/private/ulc-developer/2006/003446.html for details. A ULC application can be started by the ULC client only. Every time a client connects to the server side application a new session is created. Moreover, you cannot keep ULC components in static variables. As for your news reader, you can implement it as a service which can be used by various apps some of which may be ULC apps. News reader UI ULC App |____________________| | News Service I hope this helps. Thanks and regards, Janak -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Joe L Sent: Thursday, December 07, 2006 10:28 PM To: [email protected] Subject: Re: [ULC-developer] Different Application Components Ok, I've started to go the route of not using the AbstractApplication class. I made it a singleton class. I have a question about how ULC works though. If there is a singleton class, is it the same for all ULC Sessions or different? (I'm wanting it to be different) If this is the case, it would also mean that static variables are the same across ULC Sessions. ----- Original Message ---- From: Joe L <[EMAIL PROTECTED]> To: [email protected] Sent: Thursday, December 7, 2006 11:13:11 AM Subject: Re: [ULC-developer] Different Application Components 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Joe L Sent: Tuesday, December 05, 2006 11:59 PM To: [email protected] 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 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ ULC-developer mailing list [email protected] http://lists.canoo.com/mailman/listinfo/ulc-developer
