Craig, I've been rereading your Shale proposal and studying the use cases. To me the usecases example shows an interesting way of dealing with some of the challenges of a "dialog" situation. Your general approach makes sense.
What I don't understand is the benefit of the DialogController interface in particular. What real benefits do I obtain from extending this interface? The benefits of the ViewController interface are more obvious. The framework will call the various methods at the appropriate point in the Shale lifecycle. (I'm interested in learning more about how you might use those methods but for that I will take a look at mailreader.) I don't really see that the methods on the DialogController interface are guaranteed to be called at any point. You are of course calling them from the appropriate ViewController beans, but that's not a guarantee. Perhaps this is an area where you had some long term plans in mind? Again, I'm not criticizing the approach you are taking in the usecaess example, but for now it just strikes me as an example of how you might choose to go about it. I'm probably missing something so any light you can shed on this would be helpful. Thanks, sean --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
