Re: You have large GWT 2.x application and you don't know what to do when 3.0 is out ?

2015-12-11 Thread CodeLess Solutions
Yes I think they will be gone as well.

Regards,
Predrag.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.


Re: Getting rid of Dev mode for future GWT releases

2015-12-11 Thread Peter Donald
On Saturday, 12 December 2015,  wrote:
>
> So - my opinion - reducing the functionality of the debugger (moving from
> DevMode to SDM, for example) is in fact a loss of useful features and a
> reduction in the power of the tools at my disposal. I can use SDM - but it
> only covers like 50% of the functionality I use in a JVM debugger.
>

I keep hearing that SDM is not as good as DevMode but our experience is
that it is better in almost every way. This may be because we IntelliJ idea.

In Both you can run the debugger from the ide, set break points, inspect
variables. DevMode has the advantage that variables are easier to decipher.
SDM has the  advantage of speed for both startup and refresh and during
debug. SDM also never has to deal with differences between different modes
and can debug regular JavaScript / other is languages

The one disadvantage will surely be fixed in time so I never really
understand why people lament the imminent demise of DevMode


-- 
Cheers,

Peter Donald

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 2.8.0-SNAPSHOT jsinterop missing module

2015-12-11 Thread Thomas Broyer


On Friday, December 11, 2015 at 11:08:01 PM UTC+1, geek.m...@gmail.com 
wrote:
>
> Hi, I'm using the GWT 2.8.0-SNAPSHOT along with the Mojo GWT plugin (same 
> version). Been working fine all week, but today I suddenly get this error 
> message when doing a build: 
>
>
> [INFO] --- gwt-maven-plugin:2.8.0-SNAPSHOT:compile (default) @ 
> ritual-designer-bs ---
>
> [INFO] Loading inherited module 
> 'com.mjeffw.gurps.ritualdesigner.RitualDesignerBS'
>
> [INFO]Loading inherited module 'com.google.gwt.core.Core'
>
> [INFO]   Loading inherited module 'jsinterop.annotations.Annotations'
>
> [INFO]  [ERROR] Unable to find 
> 'jsinterop/annotations/Annotations.gwt.xml' on your classpath; could be a 
> typo, or maybe you forgot to include a classpath entry for source?
>
>
> Any ideas on how to solve this?
>

Make sure your dependencies are up-to-date and all present in the classpath 
(there's a new com.google.jsinterop:jsinterop-annotations artifact that 
com.google.gwt:gwt-user depends on)

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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: You have large GWT 2.x application and you don't know what to do when 3.0 is out ?

2015-12-11 Thread Ed
I migrated to RequestBuilder (got rid of rpc), dont use UI Binder.  Are you
saying that CellWidgets will be gone also?

Regards,

Ed

On Fri, Dec 11, 2015 at 2:58 PM, CodeLess Solutions <
codelessoluti...@gmail.com> wrote:

> We all know by now that 3.0 will bring huge changes. Widgets will be gone,
> UIBinder gone, Generators out, Requestfactory and GWT RPC as well, ...
>
> Similar is with Angular 2 and it can happen to any library as well.
>
> If you are planning to build large application and you have this kind of
> concerns, you can read our post about this problem, maybe it will help you
> out or at least give you some ideas what to do:
>
>
> http://www.codeless.solutions/#!Meta-Platform-survival-guide/enstx/566ac8fc0cf239106876cf13
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" 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 "GWT 
Users" 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.


VerticalPanel in DockLayoutPanel

2015-12-11 Thread Roberto Attias
Hi,
I have a VerticalPanel containing 100 buttons with label "Component"+idx 
wrapped by a ScrollPanel. the ScrollPanel is added as West component of a 
DockLayoutPanel, and a canvas is added to the center. 
I would have expected the LayoutPanel to automatically size the ScrollPanel 
so that the entire horizontal extent of the vertical panel is visible, but 
that's not the case and my button are cut. is there a way to automatically 
size horizontally the vertical panel to fit the entire horizontal extent of 
its content?

Thanks!

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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: Linker public artifacts are not available in SDM

2015-12-11 Thread Vitaly Litvak
Thanks for the reply. But unfortunately it does not work. In the web 
browser it shows:

XMLHttpRequest cannot load 
> http://192.168.10.4:9876/traccar/i18n/org/traccar/web/client/i18n/Messages/default.
>  
> No 'Access-Control-Allow-Origin' header is present on the requested 
> resource. Origin 'http://192.168.10.4:' is therefore not allowed access.


This is not that bad. However, on that URL there is nothing:

curl -v 
> http://192.168.10.4:9876/traccar/i18n/org/traccar/web/client/i18n/Messages/default
> * Hostname was NOT found in DNS cache
> *   Trying 192.168.10.4...
> * Connected to 192.168.10.4 (192.168.10.4) port 9876 (#0)
> > GET /traccar/i18n/org/traccar/web/client/i18n/Messages/default HTTP/1.1
> > User-Agent: curl/7.37.1
> > Host: 192.168.10.4:9876
> > Accept: */*
> >
> < HTTP/1.1 200 OK
> < Content-Length: 0
> * Server Jetty(8.y.z-SNAPSHOT) is not blacklisted
> < Server: Jetty(8.y.z-SNAPSHOT)
> <
> * Connection #0 to host 192.168.10.4 left intact


Maybe my approach to generate localized JSON objects for loading at runtime 
is wrong and I should stick with some kind of servlet. Just thought that 
for GWT this will be a blessed way. I don't know...

пятница, 11 декабря 2015 г., 22:17:42 UTC+3 пользователь Thomas Broyer 
написал:
>
> In 
> https://github.com/vitalidze/traccar-web/blob/12ceb111e20bb79aa9e046b9b9db5aae5aa84ffd/src/main/java/org/traccar/web/i18n/client/StringTranslator.java#L51
>  
> you need to use GWT.getModuleBaseForStaticFiles() instead of 
> GWT.getModuleBaseURL().
>
> http://www.gwtproject.org/javadoc/latest/com/google/gwt/core/client/GWT.html#getModuleBaseForStaticFiles()
>
> On Friday, December 11, 2015 at 4:37:39 PM UTC+1, Vitaly Litvak wrote:
>>
>> Hi
>>
>> I am trying to reduce the compilation time of my GWT app. There are about 
>> 160 permutations done for now and the reason is big number of 
>> languages/locales supported. The main idea is to get rid of the static 
>> compilation and replace it with dynamic loading of localized data. I have 
>> almost succeeded, but now I am facing the problem with linker, which does 
>> not expose public artifacts when I run project from IntelliJ Idea. I will 
>> give more details and then point where the problem is now. 
>>
>> I already have the `Messages` interface and multiple `.properties` files 
>> with defined translations and also I am using GXT library, which also uses 
>> 'static' internationalization. Thus the only way I can imagine myself is to 
>> replace the Localizable generator with my own implementation. I have 
>> defined it in a separate module:
>>
>> 
>> 
>> 
>>
>>
>> Then in generator I simply produce a single implementation, which will use 
>> another class to load the strings from module's resources available under 
>> {module.base.url}/i18n/path/to/package/ClassName/{locale}, for example 
>> MyModule/i18n/com/google/gwt/i18n/client/constants/NumberConstantsImpl/ru
>>
>>
>> I intend to store the localized strings as JSON object, which will be 
>> generated by the 'generator' as well. Here is the code of my 
>> 'LocalizableGenerator':
>>
>>
>> JsonFactory jsonFactory = new JsonFactory();
>> for (GwtLocale locale : localeParams.allLocales) {
>> AbstractResource.ResourceList resourceList = null;
>> try {
>> resourceList = ResourceFactory.getBundle(logger, targetClass, locale,
>> assignableToConstants, context);
>> OutputStream os = context.tryCreateResource(logger, resource + "/" + 
>> locale.toString());
>> if (os != null) {
>> JsonGenerator jg = jsonFactory.createGenerator(os, 
>> JsonEncoding.UTF8);
>> jg.writeStartObject();
>> for (String key : resourceList.keySet()) {
>> AbstractResource.ResourceEntry entry = 
>> resourceList.getEntry(key);
>> Collection forms = entry.getForms();
>> if (forms.isEmpty()) {
>> jg.writeStringField(key, resourceList.getString(key));
>> } else {
>> jg.writeObjectFieldStart(key);
>> jg.writeStringField("null", resourceList.getString(key));
>> for (String form : forms) {
>> jg.writeStringField(form, entry.getForm(form));
>> }
>> jg.writeEndObject();
>> }
>> }
>> jg.writeEndObject();
>> jg.flush();
>> GeneratedResource generatedResource = 
>> context.commitResource(logger, os);
>> context.commitArtifact(logger, generatedResource);
>> }
>> } catch (MissingResourceException e) {
>> throw error(logger,
>> "Localization failed; there must be at least one resource 
>> accessible through"
>> + " the classpath in package '" + 
>> targetClass.getPackage().getName()
>> + "' whose base name is '"
>> + ResourceFactory.g

Re: Getting rid of Dev mode for future GWT releases

2015-12-11 Thread geek . macbeer
I don't know why this is such a controversial topic. The debugger is just 
another tool in the developer's toolbox. I'm a huge proponent of TDD, and 
when you get code with a high percentage of code coverage, I hardly ever go 
into a debugger. There are other times when, even when all incidental 
complexity is removed from a code base, there is enough intrinsic 
complexity that when things break, its faster to just go and look what is 
really being returned by a function, or the order of events. A debugger is 
really good for that.

Heck a debugger is a good tool to learn about a new framework - set some 
breakpoints in code you don't yet understand and step through it until you 
understand it.

So - my opinion - reducing the functionality of the debugger (moving from 
DevMode to SDM, for example) is in fact a loss of useful features and a 
reduction in the power of the tools at my disposal. I can use SDM - but it 
only covers like 50% of the functionality I use in a JVM debugger.

On Thursday, December 10, 2015 at 12:29:53 PM UTC-5, Ed wrote:
>
> @Frank: you are absolutely right, but it's difficult to generalize this, 
> as it highly depends on your situation.
>
> On 10 December 2015 at 18:01, Frank > 
> wrote:
>
>> If you have to read code for hours to solve a problem without a debugger 
>> I think you have some bigger problems with your code than some bugs... 
>> (code structure)
>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "GWT Users" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/google-web-toolkit/IfLWnnCf9rM/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to 
>> google-web-toolkit+unsubscr...@googlegroups.com .
>> To post to this group, send email to google-we...@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 "GWT 
Users" 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 2.8.0-SNAPSHOT jsinterop missing module

2015-12-11 Thread geek . macbeer
 

Hi, I'm using the GWT 2.8.0-SNAPSHOT along with the Mojo GWT plugin (same 
version). Been working fine all week, but today I suddenly get this error 
message when doing a build: 


[INFO] --- gwt-maven-plugin:2.8.0-SNAPSHOT:compile (default) @ 
ritual-designer-bs ---

[INFO] Loading inherited module 
'com.mjeffw.gurps.ritualdesigner.RitualDesignerBS'

[INFO]Loading inherited module 'com.google.gwt.core.Core'

[INFO]   Loading inherited module 'jsinterop.annotations.Annotations'

[INFO]  [ERROR] Unable to find 
'jsinterop/annotations/Annotations.gwt.xml' on your classpath; could be a 
typo, or maybe you forgot to include a classpath entry for source?


Any ideas on how to solve this?

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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.


CellTable equivalent

2015-12-11 Thread Juan Pablo Gardella
Hi devs,

As GWT 3.0 will remove widgets, someone know if exists a CellTable
equivalence in JS libraries? CellTable and Datagrid are awesome components.

Juan

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 have large GWT 2.x application and you don't know what to do when 3.0 is out ?

2015-12-11 Thread CodeLess Solutions
We all know by now that 3.0 will bring huge changes. Widgets will be gone, 
UIBinder gone, Generators out, Requestfactory and GWT RPC as well, ... 

Similar is with Angular 2 and it can happen to any library as well.

If you are planning to build large application and you have this kind of 
concerns, you can read our post about this problem, maybe it will help you 
out or at least give you some ideas what to do:

http://www.codeless.solutions/#!Meta-Platform-survival-guide/enstx/566ac8fc0cf239106876cf13


-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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: Linker public artifacts are not available in SDM

2015-12-11 Thread Thomas Broyer
In 
https://github.com/vitalidze/traccar-web/blob/12ceb111e20bb79aa9e046b9b9db5aae5aa84ffd/src/main/java/org/traccar/web/i18n/client/StringTranslator.java#L51
 
you need to use GWT.getModuleBaseForStaticFiles() instead of 
GWT.getModuleBaseURL().
http://www.gwtproject.org/javadoc/latest/com/google/gwt/core/client/GWT.html#getModuleBaseForStaticFiles()

On Friday, December 11, 2015 at 4:37:39 PM UTC+1, Vitaly Litvak wrote:
>
> Hi
>
> I am trying to reduce the compilation time of my GWT app. There are about 
> 160 permutations done for now and the reason is big number of 
> languages/locales supported. The main idea is to get rid of the static 
> compilation and replace it with dynamic loading of localized data. I have 
> almost succeeded, but now I am facing the problem with linker, which does 
> not expose public artifacts when I run project from IntelliJ Idea. I will 
> give more details and then point where the problem is now. 
>
> I already have the `Messages` interface and multiple `.properties` files 
> with defined translations and also I am using GXT library, which also uses 
> 'static' internationalization. Thus the only way I can imagine myself is to 
> replace the Localizable generator with my own implementation. I have 
> defined it in a separate module:
>
> 
> 
> 
>
>
> Then in generator I simply produce a single implementation, which will use 
> another class to load the strings from module's resources available under 
> {module.base.url}/i18n/path/to/package/ClassName/{locale}, for example 
> MyModule/i18n/com/google/gwt/i18n/client/constants/NumberConstantsImpl/ru
>
>
> I intend to store the localized strings as JSON object, which will be 
> generated by the 'generator' as well. Here is the code of my 
> 'LocalizableGenerator':
>
>
> JsonFactory jsonFactory = new JsonFactory();
> for (GwtLocale locale : localeParams.allLocales) {
> AbstractResource.ResourceList resourceList = null;
> try {
> resourceList = ResourceFactory.getBundle(logger, targetClass, locale,
> assignableToConstants, context);
> OutputStream os = context.tryCreateResource(logger, resource + "/" + 
> locale.toString());
> if (os != null) {
> JsonGenerator jg = jsonFactory.createGenerator(os, 
> JsonEncoding.UTF8);
> jg.writeStartObject();
> for (String key : resourceList.keySet()) {
> AbstractResource.ResourceEntry entry = 
> resourceList.getEntry(key);
> Collection forms = entry.getForms();
> if (forms.isEmpty()) {
> jg.writeStringField(key, resourceList.getString(key));
> } else {
> jg.writeObjectFieldStart(key);
> jg.writeStringField("null", resourceList.getString(key));
> for (String form : forms) {
> jg.writeStringField(form, entry.getForm(form));
> }
> jg.writeEndObject();
> }
> }
> jg.writeEndObject();
> jg.flush();
> GeneratedResource generatedResource = 
> context.commitResource(logger, os);
> context.commitArtifact(logger, generatedResource);
> }
> } catch (MissingResourceException e) {
> throw error(logger,
> "Localization failed; there must be at least one resource 
> accessible through"
> + " the classpath in package '" + 
> targetClass.getPackage().getName()
> + "' whose base name is '"
> + ResourceFactory.getResourceName(targetClass) + "'");
> } catch (IllegalArgumentException e) {
> // A bad key can generate an illegal argument exception.
> throw error(logger, e.getMessage());
> } catch (IOException e) {
> throw error(logger, e);
> }
> }
>
>
> The generation works just fine. I can see produced files in a temporary 
> folder. Looks like they are included in the .war file as well when I produce 
> it with maven. However, they are not visible when I run my application in SDM 
> from IntelliJ Idea.
>
>
> Full source code is available on github: 
> https://github.com/vitalidze/traccar-web/tree/dynamic_i18n
>
>
> Commit with above changes: 
> https://github.com/vitalidze/traccar-web/commit/12ceb111e20bb79aa9e046b9b9db5aae5aa84ffd
>
>
> Any help appreciated.
>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 2.7.0 is here

2015-12-11 Thread wade . zang
Thanks Thomas. I have tried your solution. I installed the GPE with Java 7 
first. Then I selected jre 1.6 in the build path. However, I got an JVM 
Launcher error "Main class is not found in 
com.google.appengine.tools.enhancer.Enhance". Looks like this enhancer does 
not support java 1.6. I disabled this in the eclipse. But it still has 
problem. Do you know how to solve this issue? 



On Friday, December 11, 2015 at 4:01:00 AM UTC-5, Thomas Broyer wrote:
>
>
>
> On Friday, December 11, 2015 at 12:26:41 AM UTC+1, wade...@gmail.com 
> wrote:
>>
>> I have installed GPE with GWT 2.7 into Eclipse Luna 4.4. Everything works 
>> fine.
>> However, for some reason I have to downgrade JDK from 1.7 to 1.6. After 
>> downgrading, the GWT plugin doesn't work anymore. 
>> Does anyone know if GWT 2.7 supports JDK 1.6?
>>
>
> GWT 2.7 works with Java 6, but IIRC the GPE (either Google Plugin for 
> Eclipse or GWT Plugin for Eclipse) requires Java 7; i.e. you need to launch 
> Eclipse with a JRE 7, but then you should be able to pick a JDK 6 for your 
> project and it should work (AFAICT) 
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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.


Ready made Ui component set for GWT

2015-12-11 Thread gautam
As I understand the new advise for using GWT is when we need ready 
components such as lists, grids etc. we are encouraged to use ui components 
from polymer or other such framework. 

Is this understanding correct ?

If yes, why so ?

If not, is it a good idea to create a new pure GWT Ui component library on 
the lines of smart GWT / ext-gwt ?

TIA,
Gautam

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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.


Linker public artifacts are not available in SDM

2015-12-11 Thread Vitaly Litvak
Hi

I am trying to reduce the compilation time of my GWT app. There are about 
160 permutations done for now and the reason is big number of 
languages/locales supported. The main idea is to get rid of the static 
compilation and replace it with dynamic loading of localized data. I have 
almost succeeded, but now I am facing the problem with linker, which does 
not expose public artifacts when I run project from IntelliJ Idea. I will 
give more details and then point where the problem is now. 

I already have the `Messages` interface and multiple `.properties` files 
with defined translations and also I am using GXT library, which also uses 
'static' internationalization. Thus the only way I can imagine myself is to 
replace the Localizable generator with my own implementation. I have 
defined it in a separate module:






Then in generator I simply produce a single implementation, which will use 
another class to load the strings from module's resources available under 
{module.base.url}/i18n/path/to/package/ClassName/{locale}, for example 
MyModule/i18n/com/google/gwt/i18n/client/constants/NumberConstantsImpl/ru


I intend to store the localized strings as JSON object, which will be generated 
by the 'generator' as well. Here is the code of my 'LocalizableGenerator':


JsonFactory jsonFactory = new JsonFactory();
for (GwtLocale locale : localeParams.allLocales) {
AbstractResource.ResourceList resourceList = null;
try {
resourceList = ResourceFactory.getBundle(logger, targetClass, locale,
assignableToConstants, context);
OutputStream os = context.tryCreateResource(logger, resource + "/" + 
locale.toString());
if (os != null) {
JsonGenerator jg = jsonFactory.createGenerator(os, 
JsonEncoding.UTF8);
jg.writeStartObject();
for (String key : resourceList.keySet()) {
AbstractResource.ResourceEntry entry = 
resourceList.getEntry(key);
Collection forms = entry.getForms();
if (forms.isEmpty()) {
jg.writeStringField(key, resourceList.getString(key));
} else {
jg.writeObjectFieldStart(key);
jg.writeStringField("null", resourceList.getString(key));
for (String form : forms) {
jg.writeStringField(form, entry.getForm(form));
}
jg.writeEndObject();
}
}
jg.writeEndObject();
jg.flush();
GeneratedResource generatedResource = 
context.commitResource(logger, os);
context.commitArtifact(logger, generatedResource);
}
} catch (MissingResourceException e) {
throw error(logger,
"Localization failed; there must be at least one resource 
accessible through"
+ " the classpath in package '" + 
targetClass.getPackage().getName()
+ "' whose base name is '"
+ ResourceFactory.getResourceName(targetClass) + "'");
} catch (IllegalArgumentException e) {
// A bad key can generate an illegal argument exception.
throw error(logger, e.getMessage());
} catch (IOException e) {
throw error(logger, e);
}
}


The generation works just fine. I can see produced files in a temporary folder. 
Looks like they are included in the .war file as well when I produce it with 
maven. However, they are not visible when I run my application in SDM from 
IntelliJ Idea.


Full source code is available on github: 
https://github.com/vitalidze/traccar-web/tree/dynamic_i18n


Commit with above changes: 
https://github.com/vitalidze/traccar-web/commit/12ceb111e20bb79aa9e046b9b9db5aae5aa84ffd


Any help appreciated.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 and Polymer example does not run

2015-12-11 Thread vadim
2.8.0-SNAPSHOT does not have gwt-servlet compiled, so Maven issues the 
error.
2.8.0-beta1 does not have corresponding version for gwt-maven-plugin.  But 
combination of 2.8.0-beta1 for GWT and sub-modules and 2.7.0 for 
gwt-maven-plugin works well. This is better option than compilation for 
sure :)

Vadim.

On Friday, December 11, 2015 at 3:31:27 PM UTC+2, Ümit Seren wrote:
>
> or you can simply use GWT 2.8.0-beta/snapshot ? ;-) 
>
> On Friday, December 11, 2015 at 1:36:05 PM UTC+1, va...@ant.ee wrote:
>>
>> I was really surprised, but here is result of my investigation:
>>
>> https://github.com/vaadin/gwt-polymer-elements/issues/82
>>
>> Basically official GWT release 2.7.0 does not have JsFunction annotation. 
>> Thus it can't work with Vaadin Polymer.
>> I have to clone GWT project sources and re-compile master to be able to 
>> use Polymer elements.
>>
>> Vadim.
>>
>> On Thursday, December 10, 2015 at 6:50:57 PM UTC+2, va...@ant.ee wrote:
>>>
>>> Hello all,
>>>
>>> I have followed GWT tutorial to build TodoList polymer example 
>>> and during runtime got the following error:
>>>
>>>  [ERROR] Errors in 'com/vaadin/polymer/elemental/Function.java'
>>> [INFO][ERROR] Line 6: JsFunction cannot be resolved to a 
>>> type
>>> [INFO][ERROR] Line 3: The import 
>>> com.google.gwt.core.client.js.JsFunction cannot be resolved
>>> [INFO]  [ERROR] Hint: Your source appears not to live underneath 
>>> a subpackage called 'client'; no problem, but you'll need to use the 
>>>  directive in your module to make it accessible
>>>
>>>I have done everything like tutorial said, but is not able to 
>>> resolve the issue by myself. JsInterop mode is enabled. I have no idea 
>>> where to look into...  
>>>
>>> P.S. GWT version is 2.7.0, vaadin-gwt-polymer-elements is 1.2.1.0
>>>
>>> Thank you.
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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: maven compilation failure

2015-12-11 Thread Jimmy Pannier
Ok, i've change my profile maven to not use my own proxy repository 
(nexus). It's seems that my repo contains snapshots libraries that are not 
updated ( i suppose ).
Thanks

Le vendredi 11 décembre 2015 11:14:11 UTC+1, Jimmy Pannier a écrit :
>
> since today, when i compile my maven project with gwt 2.8.0 beta1
> there is an error :
>
> [ERROR] Failed to execute goal 
> org.codehaus.mojo:gwt-maven-plugin:2.8.0-SNAPSHOT:compile (default) on 
> project cloud-web-mobile-patient: Failed to resolve artifact: Some problems 
> were encountered while processing the POMs:
> [ERROR] [ERROR] 'dependencies.dependency.version' for 
> com.google.jsinterop:jsinterop-annotations:jar is missing. @ line 16, 
> column 21
> [ERROR] [ERROR] 'dependencies.dependency.version' for 
> com.google.jsinterop:jsinterop-annotations:jar:sources is missing. @ line 
> 20, column 21
> [ERROR] for project
> [ERROR] -> [Help 1]
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 and Polymer example does not run

2015-12-11 Thread Ümit Seren
or you can simply use GWT 2.8.0-beta/snapshot ? ;-) 

On Friday, December 11, 2015 at 1:36:05 PM UTC+1, va...@ant.ee wrote:
>
> I was really surprised, but here is result of my investigation:
>
> https://github.com/vaadin/gwt-polymer-elements/issues/82
>
> Basically official GWT release 2.7.0 does not have JsFunction annotation. 
> Thus it can't work with Vaadin Polymer.
> I have to clone GWT project sources and re-compile master to be able to 
> use Polymer elements.
>
> Vadim.
>
> On Thursday, December 10, 2015 at 6:50:57 PM UTC+2, va...@ant.ee wrote:
>>
>> Hello all,
>>
>> I have followed GWT tutorial to build TodoList polymer example 
>> and during runtime got the following error:
>>
>>  [ERROR] Errors in 'com/vaadin/polymer/elemental/Function.java'
>> [INFO][ERROR] Line 6: JsFunction cannot be resolved to a 
>> type
>> [INFO][ERROR] Line 3: The import 
>> com.google.gwt.core.client.js.JsFunction cannot be resolved
>> [INFO]  [ERROR] Hint: Your source appears not to live underneath 
>> a subpackage called 'client'; no problem, but you'll need to use the 
>>  directive in your module to make it accessible
>>
>>I have done everything like tutorial said, but is not able to 
>> resolve the issue by myself. JsInterop mode is enabled. I have no idea 
>> where to look into...  
>>
>> P.S. GWT version is 2.7.0, vaadin-gwt-polymer-elements is 1.2.1.0
>>
>> Thank you.
>>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 and Polymer example does not run

2015-12-11 Thread Marcio Alves
Same issue for me. 

Any ideas?

Thanks!

Em quinta-feira, 10 de dezembro de 2015 14:50:57 UTC-2, va...@ant.ee 
escreveu:
>
> Hello all,
>
> I have followed GWT tutorial to build TodoList polymer example and 
> during runtime got the following error:
>
>  [ERROR] Errors in 'com/vaadin/polymer/elemental/Function.java'
> [INFO][ERROR] Line 6: JsFunction cannot be resolved to a 
> type
> [INFO][ERROR] Line 3: The import 
> com.google.gwt.core.client.js.JsFunction cannot be resolved
> [INFO]  [ERROR] Hint: Your source appears not to live underneath a 
> subpackage called 'client'; no problem, but you'll need to use the  
> directive in your module to make it accessible
>
>I have done everything like tutorial said, but is not able to 
> resolve the issue by myself. JsInterop mode is enabled. I have no idea 
> where to look into...  
>
> P.S. GWT version is 2.7.0, vaadin-gwt-polymer-elements is 1.2.1.0
>
> Thank you.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 and Polymer example does not run

2015-12-11 Thread vadim
I was really surprised, but here is result of my investigation:

https://github.com/vaadin/gwt-polymer-elements/issues/82

Basically official GWT release 2.7.0 does not have JsFunction annotation. 
Thus it can't work with Vaadin Polymer.
I have to clone GWT project sources and re-compile master to be able to use 
Polymer elements.

Vadim.

On Thursday, December 10, 2015 at 6:50:57 PM UTC+2, va...@ant.ee wrote:
>
> Hello all,
>
> I have followed GWT tutorial to build TodoList polymer example and 
> during runtime got the following error:
>
>  [ERROR] Errors in 'com/vaadin/polymer/elemental/Function.java'
> [INFO][ERROR] Line 6: JsFunction cannot be resolved to a 
> type
> [INFO][ERROR] Line 3: The import 
> com.google.gwt.core.client.js.JsFunction cannot be resolved
> [INFO]  [ERROR] Hint: Your source appears not to live underneath a 
> subpackage called 'client'; no problem, but you'll need to use the  
> directive in your module to make it accessible
>
>I have done everything like tutorial said, but is not able to 
> resolve the issue by myself. JsInterop mode is enabled. I have no idea 
> where to look into...  
>
> P.S. GWT version is 2.7.0, vaadin-gwt-polymer-elements is 1.2.1.0
>
> Thank you.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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.


maven compilation failure

2015-12-11 Thread Jimmy Pannier
since today, when i compile my maven project with gwt 2.8.0 beta1
there is an error :

[ERROR] Failed to execute goal 
org.codehaus.mojo:gwt-maven-plugin:2.8.0-SNAPSHOT:compile (default) on 
project cloud-web-mobile-patient: Failed to resolve artifact: Some problems 
were encountered while processing the POMs:
[ERROR] [ERROR] 'dependencies.dependency.version' for 
com.google.jsinterop:jsinterop-annotations:jar is missing. @ line 16, 
column 21
[ERROR] [ERROR] 'dependencies.dependency.version' for 
com.google.jsinterop:jsinterop-annotations:jar:sources is missing. @ line 
20, column 21
[ERROR] for project
[ERROR] -> [Help 1]

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 2.7.0 is here

2015-12-11 Thread Thomas Broyer


On Friday, December 11, 2015 at 12:26:41 AM UTC+1, wade...@gmail.com wrote:
>
> I have installed GPE with GWT 2.7 into Eclipse Luna 4.4. Everything works 
> fine.
> However, for some reason I have to downgrade JDK from 1.7 to 1.6. After 
> downgrading, the GWT plugin doesn't work anymore. 
> Does anyone know if GWT 2.7 supports JDK 1.6?
>

GWT 2.7 works with Java 6, but IIRC the GPE (either Google Plugin for 
Eclipse or GWT Plugin for Eclipse) requires Java 7; i.e. you need to launch 
Eclipse with a JRE 7, but then you should be able to pick a JDK 6 for your 
project and it should work (AFAICT) 

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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.


Dagger 2 and GWT code splitting

2015-12-11 Thread Erik Kuefler
I've been using Dagger 2 in my GWT app happily for several months now, and
am just starting to look into doing some more serious code splitting. Has
anyone put much thought into this or come up with good patterns?

The obvious way to do it is to inject a Provider and then only call
.get() on that provider from inside a runAsync block. I vaguely recall this
working with Gin, but it doesn't seem to work with Dagger (Foo's code is
still in the main fragment). The other option is to handwrite a
FooAsyncProvider class that injects Foo's dependencies and has a get method
that takes a callback and manually constructs Foo in a runAsync block,
passing it to the callback. This seems to work but it's annoying to keep
Foo and FooAsyncProvider in sync with one another; I might end up writing
my own annotation processor to generate async providers if there isn't a
better way.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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.