I must admit I didn't spend enough time to fully understand why the
gwt original implementation did all that stuff for resetting time. Many
thanks for the detailed explanation.
At the moment I have no access to dev tools, anyway I'm just wondering if
there's still room for optimizations without
I guess com.google.gwt.user.datepicker.client.CalendarUtil.getDaysBetween(Date,
Date) was written with datepicker in mind, BTW I've seen some code making
heavy use of that method, and its performance was badly impacted.
Since actual implementation internally instantiates two new dates per every
Thanks! I'll give it a try as soon as I return at office. Did you consider
contributing the gwt project with this patch?
Davide Cavestro
Aleš Pečnik pecnika...@gmail.com ha scritto:
I use meta tag in HTML for setting locale:
meta name=gwt:property content=locale=en /
I use GWT from trunk
Hey guys, no idea at all? I would need a way to set the locale for the
super dev mode compile (even from dedicated bookmarklets would be enough...)
On Friday, July 18, 2014 4:10:50 PM UTC+2, Davide Cavestro wrote:
It seems that the super dev mode cannot benefit from the meta tag
https
It seems that the super dev mode cannot benefit from the meta tag
https://code.google.com/p/google-web-toolkit/issues/detail?id=8175 defined
within a dynamic host page. I originally tried switching to the cookie
solution, but now I guess the compilation triggered by the bookmarklet
simply
don't know how to
propose a new patch to the existing review. May I post the changed file
here?
Cheers
Davide
On Tuesday, February 25, 2014 3:31:28 PM UTC+1, Thomas Broyer wrote:
On Tuesday, February 25, 2014 3:25:47 PM UTC+1, Davide Cavestro wrote:
Hi all,
I am in the process of switching
I'm just wondering if there's a DTD available for *.gwt.xml* file related
with the 2.6.0 release
I'd expect to find it at http://google-web-toolkit.googlecode.com/svn/
tags/2.6.0/distro-source/core/src/gwt-module.dtd but actually there's no
2.6.0 tag into svn repo
--
You received this
Hi all,
I am in the process of switching linker to Cross-Site-Iframe in order to
obtain the compatibility with superdevmode, so I'd like to locate and
remove the script tags from the modules I'm inheriting from (since this
linker doesn't support them).
Now I'm just wondering if there's an easy
I've seen that SmartGWT provided the *NoScript* flavour for their modules,
i.e. instead of inheriting from *SmartGwt* you inherit from
*SmartGwtNoScript.*
I've seen also adding
set-configuration-property name='xsiframe.failIfScriptTag' value='FALSE'/
to your .gwt.xml file works (as suggested by
=
sheetFrame.contentWindow.document.createElement('script'); s.src =
'http://localhost:9876/dev_mode_on.js';
void(sheetFrame.contentWindow.document.getElementsByTagName('head')[0].appendChild(s));}
Cheers
Davide
On Wednesday, February 12, 2014 5:55:07 PM UTC+1, Davide Cavestro wrote:
I have
I have an entry point hosted into an iframe. I have to manually open the
host page into a new browser tab in order to make the superdev mode aware
of the modules available (otherwise the superdev mode UI doesn't detect any
module).
I've tried to manually tweak the bookmarklet code in order to
I have to support the deployment of additional modules in order to
dynamically extend my employer's GWT application, adding new features or
customizing the existing ones.
I mean *something like a plugin system which dynamically loads and executes
new code deployed at any point of time*.
The
@Ed
I really hope you are right... but so far I've had the same feelings of
Mauro and David
I guess some discouragement/vexation could be avoided adding an explanatory
comment before or contextually tagging an issue as *AssumedStale*, and
especially avoid stating
I spent more than half an
13 matches
Mail list logo