Next phase of current project, this will be really useful for me to have. I am perfectly willing to help you out as much as I am able. This would include testing, debugging, and some feature enhancements.
And I am strongly seconding what Pete said about asking Michael Nash for advice.
Regards, Steve
Pete Carapetyan wrote:
Willie:
I was attempting to build a Keel swing application before contract work swallowed up all my free time.
The short answer to your question is that a keel swing app would offer you the benefits you have outlined below, and many more.
Just in case it saves you any research, here is where my research has taken me so far. You will need....
1. Keel container bootstrapper 2. clnt-swing 3. SOC challenges
Details:
1. Keel container bootstrapper
-------------------------------
It would be unfair to say that Keel is hardcoded into the web application environment, because it is not. Rather, you will find that a standalone Keel application may require you to learn more about the container than you would otherwise need to do. This is where I got hung up, because I hadn't learned the basics of starting up and deploying an Avalon Fortress container without relying on all of the Keel setup features normally used.
Hint: Even though you plan to utilize the Keel version of the Fortress Avalon container, you will probably need to go straigt to the Avalon site first, to learn these basics. That should save you some heartache.
There is also some effort to segregate all of this into a separate project, but I am not sure where that stands at the moment.
Shash seems to be the go-to guy on Avalon-Fortress, when it is time to address your questions....
2. clnt-swing
-------------
Take a good look at the other clnt-whatever projects. They are pretty straigtforward, not a lot of code there, so you can get a nice idea by comparing similarities what it would take to make a nice little connector class for swing.
Also be sure to shamelessly solicit Michael Nash's assistance in this area. He won't read your mind, so you will have to be quite specific in your questions, but since he wrote the other clnt- pieces, he knows where the bodies are.
For a bit of help, I would also suggest checking out JellySwing project. Not because it can be used as is, but because they have already abstracted out much of the swing calls, something you may find useful to you as you will need to do the same thing.
http://jakarta.apache.org/commons/jelly/tutorial.html#jellyswing
3. 'Separation of Concerns' Challenges
-------------------------------------
The beauty of Keel is also what may challenge you in the initial hours. We are so accustomed to just throwing everything into one bucket and banging away at the code, you may find that you have to really bend your mind to figure out which pieces go into which bucket, and how to keep separation of concerns working.
For example, if your application's models know anything about the swing client, then something isn't right yet.
Or another way of putting it would be that everything about your application should work when you simply port your app to clnt-struts or clnt-velocity. Hmmmm. That is a nice promise, but you may find yourself challenged by this when you begin coding and all of a sudden have to figure out how those different buckets talk to each other. It took me a while anyway.
No estimates offered on time budgets for each task. Best of luck!
Willie Seabrook wrote:
-- Java/J2EE Developer/Integrator Co-Chair, Dallas/FortWorth J2EE Sig 214-724-7741
http://keelframework.org/documentation Keelgroup mailing list [EMAIL PROTECTED] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
