Custom boot-strap / setting locale from request headers
Hey Guys - There's a section on this page: http://code.google.com/webtoolkit/tutorials/1.6/i18n.html That suggests that there's an easy way to set the user's locale by parsing the Accept-Language header in the user's request. I want to have my GWT app always display the locale specified in the client's Accept-Language header - not the locale specified in the host page. I think I should be able to write a servlet to do this... and it sounds like this is possible based on that page, but I don't know enough about the bootstrap process to actually make this work. Has anyone else done this? A more general question is - is there a way I could write a servlet that pulls the client's browser type and locale from the request headers and returns the appropriate GWT permutation? This would let me skip the entire .nocache.js bootstrap process and speed up initialization. I feel like this shouldn't be too hard, but I don't really know what setup goes on in the nocache.js bootstrap file. Has anyone done this before? Can this be done? or is there essential setup that occurs in the bootstrap file? Any help will be appreciated. Thanks! -Andrew --~--~-~--~~~---~--~~ 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 google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~--~~~~--~~--~--~---
Manual Serialization / Deserialization of objects
Hi Guys -
I'm trying to write my own custom transport solution for client /
server communication so that I can make my project work cross-site. I
would like to serialize objects on the client side, send them to my
Jetty server using my own custom transport, and then deserialize those
objects on the server side for handling.
I've written the client code, and it seems to be working. It looks
like this:
(not that NetworkPacket implements IsSerializable, and EventService is
a dummy RemoteService)
public String serializePacket(NetworkPacket np)
{
String retVal = null;
SerializationStreamFactory fact = (SerializationStreamFactory)
GWT.create(EventService.class);
SerializationStreamWriter theSW = fact.createStreamWriter();
try
{
theSW.writeObject(np);
retVal = theSW.toString();
}
catch(Exception e)
{
e.printStackTrace();
}
return retVal;
}
This code seems to be working (it produces a reasonable-looking
string). I can't test if it deserializes though because the
serialization is asymmetric. The part I can't figure out though, is
how to deserialize on the server side. The closest I've found is the
ServerSerializationStreamReader class, which I found while poking
through the GWT source. It seems to be undocumented though, and its in
the "com.google.gwt.user.server.rpc.impl" package, which tells me it's
probably not intended for use by my code. How am I supposed to do
this?
Any help will be greatly appreciated!
-Andrew
--~--~-~--~~~---~--~~
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
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---
FlowPanel does not work as expected when a Panel is added to it
I'm trying to use a FlowPanel to lay out some widgets I created. I was
able to get it to lay out checkboxes and labels, just fine, but if I
add something more complex, like a Panel, everything shows up on its
own row. Following is some code that demonstrates the problem. With
label, I was able to use "display:inline" to make things work, but
with Panels it does not seem to help.
FlowPanel flowPanel = new FlowPanel();
for (int i = 0; i < 30; i++) {
HorizontalPanel wrap = new HorizontalPanel();
wrap.setStyleName("DisplayInline");
Label lx = new Label("tesfsdf ");//new PictureUploadBox());
lx.setStyleName("DisplayInline");
wrap.add(lx);
flowPanel.add(wrap);
}
My CSS:
.DisplayInline {
display: inline;
}
Any help would be greatly appreciated.
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
Re: Problems adding a "Digg This" link
Thanks for the prompt feedback guys. I played around with the HTML
widget, but I wasn't able to get it to actually execute the script. I
didn't want to just include it in my index.html file... I plan to have
multiple "digg this" links on the site, and each one will need to jump
to the appropriate place using history tokens.
I managed to get it working without running any javascript though. The
digg script just creates an iframe with some URL-encoded arguments, so
I simply created my own iframe and encoded the URL myself. The only
downside is that I'll have to watch out if digg ever changes their
API.
If anyone does find a way to use the HTML widget to actually create
and _execute_ javascript code I'd love to hear about it though.
-Andrew
On Nov 29, 9:48 am, Charlie Collins <[EMAIL PROTECTED]> wrote:
> Reinier is correct there, it's more complicated than I was making it.
> That Digg script works quite a bit differently than I was guessing
> before I actually looked at it. What I meant is still possible, but
> probably not what you want depending on the situation. If your host
> page has a separate div for your GWT content, and a separate div for
> the little Digg script, what I originally said should work - but it
> would always just link ("digg") to your host page (which would be your
> entire GWT app in the canonical case).
>
> To do this right, it looks like you would need to make sure your GWT
> app uses History and then you need to "Digg" the correct state with
> the tokens and so on. You could use HTML as Reinier suggests, and make
> sure to change the URL for the Digg button each time you have
> different state:
>
>
> digg_url = 'WEBSITE_URL';
>
> http://digg.com/tools/diggthis.js"</a>; type="text/
> javascript">
>
> Looks like they also have a "submit your own" thing that you could
> just make a GET request to to
> submit:http://digg.com/submit?url=example.com&title=TITLE&bodytext=DESCRIPTI
>
> (With that you could make your own buttons or links or whatever, and
> then just make the digg request with proper params. You could use that
> and make a Digg GWT Widget? Sorry I piped up though, I don't really
> know much about Digg in particular, I was just trying to make
> suggestions in the general GWT sense.)
>
> On Nov 29, 10:39 am, Reinier Zwitserloot <[EMAIL PROTECTED]> wrote:
>
> > I doubt digg's js thingie is written by an intelligent developer (digg
> > has a track record of sorts). There IS a way to write such widget
> > scripts so they work in all situations, including the peculiar way GWT
> > builds webpages, but not many web widgets work this way. So, assuming
> > for a moment that won't fly, here's the easiest alternative:
>
> > Use com.google.gwt.user.ui.HTML.
>
> > On Nov 29, 1:48 pm, Charlie Collins <[EMAIL PROTECTED]> wrote:
>
> > > Can't you just add the script element to your host page, the same way
> > > you would "in HTML"? That is to say, don't try to recreate the script
> > > element in Java and have GWT insert it, just put it on the host page
> > > (the same place you put the gwt script tag, etc).
>
> > > On Nov 27, 11:33 pm, mayop100 <[EMAIL PROTECTED]> wrote:
>
> > > > I'm trying to add a "Digg This" link to my gwt website. If my website
> > > > were just an html page, all I would need to do is include this line in
> > > > my HTML:
> > > > "http://digg.com/tools/diggthis.js"</a>; type="text/
> > > > javascript">"
>
> > > > I've tried adding a new element to the page with DOM.createElement
> > > > ("script"), but it ends up replacing the entire contents of the page
> > > > with my digg link. I've also tried a JSNI solution, but with no
> > > > success.
>
> > > > It seems to me there should be an easy solution for this... anyone?
>
> > > > Thanks -
>
> > > > -Andrew
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
Problems adding a "Digg This" link
I'm trying to add a "Digg This" link to my gwt website. If my website
were just an html page, all I would need to do is include this line in
my HTML:
"http://digg.com/tools/diggthis.js"; type="text/
javascript">"
I've tried adding a new element to the page with DOM.createElement
("script"), but it ends up replacing the entire contents of the page
with my digg link. I've also tried a JSNI solution, but with no
success.
It seems to me there should be an easy solution for this... anyone?
Thanks -
-Andrew
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
