Hello Paolo
Could you please give me some more info concerning your data-GUI XML
binding approach? It seems to fit perfectly into our idea where to
move now with JC stuff. Although Florian's way is also nice and I
have found interesting info in his tutorial, this GUI - data
separation I would prefer. And if you have already made some progress
in this field, I would prefer to collaborate than to reinvent the
wheel ;)
Regards
Jaroslav
On Nov 8, 2007, at 9:13 PM, [EMAIL PROTECTED]
wrote:
Hi Florijan,
it's because the core jc stuff still stays that I think It's
reasonable to continue to use in the jc application EODisplayGroup,
EOAssociation, etc. I think the status is like as the web WO where
the core stuff stays but WebObjects Builder is lacking. In the jc
client development the core stuff largely stays but now Interface
Builder is lacking. Doubtless in my xml binding approach, to edit
by hands a xml file is'nt fun as to play with Interface Builder but
it's much better that to hardcode in the gui java class all the
EODisplayGroup, EOAssociation code. The gui java class remain a
pure swing class, the needed EODisplayGroup, EOAssociation, etc.
stuff are "automagically" added following the binding described in
the xml file. One have to extends the gui class as EOApplication
but this requiremet is just only to start the application, in order
to do the applicationClassName binding in JavaClient.wo working, as
you has described in your WebObjects Java Client tutorial.
Furthermore, in the future one can creates a visually tool, an
eclipse plugin or other, which can generate the xml file
Regards
Paolo
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
