Thanks for the feedback guys. Learned lots here.
On Mon, Jun 22, 2009 at 12:20 PM, Korny Sietsma <ko...@sietsma.com> wrote:
> In dev mode, debugging is pretty good - you run a cutdown browser, which
> lets you debug the client code in java.
>
> The javascript however is a bit of a nightmare - you *can* debug it in
> firebug (as long as you turn off their javascript compression/obfuscation
> bits) but it's rather a lot of work, and only a last resort.
>
> Most of the integration is done through their quite straightforward "jsni"
> interface - you write java code stubs, with javascript implementation in
> specially formatted comments, which then lets you make callbacks to your GWT
> code. So a random example:
> private native void exportBreadcrumbNavigation()
> /*-{
> $wnd.navigateToNode = th...@com.myproj.gwt.client.entrypoint
> ::navigateToNode(D);
> }-*/
>
> - Java sees this as a native stub, and ignores it. The GWT compiler sees
> it as a javascript hook, and complies the embedded code into javascript - in
> this case, exposing a method elsewhere in our client code.
>
> - Korny
>
> On Mon, Jun 22, 2009 at 10:50 AM, Lincoln Stoll <lst...@lstoll.net> wrote:
>
>> I'm assuming it is - in dev mode (hosted in their
>> browser) it is supposedly debuggable as java byte code, which is
>> interesting. In prod, I'm not so sure.
>> But yeah, I totally agree. It seems to integrate with third party JS, so
>> the generated stuff can't be *that* hard to understand.
>>
>> The main downside is that it is java project only.
>>
>> On 22/06/2009, at 1:33 AM, Myles Byrne wrote:
>>
>> On Mon, Jun 22, 2009 at 10:15 AM, Lincoln Stoll <lst...@lstoll.net>wrote:
>>
>>> I guess less time in dev, consistency in testing and language for
>>> development, potentially more efficient output, integration with existing
>>> code?
>>> I'm not using it at the moment, but in some ways it looks interesting.
>>>
>>
>> Seems reasonable. As long the js is debuggable. Having to learn js (and
>> more importantly, the GWT style of 'compiled' js) because the abstraction
>> leaked would be my main concern as a java developer. You can't use sass
>> without already knowing css, but if you can write GWT without knowing
>> javascript then you may be running the risk of digging a very deep hole.
>>
>>
>>
>>
>>
>>
>>
>
>
> --
> Kornelis Sietsma korny at my surname dot com
> "Every jumbled pile of person has a thinking part
> that wonders what the part that isn't thinking
> isn't thinking of"
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
or Rails Oceania" group.
To post to this group, send email to rails-oceania@googlegroups.com
To unsubscribe from this group, send email to
rails-oceania+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/rails-oceania?hl=en
-~----------~----~----~----~------~----~------~--~---
