Re: [xwt-users] new to xwt - modal windows and gui size

Jeff Buhrt wrote:

> If size is an issue I have had two thoughts for 'later':
> 1) Have a simple utility to strip out what isn't needed. Basically it 
> would start at main.xwt and walk the widget tree, etc. to decide what 
> was or wasn't accessable. Dynamic calls (if possible) to widgets, might 
> be a problem.

Dynamic GUIs would indeed break this. Still, nice idea.

> 2) It might make as much or more sense to allow spliting the xwar.
> -The idea would be the 'system' widgets, etc. would have their own xwar 
> that could be separately [down]loaded. Basically once a user xwar 
> imported something in the base widgets, etc. the cached xwt.xwar could 
> be compared to see if it was up to date or not. Either download if it 
> isn't present or out of date, and use what is leftover in the cache if 
> it is fine. This loader change could also be applied to the 
> user/application xwar, the only question would be a 'safe' way to know 
> if the xwar had changed or not. This would be comparible to Java custom 
> classloading.

That assumes xwar caching in the first place. We don't have that.

Emile