Hi Ray. Thanks for the pointer. That was exactly what I needed. Took about 20 minutes of "work" to get InputStream and Reader working in GWT.
Also, my coworkers and I are wondering if GWT is single. eric On Mar 8, 5:18 pm, Ray Cromwell <[email protected]> wrote: > Look at the user/super/com/google/gwt/emul source for the GWT JRE > emulation, > e.g.http://code.google.com/p/google-web-toolkit/source/browse/trunk/user/... > <super-source/> is what you want. It allows Web mode and Hosted Mode > to see different source code. > > -Ray > > On Mon, Mar 8, 2010 at 12:54 PM, Eric B. Ridge <[email protected]> wrote: > > > > > Please don't laugh (at least not out loud). > > > I've run into a situation where I really need to use a JavaCC > > generated parser on the client-side. The generated code is all simple > > Java, except for its use of java.io.InputStream and java.io.Reader. > > > Is it possible to implement additional GWT JRE objects as maybe a GWT > > module, or through various .gwt.xml directives? Basically, could > > support for those base classes be added without modifying the GWT > > source directly? > > > If yes, is there a starting documentation page somewhere on the > > intertubes? > > > ISTM that translating java.io.InputStream would be stupid simple, and > > then I could roll my own lame implementation that uses a > > java.lang.String as the backing store. In my case, I just need to > > parse user-typed strings. I've got no need to tie the InputStream to > > an HTTP response, for example. > > > java.io.Reader might be a bit more difficult since it references stuff > > in java.nio, but I could probably work around that (even if I have to > > manually/programmatically hack the JavaCC generated parser source at > > build time). > > > Anyways, any advice on where to begin implementing an additional GWT > > JRE object will be greatly appreciated. > > > eric > > > -- > >http://groups.google.com/group/Google-Web-Toolkit-Contributors -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
