Re: GWT seems deprecated according to Thoughtworks
I am also quite deceived by the fake-arguments from M. Fowler... As a user of GWT since 1.6, i can say that i would not have acheived all the applications i wrote by writing pure Javascript. Neither would i be able to write big native applications by writing pure assembler (even macros would not help much in that case ;)) Of course, as with any technology, there are caveats, and weak points - and as always, to gain mastery over the tool, one has to know very well the platform it is build to run on (in that cas the browser - and i had never advocated that by using GWT you would not need to know the Web platform and JavaScript). But providing a typed language, the IDE debugging and developping tooling is just too precious to build complex big applications ! Of course, before beginning a project, one has to carefully choose the tools to work with, by having the long-term vision about the result one wants to obtain. I would not build a static web page with GWT, neither a simple web form (the kind of problematics Angular demonstrations are working on). When i use GWT, it is often to build complex applications - those i would have written 10 years ago with C++ natively on Windows. For me GWT is a perfect match for many projects i work on. What should be improved IMHO in GWT are those points (not exhaustive...) : - supporting other languages (C#, Clojure, Scala ...), leveraging the compiler (which should be more modular i think), - invest a lot in SDBG, the tool to debug with the same experience as with DevMode Thanks for the discussion ;) Arnaud Tournier LTE Consulting -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: Visibility problems when using css.InterfaceGenerator
just ran into this issue with gwt 2.6.0 and the css generation controlled
by gwt-maven-plugin 2.6.0
Is there a fix yet? is there some option to set to make the interface
public?
I guess I will implement your workaround extending the protected interfaces
with a public one, but I also would prefer to not have to do that.
On Friday, April 1, 2011 10:21:57 AM UTC+2, Raphael Bauer wrote:
On Wed, Mar 30, 2011 at 12:07 PM, Thomas Broyer t.br...@gmail.com
javascript: wrote:
Every member of an interface can only be public (and is implicitly so,
without the need to explicitly use the 'public' keyword), including inner
interfaces.
http://java.sun.com/docs/books/jls/third_edition/html/interfaces.html#9.5
Thanks Thomas. That makes total sense.
But the problem are not the members of the interface, but the
visibility of the interface itself I guess
http://java.sun.com/docs/books/jls/third_edition/html/interfaces.html#9.1.1
).
In my opinion
interface MyGeneratedCssInterface extends CssResource {
is quite different to
public interface MyGeneratedCssInterface extends CssResource {
Maybe my explanation of the problem was not the best. Sorry.
Best,
Raphael
--
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-we...@googlegroups.com
javascript:.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com javascript:.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
Re: Transition from Web to Mobile Web
What do you mean RPC will break? Will it be deprecated? Thanks! David. On Monday, August 11, 2014 11:47:36 PM UTC+8, Joseph Lust wrote: Make sure you've got a plan for forcing mobile users to update their app when you make new releases. Remember that RPC will break on the next release. If you don't have a graceful means to fail up for users, they will not have a good experience. Since you're not MVP, now might be a good time to do so. Otherwise, you're going to have to keep doing everything twice for your entire UI stack. MGWT and GWTP make these pretty easy to implement. Sincerely, Joseph -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
asynchronous gwt tree (Can't remember open nodes)
I've developed an asynchronous gwt tree, which means the whole tree is not
loaded from the begining when the application is started.
Nodes are loaded as you open up the tree deeper.
This was developed to minimize caching,and reduce time to start application.
The down side is that when I'm opening my tree to a certain depth, and then
close the root, the tree doesn't remember which nodes were open since its
asynchronous.
I was trying to keep a map of 'paths' open, however it would not cover all
pissiblities.
I'm looking for ideas as to how I can remember which nodes were open, or
maybe some gwt configuration I'm not aware of.
Thank you, please see my code attached.
package com.corena.lifeweb.gwt.client.modules.TOC;
import java.io.Serializable;
import java.net.URLEncoder;
import java.util.ArrayList;
import java.util.HashMap;
import java.util.List;
//import com.treecell.TreeCell.ColorCell.Templates;
import com.aerosoftsys.digidocCMS.TOC.TOC_Item;
import com.corena.lifeweb.gwt.client.RpcClient;
import com.google.gwt.cell.client.AbstractCell;
import com.google.gwt.core.client.EntryPoint;
import com.google.gwt.core.client.GWT;
import com.google.gwt.resources.client.ImageResource;
import com.google.gwt.safecss.shared.SafeStyles;
import com.google.gwt.safehtml.client.SafeHtmlTemplates;
import com.google.gwt.safehtml.shared.SafeHtml;
import com.google.gwt.safehtml.shared.SafeHtmlBuilder;
import com.google.gwt.user.cellview.client.CellTree;
import
com.google.gwt.user.cellview.client.HasKeyboardSelectionPolicy.KeyboardSelectionPolicy;
import com.google.gwt.user.cellview.client.TreeNode;
import com.google.gwt.user.client.Window;
import com.google.gwt.user.client.rpc.AsyncCallback;
import com.google.gwt.user.client.ui.AbstractImagePrototype;
import com.google.gwt.user.client.ui.ImageBundle.Resource;
import com.google.gwt.user.client.ui.RootPanel;
import com.google.gwt.user.client.ui.TreeImages;
import com.google.gwt.user.client.ui.VerticalPanel;
import com.google.gwt.view.client.AsyncDataProvider;
import com.google.gwt.view.client.HasData;
import com.google.gwt.view.client.TreeViewModel;
public class TreeCell implements EntryPoint {
private static RpcClient rpc = RpcClient.getInstance();
// Create a data provider.
static class MyDataProvider extends AsyncDataProviderTOC_Item{
private TOC_Item dir;
public MyDataProvider(Object currDir){
dir = (TOC_Item)currDir;
}
@Override
protected void onRangeChanged(final HasDataTOC_Item display) {
//com.google.gwt.user.client.Window.alert(Testing Closing2);
rpc.getValueObject(com.corena.lifeweb.gwt.server.TOC.TOC_ItemProcessor,
getSubItem, new Serializable[]{dir}, new AsyncCallbackSerializable(){
public void onFailure(Throwable caught) {
//show error message as popup
com.google.gwt.user.client.Window.alert(Error in Loading TOC: + dir);
}
public void onSuccess(Serializable _result) {
if (dir != null)
{
node = dir.getName();
if (!openDirs.contains(node))
{
openDirs.add(node);
}
//com.google.gwt.user.client.Window.alert(Node: + node);
String path = ;
for (int i = 0 ; i openDirs.size() ; i++)
{
if (!openDirs.get(i).equals(ROOT))
{
path = path + / + openDirs.get(i);
}
}
com.google.gwt.user.client.Window.alert(Path: + path);
setPath(ROOT + path + /, rootDir);
}
ListTOC_Item result = (ListTOC_Item)_result;
display.setRowData(display.getVisibleRange().getStart(), result);
// com.google.gwt.user.client.Window.alert(Open String: + open );
String open = newopen.substring(0, newopen.indexOf('/'));
for (int i = 0; i result.size(); i++){
String treeopen = result.get(i).getName();
if (open.equals(treeopen)){
newopen = newopen.substring(newopen.indexOf('/') + 1);
rootNode = rootNode.setChildOpen(i, true);
}
}
}
});
}
};
static class DirectoryCell extends AbstractCellTOC_Item {
interface Templates extends SafeHtmlTemplates {
//@SafeHtmlTemplates.Template(input type='text'
value='tc-'button type='button'Search/button)
@SafeHtmlTemplates.Template()
SafeHtml cell(SafeStyles styles, SafeHtml value);
}
interface Templates2 extends SafeHtmlTemplates {
@SafeHtmlTemplates.Template()
SafeHtml cell(SafeStyles styles, SafeHtml value);
}
// private static Templates templates = GWT.create(Templates.class);
// private static Templates2 templates2 = GWT.create(Templates2.class);
@Override
public void render(Context context, TOC_Item value, SafeHtmlBuilder sb)
{
GWT support for Chromium OS
I would like to know the GWT support for Chrome OS. For more info: https://groups.google.com/d/msg/google-web-toolkit/AYDbClS-fGQ/RF7526B2egsJ -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT support for Chromium OS
GWT supports Chrome and thus it should support Chrome OS without issues. If your Gradebook2 thing doesn't work then you better ask the Gradebook2 developers. Maybe they need to update the libraries they use. -- J. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
GwtBootstrap3 v0.8 Released!!
Hey guys, Just wanted to announce that we released a big update to GwtBootstrap3. You can find the zip and release notes here: https://github.com/gwtbootstrap3/gwtbootstrap3/releases. Thanks, Joshua -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT support for Chromium OS
Thanks for reply. On Tuesday, August 12, 2014 3:36:59 PM UTC+5:30, Chaitanya Kumar Ch wrote: I would like to know the GWT support for Chrome OS. For more info: https://groups.google.com/d/msg/google-web-toolkit/AYDbClS-fGQ/RF7526B2egsJ -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT seems deprecated according to Thoughtworks
My comments to ThoughtWorks radar (I guess they are not from Martin Fowler, but from some more novice JS developer): write Swing-like Java code... GWT widgets are much simpler and cleaner than Swing. But you don't have to use GWT widgets - you can use UI Binder with pure HTML and style it with CSS... Second, if the JavaScript doesn’t behave exactly as you want you will have to hack the generated code. This comment shows, that the writer has no deep knowladge of GWT. I've been using it since 2008 on MANY projects and never needed to hack the generated code. Third, using Java to generate JavaScript means that you can’t take direct advantage of the powerful features of JavaScript or numerous libraries such as JQuery. This is also not true. On one of my project I've integrated JQuery and GWT. Finally, the JUnit support is quite limited, for example code using reflection cannot be tested. Please show me your JavaScript code with reflection you would like to test... :-) I rarely use reflection anyway... First, in many ways, JavaScript is more powerful and expressive than Java This is a very subjective one. I feel exactly the other way around... :-9 Secondly, it is impossible to hide a complex abstraction difference like that from event-driven desktop to stateless-web without leaky abstraction headaches eventually popping up. Stateless web means request-based web apps, which is very bad for me. I like client based event-driven UI (AJAX / GMail-like). Third, it suffers from the same shortcomings of many elaborate frameworks, where building simple, aligned applications is quick and easy, building more sophisticated but not supported functionality is possible but difficult, and building the level of sophistication required by any non-trivial application becomes either impossible or so difficult it isn’t reasonable. Once again the author show it has no deep knowledge of GWT. With GWT you can build very complex apps in a structured way. Everything is type and compile-time checked... And some have said before me: GWT is not perfect, but up until now I haven't seen any better alternative... -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT seems deprecated according to Thoughtworks
Generally I agree with most of the comments, GWT is trying to bring sanity (which is good) to an insane platform HTML/CSS/JS essentially a document viewing platform gone mad. However 1) GWT widgets are not simpler than Swing. I have done Qt (that's sane), Swing (so and so with occasional insanities and weird memory leaks) and GWT (platform is insane), In Qt and Swing I was doing pixel hunting while I was learning the platform. In GWT I am always doing it. Not a GWT fault per se but still I don't think it is true to state that GWT is simpler that swing in its widgets (i.e easier layout, clear parent child relationships) 2) When the author speaks about the powerfulness of javascript I think he is referring to something like this http://www.paulgraham.com/avg.html . I don't know Lisp but supposedly javascript took its closures from scheme, a Lisp dialect, so that makes javascript pretty powerful according to the link I provided. Got it. In the mean time I simply cannot live without a compiler and strong type checking. I can't live, I can't maintain. 3) Stateless: I don't understand how the author managed to connect event driven GUI (which is good) with stateless. Stateless is good. The opposite is stateful. Stateful means the server knows stuff about the client and has some state to track him. Stateful doesn't scale. Stateles does scale. Vassilis On Tue, Aug 12, 2014 at 3:34 PM, Marko marko.kra...@cursor.si wrote: My comments to ThoughtWorks radar (I guess they are not from Martin Fowler, but from some more novice JS developer): write Swing-like Java code... GWT widgets are much simpler and cleaner than Swing. But you don't have to use GWT widgets - you can use UI Binder with pure HTML and style it with CSS... Second, if the JavaScript doesn’t behave exactly as you want you will have to hack the generated code. This comment shows, that the writer has no deep knowladge of GWT. I've been using it since 2008 on MANY projects and never needed to hack the generated code. Third, using Java to generate JavaScript means that you can’t take direct advantage of the powerful features of JavaScript or numerous libraries such as JQuery. This is also not true. On one of my project I've integrated JQuery and GWT. Finally, the JUnit support is quite limited, for example code using reflection cannot be tested. Please show me your JavaScript code with reflection you would like to test... :-) I rarely use reflection anyway... First, in many ways, JavaScript is more powerful and expressive than Java This is a very subjective one. I feel exactly the other way around... :-9 Secondly, it is impossible to hide a complex abstraction difference like that from event-driven desktop to stateless-web without leaky abstraction headaches eventually popping up. Stateless web means request-based web apps, which is very bad for me. I like client based event-driven UI (AJAX / GMail-like). Third, it suffers from the same shortcomings of many elaborate frameworks, where building simple, aligned applications is quick and easy, building more sophisticated but not supported functionality is possible but difficult, and building the level of sophistication required by any non-trivial application becomes either impossible or so difficult it isn’t reasonable. Once again the author show it has no deep knowledge of GWT. With GWT you can build very complex apps in a structured way. Everything is type and compile-time checked... And some have said before me: GWT is not perfect, but up until now I haven't seen any better alternative... -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout. -- Vassilis Virvilis -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: How to embed HTML from TextResource using UiBinder
Is there an easier way by now?
Am Mittwoch, 3. April 2013 01:10:52 UTC+2 schrieb Thomas Broyer:
On Wednesday, April 3, 2013 12:34:06 AM UTC+2, Pat wrote:
I found something that works, even though I think that should be possible
with less glue code...
It should be possible to create a SafeHtmlResource, that could validate
the content of the resource at build-time.
Otherwise, your solution below is the only one I could think about.
interface TextsBundle extends ClientBundle { @Source(text.txt)
TextResource myText(); }
class SafeHtmlTexts {
@Inject TextBundle texts;
public SafeHtml myText() { return
SafeHtmlUtils.fromSafeConstant(texts.myText().getText()); }
}
class ViewImpl {
private final SafeHtmlTexts texts;
@Inject public ViewImpl(..., SafeHtmlTexts texts) { this.texts = texts;
... }
...
@UiFactory SafeHtmlTexts create() { return texts; }
You could simply use a @UiField for 'texts' rather than the @UiFactory. If
you want the SafeHtmlTexts to be provided (by GIN apparently), use
@UiField(provided=true) (and you can then have your field 'final').
}
ViewImpl.ui.xml:
ui:with field='texts' type='SafeHtmlTexts'/
...
divui:safehtml from={texts.myText}//div
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
GWT-client math vs. java-math
Hi guys, we are developing a GWT-project with a lot of shared files. We discovered a few discrepancies in the gwt-math and server-math and wanted to share them for anybody else having those issues: - First and foremost: all native double calculations are identical (+ - * / %) - All trig-functions (sin,cos,tan,asin,acos,atan,atan2) seem to produces slightly different results. We recommend doing your own impl using lookup-maps - sqrt,log and pow seem to be identical although we only tested sqrt thoroughly - As far as we know all functions like max,min,abs etc are identical - toDegrees and toRadian are actually different because GWT uses a constant for 180./PI and PI/180. which changes the order of operation compared to java - For serialization of doubles we strongly suggest using Double.doubleToLongbits and Double.longBitsToDouble. You can additionally use Long.toString(long,32) and Long.parseString(string,32) to compress the String-representation I hope we can help some people with this info. Especially the toDegrees/toRadians was very surprising to find. This issue was reported though and might be fixed in a future GWT-version (we tested 2.6.1). In case you are interested how we solved the issues here is the open-source-part of our project https://xp-dev.com/sc/182005/HEAD/%2FGWTCommon%2Fsrc%2Fcom%2Funiverseprojects%2Fcommon%2Fshared%2Fmath so you can check it out Regards Oskar Stangenberg -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT-client math vs. java-math
Thanks for sharing. It will very useful track each problem to GWT issue tracker. 2014-08-12 13:09 GMT-03:00 Oskar Stangenberg crokok...@gmail.com: Hi guys, we are developing a GWT-project with a lot of shared files. We discovered a few discrepancies in the gwt-math and server-math and wanted to share them for anybody else having those issues: - First and foremost: all native double calculations are identical (+ - * / %) - All trig-functions (sin,cos,tan,asin,acos,atan,atan2) seem to produces slightly different results. We recommend doing your own impl using lookup-maps - sqrt,log and pow seem to be identical although we only tested sqrt thoroughly - As far as we know all functions like max,min,abs etc are identical - toDegrees and toRadian are actually different because GWT uses a constant for 180./PI and PI/180. which changes the order of operation compared to java - For serialization of doubles we strongly suggest using Double.doubleToLongbits and Double.longBitsToDouble. You can additionally use Long.toString(long,32) and Long.parseString(string,32) to compress the String-representation I hope we can help some people with this info. Especially the toDegrees/toRadians was very surprising to find. This issue was reported though and might be fixed in a future GWT-version (we tested 2.6.1). In case you are interested how we solved the issues here is the open-source-part of our project https://xp-dev.com/sc/182005/HEAD/%2FGWTCommon%2Fsrc%2Fcom%2Funiverseprojects%2Fcommon%2Fshared%2Fmath so you can check it out Regards Oskar Stangenberg -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: master/3.0.0 js interop ready to play with?
Ahhh. I didn't know I needed -XjsInteropMode JS up and running now. I also didn't know 2.7.0-SNAPSHOT was available -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: How to dynamically choose locale at SuperDevMode compile time?
I use meta tag in HTML for setting locale:
meta name=gwt:property content=locale=en /
I use GWT from trunk, in Eclipse with -superDevMode argument, without
bookmarklet. This patch works for me:
diff --git
a/dev/codeserver/java/com/google/gwt/dev/codeserver/dev_mode_on.js
b/dev/codeserver/java/com/google/gwt/dev/codeserver/dev_mode_on.js
index 2964be7..9bb0a92 100644
--- a/dev/codeserver/java/com/google/gwt/dev/codeserver/dev_mode_on.js
+++ b/dev/codeserver/java/com/google/gwt/dev/codeserver/dev_mode_on.js
@@ -380,6 +380,11 @@
var url = url_prefix +
'_callback=__gwt_bookmarklet_globals.callbacks.' +
callback_id;
+var nodelist=document.getElementsByTagName('meta');
+for(var i=0; inodelist.length; i++) {
+if(nodelist[i].getAttribute('name')=='gwt:property')
+url+=''+nodelist[i].getAttribute('content');
+}
var script = $doc.createElement('script');
script.src = url;
diff --git
a/dev/codeserver/java/com/google/gwt/dev/codeserver/stub.nocache.js
b/dev/codeserver/java/com/google/gwt/dev/codeserver/stub.nocache.js
index 0b83ae6..bcb95de 100755
--- a/dev/codeserver/java/com/google/gwt/dev/codeserver/stub.nocache.js
+++ b/dev/codeserver/java/com/google/gwt/dev/codeserver/stub.nocache.js
@@ -202,6 +202,12 @@
var compileScript = $doc.createElement('script');
compileScript.src = serverUrl +
'/recompile/__MODULE_NAME__?user.agent=' + ua + '_callback=' +
callback;
+var nodelist=document.getElementsByTagName('meta');
+for(var i=0; inodelist.length; i++) {
+if(nodelist[i].getAttribute('name')=='gwt:property')
+compileScript.src+=''+nodelist[i].getAttribute('content');
+}
+
$head.appendChild(compileScript);
compileButton.className = buttonClassName + ' gwt-DevModeCompiling';
}
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
[gwt-contrib] Re: What's the current plan for GWT 2.7 release?
I am interested in the schedule of GWT 2.7 too! Am Donnerstag, 7. August 2014 11:40:06 UTC+2 schrieb Александр Новоселов: Though Google I/O was 6 weeks ago, I did not ask why 2.7 is not released yet? My question about the *current* status and plans. среда, 6 августа 2014 г., 22:30:10 UTC+4 пользователь Gilberto Torrezan Filho написал: It's easier to understand and accept the schedule from GWT project (or any other Google or driven-by-Google-culture project) when you apply the Valve time calendar to it. Yes, Valve is the pioneer (that's why the calendar received their name), but a lot of companies and groups use that calendar, deliberately or not. At GWT.create it was said the target was to release GWT 3.0 after Google I/O. Then it was changed to release a 2.7 version shortly after Google I/O, and GWT 3.0 on GWT.create 2015. Well, using some Valve time rules, I'd say we probably will have the 2.7 version about two months after GWT.create 2015. More about the past plans: http://blog.oio.de/2014/03/31/upcoming-gwt-releases-2-7-3-0-2014-beyond/ More about Valve time: https://developer.valvesoftware.com/wiki/Valve_Time and http://www.urbandictionary.com/define.php?term=Valve%20Time Of course, the Valve time is as inaccurate as using CSS layouts on IE6, so there are chances we get GWT 3.0 like tomorrow (in actual time). But I wouldn't bet on that. On Wednesday, August 6, 2014 5:15:32 AM UTC-3, Александр Новоселов wrote: Will you update to Jetty 9.2 (with JVM 8 support)? What's the schedule: how many days/weeks/months before beta/rc/release version? -- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/2d759bfc-02e0-4c47-bbce-dcfd66b97a46%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
