As far as I am aware off you can always collapse different permutations into a single one or a subset. Also we want to control it to the level that we have our own internationalization support by embed certain keys we draw from external message collections.
So a permutation explosion is what we dont want. Also we want to control the scripts reload and caching ourself. Simple as that. This configuration issue is that critical that we consider using Dart to simply generate a single js file and do not deal with inherited modules and this permutation / script selecting configuration issues. I know its simple and I understand the reason why it exists. But since we fairly dont update the javascript that often and different teams are developing certain parts, we want to have it as clear and close to what exists as we would when writing javascript directly.
Cheers,
Martin (Kersten),
Germany
Am Freitag, 20. Dezember 2013 01:57:07 UTC+1 schrieb Jens:
-- So a permutation explosion is what we dont want. Also we want to control the scripts reload and caching ourself. Simple as that. This configuration issue is that critical that we consider using Dart to simply generate a single js file and do not deal with inherited modules and this permutation / script selecting configuration issues. I know its simple and I understand the reason why it exists. But since we fairly dont update the javascript that often and different teams are developing certain parts, we want to have it as clear and close to what exists as we would when writing javascript directly.
Cheers,
Martin (Kersten),
Germany
Am Freitag, 20. Dezember 2013 01:57:07 UTC+1 schrieb Jens:
Are you aware that this approach will fail as soon as you have deferred binding properties (your own or through a 3rd party lib) that can only be filled with a value through JS execution inside the browser? Or put differently: If you have a deferred binding property whose values can not be inferred from the user agent string.It would be far more robust if you would only embed the app.nocache.js contents into your index.php/jsp and leave the permutation files untouched. That way you eliminate the request of app.nocache.js but you can still have any kind of deferred binding property.If you still want to follow your path, I think you need to implement your own linker that changes the names of the emitted artifacts to the format you would like to have.A basic example of a custom linker: http://webcentersuite.blogspot.de/2011/05/writing- gwt-linker-for-offline.html -- 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+unsubscribe@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/groups/opt_out.
No comments:
Post a Comment