GAE - GWT
Get flash to fully experience Pearltrees
GAE sur les blogs
GWT sur les blogs
Une introduction à la mobilité sur le Web - Blog - Veille - Clever Age
Cet article constitue l’introduction d’une série de billets sur la mobilité, qui sera publiée dans les semaines à venir sur le blog de Clever Age. Pas facile de trouver un angle d’attaque, le sujet est large, il adresse de nombreuses problématiques fonctionnelles, marketing, technologiques.... Je pourrais classiquement commencer par rappeler les chiffres, mais je prends l’hypothèse que si vous lisez ce billet, vous êtes déjà convaincus de l’intérêt qu’il faut porter à la mobilité et à son potentiel, et surtout de la nécessité de l’inscrire dans la stratégie globale des SI de l’entreprise voire de l’entreprise elle-même. La sacro-saint Google l’annonce depuis un moment, son CEO l’a encore exprimé clairement lors de la keynote de Barcelone en février dernier : twitté par @GoogleTravel le 19 octobre 2010 Considérons donc que la question n’est plus de savoir s’il faut initier une stratégie mobile mais de savoir par quelle porte entrer.
Google App Engine - Aperçu (Blog - Veille - Clever Age)
Le Google App Engine permet à n’importe quel développeur Java (mais également Python) d’héberger son application en utilisant le cloud de Google. Qu’apporte cette solution de cloud made-in Google ? Quelles sont ses limites ? SaaS (Software As A Service) : Comme Gmail ou Salesforce, le logiciel est hébergé sur des serveurs qui ne sont pas possédés par la société (ou le particulier) qui s’en sert.De MacodaWiki. L'objectif de cette page est de tracer ce que j'ai compris et retenu pour pouvoir le refaire dans x semaines, quand j'aurais tout oublié ;-) Attention, il faut d"abord télécharger MyLyn (voir cette page ).
Google App Engine - Programmer avec GWT - MacodaWiki
Update: If you like following a video more than reading some text, Mano Marks from Google created a screencast about how to get started with App Engine . Since Google published their App Engine , I am highly interested in it. Too bad I didn't get an App Engine account, but at least I am able to test it locally... As a fan of eclipse and being new to Python development, I searched for an eclipse Python extension and finally found PyDev sourceforge project .
The Daily Profeth: Google App Engine & eclipse (PyDev)
Part 1: Getting started « GWT / GAE development blog
Please read the Read these first pages before continuing. If you need help with importing project, setting up version control or whatever, please have a look at the Help / Howto page and post comments on that page if you need assistance. Note: To get all the libraries needed for this project, please follow the instructions at: Hive Development Best Practice Hello World .
Please read gwt-presenter explained first! After doing some research on gwt-presenter and browsing the source code, I realized that it had more features than I orginally thought. Besides an implementation of the Presenter/View paradigm, gwt-presenter also integrates the eventbus and history handling. We will see later in this/next post how it all integrates very nicely. I decided to divide this topic into two posts for better structural overview. This part handles the MVP pattern on a widget level.
Part 2: MVP pattern 1 « GWT / GAE development blog
Part 3: MVP pattern 2 « GWT / GAE development blog
Please read gwt-presenter explained and step 1 before this part. In the previous post we saw an example of how to apply the MVP pattern to display person details. Now we will move to the next level and look at events, place requests, widget containers and binding it all together. In a typical web scenario, we will have a center container where we add widgets to present our content. We must be able to add and delete widgets from this container, as well as setting visibility on added widgets. gwt-presenter provides a nice mechanism for this via WidgetContainerPresenter and WidgetContainerDisplay. Note that this is currently only available in the svn, not in the published 1.0.0 jar file.Let's convert our code to use dependency injection with the help of Google Guice/GIN. If you have never heard about dependency injection or Guice/GIN before, read: Wikipedia on DI , Guice , GIN . We will be using Guice on server side and GIN on client side. This post is about GIN only. We start by creating a new package called gin in our client package.
Part 4: DI with GIN « GWT / GAE development blog
Part 5: RPC with gwt-dispatch « GWT / GAE development blog
Now that we have GIN setup, we will integrate the gwt-dispatch library to handle our client/server communication. We will also enable Guice for dependency injection on server side. What is gwt-dispatch?
In this part we will implement basic database handling based on the GAE datastore and the JDO platform. I will not go into any details on GAE datastore or how JDO works here, since this information is well documented in GAE docs , JDO docs and DataNucleus docs . void createTestEntities(); We have defined methods to retrieve single model instances by key, or a list of models based on a custom query. We also define a method to save/update models. Nothing strange here.
Part 6-1: Datastore/JDO « GWT / GAE development blog
Part 6-2: Entities #1 « GWT / GAE development blog
In this part we will take a look at our database model and entity relationships. We will build the entire entity relationship tree in steps and this post will cover the first step where we look at how teams, persons and players relate to each other. In future posts, we will add new entities and relationships to the tree until we have satisfied all the use cases from a database perspective. Ok.As I've mentioned earlier, there has been some stuff going on in the replace-branch for gwt-presenter. I have now investigated that a bit further and decided to make an upgrade, so that's what this post will be about. I have built the library from source (as of Feb 12, 2010) and you can download the jar file here . It's version 1.1.1 and the last change on the branch as of now was Jan 10, 2010. The changes on the replace-branch is mainly related to places and history handling.
Part 7: gwt-presenter upgrade « GWT / GAE development blog
We have reached a point in the project where we need to define our application level layout. We will implement our own version of WidgetContainerPresenter in this post to support this. My first attempt at this was to extend WidgetContainerPresenter, but that involved too many workarounds, so our classes will extend BasicPresenter directly instead. We will also modify our BasePresenter to add logic for lazy loading. But before we go into that, let's discuss the application level layout structure.
Part 8: MVP refactoring « GWT / GAE development blog
There are different ways to solve this, but I think what Thomas Broyer suggests here is the cleanest solution that integrates nicely with GWT. What we are going to do is to add an invisible div to our HTML file that contains our login form, and then we fetch the elements from the DOM by id in our LoginView. I have used a table here to align the components, but you can use any style you want as long as the login form is defined correctly.