Skip to main content

Home/ GWT - Samples/ Group items tagged http

Rss Feed Group items tagged

Esfand S

Maven and GWT - a never ending story? - 0 views

  • One of the cool things on GWT is, that you cannot just use Java as a programming language, you can also use all your cool and great tools, like Eclipse, JUnit, or build tools like Ant, Gradle or Maven. Sure you can, but this Maven thing seems not to be so easy. So lets take a look on how to solve it.
  • keep the structure clean by separating client (GWT) and server (maybe Java or even any other language) code in a strict way. This means, that your GWT code will not be in the same project as your Java EE web descriptor (web.xml).
  • If you have done the import, our photo-album-server module will be a Dynamic Web Project in Eclipse and you can add it to your Tomcat, JBoss or whatever server runtime. You can start it and run it as you like.
  • ...2 more annotations...
  • the GWT compiler configuration is done in the web application project. This is the best place, since you can just change the dependency and the GWT module and the compiler will compile a completly different GWT client. With other words, the web application pulls the right JAR out from the Maven space and uses it. This is much better than letting another project compile some JavaScript and than copy the JavaScript to your web application, or whatever solution you might find. So just add the GWT Maven plugin configuration and dependency below to the photo-album-server module’s POM.
  • our project is just a simple Java project.
Esfand S

My First GWT IGoogle Gadget, What do you think? - Google Web Toolkit | Google Groups - 0 views

  • I built a basic and more complex gadgets which are demoed here. More Info here: http://code.google.com/p/gwt-examples/wiki/project_Gadget?ts=12722477... Basic Gadget is released here: IGoogle Directory: http://www.google.com/ig/directory?url=demogadgetmathflashcard.appspo...
Esfand S

http://code.google.com/p/google-web-toolkit/wiki/RequestFactoryPlusPaths - 0 views

shared by Esfand S on 27 Sep 10 - Cached
  •  
    "> its one project example? As the name implies [1], it's where new features are being developped "in the open": - Enterprise widgets (complete rewrite of the incubators PagingScrollTable and the like) - data binding http://code.google.com/p/google-web-toolkit/wiki/RequestFactoryPlusPaths - lightweight collections Note that the current development seems to have moved over to / branches/2.1/bikeshed instead of /trunk/bikeshed [1] http://en.wikipedia.org/wiki/Bikeshed "
Esfand S

Can anyone provide a step by step maven + gwt mvp tutorial? - 0 views

  • There is an outdated archetype which creates a very simple Gwt project without tests nor RPCs. Unfortunately the generated pom.xml is for old gwt versions and needs that you do a bunch of changes by hand.   mvn archetype:generate  -DarchetypeGroupId=org.codehaus.mojo \    -DarchetypeArtifactId=gwt-maven-plugin  -DarchetypeVersion=1.1 \    -DgroupId=com.foo  -DartifactId=myApplication - Lately I have sent a patch to gwt which adds the ability to generate pom.xm to webAppCreator. But the patch is under review and it wont be available until a new gwt version (in the case it is included). http://gwt-code-reviews.appspot.com/397801/show - So, I recommend you to get the pom.xml from a working application and use it as a template for your project. Some days ago, I  ported the google contacts example application in order to use available libraries for MVP and add tests for all the code. I think It should be a good point for starting your project: http://gwt-workshop.googlecode.com/files/GwtWsMvpContacts.zip
Esfand S

developerlife - Tutorials » GWT Tutorial - Managing History and Hyperlinks - 0 views

  • GWT provides a way for your apps to hook into the browser’s history mechanism, so that you can control what happens when a user hits Back or Forward in their browser. You can also programmatically manipulate the browser’s history, and even create hyperlinks in your apps that can hook into the browser’s history mechanism. You can even intercept these hyperlinks when a user clicks on them, instead of having the browser handle it, or both.
  • tokens allow you to map a specific state of your application to what’s in the browser’s history stack. When your app starts up, the stack is empty. When the user interacts with your app, and clicks on something, you can add tokens to this stack (either via hyperlinks or calls to History.newItem(String token)). This lets you change the history. You can also attach a HistoryListener to your app which will allow your app to respond to this change of history.
  • Why do it this way? I mean, if your app generates the tokens themselves, why not just change the state instead of dealing with receiving a history change notification (that you just initiated) and then respond to it? A good reason for taking the trouble to do this, is to allow people to bookmark certain states of your application. If you don’t want them to do this, then you can just plug into the history mechanism, and then ignore all the history state change events, and make it so that the Back or Forward button does not mess your app up.
  • ...7 more annotations...
  • If there are tokens in the history stack, and the user presses the Back button, or you invoke the History.back() method, then the following steps occur: a token is retrieved from the top of the stack this token (which is just a String) is then passed to your HistoryListener implementation, and this is how you know that the Back button is pressed. You then have to parse that token and change the state of your application to match what this token represents to your app.
  • no matter what happens, all these Back/Forward actions (whether initiated programmatically by your app, or by a user) ends up calling your HistoryListener’s onHistoryChanged(String token) method, which can act as a traffic cop of your state machine. You are in control of defining what a token is, and how it should map to various states in your application. You can encode parameters in the token and then parse them out later, to understand what your app is supposed to do now.
  • If you noticed the change in the browser’s displayed URL, when a hyperlink with a history token is clicked, then can see how the user is able to bookmark a specific state in your app… the token is simply added to the URL in the browser prefixed with a “#”. So, is it possible to add your own history token by typing in the URL for your app and just appending “#mynewtoken” to it? Yes! This is how GWT handles people bookmarking specific states of your application. One thing to keep in mind is that if you end the browser session, and then come into the app, then your app will have to process the initial history state, and it will have to check to see if there is “#mynewtoken” passed in the URL to the browser, and then adjust it’s state accordingly
  • you can hook into this mechanism and make it possible for the app to go to a particular state or load a particular resource or perform a function based on what is passed as a token to the URL.
  • You can use pass parameters to your app via the URL (here’s a coding quickie that shows you how), and you can use it along with tokens, but it’s bit confusing to use both.
  • let’s use this URL as an example: http://localhost:8888/Sample.Client/index.html#link2token?p1=v1&p2=v2 When you run the app with this URL, you will get the following string as the token: “link2token?p1=v1&p2=v2“. So as you can see it’s not a great idea to mix the two. This is the kind of URL that’s generated by the GWT Hyperlink class, so you can’t really mix and match query strings with history tokens.
  • If you want to create the URL yourself, then you can pass history tokens and query strings. In order to do this, you have to make sure to place the query string (?p1=v1&p2=v2) before the “#” in the URL and it will work. If you use this URL as an example: http://localhost:8888/Sample.Client/index.html?p1=v1&p2=v2#link2token When you run the app with this URL, you will get the following string as the history token: “link2token“. And a call to GWTUtils.getParamString() will return “?p1=v1&p2=v2“.
John Smith

Paper Shopping Bags Can Advertise My Brand - 1 views

I am so happy with Express Retail Packaging because they were able to give me the right color and design for my paper shopping bags and my business logo was perfectly printed on the paper bags. I a...

paper shopping bags

started by John Smith on 16 Sep 11 no follow-up yet
Esfand S

App Engine Fan: ServiceAsync? We don't need no stinking... - 0 views

  • Let's give it a try and build an browser-only app that sends a user query to Google base and displays the results in our application.
Esfand S

Anchors in GWT | GWT Tutorials - 0 views

  • The primary reason why I am writing a specific tutorial on the Anchor widget is because without it you will not be able to easily use GWT’s history framework
  • let’s talk about a hash, and how to use them. Since GWT is an easy way to use AJAX we are going to stay within that realm when talking about the hash. A hash is simply anything with the pound symbol in front of it. For example “#gwt” is a hash that points somewhere in your web application. We are going to learn more about the hash in the tutorial on GWT history.
  • Anchor anchor = new Anchor("GWT Tutorials", "http://www.gwttutorials.com?action=hello", "_blank");   String paramAction = Window.Location.getParameter("action");   //Do something with paramAction.
  • ...1 more annotation...
  • So basically the way this works is that you can create a new Anchor widget and append a parameter to it. In your onModuleLoad function you can get the parameter from the window’s location, and then use this parameter to load a different state of your application. To create a parameter just append a “?” then the name of the parameter and finally the value of the parameter. Also you can include multiple paramters by using the “&” symbol, so for example you could do this: “?action=hello&noaction=bye”.
Esfand S

Tell the FCC - 0 views

Esfand S

GWT, Blobstore, the new high performance image serving API, and cute dogs on ... - 0 views

  • Blobstore crash course It’ll be best if we gave a quick refresher course on the blobstore before we begin. Here’s the standard flow for a blobstore upload: Create a new blobstore session and generate an upload URL for a form to POST to. This is done using the createUploadUrl() method of BlobstoreService. Pass a callback URL to this method. This URL is where the user will be forwarded after the upload has completed. Present an upload form to the user. The action is the URL generated in step 1. Each URL must be unique: you cannot use the same URL for multiple sessions, as this will cause an error. After the URL has uploaded the file, the user is forwarded to the callback URL in your App Engine application specified in step 1. The key of the uploaded blob, a String blob key, is passed as an URL parameter. Save this URL and pass the user to their final destination
Esfand S

Exploring data binding with Gwittir | GWT Site - 0 views

  • Gwittir is a library for GWT that provides a lot of interesting features including data binding, animation, reflection, and more. To help me learn more about this library, I decided to take it a spin and create a small GWT application to experiment with Gwittir’s data binding capabilities.
  • It allows you to glue together your user-interface widgets with the properties on your domain model. Whenever a user does something to a bound widget, its associated property in the model will be updated automatically. The binding is bi-directional as well,
1 - 20 of 201 Next › Last »
Showing 20 items per page