Adding a PieChart tooltip.text to the piechart options
Folks,
I want to hide the value of pie chart slices in the tooltip. I found
the property 'tooltip.text' in the JavaScript doc for PieChart. Here
is the JavaScript example I modified to work as I want it:
=
function drawVisualization() {
// Create and populate the data table.
var data = new google.visualization.DataTable();
data.addColumn('string', 'Task');
data.addColumn('number', 'Hours per Day');
data.addColumn({type:'string', role:'tooltip'});
data.addRows(5);
data.setValue(0, 0, 'Work');
data.setValue(0, 1, 11);
data.setValue(1, 0, 'Eat');
data.setValue(1, 1, 2);
data.setValue(2, 0, 'Commute');
data.setValue(2, 1, 2);
data.setValue(3, 0, 'Watch TV');
data.setValue(3, 1, 2);
data.setValue(4, 0, 'Sleep');
data.setValue(4, 1, 7);
var options = {title:"So, how was your day?", tooltip: {text:
"percentage"}};
// Create and draw the visualization.
new
google.visualization.PieChart(document.getElementById('visualization')).
draw(data, options );
}
=
How do I make this work with the GWT Visualization interfaces?
Stuart
--
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.
onBlur called twice because of FocusWidget.setFocus implementation
My use case:
I have a TextBox which I want to validate onBlur. If validation fails,
I want to setFocus on it again. Which makes onBlur fire again, hence
the validation routine runs again (not ideal, in fact, a defect in my
mind).
My code:
== snip ==
public void onBlur(BlurEvent event) {
TextBox tb = (TextBox) event.getSource();
try {
Long longValue = Long.valueOf(tb.getText());
} catch (NumberFormatException e) {
// warn the user in the UI
// set the focus back on the TextBox
tb.setFocus(true);
}
}
== end snip ==
The onBlur is running again because FocusWidget does this:
== snip ==
public void setFocus(boolean focused) {
if (focused) {
impl.focus(getElement());
} else {
impl.blur(getElement());
}
}
== end snip ==
So, when I insert non-digits in my text box, and tab or click into the
next form element, onBlur fires once. In my catch block, I set the
focus again, which triggers onBlur again because of how
FocusWidget.setFocus is implemented.
This defect prevents me from displaying a message to the user just
once (ie, with an alert) or setting and clearing a message on fail/
pass of the validation.
Anyone have a workaround?
--
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-tool...@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.
Issue with RootLayoutPanel vs RootPanel and quirks mode
Different renderings based on RootLayout or RootPanel and DOCTYPE. Background - UI is programmatically created (no UiBinder) - VerticalPanel in the center of a DockPanel holds 3 widgets. Only one of them is to show at a time. Turn one on, turn the others off, etc. - Depending on the combination of different access to the Root and DTD declarations, I get _way_ different rendering 1) RootPanel + - Chrome Win: BAD UI - all widgets displayed (ie, setVisible(false) does not work on container) - FF Win: works as expected - IE7 Win: works as expected 2) RootPanel + - Chrome Win: BAD UI - all widgets displayed (ie, setVisible(false) does not work on container) - FF Win: works mostly as expected except some divs don't have correct height set - IE7 Win: works as expected 3) RootLayoutPanel + - Chrome Win: works as expected - FF Win: works as expected - IE7 Win: BAD UI - blank screen 4) RootLayoutPanel + - Chrome Win: BAD UI - works mostly as expected except some divs don't have correct height set - FF Win: BAD UI - works mostly as expected except some divs don't have correct height set - IE7 Win: works as expected Strange that IE7 works exactly as expected in 3 out of 4, when the browsers I like have rendering issues. Besides saying "quirks mode, go figure" are there any other explanations? Looks like I will use Option 4, but now I have to debug Chrome and FF for height setting issues in nested divs. Suggestions? Stuart -- 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-tool...@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.
Mixing createAndBindUi (UiBinder) and runAsync
@gwt-team The new features of declarative UI via UiBinder and code-splitting via runAync of 2.0 are great, but don't seem to play together very well. I am working on a large application where (almost) all of the UI is wired via binding. When I look at soyc reports -- specifically method dependency -- I notice that the entire UI is in the initial fragment because of the createAndBindUi setup in all of the app's widgets. You can guess that wrapping createAndBindUi in a runAync doesn't really work because ui binding is at compile time and creates new binder implementation classes for runtime. (An interesting artifact of DevMode is wrapping createAndBindUi in a runAsync actually does work because of the runtime hooks.) The Aync Provider pattern (see http://code.google.com/webtoolkit/doc/latest/DevGuideCodeSplitting.html#patterns) appears to be one general way of dealing with code-splitting (albeit the docs are a little light on full examples), but it doesn't seem like this pattern will work with ui binding. Please correct me if I am wrong here. One approach that I am considering is to revert back to a programmatic UI in my EntryPoint (ie, get rid of UI binding at the top of my app), and wrap each main UI component in a runAsync. From there down the UI hierarchy I can decide which UI bits use createAndBindUI and which are created the old way but take advantage of code-splitting. Are there any other approaches that might help me out? Stuart -- 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-tool...@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.
Re: New layouts not playing nicely with Maps
I am using UI binding to setup my app, so I needed a little extra
tweak to Eric's code.
If I placed the timer either before or after the createAndBindUi call
in my widget containing the map, I was still experiencing the map UI
rash Jeff and Andrew had.
However, since my app also uses event handling (via gwt-dispatch), I
was able to fire a custom RetrievedMap event at a place in the code
when I know the app has completely finished UI binding (ie, the user
clicks on a nav item to fetch map data, the app retrieves a success
from the server, the app then fires the RetrievedMap event ). My
docker widget containing the MapWidget listens for the RetrievedMap
event, and so I tucked in Eric's timer code to the method handling the
RetrievedMap event and it worked wonderfully.
Phew. What I am trying to say is: if you are using UI binding, a plain
Timer fix may not work because of arbitrary times that your UI may
complete binding. Best to fire an event when you know the UI is
completely loaded, and in handling the event run Eric's timer code.
Stuart
On Dec 21, 11:06 am, Andrew Winter wrote:
> Thanks, Eric. The timer thing does exactly what I wanted.
>
> Andrew.
>
> On Dec 21, 12:54 pm, Eric Ayers wrote:
>
>
>
> > On Mon, Dec 21, 2009 at 6:19 AM, Andrew Winter
> > wrote:
> > > Hi,
>
> > > I have the exact same problem as Jeff. One difference between Jeff's
> > > case and Eric's case is that in Jeff's case, the dimensions of the map
> > > are not known; in Eric's case the map is 400px by 500px. It seems this
> > > problem occurs when the dimensions of the map are not known at build-
> > > time.
>
> > > I want my map to occupy the bottom-right corner of my UI (like Google
> > >Maps). When I use setSize("100%,"100%"), theMapWidgetis given the
> > > correct size (the Google logo etc appear in the right place) but the
> > > tiles don't cover the whole of the widget.
>
> > The trick I used to schedule checkResizeAndCenter() in a timer
> > callback solved that issue for me
>
> > > When I provide an explicit
> > > size, or resize the browser, the tiles are displayed correctly.
>
> > > I don't really want to provide dimensions in pixels if I don't have
> > > to. Is this the only way?
>
> > In the past I've always recommended dimensions in pixels for best
> > results. You could hack around this by hooking into the resize event
> > listener.
>
> > > Thanks
>
> > > Andrew.
>
> > > On Dec 17, 6:44 pm, Eric Ayers wrote:
> > >> Hi Jeff,
>
> > >> I played around with this and got it to work with these panels:
>
> > >> privateMapWidgetmap;
>
> > >> // GWT module entry point method.
> > >> public void onModuleLoad() {
> > >>Maps.loadMapsApi(null, null, false, new Runnable() {
> > >> public void run() {
> > >> LatLng cawkerCity = LatLng.newInstance(39.509, -98.434);
> > >> // Open a map centered on Cawker City, KS USA
>
> > >> map = newMapWidget(cawkerCity, 2);
> > >> map.setSize("100%", "100%");
> > >> map.setUIToDefault();
>
> > >> DockLayoutPanel dock = new DockLayoutPanel(Unit.PX);
> > >> dock.setHeight("600px");
> > >> dock.setWidth("400px");
> > >> SplitLayoutPanel split = new SplitLayoutPanel();
> > >> dock.add(split);
> > >> split.addNorth(map, 500);
> > >> split.setWidth("100%");
> > >> split.setHeight("100%");
> > >> // Add the map to the HTML host page
> > >> RootPanel.get().add(dock);
> > >> new Timer() {
> > >> public void run() {
> > >> map.checkResizeAndCenter();
>
> > >> }
> > >> }.schedule(1);
> > >> }
> > >> });
> > >> }
> > >> On Sat, Dec 12, 2009 at 3:51 AM, Jeff Schnitzer
> > >> wrote:
> > >> > Does anyone have the GWT Googlemapsworking inside the new Layout
> > >> > panels?
>
> > >> > My page is basically a DockLayoutPanel whose main element is a
> > >> > SplitLayoutPanel whose main element is aMapWidget. TheMapWidgetis
> > >> > set to 100% size.
>
> > >> > On startup, the map tiles are sized to a very small part of the area,
> > >> > although the grey background does seem to cover the entire space:
>
> > >> >http://www.infohazard.org/~jeff/mapnolayout.png
>
> > >> > If I resize th
Re: GWT 2.0 crash on IE7 - post-UiBinder setCellHeight with VerticalPanel
Logged as issue 4331 http://code.google.com/p/google-web-toolkit/issues/detail?id=4331 On Dec 9, 7:51 pm, Stuart wrote: > Environment: MS Windows, Eclipse 3.5 with GWT 2.0 plugin. > Testing on: FF (Win/Mac), Chrome (Win/Mac), IE7(Win) > > Basic widget hierarchy: > - EntryPoint loads a DockLayoutPanel via UiBinder. > - in the center of the dock, loads a VerticalPanel > - the VerticalPanel has 3 custom composite widgets in my app's > namespace, each of which have to "appear" exclusively in the dock's > center pane when certain events are fired > > Post-binding logic: > - after the EntryPoint creates and binds the UI, we need to "turn off" > 2 of the 3 custom widgets. > - this is accomplished by the following code: > > // turn off widget 1 > vPanel.setCellHeight(customWidget1, "0px"); > customWidget1.setVisible(false); > > // turn off widget 2 > vPanel.setCellHeight(customWidget2, "0px"); > customWidget2.setVisible(false); > > // turn on widget 3 > vPanel.setCellHeight(customWidget3, "100%"); > customWidget1.setVisible(true); > > Error: > > In IE7, the first reload in DevMode crashes with: > > com.google.gwt.core.client.JavaScriptException: (Error): Invalid > argument. > number: -2147024809 > description: Invalid argument. > at com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript > (BrowserChannelServer.java:195) > at com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke > (ModuleSpaceOOPHM.java:120) > at com.google.gwt.dev.shell.ModuleSpace.invokeNative > (ModuleSpace.java:507) > at com.google.gwt.dev.shell.ModuleSpace.invokeNativeVoid > (ModuleSpace.java:284) > at com.google.gwt.dev.shell.JavaScriptHost.invokeNativeVoid > (JavaScriptHost.java:107) > at com.google.gwt.dom.client.Element$.setPropertyString$ > (Element.java) > at com.google.gwt.user.client.ui.CellPanel.setCellHeight > (CellPanel.java:104) > > > The next line in the stack trace is the first attempt at: > vPanel.setCellHeight(customWidget1, "0px"); > > FF (Win/Mac), Chrome (Win/Mac) all do this properly. > The IE7 dev plugin tells me gracefully that the server is > disconnected. > My eclipse console reports the above stack trace. > > The end result is I have no application in IE. > > (Now, someone is going to say: Why are you using VerticalPanels? Long > story, but I have not found a suitable replacement in the new UI > panels to handle sizing without becoming a PhD in CSS quirks.) > > As I trace through the code, I am looking at this path: > > - We programmatically set the cell height of the widget to 0px > (allowed by CSS) from its parent vPanel > - CellPanel.setCellHeight gets the widgetTd as an Element > - Element.setPropertyString sets the property string of 'height' to > '0px' > - this method is JSNI that sets this[name] = value in the > JavaScriptObject > > I lose the code for a little while as it delegates through to > ModuleSpaceOOPHM(ModuleSpace).onLoad(TreeLogger). > > When we try to exit the onModuleLoad via line 374 of > com.google.gwt.dev.shell.ModuleSpace > exit.invoke(null, true); > > ... we step into oblivion. > > The user agent for this terrible show-stopping surprise for my > application is: > "Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR > 2.0.50727)" > > Help! -- 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-tool...@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.
Re: [gwt-contrib] Re: GWT 2.0 dead in IE7?
@jgw,
Thanks for the rescue. I thought I was going crazy. Totally forgot about the
effects of doctype.
Nice to have: when the eclipse project wizard (or the app creator tool) is
updated to create a UiBinder-style Greeting template, it would be nice if
the doctype in the template html page was switched to standards-mode. Less
heart attacks for sleepy coders ;)
sfm
On Thu, Dec 10, 2009 at 9:18 AM, Joel Webber wrote:
> [duplicating my last message because it failed to post to groups/gwt last
> time]
>
>
> On Thu, Dec 10, 2009 at 9:11 AM, Joel Webber wrote:
>
>> The problem here is that you're using RootLayoutPanel explicitly, which
>> requires the use of a standards-mode doctype.
>>
>> * This widget will only work in standards mode, which requires
>> that
>> * the HTML page in which it is run have an explicit <!DOCTYPE>
>> * declaration.
>>
>> The good news is that these days you can just throw a
>> declaration at the top of the page to get there -- no need to dig through
>> the 37 different versions of [x]html doctypes. IE is particularly strange in
>> quirks mode, which is why you're seeing such a large difference.
>>
>> Hope that helps,
>> joel.
>>
>> On Wed, Dec 9, 2009 at 9:36 PM, Stuart wrote:
>>
>>> @bruce, @jwg, @rjrjr
>>>
>>> (and any other gwt'ers listening)
>>>
>>> I just posted about a fairly severe show-stopper for my application
>>> (that is, the app doesn't even finish onModuleLoad() in IE7 (see
>>>
>>> http://groups.google.com/group/google-web-toolkit/browse_thread/thread/952cdae8b5efa1d3
>>> )
>>>
>>> I thought it was likely due to my code. So I built a dead simple
>>> EntryPoint using the UiBinder wizard with a few touch ups:
>>>
>>> import com.google.gwt.core.client.EntryPoint;
>>> import com.google.gwt.core.client.GWT;
>>> import com.google.gwt.uibinder.client.UiBinder;
>>> import com.google.gwt.uibinder.client.UiField;
>>> import com.google.gwt.user.client.ui.Button;
>>> import com.google.gwt.user.client.ui.HTMLPanel;
>>> import com.google.gwt.user.client.ui.RootLayoutPanel;
>>> import com.google.gwt.user.client.ui.Widget;
>>>
>>> public class UiBinderTestForIE implements EntryPoint {
>>>
>>>private static UiBinderTestForIEBinder uiBinder = GWT.create
>>> (UiBinderTestForIEBinder.class);
>>>interface UiBinderTestForIEBinder extends UiBinder>> UiBinderTestForIE> {}
>>>
>>>@UiField Button button;
>>>@UiField HTMLPanel htmlPanel;
>>>
>>>public void onModuleLoad() {
>>>
>>>Widget w = uiBinder.createAndBindUi(this);
>>>RootLayoutPanel root = RootLayoutPanel.get();
>>>root.add(w);
>>>}
>>>
>>> }
>>>
>>> And here is the ui.xml
>>>
>>> http://dl.google.com/gwt/DTD/xhtml.ent";>
>>> >>xmlns:g="urn:import:com.google.gwt.user.client.ui">
>>>
>>>.important {
>>>font-weight: bold;
>>>}
>>>
>>>
>>>Hello,
>>>>> ui:field="button">User>> g:Button>
>>>
>>>
>>>
>>> When I launch this in Chrome / FF, I get what I expect. When launched
>>> in IE7, there is nothing on the page. Yet, the console reports that
>>> the module has been loaded.
>>>
>>> At first I thought it was a problem with the developer plugin in IE,
>>> so I compiled it and put it up on my App Engine sandbox:
>>> http://uibindertestforie.latest.emcode-dev.appspot.com and tested from
>>> two different machines. Works in FF/Chrome on both machines. Nothing
>>> in IE7 on either machine.
>>>
>>> What's the deal?
>>>
>>> Again, it could be my code. But, really? GWT 2.0 is dead in IE7? I
>>> can't actually believe it, so someone please tell me what I am doing
>>> wrong.
>>>
>>> Stuart
>>>
>>> [cross-posting to gwt, gwt-contrib]
>>>
>>> --
>>>
>>> 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.
>>>
>>>
>>>
>>
> --
> http://groups.google.com/group/Google-Web-Toolkit-Contributors
>
--
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-tool...@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.
GWT 2.0 dead in IE7?
@bruce, @jwg, @rjrjr
(and any other gwt'ers listening)
I just posted about a fairly severe show-stopper for my application
(that is, the app doesn't even finish onModuleLoad() in IE7 (see
http://groups.google.com/group/google-web-toolkit/browse_thread/thread/952cdae8b5efa1d3)
I thought it was likely due to my code. So I built a dead simple
EntryPoint using the UiBinder wizard with a few touch ups:
import com.google.gwt.core.client.EntryPoint;
import com.google.gwt.core.client.GWT;
import com.google.gwt.uibinder.client.UiBinder;
import com.google.gwt.uibinder.client.UiField;
import com.google.gwt.user.client.ui.Button;
import com.google.gwt.user.client.ui.HTMLPanel;
import com.google.gwt.user.client.ui.RootLayoutPanel;
import com.google.gwt.user.client.ui.Widget;
public class UiBinderTestForIE implements EntryPoint {
private static UiBinderTestForIEBinder uiBinder = GWT.create
(UiBinderTestForIEBinder.class);
interface UiBinderTestForIEBinder extends UiBinder {}
@UiField Button button;
@UiField HTMLPanel htmlPanel;
public void onModuleLoad() {
Widget w = uiBinder.createAndBindUi(this);
RootLayoutPanel root = RootLayoutPanel.get();
root.add(w);
}
}
And here is the ui.xml
http://dl.google.com/gwt/DTD/xhtml.ent";>
.important {
font-weight: bold;
}
Hello,
User
When I launch this in Chrome / FF, I get what I expect. When launched
in IE7, there is nothing on the page. Yet, the console reports that
the module has been loaded.
At first I thought it was a problem with the developer plugin in IE,
so I compiled it and put it up on my App Engine sandbox:
http://uibindertestforie.latest.emcode-dev.appspot.com and tested from
two different machines. Works in FF/Chrome on both machines. Nothing
in IE7 on either machine.
What's the deal?
Again, it could be my code. But, really? GWT 2.0 is dead in IE7? I
can't actually believe it, so someone please tell me what I am doing
wrong.
Stuart
[cross-posting to gwt, gwt-contrib]
--
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-tool...@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.
GWT 2.0 crash on IE7 - post-UiBinder setCellHeight with VerticalPanel
Environment: MS Windows, Eclipse 3.5 with GWT 2.0 plugin. Testing on: FF (Win/Mac), Chrome (Win/Mac), IE7(Win) Basic widget hierarchy: - EntryPoint loads a DockLayoutPanel via UiBinder. - in the center of the dock, loads a VerticalPanel - the VerticalPanel has 3 custom composite widgets in my app's namespace, each of which have to "appear" exclusively in the dock's center pane when certain events are fired Post-binding logic: - after the EntryPoint creates and binds the UI, we need to "turn off" 2 of the 3 custom widgets. - this is accomplished by the following code: // turn off widget 1 vPanel.setCellHeight(customWidget1, "0px"); customWidget1.setVisible(false); // turn off widget 2 vPanel.setCellHeight(customWidget2, "0px"); customWidget2.setVisible(false); // turn on widget 3 vPanel.setCellHeight(customWidget3, "100%"); customWidget1.setVisible(true); Error: In IE7, the first reload in DevMode crashes with: com.google.gwt.core.client.JavaScriptException: (Error): Invalid argument. number: -2147024809 description: Invalid argument. at com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript (BrowserChannelServer.java:195) at com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke (ModuleSpaceOOPHM.java:120) at com.google.gwt.dev.shell.ModuleSpace.invokeNative (ModuleSpace.java:507) at com.google.gwt.dev.shell.ModuleSpace.invokeNativeVoid (ModuleSpace.java:284) at com.google.gwt.dev.shell.JavaScriptHost.invokeNativeVoid (JavaScriptHost.java:107) at com.google.gwt.dom.client.Element$.setPropertyString$ (Element.java) at com.google.gwt.user.client.ui.CellPanel.setCellHeight (CellPanel.java:104) The next line in the stack trace is the first attempt at: vPanel.setCellHeight(customWidget1, "0px"); FF (Win/Mac), Chrome (Win/Mac) all do this properly. The IE7 dev plugin tells me gracefully that the server is disconnected. My eclipse console reports the above stack trace. The end result is I have no application in IE. (Now, someone is going to say: Why are you using VerticalPanels? Long story, but I have not found a suitable replacement in the new UI panels to handle sizing without becoming a PhD in CSS quirks.) As I trace through the code, I am looking at this path: - We programmatically set the cell height of the widget to 0px (allowed by CSS) from its parent vPanel - CellPanel.setCellHeight gets the widgetTd as an Element - Element.setPropertyString sets the property string of 'height' to '0px' - this method is JSNI that sets this[name] = value in the JavaScriptObject I lose the code for a little while as it delegates through to ModuleSpaceOOPHM(ModuleSpace).onLoad(TreeLogger). When we try to exit the onModuleLoad via line 374 of com.google.gwt.dev.shell.ModuleSpace exit.invoke(null, true); ... we step into oblivion. The user agent for this terrible show-stopping surprise for my application is: "Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 2.0.50727)" Help! -- 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-tool...@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.
TaskEngine sample patched for GWT 2.0 MS 2
All, [excuse the cross posting to gwt/appengine] The TaskEngine sample application (http://taskengine.googlecode.com) by jaimeyap is a Google Web Toolkit application that runs on App Engine (http://taskengine.appspot.com) but is especially designed for use on iPhone. TaskEngine depends on GWT Incubator (http://code.google.com/p/google- web-toolkit-incubator) for CssResource, which is now folded into the main GWT trunk with GWT 2.0 Milestone 2. (http://code.google.com/p/ google-web-toolkit/downloads/list?can=1&q=2.0+Milestone+2). I have patched the TaskEngine sample code to remove the dependency for the incubator jar, and use the updated annotations for CssResource and ClientBundle available in GWT 2.0 MS 2. The patch is located at: http://code.google.com/p/emcode/wiki/TaskEnginePatchGWT20MS2 I have posted a screencast of TaskEngine running in the iPhone SDK emulator at: http://www.youtube.com/watch?v=LuJi6nadVhU Stuart -- 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-tool...@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=.
Apple Guice: A demo of App Engine, GWT, MVP, Guice, GIN
All, Apple Guice is a demo App Engine application using GWT with MVP (via gwt-dispath and gwt-presener), dependency injection (GIN on the client, Guice on the server), and a sharded counter to track the number of visitors. Demo is available at: http://appleguice.latest.emcode-dev.appspot.com/ Source is available at: http://appleguice.googlecode.com/ Stuart P.S. Pardon my cross-posting on: gwt, appengine for java, gwt-dispatch and gwt-presenter --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
