Hi Lawrence, That's life I guess. You still have some options, though. For instance, what if you create an alternate set of transforms that output JSON, and again just concentrate on outputting application data, not HTML elements. Then you can do RequestBuilder requests from your client to fetch application data, not "pages", and still use GWT widget programming to control the UI. You really need to find a bridge from your current stuff to *widget programming* on the client, or else I fear that GWT will give you little for your investment.
If your management wants to ride the web 2.0 wave, they're going to have to invest something too. It ain't free. Walden On Sep 30, 5:45 am, Lawrence <[EMAIL PROTECTED]> wrote: > Walden, > > What you say is quite true. Transformation/XSLT is not ideal. > However, our system is all written in C++ and generates XML. > I can't change that. I can't put java on the server and I'm not sure > it would make any sense. > So basically no RPC, no serialization of objects .. i'm stuck with > xml. > > The xml transformation is done by a stylesheet that is very old, about > 750 lines of xsl. > It takes the xml and transforms it in a xhtml form with tabs, fields, > drop downs, etc .. > Actually, it shouldn't be too hard to rewrite that in java .. its just > about 1500 words. > > So I guess I will look into it..Its always hard to convince management > that rewriting/refactoring something is > *that* necessary.. > > On Sep 29, 8:06 pm, walden <[EMAIL PROTECTED]> wrote: > > > > > Lawrence, > > > To paraphrase you, what you would like to do is switch to a client- > > centric model of writing your client. That's good. GWT is good for > > that. > > > The part that doesn't make sense to me is to keep the XML->HTML via > > XSLT transformations. That's not the way to build portable widgets in > > GWT. Why don't you try writing a simple client in GWT that gets Java > > Objects from the server, and constructs Widgets to display information > > and ineract with the user? Calling a widget constructor automatically > > invokes the right code for the browser where your application is > > running, where doing an XSLT transform puts you back in charge of > > managing N transforms for N browsers. > > > As a bonus, you get to design, write and debug your entire application > > as if it were Java, including the user's interaction with it. Who > > wants to debug an xslt transform session? > > > Walden > > > On Sep 29, 9:47 am, Lawrence <[EMAIL PROTECTED]> wrote: > > > > Hi all! > > > > Been lurking for a while now and I like this vibrant community a lot, > > > so, thank you for that :) > > > > I need to redesign our web app so that it can support IE 7, gecko, > > > Opera, webkit (one day IE8). > > > The old one was hand crafted to work only with IE6. > > > > The idea is to use gwt and get coding on business requirements rather > > > than trying to work around all browsers .. but I have a few question : > > > > Currently we serve dynamic pages and we use ajax just to get > > > notifications if something changed. > > > We then recreate the page with the updated content and send it back to > > > the browser. > > > Part of this pages is generated via XSLT (on server) > > > We have our XML data we transform it via xslt with our stylesheet > > > (xhtml) and we return the new consturcted page. > > > This styleshee converts our data to all sort of controls : checkboxes, > > > date pickers, drop down, labels, buttons, etc. > > > Every "data" page can be bookmarked. > > > > What I would like to do is recreate the web app via GWT, but instead > > > of retrieving an entire page every time some data > > > is requested I would prefer to only do an ajax request for the xml and > > > then to the transformation locally on the client. > > > I saw someone porting sarissa to GWT so this should be possible. > > > > The only problem is that we embedded quite a few js calls in the > > > stylesheet, and those now will need to be handled by GWT rather than > > > the old, IE6 only, js scripts. > > > I know that gwt compress/obscure the output js to make it faster, so I > > > wonder, how can I mix the two ? Is it possible ? > > > > Also, if I do everything via ajax/xml, does this mean people can no > > > longer save link to pages, bookmark them ? > > > > Thanks > > > > Lawrence- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
