Re: com.google.gwt.core.client.JsonUtils,safeEval(String) throws exception in GWT 2.7

[funkforce]

Thanks Jens, I think that should be it. I was able to recreate the error my 
self when setting compatibility view on ie 8. 

OT: Reading the gwt source is a joy! So clear and so easy to understand and 
good comments. Yes I am sure there are places were this is not the case but 
from what I have seen it looks good.

On Monday, January 5, 2015 3:14:40 PM UTC+1, Jens wrote:
>
> GWT 2.7. has removed a runtime check if JSON.parse() is available in the 
> browser because GWT 2.7. does not support IE6/7 anymore and JSON.parse() is 
> available in IE 8+ when in standards mode.
>
> So maybe these users launch your app in compatibility view / quirks mode 
> for whatever reason. Alternatively they might have browser addons installed 
> that cause strange behavior.
>
> -- 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+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.

Can IntelliJ show variable values rather than type when debugging via SDM?

[Richard Wallis]

Trying out IntelliJ and the one thing keeping me from switching is that the 
debugger shows a variable's type instead of value.

eg: an ArrayList containing "Foo" and "BAR" will show as ArrayList$ 
instead of ["FOO", "BAR"]

Has anyone got the debugger to show the value of toString() instead of the 
varaible's type?

---

It should be possible because SDBG manages it in eclipse using the 
callToString() method in it's WebkitRuntime class:

https://github.com/sdbg/sdbg/blob/master/com.github.sdbg.debug.core/src/com/github/sdbg/debug/core/internal/webkit/protocol/WebkitRuntime.java#L191

-- 
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+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: Can IntelliJ show variable values rather than type when debugging via SDM?

[Jens]

Only manually. Right click on a node in the variables section and select 
"evaluate expression...". In the new window add .toString() to the 
expression and hit evaluate. 

-- 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+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: Can IntelliJ show variable values rather than type when debugging via SDM?

[Richard Wallis]

Thanks will give it a try.

On Wed, Jan 7, 2015 at 4:27 PM, Jens  wrote:

> Only manually. Right click on a node in the variables section and select
> "evaluate expression...". In the new window add .toString() to the
> expression and hit evaluate.
>
> -- J.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Google Web Toolkit" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-web-toolkit/qAN3TrfQZ50/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-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 
"Google Web Toolkit" 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: SafeHtmlTemplate display alternative (backgorund- or cell-) image inside (mgwt)CellList-Item if image not available

[marian lux]

I tried to create my own custom ImageLoadingCell but I have a problem to 
get any Browser Event fired.

My custom cell extends AbstractCell and if I overwrite the Browser 
Event method. E.g.:

@Override
 public void onBrowserEvent(Context context, Element parent, ActivityItem 
value,
NativeEvent event, ValueUpdater updater) {
 Window.alert("browserevent!");
 } 


the alert-box will never called.

I also called in the constructor e.g.: 
super(BrowserEvents.CLICK);

to listen for click-events. But nothing happens If I click.

As I said before, I use mgwt CellList. The mgwt-CellList does not need the 
" extends AbstractCell", it needs " implements Cell" and 
it's own render method. I think there is no event support implemented. 
(https://github.com/mgwt/mgwt/blob/master/src/main/java/com/googlecode/mgwt/ui/client/widget/list/celllist/CellList.java)
 
How can I achieve it to listen on events to get notified if an Image could 
not be loaded correctly? So I could replace it with a default image.


Am Dienstag, 6. Januar 2015 09:57:04 UTC+1 schrieb marian lux:
>
> @Thomas: Thank you. After a quick research, ImageLoadingCell was also in 
> my opinion.
> But if I use ImageLoadingCell, how do I apply to use the image displaying 
> as background image? I want to overlay a text over the image as you can see 
> in my template above. Also as you can see, I did this (as background image) 
> with SafeStylesBuilder.
> The other thing: I experimented a little bit with the ImageLoadingCell and 
> ImageCell and didn't get the ImageLoadingCell working inside a mgwt 
> CellList e.g.:
> CellList cellList = new CellList(new MyItemCell());
> (inside a CellWidget I could display it without any problem).
>
> Can you give me a code snippet - based on my sample code above - how this 
> should work?
>
>
> @Ignacio: I have no control over the server code and the images(URLs) 
> could be temporary offline.
>

-- 
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+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: ClassCastException when trying SuperDevMode on my application with 2.7

[Roland]

Here's a bit of follow up on this issue.

First of all as pointed out in the discussion in this issue 
 (which 
links to this G+ post 
) this 
problem is not related to SDM and this issue is not what was preventing my 
application from starting in SDM.

Turns out my EntryPoint was a sub-class of another class and neither class 
was marked as "implements EntryPoint". Inspite of this problem, the 
application runs when compiled and deployed and would start and run under 
SDM with GWT 2.6.0, but would not run in SDM in GWT 2.7.0. After correcting 
that problem the I can use SDM and am quite happy with it in combination 
with the SDBG plug-in (thanks for the setup tutorial 
).

The exception is still thrown (as is a similar exception when the code 
server runs in 2.6), but the application starts and I can debug. Bottom 
line: pilot error.

Roland

On Tuesday, November 25, 2014 4:56:44 PM UTC-6, Roland wrote:
>
> Thanks. So far I have been unable to isolate this into a smaller example. 
> I've tried some very basic entrypoint classes and added the external 
> modules I use like the Openlayers gwt wrapper and the gwttime (which has 
> one of its classes mentioned in the trace). They all have worked fine.
>
> Open to any suggestions for how to get more information about what's going 
> on that I can report back...
>
> Roland
>
> On Saturday, November 22, 2014 1:20:45 PM UTC-6, John Stalcup wrote:
>>
>> It sounds like one of the registered EntryPoint classes or something that 
>> one of the EntryPoint classes is being rebound to does not implement the 
>> EntryPoint interface.
>>
>> On Sat, Nov 22, 2014, 1:29 AM Thomas Broyer  wrote:
>>
>>> +cc stalcup@
>>>
>>> Any idea John?
>>>
>>> Roland, can you make a small repro-case?
>>>
>>> On Saturday, November 22, 2014 12:38:16 AM UTC+1, Roland wrote:

 With the advent of 2.7 I am determined to get going with SuperDevMode. 
 However, once my development environment (Eclipse) is all set to run the 
 code server when I try to load my application using SuperDevMode I get the 
 following error. This actually happens whether I compile with debug mode 
 on 
 or debug mode off when loading the code this way. I don't know what piece 
 of the tool chain is reporting the error, but this shows up in my 
 JavaScript console.

 Uncaught java.lang.ClassCastExceptionCast.java:59 

 dynamicCast_0_g$   
   gov_00046noaa_00046pmel_00046tmap_00046las_00046UI__
 EntryMethodHolder.java:3

 init_2_g$ModuleUtils.java:44 

 initializeModules_0_g$   Impl.java:247 

 apply_1_g$   Impl.java:306 

 entry0_0_g$  Impl.java:72 

 (anonymous function) ModuleUtils.java:55 

 gwtOnLoad_0_g$   PeriodPrinter.java:40 
 (anonymous function)

 This happens both when I try Firefox 33.0 and Chrome Version 
 39.0.2171.65 (64-bit) as the browser. The application runs fine as a 
 production app if I compile it and deploy it to the server from the 
 command 
 line. I could also debug it using Classic Development Mode using FF 24 
 just 
 prior to now when I was using GWT 2.5. I run in MyEclipse 2015 on Ubuntu 
 14.04 if that makes a difference.

 If this is a problem with the framework and not my application I'm 
 happy to help try to gather the information to get it fixed, but I would 
 need some guidance for how to gather the details needed to debug.

 Thanks,

 Roland



-- 
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+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: SafeHtmlTemplate display alternative (backgorund- or cell-) image inside (mgwt)CellList-Item if image not available

[Jens]

A bit unfortunate that GWT has a CellList and MGWT has a CellList and both 
are totally different. Maybe you should ask this on a MGWT mailing list?

But given that MGWT CellList is a Widget you can add any event handler to 
it using addDomHandler(). I am not sure about the error event but I would 
try adding a ErrorEvent/ErrorHandler to the CellList. If it really triggers 
then you should be able to figure out the  element and change its src 
attribute if loading has failed.

And yes you need an  element because no event exists that tells you if 
a CSS background image has been loaded or not.

-- 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+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.

HTTP Client API for GWT - Requestor (Announcement)

[Danilo Reinert]

Finally, a real HTTP Client API is available for the GWT ecosystem: 
Requestor.
It was released today (Jan 7th) under the version 0.1.0 but is being 
developed for almost a year.
The project has a great documentation and a showcase application.
More features and improvements are already planned.
The initial release is stable and ready for production.
The community is invited to know and dig deep in the project.

Following the release notes.


Requestor - Requesting made easy for GWT

Requesting is the most common operation in AJAX applications. 
GWT is an excellent platform for developing AJAX applications, but it still 
bother us when it comes to requesting.
Using RequestBuilder, the default GWT way of requesting, is a low-level 
approach which requires too many steps and manual processing to achieve 
meaningful data for our application.
Requestor solves theses issues with a full featured and fluent API for 
requesting. 
A real HTTP Client API for GWT, it is made upon modern programming concepts 
like Promises and Method Chaining, and is designed to be as extensible as 
possible.
Carefully crafted, Requestor provides many features while allows the easy 
configuration and customization of them all.


Features

* Promises (integrate any promise library)
* Fluent API
* Full support to Form requests (urlencoded or multipart)
* Full support to raw binary data (File, Blob, ArrayBuffer, Json, Document)
* Progress monitoring of uploads and downloads
* BASIC and CORS authentication
* Support for implementing any custom authentication
* Nice header manipulation
* Uri Building
* Filters (enhance requests and responses)
* Interceptors (transform payloads)
* Auto JSON serialization for POJOs, JavaBean Interfaces and Overlay types
* Integrated to the AutoBean Framework
* Integrated to gwt-jackson
* Integrated to TurboGWT
* Handle multiple serialization of the same java type for different media 
types
* Customizable request dispatching (support for caching and synchronization)


Links

Repo: https://github.com/reinert/requestor
Site: http://reinert.io/requestor/latest
Wiki: https://github.com/reinert/requestor/wiki
Group: https://groups.google.com/forum/#!forum/requestor
Showcase: http://reinert.io/requestor/latest/examples/showcase

-- 
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+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: Where to call an Action when user remove an uploaded image in GWTUpload?

[Manuel Carrasco Moñino]

Answered in stackoverflow, let me know if this solution works for you.


On Tue, Sep 30, 2014 at 11:38 AM, Tom  wrote:

> I am using GWTUpload , the library is in here
> https://code.google.com/p/gwtupload/
>
> The Example code at client side found on that website has this structure:
>
>  // Attach an image to the pictures viewer
> private OnLoadPreloadedImageHandler showImage = new 
> OnLoadPreloadedImageHandler() {
> public void onLoad(PreloadedImage image) {
>   //showImageFlowPanel code solution 1
>   image.setWidth("75px");
>   showImageFlowPanel.add(image);
> }
> };
>
>
> private IUploader.OnFinishUploaderHandler onFinishUploaderHandler = new 
> IUploader.OnFinishUploaderHandler() {
>   public void onFinish(IUploader uploader) {
> if (uploader.getStatus() == Status.SUCCESS) {
>
>   new PreloadedImage(uploader.fileUrl(), showImage);
>
>   UploadedInfo info = uploader.getServerInfo();
>
>   String headShotImageUrl="http://"+Window.Location.getHost()+"/" 
> +"images/uploaded/"+info.message;
>   //headShotImage code solution 2
>   if(!"".equals(headShotImageUrl) && 
> UriUtils.isSafeUri(headShotImageUrl)){
>   headShotImage.setUrl(UriUtils.fromString(headShotImageUrl));
>   }
>
>
>
> }
>   }
> };
>
> The example uses showImageFlowPanel (solution 1) to store the image but I
> want to store the image inside headShotImage which take the url after
> user uploaded image successfully, see the headShotImage (solution 2) code
> above.
>
> Ok, the headShotImage code work fine but I dont know how to remove it when
> users remove the image. If I use showImageFlowPanel as in the solution 1
> then the program remove the image automatically for me and I do not need to
> do anything.
>
> So my question is "*Where to call an Action when user remove an uploaded
> image in GWTUpload?*"
>
>
> http://stackoverflow.com/questions/26117517/where-to-call-an-action-when-user-remove-an-uploaded-image-in-gwtupload
>
> --
> 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+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 
"Google Web Toolkit" 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: Development Mode will not be supported in Firefox 27+

[Slava Pankov]

Just tiny update. Dev mode is still working just fine on Windows with 
Chromium 38.0.2125.0 (292384) from Dart 1.8.3 distribution.

On Monday, February 3, 2014 4:01:41 PM UTC-8, Brian Slesinsky wrote:
>
> Mozilla has stopped exporting some C++ symbols that the Firefox plugin 
> relies on [1]. Therefore it's not possible to support Development Mode in 
> any new versions of Firefox starting with 27.
>
> As a workaround, I am doing one last release to get the plugin working 
> again with Firefox 24.2 (and hopefully newer point releases on the ESR 
> track). If you wish to continue to use Development Mode on Firefox, you 
> will need to download this version from Mozilla [2]. For more details see 
> the issue tracker [3]. 
>
> Long-term, the plan is to improve Super Dev Mode.
>
> I apologize for the late notice; when I said at GWT.create that Firefox 
> could stop working with any release, I didn't expect it to be the next one.
>
> - Brian
>
> [1] https://bugzilla.mozilla.org/show_bug.cgi?id=920731
> [2] 
> http://download.cdn.mozilla.net/pub/mozilla.org/firefox/releases/24.2.0esr/
> [3] https://code.google.com/p/google-web-toolkit/issues/detail?id=8553
>
>

-- 
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+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: HTTP Client API for GWT - Requestor (Announcement)

[Slava Pankov]

Sounds great! Thank you.

On Wednesday, January 7, 2015 12:31:19 PM UTC-8, Danilo Reinert wrote:
>
> Finally, a real HTTP Client API is available for the GWT ecosystem: 
> Requestor.
> It was released today (Jan 7th) under the version 0.1.0 but is being 
> developed for almost a year.
> The project has a great documentation and a showcase application.
> More features and improvements are already planned.
> The initial release is stable and ready for production.
> The community is invited to know and dig deep in the project.
>
> Following the release notes.
>
>
> Requestor - Requesting made easy for GWT
>
> Requesting is the most common operation in AJAX applications. 
> GWT is an excellent platform for developing AJAX applications, but it 
> still bother us when it comes to requesting.
> Using RequestBuilder, the default GWT way of requesting, is a low-level 
> approach which requires too many steps and manual processing to achieve 
> meaningful data for our application.
> Requestor solves theses issues with a full featured and fluent API for 
> requesting. 
> A real HTTP Client API for GWT, it is made upon modern programming 
> concepts like Promises and Method Chaining, and is designed to be as 
> extensible as possible.
> Carefully crafted, Requestor provides many features while allows the easy 
> configuration and customization of them all.
>
>
> Features
>
> * Promises (integrate any promise library)
> * Fluent API
> * Full support to Form requests (urlencoded or multipart)
> * Full support to raw binary data (File, Blob, ArrayBuffer, Json, Document)
> * Progress monitoring of uploads and downloads
> * BASIC and CORS authentication
> * Support for implementing any custom authentication
> * Nice header manipulation
> * Uri Building
> * Filters (enhance requests and responses)
> * Interceptors (transform payloads)
> * Auto JSON serialization for POJOs, JavaBean Interfaces and Overlay types
> * Integrated to the AutoBean Framework
> * Integrated to gwt-jackson
> * Integrated to TurboGWT
> * Handle multiple serialization of the same java type for different media 
> types
> * Customizable request dispatching (support for caching and 
> synchronization)
>
>
> Links
>
> Repo: https://github.com/reinert/requestor
> Site: http://reinert.io/requestor/latest
> Wiki: https://github.com/reinert/requestor/wiki
> Group: https://groups.google.com/forum/#!forum/requestor
> Showcase: http://reinert.io/requestor/latest/examples/showcase
>
>

-- 
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+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.