Anyone have any idea on this ? It seems strange to me that the ISP could do
this kind of alteration to the code. Although the tests I did so far seem
to confirm this : I tested my apps on two other ISPs mobiles and it worked.
(There are 3 majors mobile ISPs here in France, one of which - *SFR*
Anyone have an idea on this ? It seems wierd to me that the 3G ISP can
alter the code like this. Although some additionnal tests I did seem to
confirm this : I tested 2 other majors 3G ISPs and the problem didnt occur.
Am I the only one having this issue ? I have the problem with *SFR* which
Hi,
We are trying to create a cell table with tons of entries.
We use pagination. (AsyncDataProvider and Pager) and would like to fetch
on demand entries.
Currently it does work as intended,
only problem is, when we show some entries on the cell table (let's say
entries #1-#25)
and then
It is good approach to fetch same data from server instead of maintain data
block at client side.
If you write such a logic like
1)Maintain index in contact object or create one custom bean which has
three variable like start, end and ListContact.
2)Create one ListContact or custom bean in
I tryed to post two answers in here but they didnt get posted. I guess
there was something wrong with them. Can I have some clarification on it
please ? :)
Thanks alot !
Le dimanche 6 octobre 2013 12:20:26 UTC+2, Martones a écrit :
Hi Jens,
This is exactly the case. The nocache.js is gone
You could use it as a feature ;-)
I have a HostPageServlet that generates the index.html file and
automatically inlines app.nocache.js along with other one time
information I need on app start. This reduces the app startup time by
minimizing the required network requests. All resources that
Oh my, my messages got all posted. I dont know why I didnt see them in my
session. Sorry for the spam. I'm deleting the useless ones.
I see what you mean, but I dont have the possibility to change the relative
path from where GWT fetches the permutations, do I ? I'm using quite a few
code
Oh my, my messages got all posted. I dont know why I didnt see them in my
session. Sorry for the spam. I'm deleting the useless ones.
I see what you mean, but I dont have the possibility to change the
relative path from where GWT fetches the permutations, do I ? I'm using
quite a few
I am currently working on a reporting tool. Therefore I need a very
intuitive UI that allows users with no background in SQL to build
themselves a query and get the retrieved information bundled in a report. I
searched for sql query builders and must say that this one tops all of them
at the
Hi Thomas,
is it possible to use ValueProxy to make serialization of 3rd party classes
easier? I have a bunch of Solrj classes and I had to create DTOs and copy
data to them manually.
I consider to use RequestFactory and ValueProxy for automatic mapping. Does
it make sense?
Here is the SO
I ran into the same issue. See the previous post. I still don't have a
solution for it. Some questions that I have are (1) Is there a size
threshold for when the carrier does not optimize the js in inline (2) Is
there a way to whitelist a GWT site to not be optimized by the carrier (3)
Is
Jens, it that code public for always inlining?
No as it contains some app specific code. But its really easy to implement.
Create index.tpl that contains the index.html code (host page). Instead of
script src=..app.nocache.js/ you put a replacement tag in the file like
I had the same problem with EE in the UK. Changing the URL to https fixed
the problem.
-ken
On Tuesday, October 8, 2013 2:58:59 PM UTC+1, Paul Mazzuca wrote:
I ran into the same issue. See the previous post. I still don't have a
solution for it. Some questions that I have are (1) Is
I do it as a simple JSP:
https://github.com/tbroyer/gwt-maven-archetypes/blob/master/guice-rf-activities/src/main/resources/archetype-resources/__rootArtifactId__-server/src/main/webapp/index.jsp
(note the meta to tell the nocache.js file where to find the *.cache.*
files)
On Tuesday, October
I'm trying to verify that some JavaScript code behaves identically to an
existing Java library. I've created some tests that subclass GWTTestCase to
check this. Unfortunately, when I try and do the pure-java test in
development mode (by returning null for the module name, as the
documentation
On Tuesday, October 8, 2013 5:08:04 PM UTC+2, Derek Thurn wrote:
I'm trying to verify that some JavaScript code behaves identically to an
existing Java library. I've created some tests that subclass GWTTestCase to
check this. Unfortunately, when I try and do the pure-java test in
Hi GWT people !
I am pleased to annonce the first public ralease
of arondor-common-reflection, a tiny lib which provides Spring-Beans IoC to
GWT.
Licensed under Apache Public License, and performs quite well !
As most of you I guess, we came from the Java world and jumped to GWT with
our Java
Hi André,
Would you mind sharing the code from your solution so that implements Jens
idea? It would be great for newbies like me looking for a solution for this
problem.
Thanks!
Manu
On Friday, 11 May 2012 13:45:49 UTC+2, André Salvati wrote:
I've just translated messages to portuguese
Which is the library URL?
2013/10/8 Francois Barre francois.ba...@gmail.com
Hi GWT people !
I am pleased to annonce the first public ralease
of arondor-common-reflection, a tiny lib which provides Spring-Beans IoC to
GWT.
Licensed under Apache Public License, and performs quite well !
As
That sounds promising, got a link to the tests?
On Tuesday, October 8, 2013 8:22:18 AM UTC-7, Thomas Broyer wrote:
On Tuesday, October 8, 2013 5:08:04 PM UTC+2, Derek Thurn wrote:
I'm trying to verify that some JavaScript code behaves identically to an
existing Java library. I've created
I have given it a go. Here is my working
codehttps://gist.github.com/manubotija/6890550
Now that I understand how this works, I wonder if there is a simpler
solution for just setting the default Interpolator locale...
This guy here http://stackoverflow.com/a/928/2819482 seems to have a
I am still stuck here. I have seen this nice post
http://stackoverflow.com/a/5642394/2819482on SO and verified that I
comply to its recommendations.
- I don't store any RequestContext instance.
- I have two immutable EntityProxy that I retain beyond the duration of
their associated context's
Google suggets use FlowPanel in replace of VerticalPanel since
VerticalPanel does not work well in Standards Mode.
So How to make FlowPanel flow its children vertically like VerticalPanel?
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
[cc: gwt-contrib, please follow-up there]
On Tue, Oct 8, 2013 at 10:06 AM, Artur Signell ar...@vaadin.com wrote:
On Oct 8, 2013, at 4:59 AM, Matthew Dempsky mdemp...@google.com wrote:
On Mon, Oct 7, 2013 at 1:17 AM, Joonas Lehtinen joo...@vaadin.com wrote:
Furthermore we should decide if
As long as we don't use Java8 specific features in non-supersourced code,
we can get away with running on other JREs. So for example, the public
interfaces and internal implementations of gwt-user APIs could probably not
rely on java.util.function, java.util.streams, or java.time. If that were
the
I think we can require Java7 or 8 to build GWT applications, but we need to
make sure that GWT applications can be deployed to servers running Java6
for a while. This would mean not using any Java7 or 8 language features in
gwt-servlet and RequestFactory.
For many companies it is a problem to
I think we can require Java7 or 8 to build GWT applications, but we need
to make sure that GWT applications can be deployed to servers running Java6
for a while. This would mean not using any Java7 or 8 language features in
gwt-servlet and RequestFactory.
For many companies it is a
On Tuesday, October 8, 2013 12:35:36 PM UTC+2, Jens wrote:
I think we can require Java7 or 8 to build GWT applications, but we need
to make sure that GWT applications can be deployed to servers running Java6
for a while. This would mean not using any Java7 or 8 language features in
Re. Java, we should align with Oracle's lifecycles. Yes OpenJDK 6 is still
maintained, but I can't see any reason not to mandate Java 7 (for the
developer). For deployment, maybe we could say the two latest major Java
versions, which means 6 and 7 for GWT 2.6, and 7 and 8 for GWT 3.0
This discussion has covered what the general rules for dropping support for
browsers, APIs and JVMs should be. That's a good thing, but what I would really
like is for GWT to specify the actual dates when it is expected that GWT will
no longer support particular runtime server JVM versions and
On Tuesday, October 8, 2013 3:31:09 PM UTC+2, Paul Robinson wrote:
This discussion has covered what the general rules for dropping support
for browsers, APIs and JVMs should be. That's a good thing, but what I
would really like is for GWT to specify the actual dates when it is
expected
[...] since in practice we won't consider ourselves bound to them.
Why not?
-- J.
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
---
You received this message because you are subscribed to the Google Groups GWT
Contributors group.
To unsubscribe from this group and
Le 8 oct. 2013 20:27, Brian Slesinsky skybr...@google.com a écrit :
I don't think we should be publishing general rules to the GWT website,
since in practice we won't consider ourselves bound to them. At this point
I think we're in general agreement that IE6/7 will be dropped after GWT 2.6
and
On Tue, Oct 8, 2013 at 12:15 PM, Jens jens.nehlme...@gmail.com wrote:
[...] since in practice we won't consider ourselves bound to them.
Why not?
Because we'll either we'll forget about that page due to turnover or
something new will happen and priorities will change. Put it this way: how
But we now have a steering committee, and decisions are made in public so
anyone can bug you when you forget. That's a different situation than
before.
Le 8 oct. 2013 22:43, Brian Slesinsky skybr...@google.com a écrit :
On Tue, Oct 8, 2013 at 12:15 PM, Jens jens.nehlme...@gmail.com wrote:
In practice on open source projects, things happen because some person or
company volunteers to implement them and sees the project through to the
end. So I don't really see steering committee schedule-making as a process
that's going to work. The Google GWT team is going to set its own quarterly
I don't think we should make hard guarantees, but we should have roadmaps
and milestones. If you look at how Firefox and Chromium work, they put all
kinds of new HTML5 features on the wishlist, prototype implementations are
done behind experimental flags, but most don't make the cut. Finally, they
Sounds to me that you suddenly start talking about feature guarantees for
features that do not yet exist, e.g. supporting a new browser or a new HTML
5 API. That wasn't really my intention and maybe you misunderstood it.
What I was talking about are guarantees about how long *existing* features
38 matches
Mail list logo
