Issue 5041 - google-web-toolkit - When removing GWT or App Engine nature, give users th... - 0 views
-
Right now, when the user removes the GWT/App Engine nature from the project, if they have a SDK container on their build path, it is collapsed into its individual jars, and they are added to the classpath. In some cases, users do not expect this behavior (for example, if they mistakingly added the wrong nature).
Building a GAE+GWT application using the best practices, Part 2 « Reminiscent... - 0 views
Building a GAE+GWT application using the best practices, Part 1 « Reminiscent... - 0 views
Forty-Two: 1st look at App Engine using JDO persistence capable classes over GWT RPC - 0 views
Guest Post Online - 0 views
-
Article Writing & Guestpost You Can Join this Site for Your Article & guest post, Just Easy way to join this site & total free Article site. This site article post to totally free Way. Guest Post & Article Post live to Life time only for Current & this time new User. http://guestpostonline.com
Is _ah/openid_logout going to be a stable logout URL - Google App Engine | Google Groups - 0 views
-
It was one of the other ways to do it, I just wanted to avoid more code in my architecture just to do this (MVP has the disadvantage of added boilerplate for simple tasks like this one). Anyway I found a workaroud, passing the URL in an invisible div in my page and then reading and populating another field in my page using GWT RootPanel.get(id), using different ids for various parts of the page.
Learning Google App Engine and GWT Best Practices: Dumbassing things up - 0 views
Google Web Toolkit Blog: How to Use Google Plugin for Eclipse with Maven - 0 views
-
to enable both Maven and GPE for the same project. This article explains how to do that.
-
Mavenizing an existing GPE project To use Maven with an existing GPE project, follow these steps:
App Engine Fan: Schluesselmeister - 0 views
Handling very large lists of objects without paging? - Stack Overflow - 0 views
-
I have a class which can contain many small elements in a list. Looks like: public class Farm { private ArrayList<Horse> mHorses;} just wondering what will happen if the mHorses array grew to something crazy like 15,000 elements. I'm assuming that trying to write and read this from the datastore would be crazy, because I'd get killed on the serialization process. It's important that I can get the entire array in one shot without paging, and each Horse element may only have two string properties in it, so they are pretty lightweight: public class Horse { private String mId; private String mName;} I don't need these horses indexed at all. Does it sound reasonable to just store the mHorse array as a raw Text field, and force my clients to do the deserialization? Something like: public class Farm { private Text mHorsesSerialized;} then whenever the client receives a Farm instance, it has to take the raw string of horses, and split it in order to reinstantiate the list, something like: // GWT client perhapsFarm farm = rpcCall.getMyFarm();String horsesSerialized = farm.getHorses();String[] horseBlocks = horsesSerialized.split(",");for (int i = 0; i < horseBlocks.length; i++) { // .. continue deserializing the individual objects ...} yeah...
Schluesselmeister (App Engine Fan) - 0 views
‹ Previous
21 - 40 of 56
Next ›
Showing 20▼ items per page