[gwt-contrib] Questions about initial contributor configuration - build errors in Eclipse
Hello,
I attended the GWT Contributors workshop at GWT.create SF. Thanks to
Michael Vogt and the contributors in attendance, it was very helpful. But
we did not get through building gwt-user and gwt-dev.
*Adding the following to the .gitignore_global file helped quite a bit with
ignoring generated Elemental files:*
*elemental/idl/***
I loaded up the source on my Pixel on the plane and ran into about 16
Eclipse errors following the instructions provided. Today, I just got
everything loaded up on my desktop (Ubuntu 13.04, oracle java 7u40, ant
1.8.2, Eclipse 4.3, etc) and I'm seeing the same issues.
The following code
in trunk/user/test/com/google/gwt/uibinder/test/client/WidgetBasedUi.ui.xml:
*
.menuBar {
font-family: sans-serif;
}
Gives me the following error in Eclipse:* CSS file
com/google/gwt/uibinder/test/client/Menu.css is missing*
Changing that line to: *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 stop receiving emails from it, send an email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] Re: Start eclipse from console?
Good to know. I was trying to resolve some build issues in Eclipse on my flight home, but launching from trunk/eclipse didn't seem to help me (or make a difference) at all. On Tuesday, December 17, 2013 9:49:29 AM UTC-5, Michael Vogt wrote: > > Ok, thanks. I prepare a patch to remove this from the Read-me. > -- 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 stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Re: Questions remain for the GWT.create Steering Committee members
That would be great. I know that they are busy with the EU conference this week, but there were a lot more questions to be addressed. I already gave some feedback that we might need to expand the panel Q&A's next year (either split them by some topics or extend the time). On Monday, December 16, 2013 3:58:07 PM UTC-5, Boris Brudnoy wrote: > > Hello, > > The closing session of the GWT.create 2013 US saw a panel of the GWT > Steering Committee members answer attendee questions. It so happened that > the issue of the changing debugging tools hijacked (most of) the > conversation but there were plenty more good questions the attendees > entered on the Moderator page for the panel: > https://www.google.com/moderator/#7/e=21396f. > > I am wondering if perhaps the Steering Committee members could find time > to address the remaining questions in writing and, for example, post it on > the G+ community page? > > > -- 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 stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] Re: Start eclipse from console?
Ok, thanks. I prepare a patch to remove this from the Read-me. -- 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 stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Re: Start eclipse from console?
On Tuesday, December 17, 2013 3:03:53 PM UTC+1, Jens wrote: > > I have never done this and it has always worked for me (Mac OS). Maybe its > needed on Linux or with a really old Eclipse version? But in general I > would guess launching eclipse from trunk/eclipse is not needed anymore. > Not needed, neither on Linux or Windows (I haven't used Windows for a while, but a few years back it wasn't needed either) -- 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 stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Re: Start eclipse from console?
I have never done this and it has always worked for me (Mac OS). Maybe its needed on Linux or with a really old Eclipse version? But in general I would guess launching eclipse from trunk/eclipse is not needed anymore. -- 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 stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Start eclipse from console?
Hello. In the Eclipse Read-me is written: All relative paths are relative to the GWT source repository's 'trunk/eclipse' folder. For best results, launch Eclipse from the trunk/eclipse folder from the command line. Is this still the case? I didn't see any immediate difference in starting up Eclipse from the desktop or from trunk/eclipse via command line. Greetings, Michael -- 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 stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] GWT,jsni() implemented as rebinding method
BTW, my implementation of GWT.jsni() with rebinding methods was just to
show the power of the proposal, not to support the inclusion of the method.
El martes, 17 de diciembre de 2013 09:28:25 UTC-3, Andrés Testi escribió:
>
> Honestly, I think JSNI should be fully removed from GWT, even GWT.jsni().
> JsInterop seems to cover all the JS binding cases, I can't see where JSNI
> is still useful. JSNI is a dirty hack, it doesn't supports refactoring nor
> typesafe and it's not really Java. In the other hand, a thing like
> GWT.debugger() is ugly. It could be useful in JS development, but it
> doesn't differs so much from Window.alert("Hi bro, I'm debugging the line
> 123"). We already have a debugger, who needs a debugger statement? GWT.*
> methods are usually intrusive and source of code coupling.
> That said, I see the need of method rebinding only at JavaToSimplerJava
> level. JavaToJavaScript should be orthogonal, and fully covered by
> JsInterop.
>
> Of course, I'm really interested in enhance code generation. :-)
>
> - Andrés Testi
>
>
> El lunes, 16 de diciembre de 2013 17:51:15 UTC-3, Goktug Gokdogan escribió:
>>
>>
>>
>>
>> On Mon, Dec 16, 2013 at 12:14 PM, Andrés Testi wrote:
>>
>>> Well, there is a sample for String.format() in the prototype:
>>> https://github.com/andrestesti/gwt-rebindingmethods/blob/master/samples/hellorebinding/src/com/google/gwt/sample/hellorebinding/client/util/Strings.java#L39
>>> I agree, method rebinding should eliminate the need of magic methods and
>>> simplify the compiler. GWT.debugger() is a controvesial case because Java
>>> doesn't has a semantically equivalent for it..
>>>
>>
>> Yes, that is also true for the GWT.jsni case. I think at the end there
>> should be 2 types of rewriters; one for java and one for javascript and
>> they should do real method replacement. Developer can choose either one.
>>
>> It looks like you are really interested in this. Can you also improve
>> your proposal with real method rewriting?
>>
>>
>>>
>>> - Andrés Testi
>>>
>>>
>>> El lunes, 16 de diciembre de 2013 16:48:52 UTC-3, Goktug Gokdogan
>>> escribió:
I actually implemented with simple eval for demonstration purposes but
probably yours is preferable :)
Yes, GWT.jsni is one of the use cases for method rebinding; that was
something I was discussing as part of the original discussion.
In reality GWT.jsni is better to be implementable without "native"
method definitions so we could eventually take native methods out of the
compiler.
There are also other use cases like String.format, GWT.debugger and
GWT.create itself. The ideal solution should cover all to avoid redundant
features in the SDK.
On Mon, Dec 16, 2013 at 10:00 AM, Andrés Testi wrote:
> This morning I read the Goktug's slides and was surprised by the
> GWT.jsni() method. It is a nice use case for rebinding methods. I just
> added a version of GWT.jsni() to HelloRebinding sample, implementing it
> as
> a rebinding method (no compiler mods). It took me just 30 minutes of
> coding
> to add an extension to support this:
>
> JsniUtil.jsni("$wnd.alert(#)", message);
>
> - Usage: https://github.com/andrestesti/gwt-
> rebindingmethods/blob/master/samples/hellorebinding/src/
> com/google/gwt/sample/hellorebinding/client/MainWidget.java#L65
>
> - Definition: https://github.com/andrestesti/gwt-
> rebindingmethods/blob/master/samples/hellorebinding/src/
> com/google/gwt/sample/hellorebinding/client/util/JsniUtil.java#L38
>
> - Generator: https://github.com/andrestesti/gwt-
> rebindingmethods/blob/master/samples/hellorebinding/src/
> com/google/gwt/sample/hellorebinding/rebind/
> JsniSnippetGenerator.java#L32
>
>
> Regards.
>
> - Andrés Testi
>
>
> --
> 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 stop receiving emails from it, send
> an email to google-web-toolkit-contributors+unsubscribe@
> googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
>>> 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 stop receiving emails from it, send
>>> an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com
>>> .
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>
>>
--
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
Re: [gwt-contrib] GWT,jsni() implemented as rebinding method
Honestly, I think JSNI should be fully removed from GWT, even GWT.jsni().
JsInterop seems to cover all the JS binding cases, I can't see where JSNI
is still useful. JSNI is a dirty hack, it doesn't supports refactoring nor
typesafe and it's not really Java. In the other hand, a thing like
GWT.debugger() is ugly. It could be useful in JS development, but it
doesn't differs so much from Window.alert("Hi bro, I'm debugging the line
123"). We already have a debugger, who needs a debugger statement? GWT.*
methods are usually intrusive and source of code coupling.
That said, I see the need of method rebinding only at JavaToSimplerJava
level. JavaToJavaScript should be orthogonal, and fully covered by
JsInterop.
Of course, I'm really interested in enhance code generation. :-)
- Andrés Testi
El lunes, 16 de diciembre de 2013 17:51:15 UTC-3, Goktug Gokdogan escribió:
>
>
>
>
> On Mon, Dec 16, 2013 at 12:14 PM, Andrés Testi
>
> > wrote:
>
>> Well, there is a sample for String.format() in the prototype:
>> https://github.com/andrestesti/gwt-rebindingmethods/blob/master/samples/hellorebinding/src/com/google/gwt/sample/hellorebinding/client/util/Strings.java#L39
>> I agree, method rebinding should eliminate the need of magic methods and
>> simplify the compiler. GWT.debugger() is a controvesial case because Java
>> doesn't has a semantically equivalent for it..
>>
>
> Yes, that is also true for the GWT.jsni case. I think at the end there
> should be 2 types of rewriters; one for java and one for javascript and
> they should do real method replacement. Developer can choose either one.
>
> It looks like you are really interested in this. Can you also improve your
> proposal with real method rewriting?
>
>
>>
>> - Andrés Testi
>>
>>
>> El lunes, 16 de diciembre de 2013 16:48:52 UTC-3, Goktug Gokdogan
>> escribió:
>>>
>>> I actually implemented with simple eval for demonstration purposes but
>>> probably yours is preferable :)
>>>
>>> Yes, GWT.jsni is one of the use cases for method rebinding; that was
>>> something I was discussing as part of the original discussion.
>>>
>>> In reality GWT.jsni is better to be implementable without "native"
>>> method definitions so we could eventually take native methods out of the
>>> compiler.
>>> There are also other use cases like String.format, GWT.debugger and
>>> GWT.create itself. The ideal solution should cover all to avoid redundant
>>> features in the SDK.
>>>
>>>
>>> On Mon, Dec 16, 2013 at 10:00 AM, Andrés Testi wrote:
>>>
This morning I read the Goktug's slides and was surprised by the
GWT.jsni() method. It is a nice use case for rebinding methods. I just
added a version of GWT.jsni() to HelloRebinding sample, implementing it as
a rebinding method (no compiler mods). It took me just 30 minutes of
coding
to add an extension to support this:
JsniUtil.jsni("$wnd.alert(#)", message);
- Usage: https://github.com/andrestesti/gwt-
rebindingmethods/blob/master/samples/hellorebinding/src/
com/google/gwt/sample/hellorebinding/client/MainWidget.java#L65
- Definition: https://github.com/andrestesti/gwt-
rebindingmethods/blob/master/samples/hellorebinding/src/
com/google/gwt/sample/hellorebinding/client/util/JsniUtil.java#L38
- Generator: https://github.com/andrestesti/gwt-
rebindingmethods/blob/master/samples/hellorebinding/src/
com/google/gwt/sample/hellorebinding/rebind/
JsniSnippetGenerator.java#L32
Regards.
- Andrés Testi
--
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 stop receiving emails from it, send
an email to google-web-toolkit-contributors+unsubscribe@
googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>> --
>> 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 stop receiving emails from it, send an
>> email to
>> google-web-toolkit-contributors+unsubscr...@googlegroups.com
>> .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>
--
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 stop receiving emails from it, send an email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Questions remain for the GWT.create Steering Committee members
Hello, The closing session of the GWT.create 2013 US saw a panel of the GWT Steering Committee members answer attendee questions. It so happened that the issue of the changing debugging tools hijacked (most of) the conversation but there were plenty more good questions the attendees entered on the Moderator page for the panel: https://www.google.com/moderator/#7/e=21396f. I am wondering if perhaps the Steering Committee members could find time to address the remaining questions in writing and, for example, post it on the G+ community page? -- 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 stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
