Please check carefully all these Laszlo demos, Al, and you'll see that it's a real killer MVC-View approach that deliver great value for customers (in its segment - of course):
http://www.laszlosystems.com/demos/ And please note that you don't have "MVC-Control" in Laszlo - it's focused in the View - such as JSF - and it's too much elegant for that - for example, it has no eclipsed areas with Struts Controllers! You also don't have to know Flash script language - you can get amazing usefull web GUIs by declaring LPZ (XML macros) and Javascript... Laszlo isn't "more of the same" - it's the kind of solution that enabled us to exceed our customers expectations in our first "proof of concept" (previous Macromedia's Flex and other proprietary "flash" tools didn't deliver this result). Alvim -----Mensagem original----- De: Fogleson, Allen [mailto:[EMAIL PROTECTED] Enviada em: terca-feira, 5 de abril de 2005 17:08 Para: Struts Users Mailing List Assunto: [OT] RE: AW: JSF (the same old stuff?). We prefer Laszlo + Struts Paulo, I can certainly agree that value to the customer is the prime ingredient in any solution. However the problem I have seen, at least here in the US (I can't speak to the west coast but I have had clients up and down the east coast, most of the Midwest, and very little on the west coast) is that clients want several things out of a solution (in decreasing order of importance or relevancy. i.e. often a standards based solution overrules a perfectly valid, easier and in some cases better implementation) 1) Standards based. In the java world this means J2EE in general, and probably in the specific case here JSF over Laszlo. 2) Widely accepted in the industry if using open source. Until relatively recently it was not that easy to sell a customer on using struts. As recently as 2 months ago I had to justify the use of Springs IOP stuff to a client (and I didn't architect the solution) and we came very close to having to refactor any use of spring OUT of the application. "Widely accepted" obviously is a subjective assessment. Those are the top 2 things. Now I personally have not used Laszlo (I looked at it briefly a while back but haven't even played with it in my "free time") So you, having experience with it, may be able to make a better value statement about it to a client. Of course it is nearly impossible to keep up with all the projects out there. As an architect, usually with several simultaneous client engagements, it has become even more difficult :) With that said.... I don't think there is anything preventing someone from doing a Laszlo struts integration. I think it would end up in contrib. My personal view of struts is that it really provides the C part of MVC. (I don't really think you can make a case for struts providing the model, and the normal view layer is jsp which is not a part of struts of course.) The struts taglibs for instance, although very useful, are not required to use or even recognize the power of struts. Of course its just my opinion, and since no 2 developers will ever agree my opinion and 5 bucks can buy a cup of coffee at starbucks :) Al --------------------------------------------------------------------- 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]
