Re: A setClient method in SwixEngine

Ted,

Boy did I strike up a a mess today on the forum.

I would agree that if we use an XML parser every time the engine 
starts, this could be a possible drain of
performance.  I think performance is one of those items everyone is 
scared about, but needs to be tested before
everyone jumps to conclusion.

I have thought about the idmap issue.  There should be no reason to 
start up many engines in any one program.

The trick is going to be to have a hashmap of idmaps.

I am looking into that as well.

If we had a  hashmap of idmaps, we should be able to run one engine, 
specifiying a different hash entry for the map to be stored in.

Anyways, all ideas.

Brian
On Friday, October 24, 2003, at 07:23  PM, Ted Hesselroth wrote:

> Wolf,
>
> I am using swixml for a medium-size java application, and have found 
> it to be very useful. I like the fact that it is quite focussed and 
> works well. I was pretty impressed upon reading the source code, too.
>
> The application I am writing is highly modularized. Using swixml I 
> have been able to write generic model-view-controller functions and 
> have the view components filled in upon reading an xml file. I have a 
> dozen or so different panels, and they can all use the same class for 
> the view. For each panel I have only to write the swixml file and the 
> action listeners.
>
> For modularities sake I want the action listeners to be in separate 
> classes. Therefore I am using the swix engine construction which 
> allows the "client" to be specified. This requires the creation of a 
> new swix engine object every time a new panel is created. I'm 
> concerned about the speed as the application grows larger. Would it be 
> possible to include a setClient call in SwixEngine so that the client 
> could be changed in an existing swixengine? Seeing how client is used 
> in the code, it seems so, assuming that idmap would be cleared in this 
> step. Another reason for this addition is in the use of registerTag in 
> this situation. I'd like the individual modules to be able to register 
> custom components and have them be available to all subsequent panels, 
> but this information gets lost for a new swix engine occurrence unless 
> I somehow maintain it and reregister everthing. So I think the 
> setClient and a tag that registers custom components would be very 
> powerful.
>
> Another suggestion would be to make comboboxes easier, some 
> alternative to coding a special class for each combo box. A list of 
> strings as nodes or an attribute would be fine. As mentioned above, my 
> goal is to have a single view class and a single action class for each 
> panel.
>
> Thanks for writing a very nice package, and please feel free to 
> explain if I am not fully understanding its use.
>
> Ted Hesselroth
>
>
>
>
> _______________________________________________
> Forum mailing list
> [email protected]
> http://carlsbadcubes.com/mailman/listinfo/forum_carlsbadcubes.com
>
>
Sincerely,

Brian P Michael
630-897-8364 x17
[email protected]

_______________________________________________
Forum mailing list
[email protected]
http://carlsbadcubes.com/mailman/listinfo/forum_carlsbadcubes.com

BEGIN:VCARD
VERSION:2.1
N:Michael;Brian;P
FN:Brian P Michael
ORG:GoldParrot Corporation
TITLE:President
TEL;WORK;VOICE:630-897-8364 x17
TEL;WORK;FAX:630-897-8364 x21
ADR;WORK:;;1326 Eastwood Dr;Aurora;IL;60506;USA
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:1326 Eastwood Dr=0D=0AAurora, IL 60506=0D=0AUSA
EMAIL;PREF;INTERNET:[email protected]
REV:20020311T030256Z
END:VCARD