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

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.
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.

-Jeff

Jeff Buhrt
Achievement Focused Technology, Inc.
[email protected]
http://aftinc.net

Andrew Kohlsmith wrote:

>>Q2. If you build quite a complex user interface I suppoe that the file
>>size can easily get 300+ Kb. Are there any know values for gui file size
>>or is it possible to load parts of the gui (sub windows) only upon
>>request?
>>    
>>
>
>Right now the most complex XWT app we have going is the Benshaw sales 
>application -- it's weighing in at 286k, but I don't remember if it's been 
>compressed like elephant (-9) or compressed like fat man (-4).
>
>The original mail application was also complex but it was only 156k.
>
>Regards,
>Andrew
>
>_______________________________________________
>users mailing list
>[email protected]
>http://lists.xwt.org/listinfo/users
>
>  
>