[gwt-contrib] [google-web-toolkit] r9110 committed - Removed stale information in the Expenses Sample App README-MAVEN.txt...
Revision: 9110 Author: gwt.mirror...@gmail.com Date: Sat Oct 16 17:24:12 2010 Log: Removed stale information in the Expenses Sample App README-MAVEN.txt Review at http://gwt-code-reviews.appspot.com/1003801 http://code.google.com/p/google-web-toolkit/source/detail?r=9110 Modified: /trunk/samples/expenses/README-MAVEN.txt === --- /trunk/samples/expenses/README-MAVEN.txtWed Aug 25 11:12:04 2010 +++ /trunk/samples/expenses/README-MAVEN.txtSat Oct 16 17:24:12 2010 @@ -1,22 +1,15 @@ Generated by GWT WebAppCreator --- - -Congratulations, you've successfully generated a starter project! What next? - -- Option A: Import your project into Eclipse (recommended) -- -If you use Eclipse, you can simply import the generated project into Eclipse. -We've tested against Eclipse 3.4 and 3.5. Later versions will likely also -work, earlier versions may not. - -If the directory containing this file does not have a .classpath or .project -file, generate them by running 'ant eclipse.generate' - -Eclipse users will need to have the m2eclipse, or equivalent, pluigin installed. -Instructions for how to install the m2eclipse plugin can be found here: -http://m2eclipse.sonatype.org/installing-m2eclipse.html - -Eclipse users will also want to run mvn package before importing into Eclipse. -This will unpack the App Engine SDK to the local repository. +If you use Eclipse, you can simply import the generated project into +Eclipse. We've tested against Eclipse 3.5. Later versions will likely +also work, earlier versions may not. + +Eclipse users will need to have the m2eclipse, or equivalent, pluigin +installed. Instructions for how to install the m2eclipse plugin can +be found here: http://m2eclipse.sonatype.org/installing-m2eclipse.html + +Ensure Eclipse is configured to use Java 1.6 as this sample uses +AppEngine. In Eclipse, go to the File menu and choose: @@ -24,46 +17,41 @@ Browse to the directory containing this file, select Expenses. - + Click Finish. - + You can now browse the project in Eclipse. -To launch your web app in GWT development mode, go to the Project - Properties -and expand the Google menu item. From there: - - Navigate to App Engine item, select Use App Engine, and specify which App Engine - SDK to use. - - Navigate to the Web Appliation item, select This project has a WAR directory, - speicigy src/main/webapp, and uncheck Launch and deploy - - Navigate to Web Toolkit, select use Google Web Toolkit, and specify which - GWT SDK you want to use. - - Go to the Run menu item and select Run - Debug as - Web Application. - +To launch your web app in GWT development mode + + Go to the Run menu item and select Run - Run as - Web Application. + + - To load a set of initial data choose: LoadExpensesDB.html + + - To run the Expenses Application choose: Expenses.html + + - To run the Mobile version of the Expenses Application choose: +ExpensesMobile.html + When prompted for which directory to run from, simply select the directory that Eclipse defaults to. You can now use the built-in debugger to debug your web app in development mode. -If you supplied the junit path when invoking webAppCreator, you should see -launch configurations for running your tests in development and production -mode. - -- Option B: Build from the command line with Maven -- -If you prefer to work from the command line, you can use Maven to build your -project. (http://maven.apache.org/) Maven uses the supplied 'pom.xml' file -which describes exactly how to build your project. This file has been tested -to work against Maven 2.2.1 The following assumes 'mvn' is on your command +If you prefer to work from the command line, you can use Maven to +build your project (http://maven.apache.org/). You will also need Java +1.6 JDK. Maven uses the supplied 'pom.xml' file which describes +exactly how to build your project. This file has been tested to work +against Maven 2.2.1. The following assumes 'mvn' is on your command line path. -To run development mode, just type 'mvn gae:run'. +To run development mode use the Maven GWT Plugin. + + cd src/main/webapp; mvn -f ../../../pom.xml gwt:run To compile your project for deployment, just type 'mvn package'. For a full listing of other goals, visit: http://mojo.codehaus.org/gwt-maven-plugin/plugin-info.html - -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] [google-web-toolkit] r9111 committed - - Set GWT version to 2.1.0...
Revision: 9111
Author: gwt.mirror...@gmail.com
Date: Sun Oct 17 07:45:01 2010
Log: - Set GWT version to 2.1.0
- Added gwt version property
- Set gwt-servlet scope to runtime.
Review at http://gwt-code-reviews.appspot.com/1019801
http://code.google.com/p/google-web-toolkit/source/detail?r=9111
Modified:
/trunk/samples/expenses/pom.xml
===
--- /trunk/samples/expenses/pom.xml Fri Oct 15 05:42:32 2010
+++ /trunk/samples/expenses/pom.xml Sun Oct 17 07:45:01 2010
@@ -7,6 +7,7 @@
version0.1.0.BUILD-SNAPSHOT/version
nameexpenses/name
properties
+gwt.version2.1.0/gwt.version
roo.version1.1.0.M2/roo.version
spring.version3.0.3.RELEASE/spring.version
slf4j.version1.6.1/slf4j.version
@@ -54,13 +55,6 @@
urlhttps://repository.jboss.org/nexus/content/repositories/releases/url
nameJBoss Repo/name
/repository
-!--
-repository
-idgwt-repo/id
-
urlhttp://google-web-toolkit.googlecode.com/svn/2.1.0.M3/gwt/maven/url
-nameGoogle Web Toolkit Repository/name
-/repository
---
/repositories
pluginRepositories
pluginRepository
@@ -408,12 +402,13 @@
dependency
groupIdcom.google.gwt/groupId
artifactIdgwt-servlet/artifactId
-version2.1-SNAPSHOT/version
+version${gwt.version}/version
+scoperuntime/scope
/dependency
dependency
groupIdcom.google.gwt/groupId
artifactIdgwt-user/artifactId
-version2.1-SNAPSHOT/version
+version${gwt.version}/version
scopeprovided/scope
/dependency
dependency
@@ -625,7 +620,7 @@
configuration
logLevelINFO/logLevel
stylePRETTY/style
-gwtVersion2.1-SNAPSHOT/gwtVersion
+gwtVersion${gwt.version}/gwtVersion
runTarget/Expenses.html/runTarget
hostedWebapp${project.build.directory}/${project.build.finalName}/hostedWebapp
modules
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] [google-web-toolkit] r9112 committed - Adding 2.1.0 tag
Revision: 9112 Author: p...@google.com Date: Sun Oct 17 09:00:14 2010 Log: Adding 2.1.0 tag http://code.google.com/p/google-web-toolkit/source/detail?r=9112 Added: /tags/2.1.0 -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
Re: [gwt-contrib] Add Support for server side script selection in linker (issue941802)
Hello Unnur, That's a very good point, but I guess either inlining manually for a production deploy or making a linker for my specific case works fine. If I get a chance, I'll try and experiment with the server side selector to see if I can get it to work. Thanks again for all the info! -- Arthur Kalmenson On Wed, Oct 13, 2010 at 3:08 PM, Unnur Gretarsdottir unn...@google.com wrote: Hi Arthur - Yes - we probably could build it, but then you wouldn't be able to customize any of the aspects of that HTML page. Most people want something else on that page other than just the GWT module include (even if it's something as simple as setting the title tag in the head to something specific). In general, we sort of count on people who are trying to do semi-advanced optimizations to be able to do some work, like adding the contents of the nocache.js file to the initial html file themselves. Alternatively - you could subclass the linker and have it do what you want for your specific project since you would know exactly what other stuff you might want in your particular html file. I also just wanted to reiterate one more time that support for server side selection is not coming soon. We are (experimentally) adding the ability for people do server side selection, assuming that they do some configuration themselves. Specifically, you'll have to subclass the linker to turn on some of the options. More significantly, you'll need parse the configuration-mappings.txt file to determine the correct md5 file and dynamically generate your HTML with a script tag pointing to that md5 file. Doing this is harder than inlining the selection script, so if your primary interest is in cutting out one of the round trips, I'd recommend that you go ahead with getting that working first. Although we may add it eventually, there is no current plan to make server side selection available out of the box. - Unnur On Wed, Oct 13, 2010 at 9:28 AM, Arthur Kalmenson arthur.k...@gmail.com wrote: Hey Unnur, You're right, gwt doesn't have access to the initial HTML page, but I wonder if it'd be possible to build a linker to make that dynamically generated page. Doesn't the linker have access to what gets generated in the nocache.js? Theoretically you could just output a simple HTML page that includes its contents. Then again, if this server side selection is coming soon (gwt 2.2?), building this linker won't make much sense. Thanks again for all the info! All the best, -- Arthur Kalmenson On Mon, Oct 11, 2010 at 1:03 PM, Unnur Gretarsdottir unn...@google.com wrote: Hi Arthur - Are you asking if there's an existing linker for the inlining of your selection script? If so, no - the linker has no access to the contents of your initital html page. What you need to do is, rather than serve a static html page, your server will have to dynamically generate it, by reading the content of the nocache.js file and putting it directly in the html which is served on the initial request. In theory, if you rarely release your code, you could do this manually - basically, every time you do a gwt compile, manually copy the contents of nocahce.js into the initial html page. - Unnur On Fri, Oct 8, 2010 at 12:41 PM, Arthur Kalmenson arthur.k...@gmail.com wrote: That's a great idea Unnur. Is there an existing linker for this or would I have to build it (it seems like something the linker would do, if I understood them correctly)? -- Arthur Kalmenson On Fri, Oct 8, 2010 at 1:57 PM, Unnur Gretarsdottir unn...@google.com wrote: Hi Arthur - This is, and will probably remain for some time, experimental. In order to use this, you'll need to extend the linker and change the variable - also, you'll need to write your own server code to parse the compilation mappings text file and decide which permutation you want to use. Sorry not to have a better answer - we did want to make sure that this new linker is set up to support this sort of linking, but it is not currently a feature that we are officially releasing. FYI - if your primary concern is the double round trips, as opposed to the size of the permutation selection JS, then an easy solution for you is to simply inline the foo.nocache.js script into your page rather than requesting it using a script tag - Unnur On Mon, Oct 4, 2010 at 2:06 PM, Arthur Kalmenson arthur.k...@gmail.com wrote: Wow, this is great! I'm guessing this means we can cut the startup round trips to one? Is this going into GWT 2.1? Exciting stuff. -- Arthur Kalmenson On Fri, Oct 1, 2010 at 6:09 PM, unn...@google.com wrote: Reviewers: jgw, Description: Add Support for server side script selection in linker Please review this at http://gwt-code-reviews.appspot.com/941802/show Affected files: A dev/core/src/com/google/gwt/core/ext/linker/impl/PermutationsUtil.java A
