On 06/23/2009 06:50 PM, progen wrote: > Hi Jeff, > > Thank you for the suggestion, > > This is exactly what i tried to do, i changed the UserAgent.gwt.xml to > make GWT identify Ant Galio as other browsers one by one and > found that it works well when i set as safari. But when i browse the > pages in my PC with Ant Galio it works perfect, and when i use the set > top box browser, > it doens't works :-(, it's not loading the cache.html. Any ideas?
Different browser ident strings? It sounds like you have your own http daemon. If it's Apache, and you have a reasonably default configuration, you should see the ident string in access.log Check a similar log for other http daemons. Do you see any differences between the PC-based browser ident string and the ident string from the set-top browser? Absent access to the httpd log, you might install a wire-sniffer to watch the TCP/IP traffic > > > > On Jun 11, 1:24�am, Jeff Chimene <[email protected]> wrote: >> On 06/08/2009 07:54 PM, proge wrote: >> >>> Is there a way to make GWT support other browsers? We have project for >>> IPTV, and would like to use GWT to build the UI. But the settop box we >>> use is havingANTGaliobrowser in that, I tried to create a sample >>> project with few controls but unfortunately it doesn't works withANT >>> Galiobrowser, any workarounds? Please help.. >> Your sample probably failed in that the GWT bootstrap sequence couldn't >> identify the browser. From a cursory examination of their site, >> theANTGaliobrowser seems reasonably standards-compliant. >> >> If you can cause the browser to identify itself as a GWT-supported >> browser, the GWT bootstrap code will send the appropriate file. Absent >> browser ident games, you'll want to modify the Java code to include >> theGaliobrowser in its browser-sniffing logic. >> >> If you can't get the browser to send an alternate ident string, you >> might try hacking the *.nocache.js to handle theGaliobrowser ident >> string and instead reply with either the IE or Firefox branch to the >> client. Compile your GWT code as "PRETTY" to get code that's easier to >> understand. >> >> Your goal is to get the GWT bootstrap sequence to send code to the >> client that can be tested. This code may be for Gecko, IE, or Safari. >> This will give you a go/no-go decision point. If the proof-of-concept >> works, you'll probably wind up modifying the Java source to recognize >> theGaliobrowser ('cos you're not going to be able to change the >> browser ident string on the customer's box). If you're lucky, theGalio >> browser will respond well to code generated for one of the GWT supported >> browsers. If not, you'll have to addGalio-specific code to GWT. >> >> To repeat: your first try should be to cause the browser to identify >> itself as Gecko, IE or Safari. If you can't do that, you'll have to >> resort to Other Measures. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
