I am also confused ...
I understand the cleaning up action but don't understand certain
bug/issues being marked as Stale that have many votes... (like mentioned
above)
Maybe an idea that the gwt dev team adds additional comments to these
kind of issues such that we get a better understanding.
Hello,
For example take the example in the documentation:
https://developers.google.com/web-toolkit/doc/latest/DevGuideCodingBasicsHistory
In short, it is a tab panel with 3 tabs, and history functionality is added
so you can use back and forth browser buttons to navigate to previous/next
You use the same emulators that you would use when developing a native app
:-)
On Thursday, May 23, 2013 5:32:22 AM UTC+2, mike b wrote:
Ed , thx for the reply. Can you point me to a device emulator?
--
You received this message because you are subscribed to the Google Groups
Google Web
I think its not the default behavior because its more likely that you use
the history.newItem() method to actually navigate to a different place.
Actually when your whole app uses history tokens, then clicking on the tab
title would not cause the tab panel to switch tabs itself but it would
On Monday, May 27, 2013 2:25:28 AM UTC+2, V.B. wrote:
3) How much weight does the Steering Committee give to heavily starred
issues (i.e. the kind that are too large for individuals to tackle)? The
top three open issues are:
java.util.Calendar
Hi,
I have a DTO object to transfer some data via RPC from client to server
back and forth.
Therefore I though placing this DTO in the /shared folder would be right.
BUT: if I do so, I constantly get an exception.
IF I move the DTO into the /client folder instead, everything works fine.
Why is
First you have to add source path=shared/ to your App.gwt.xml and then
you have to make sure that the class file is deployed to your server. The
last part is probably already given as you have said it works when putting
the file into the client package. Sounds like you deploy all classes to the
Use History.newItem(token,false) to avoid firing the history event in the
first part of your code.
Calling History.newItem(token) cause firing of the history event...
On Mon, May 27, 2013 at 1:51 PM, Jens jens.nehlme...@gmail.com wrote:
I think its not the default behavior because its more
Hi,
I am trying to store blob data into datastore, successfully i have inserted
two rows of data. after that am not able to run the application and am
getting below error. Pls advice me what to do? i tried with adding of
Jdk1.7 in the build path but it did't work. error code is :
May 27, 2013
Hi
I done a internationalization in GWT.Everthing works perfectly.But i didn't
find my properties file after deployed the project.if i want to change the
property file content how to do ?
Pls advise...
On Wednesday, July 16, 2008 2:29:43 PM UTC+5:30, Nicole wrote:
Hi GWT experts,
I need
I am happy to read that I am not the only one who has this feeling.
And I don't agree with using purely the number of stars to drive the
triage. Certainly taking 100 as a minimum is extremely high if you consider
the small number of advanced GWT developers (who would bother reporting
these
Check, if there is an old version of the gwt-servlet.jar in your classpath.
Am Montag, 27. Mai 2013 13:02:42 UTC+2 schrieb membersound:
Hi,
I have a DTO object to transfer some data via RPC from client to server
back and forth.
Therefore I though placing this DTO in the /shared folder
You could try m-gwt http://www.m-gwt.com/'s slider:
- demo http://mobilegwt.appspot.com/showcase/#SliderPlace:
-
javadochttp://docs.mgwt.googlecode.com/git/javadoc/latest/com/googlecode/mgwt/ui/client/widget/MSlider.html
Milan
On Tuesday, March 5, 2013 8:46:57 PM UTC+1, Ignacio Baca
And I don't agree with using purely the number of stars to drive the
triage. Certainly taking 100 as a minimum is extremely high if you consider
the small number of advanced GWT developers (who would bother reporting
these issues).
Totally agree.
If you wait till people vote the issue
Hi David and Ed and Jim,
Thanks for chiming in. I'm glad I'm not alone. I completely agree that
bugs should come first, period. That goes without saying. My previous
question about weighing by stars was intended to be specific to
enhancements and feature requests. You're right, bugs should
Posting David's comment (in blue) from Issue
1328https://code.google.com/p/google-web-toolkit/issues/detail?id=1328#c11
:
#8
[Issue marked as AssumedStale]
#9 (*David*)
Hey, why make this stale? When you are using IFrames in applications you
really need more events than GWT is offering.
#10
Hi,
I have small question, since google move from 3.11 to maps version 3.12 as
a new stable release, my application started to act uncorrect.
What is interesting is that the devmode works all ok on FF, but after
compile and deploy the polylines and markers are not working...(on any
browser)
Hi,
I would like to extend one of my EntityProxy hierarchies (BaseProxy,
ALeafProxy, BLeafProxy) with a typical Visitor pattern implementation.
Is there a solution ready for this?
I suspect this would require extending the GWT compiler or something like
that.
Would someone point us in the
EntityProxys are implemented using AutoBeans so you can use
AutoBeanUtils.getAutoBean(EntityProxy proxy) to get an AutoBean instance
from your proxy and then use an AutoBeanVisitor to traverse your hierarchy.
-- J.
--
You received this message because you are subscribed to the Google Groups
I like to use vanilla maven + antrun plugin for invoking the gwt compiler.
See:
http://dmenounos.blogspot.gr/2011/01/maven-gwt.html
You gain complete control of the build process.
Τη Πέμπτη, 23 Μαΐου 2013 2:32:35 π.μ. UTC+3, ο χρήστης Srinivasa Rao έγραψε:
Hi , I am looking for the GWT
You can run webAppCreator for Maven, see what is creates, and tweak it.
$ webAppCreator -templates sample,maven,readme -out app251 -junit
~/dev/junit4.10/junit-4.10.jar
On Wednesday, May 22, 2013 7:32:35 PM UTC-4, Srinivasa Rao wrote:
Hi , I am looking for the GWT project with the maven
It just happens that way from time to time, although I've never had do to a
full restart. Many recommend moving to Super Dev
Modehttps://developers.google.com/web-toolkit/doc/latest/ReleaseNotes#superdevmodefor
Chrome.
On Sunday, May 26, 2013 7:15:34 PM UTC-4, Mike John wrote:
Hey there,
Hi, I wrote this in the issue tracker but I was redirected to here.
Found in GWT Release (2.5.1, 2.5.0.rc1)
Encountered on OS / Browser (Win7, Google Chrome):
Detailed description:
Dear folks,
we have a complex and large gwt app with many rpc calls.
In Google Chrome, there are some rpc call
This looks like you have some old versions of the gwt-servlet.jar in your
classpath.
Am Montag, 27. Mai 2013 13:48:03 UTC+2 schrieb Raghu rao:
Hi,
I am trying to store blob data into datastore, successfully i have
inserted two rows of data. after that am not able to run the application
Just my 5 cents,
Decisions on browser support seems to be mostly driven by Google statistics
... but many GWT apps are running outside of the internet. The apps that I
am maintaining and developing run in a banking environment, where the
browser usage statistics are a lot different - IE8 is
Thomas Broyer has uploaded a new change for review.
https://gwt-review.googlesource.com/2980
Change subject: Fix ValuePicker.setValue(T) to no longer fire events.
..
Fix ValuePicker.setValue(T) to no longer fire events.
Thomas Broyer has uploaded a new patch set (#2).
Change subject: Fix ValuePicker.setValue(T) to no longer fire events.
..
Fix ValuePicker.setValue(T) to no longer fire events.
Bug: issue 7330
Change-Id:
Thomas Broyer has posted comments on this change.
Change subject: Fix for issue 1525
..
Patch Set 2:
On mousedown, capture is used to mimick native buttons with the *purpose*
the prevent mouse events on other elements until
Jens Nehlmeier has posted comments on this change.
Change subject: Fix ValuePicker.setValue(T) to no longer fire events.
..
Patch Set 2: Code-Review+1
Looks good.
The only minor nip-pick would be that calling setValue() with
Thomas Broyer has posted comments on this change.
Change subject: Fix ValuePicker.setValue(T) to no longer fire events.
..
Patch Set 2:
AFAICT, no, they won't be in sync, as it's the purpose of the
SelectionChangeHandler to
Jens Nehlmeier has posted comments on this change.
Change subject: Fix ValuePicker.setValue(T) to no longer fire events.
..
Patch Set 2:
Oh right, makes totally sense.
--
To view, visit
Thomas Broyer has posted comments on this change.
Change subject: Add support for the newer bindery HandlerRegistration
Bug: issue 7079
..
Patch Set 3: Code-Review+1
(1 comment)
Daniel Kurka has submitted this change and it was merged.
Change subject: Fix javadoc URL for geolocation.
..
Fix javadoc URL for geolocation.
Change-Id: I58ace2957b4c04764aa2602f339da68bd1debca7
---
M
Daniel Kurka has posted comments on this change.
Change subject: Fix javadoc URL for geolocation.
..
Patch Set 1: Verified+1 Code-Review+2
Submitted, thanks for putting in the time!
--
To view, visit
[-gwt-steering, +gwt-contrib]
On Mon, May 27, 2013 at 9:32 AM, Daniel Kurka danku...@google.com wrote:
We also need the permutations for blink.
Are there technical reasons for why we need to remove permutations to be
able to add new ones? E.g., why can't we start using soft
Daniel Kurka has uploaded a new change for review.
https://gwt-review.googlesource.com/2972
Change subject: JsRootScope contained typo in literal
..
JsRootScope contained typo in literal
fixes issue 8123
Change-Id:
Thomas Broyer has posted comments on this change.
Change subject: JsRootScope contained typo in literal
..
Patch Set 1: Code-Review+2
--
To view, visit https://gwt-review.googlesource.com/2972
To unsubscribe, visit
Daniel Kurka has posted comments on this change.
Change subject: fix mismatch in Double/Float.isInfinite between dev /
production
..
Patch Set 1:
Can someone approve this, so we can get this committed?
--
To view, visit
Daniel Kurka has uploaded a new change for review.
https://gwt-review.googlesource.com/2973
Change subject: make FastMap use JavaScriptObject
..
make FastMap use JavaScriptObject
fixes issue 2356
Change-Id:
Thomas Broyer has posted comments on this change.
Change subject: make FastMap use JavaScriptObject
..
Patch Set 1: Code-Review+2
--
To view, visit https://gwt-review.googlesource.com/2973
To unsubscribe, visit
John A. Tamplin has posted comments on this change.
Change subject: fix mismatch in Double/Float.isInfinite between dev /
production
..
Patch Set 1: Code-Review+2
--
To view, visit https://gwt-review.googlesource.com/2250
Daniel Kurka has posted comments on this change.
Change subject: fix mismatch in Double/Float.isInfinite between dev /
production
..
Patch Set 1:
Still seem to be missing a verified from jenkins. Guy seems to be on
On Mon, May 27, 2013 at 4:40 AM, stuckagain david.no...@gmail.com wrote:
Decisions on browser support seems to be mostly driven by Google
statistics ... but many GWT apps are running outside of the internet. The
apps that I am maintaining and developing run in a banking environment,
where the
Note that, just to make things clear for everyone, removing the ie6
permutation means removing support for IE8 in IE7 mode and quirks mode
(this one has been discouraged, if not deprecated, for years now).
This is a step forward and, if you ask me, I don't care about those
companies that don't
John A. Tamplin has posted comments on this change.
Change subject: FileUpload failed to initialize internal state
..
Patch Set 1: Code-Review+2
--
To view, visit https://gwt-review.googlesource.com/2981
To unsubscribe, visit
Daniel Kurka has uploaded a new change for review.
https://gwt-review.googlesource.com/2981
Change subject: FileUpload failed to initialize internal state
..
FileUpload failed to initialize internal state
fixes issue 5055
Thomas Broyer has posted comments on this change.
Change subject: FileUpload failed to initialize internal state
..
Patch Set 1: Code-Review-1
(1 comment)
File
Hello John A. Tamplin, Thomas Broyer,
I'd like you to reexamine a change. Please visit
https://gwt-review.googlesource.com/2981
to look at the new patch set (#2).
Change subject: FileUpload failed to initialize internal state
Thomas Broyer has posted comments on this change.
Change subject: FileUpload failed to initialize internal state
..
Patch Set 2: Code-Review+2
--
To view, visit https://gwt-review.googlesource.com/2981
To unsubscribe, visit
Some companies have slow upgrade cycles but we can still have sympathy for
the developers who work for them. But I agree that since upgrading GWT is
optional (for those using stable releases), we shouldn't have to worry
about them too much.
Note that Microsoft stops supporting Windows XP next
Daniel Kurka has uploaded a new change for review.
https://gwt-review.googlesource.com/2974
Change subject: ActivityManager fails to clear Eventbus
..
ActivityManager fails to clear Eventbus
fixes issue 5621
Change-Id:
Thomas Broyer has posted comments on this change.
Change subject: ActivityManager fails to clear Eventbus
..
Patch Set 1: Code-Review+2
Are there tests for this class? Can that behavior be tested?
--
To view, visit
May be you have to resubmit the patch? I think the patch was submitted
before we hired Jenkins and he did not notice that he should be also
verifying old patches. May be there is a way to force Jenkins to verify a
patch.
Roberto Lublinerman | Software Engineer | rlu...@google.com | 408-500-9148
53 matches
Mail list logo
