He may be able to reproduce the front-end but JQuery is going to do nada on the backend. AFAIK there's no solution for any sort of remote objects with JQuery, the data transfer would all be through HTTP web services, encapsulating the data in XML or JSON or something like that. The problem that JQuery solves really well is providing a cross-browser way to find and manipulate the DOM but it's not going to solve the other CSS related cross-browser issues.
-- Howard Fore, [email protected] "The worthwhile problems are the ones you can really solve or help solve, the ones you can really contribute something to. ... No problem is too small or too trivial if we can really do something about it." - Richard P. Feynman On Wed, Sep 16, 2009 at 8:26 PM, adamsch1 <[email protected]> wrote: > We were showing our product [written entirely in Flex BTW] to a web > developer who commented that he could [with about as much trouble] duplicate > our application via JQuery. > > I am not a web developer, so I am not qualified to agree or disagree with > his comment. I'm not even sure its a valid statement? Our application is > entirely written in Flex [on top of blazeds], and is very involved, we have > written many custom components for performance or custom behavior in many > situations. > > My guess is a pure JS route, even with JQuery or another framework would > still lead you to some porting challenges with the various browsers? >
