Did you provide a link for Laszlo? I might have missed it. I've frankly never heard of it, I'd like to take a look.
-- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com On Tue, April 5, 2005 2:52 pm, Paulo Alvim said: > Thanks for your help, Frank... > > My English is not so good - but that's exactly what I'd like to say. > (you know - after 20 years migrating to lots of tools - COBOL, UNIX, RAD > C/S, Java App Server, J2EE, Open-Source, we know that, at the end, > delivery > value to the end customers has to be the main goal). > > In our opinion, JSF isn't that good...specially if we already have an > exceptional alternative such as Laszlo. > > But what you guys think about Laszlo + Struts? Is there anyone thinking > about target Struts 1.3 or greater to integrate "out-of-box" with Laszlo? > Did anyone post about that before? > > After our research we're sure that it would be a very strong alternative > to > JSF, because it would be focused in immediate results to the end > customers! > > Alvim. > > -----Mensagem original----- > De: Frank W. Zammetti [mailto:[EMAIL PROTECTED] > Enviada em: terça-feira, 5 de abril de 2005 13:39 > Para: Struts Users Mailing List > Cc: 'Struts Users Mailing List' > Assunto: Re: AW: JSF (the same old stuff?). We prefer Laszlo + Struts > > > On Tue, April 5, 2005 12:16 pm, Leon Rosenberg said: >> Aehm, could you please explain what exactly the "high level RAD+Html >> approach" is? >> >> Regards >> Leon >> >> >> P.S. RAD as in Rapid Application Development? > > I think that is indeed what he is referring to. I could probably just let > him answer for himself, but what would be the fun in that?!? :) > > JSF for instance (as well as ASP.Net) were created with the idea of being > tool-centric in that they generally envision development being done in a > drag-and-drop RAD-type IDE environment. Not that you HAVE to do it that > way of course, but they started with that as a goal. > > In such an approach, you tend to write very little HTML yourself and > instead let the tool (or whatever is processing your pages' macro > definition) generate the final markup. Note that this is even moreso than > JSPs and taglibs and such which, of course, are themselves rendering the > final markup too, but with JSF and other such platforms it's meant to be > even more abstract: drag a Select Component onto the canvas and that will > result in a bunch of HTML that you'll possibly never see or care about. > > -- > Frank W. Zammetti > Founder and Chief Software Architect > Omnytex Technologies > http://www.omnytex.com > >> >> >> --------------------------------------------------------------------- >> 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
