Jack, Since we're all developers here ... you might consider trying to demonstrate with *code* instead of words (or pretty pictures :-) why a proposed solution is better. Show us that it makes the framework code easier to write and maintain. Show us an application based on that design (preferably one also implemented on the alternative approaches so we can compare -- and it doesn't have to be mailreader; I'm game for a different one).
You've said you don't like the page controller approach. Fine ... that's your right. But "Struts is dead" comments are just noise, until you demonstrate exactly why and how your approach is better. I don't *care* if you like page controller or not. I don't *care* if your picture indicates a mythical complete separation between the various elements -- it doesn't mean anything until its cast in something concrete. And, by the way, PLEASE move the discussions over the the developer list where they belong. Anyone on the user list who wants to participate in the discussion (or just follow along) is welcome to subscribe. Users who are interested primarily in getting the current version to work will appreciate the lower volume on a pretty high volume list. Craig On Thu, 18 Nov 2004 07:49:01 -0800, Dakota Jack <[EMAIL PROTECTED]> wrote: > Hi, Joe, > > This is certainly a reasonable request and I don't take it personally > at all. I don't think what I have said is overblown. I will add more > later, but for the moment let me say that one needs to articulate what > Struts does and ask what is left with the new proposals. I will add > more on that later today if I find the time. We can all do that, > however. I do think that, if you want in any sense what Struts has > been, I don't think what I said is alarmist but true. If not, I > certainly would like to get the truth clarified. I have found your > contributions to be clear, thought, and sound at all levels. I am > more than happy to meet this request. > > Jack > > > > > > At 11:56 PM -0800 11/17/04, Dakota Jack wrote: > > >The bottom line is that Shale is wholly inconsistent with the Struts > > >approach. If Struts 2.0 becomes Shale, Struts is dead. > > > > Jack, don't take this personally, as I appreciate your energy and > > your efforts to articulate an alternative -- but I see this as > > alarmist and overblown. I have been trying to track this thread, and > > I have yet to see a convincing argument backing up this statement. > > > > I'm still looking for the personal time to get Shale running and to > > look at making an app with it, but if you're going to make this > > statement (and you have a couple of times), then I think you need to > > come up with a concise explanation of why Shale is "wholly > > inconsistent with Struts." If you've made this point, I apologize > > for missing that email. Maybe you could add it to the web site > > you're developing, or on a page in the Wiki? > > > > Elaborating from this, one might ask "what is Struts?" Particularly > > when one looks at the chain-processing model, the definition becomes > > much more amorphous. Then again, I don't think the answer is > > critically important. I don't really care what it's called; I just > > want a webapp framework that makes my job easier. Continuity with > > Struts 1.x will help with that, since I won't have to live through > > retraining myself and the whole team -- but we've learned to deal > > with lots of change anyway. > > > > Joe > > > > -- > > Joe Germuska > > [EMAIL PROTECTED] > > http://blog.germuska.com > > "Narrow minds are weapons made for mass destruction" -The Ex > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
