[gwt-contrib] Re: Bad news for GWT DevMode!

2013-10-21 Thread Ivan Dimitrijevic 
IMO Firefox

On Friday, October 18, 2013 11:47:13 PM UTC+2, Alex Raugust wrote:
>
> Just curious, is there a preferred browser for Classic DevMode?
>
> What do the cool kids use? :)
>
> On Tuesday, September 24, 2013 4:05:59 AM UTC-7, Thomas Broyer wrote:
>>
>> Just saw this passing on Twitter: 
>> http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html
>> This is really bad for DevMode in Chrome (maybe also in Firefox, which 
>> was already a nightmare). Means we really need to improve SuperDevMode, or 
>> find a non-NPAPI way to plug into the browser.
>>
>

-- 
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: Bad news for GWT DevMode!

2013-10-21 Thread Thomas Broyer 
I don't think any committer to the GWT project uses Windows (other than for 
testing, using VMs then), so it'd be either Firefox or Chrome (no other 
choice on Linux; and on OSX, Safari is no longer supported started with 
5.1, and I don't think anyone uses OmniWeb or similar).
Both work well.

To answer the question about a “preferred browser”, I've been told that, on 
Windows, IE works best (is the fastest); that was a while back though, so 
things might have changed.

On Monday, October 21, 2013 3:21:49 PM UTC+2, Ivan Dimitrijevic wrote:
>
> IMO Firefox
>
> On Friday, October 18, 2013 11:47:13 PM UTC+2, Alex Raugust wrote:
>>
>> Just curious, is there a preferred browser for Classic DevMode?
>>
>> What do the cool kids use? :)
>>
>> On Tuesday, September 24, 2013 4:05:59 AM UTC-7, Thomas Broyer wrote:
>>>
>>> Just saw this passing on Twitter: 
>>> http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html
>>> This is really bad for DevMode in Chrome (maybe also in Firefox, which 
>>> was already a nightmare). Means we really need to improve SuperDevMode, or 
>>> find a non-NPAPI way to plug into the browser.
>>>
>>

-- 
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: Bad news for GWT DevMode!

2013-10-21 Thread Colin Alworth 
I end up debugging IE in dev mode on a regular basis as well, though in a
VM, through to my host OS's Eclipse or IntelliJ debugger. It is
significantly slower than running the IDE and browser on the same OS, but
it does let you set up your env once and debug multiple OSes whenever you
like.




On Mon, Oct 21, 2013 at 8:56 AM, Thomas Broyer  wrote:

> I don't think any committer to the GWT project uses Windows (other than
> for testing, using VMs then), so it'd be either Firefox or Chrome (no other
> choice on Linux; and on OSX, Safari is no longer supported started with
> 5.1, and I don't think anyone uses OmniWeb or similar).
> Both work well.
>
> To answer the question about a “preferred browser”, I've been told that,
> on Windows, IE works best (is the fastest); that was a while back though,
> so things might have changed.
>
>
> On Monday, October 21, 2013 3:21:49 PM UTC+2, Ivan Dimitrijevic wrote:
>>
>> IMO Firefox
>>
>> On Friday, October 18, 2013 11:47:13 PM UTC+2, Alex Raugust wrote:
>>>
>>> Just curious, is there a preferred browser for Classic DevMode?
>>>
>>> What do the cool kids use? :)
>>>
>>> On Tuesday, September 24, 2013 4:05:59 AM UTC-7, Thomas Broyer wrote:

 Just saw this passing on Twitter: http://blog.chromium.**
 org/2013/09/saying-goodbye-to-**our-old-friend-npapi.html
 This is really bad for DevMode in Chrome (maybe also in Firefox, which
 was already a nightmare). Means we really need to improve SuperDevMode, or
 find a non-NPAPI way to plug into the browser.

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



-- 
218.248.6165
niloc...@gmail.com

-- 
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] Gerrit presubmit changes

2013-10-21 Thread Roberto Lublinerman 
Fantastic.



On Sun, Oct 20, 2013 at 9:28 PM, Stephen Haberman
wrote:

>
> Wow, that sounds awesome, Matthew. Great work. I'm looking forward to
> hopefully *not* triggering this great feedback. :-)
>
> - Stephen
>
> --
> 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.

Re: [gwt-contrib] Re: packages com.google.gwt.thirdparty.*

2013-10-21 Thread Roberto Lublinerman 
On Sun, Oct 20, 2013 at 3:21 PM, Thomas Broyer  wrote:

See $GWT_TOOLS/lib/eclipse/README.jdt-upgrade (last paragraph), and
> comments in https://gwt-review.googlesource.com/#/c/2361/1/dev/build.xml (if
> you understand them; reading them now, I don't ;-) )
>

In retrospective I am not sure if extracting jdtCompilerAdapter.jar from
JDT is really needed.

-- 
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] being cute with git describe

2013-10-21 Thread Stephen Haberman 

> I was thinking about something like that too.  I actually kinda like
> it, and it gives an easy monotonic counter for tracking master.

Agreed.

> I don't think we're using proper git tags yet.  The 'tags' currently
> in the tree for 2.5.1, etc that were imported from SVN are actually
> just regular git commits.

I think the svn import was smarter than that..."git tag -l" shows tags
for 2.5.0, 2.5.1, 2.5.1-rc1, etc.

> while intermediary development steps would still be "2.6rc1-42-blah".

Yep, that makes sense.

> Hm, something to consider though, I was planning on creating the 2.6
> branch and then immediately tagging as 2.6rc1.  Since tags are
> independent of branches, I think that would actually cause the 2.6rc1
> tag to be picked up by master too.

Hm, true...you'd need at least one commit on the 2.6 branch to avoid
it's tags getting picked up by "git describe" on master. I dunno.

Looking at the DAG for the 2.5.1 branch, it looks like svn had a
"Cutting at r11495 for 2.5.1 RC1" commit at the start of that branch
(granted, svn semantics require that). We could always make a similar
dummy commit. Not great, but not horrible, I think.

- Stephen

-- 
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: packages com.google.gwt.thirdparty.*

2013-10-21 Thread Cristiano Costantini 
yes, it is :-(  I got unresolved imports without it.

I cannot say why exactly but I can find it if required.

Curiously, the dependency of JDT from Jetty Orbit, which is the most close
to the JDT jar available on GWT-Tools, include the contents of
jdtCompilerAdapter.jar,
but with the Jetty artifact there ware other missing imports and I had to
move to the approach suggested by Thomas and deploy them to the Maven repo
(even if I did it with a partially automated process that adds them from
the GWT tools folder during the maven build).

I've made progresses but I'm still far from my goal,
thank you again for now.






2013/10/21 Roberto Lublinerman 

> On Sun, Oct 20, 2013 at 3:21 PM, Thomas Broyer  wrote:
>
> See $GWT_TOOLS/lib/eclipse/README.jdt-upgrade (last paragraph), and
>> comments in https://gwt-review.googlesource.com/#/c/2361/1/dev/build.xml (if
>> you understand them; reading them now, I don't ;-) )
>>
>
> In retrospective I am not sure if extracting jdtCompilerAdapter.jar from
> JDT is really needed.
>
>
> --
> 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.

Re: [gwt-contrib] Re: Bad news for GWT DevMode!

2013-10-21 Thread Alex Raugust 
"Safari is no longer supported started with 5.1..."

Say what now?


On Mon, Oct 21, 2013 at 6:56 AM, Thomas Broyer  wrote:

> I don't think any committer to the GWT project uses Windows (other than
> for testing, using VMs then), so it'd be either Firefox or Chrome (no other
> choice on Linux; and on OSX, Safari is no longer supported started with
> 5.1, and I don't think anyone uses OmniWeb or similar).
> Both work well.
>
> To answer the question about a “preferred browser”, I've been told that,
> on Windows, IE works best (is the fastest); that was a while back though,
> so things might have changed.
>
>
> On Monday, October 21, 2013 3:21:49 PM UTC+2, Ivan Dimitrijevic wrote:
>>
>> IMO Firefox
>>
>> On Friday, October 18, 2013 11:47:13 PM UTC+2, Alex Raugust wrote:
>>>
>>> Just curious, is there a preferred browser for Classic DevMode?
>>>
>>> What do the cool kids use? :)
>>>
>>> On Tuesday, September 24, 2013 4:05:59 AM UTC-7, Thomas Broyer wrote:

 Just saw this passing on Twitter: http://blog.chromium.**
 org/2013/09/saying-goodbye-to-**our-old-friend-npapi.html
 This is really bad for DevMode in Chrome (maybe also in Firefox, which
 was already a nightmare). Means we really need to improve SuperDevMode, or
 find a non-NPAPI way to plug into the browser.

>>>  --
> http://groups.google.com/group/Google-Web-Toolkit-Contributors
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "GWT Contributors" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-web-toolkit-contributors/NQSjAkbiR9U/unsubscribe
> .
> To unsubscribe from this group and all its topics, 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.

Re: [gwt-contrib] Re: Bad news for GWT DevMode!

2013-10-21 Thread Matthew Dempsky 
On Mon, Oct 21, 2013 at 1:04 PM, Alex Raugust  wrote:

> "Safari is no longer supported started with 5.1..."
>
> Say what now?
>

The GWT Developer Mode plugin has never supported Safari 5.1.  This is
orthogonal to compiler/library support for Safari 5.1 in deployed
applications though.

-- 
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: Reminder: GWT 2.6 feature complete is Nov 4

2013-10-21 Thread Colin Alworth 
Patrick, looking at these, only two appear to have code reviews, and both 
are in the pre-git system. Gerrit, the current system, needs a CLA before 
it allows changes, to make sure that there are no copyright/licensing 
issues with contributions, and makes history/change management a little 
easier. Can you migrate those to Gerrit so they can be reviewed and merged? 
Link back to the original so any discussion there can be read and taken 
into account by future reviewers.

On Friday, October 18, 2013 7:18:40 AM UTC-5, Patrick Tucker wrote:
>
> I really would like to see some of these make the cut.  Most of the which 
> are trivial fixes, some have patches proposed.
>  
> title set on parent TreeItem appears also on its children
>
> http://code.google.com/p/google-web-toolkit/issues/detail?id=1393
>
> HeaderPanel setHeaderWidget is broken
>
> http://code.google.com/p/google-web-toolkit/issues/detail?id=7037
>
> BorderStyle enum is missing values
>
> http://code.google.com/p/google-web-toolkit/issues/detail?id=8071
>
> Inconsistent TextArea border-top style
>
> http://code.google.com/p/google-web-toolkit/issues/detail?id=8176
>
> Vertical MenuBar popup is always left aligned even if there is not enough 
> right-space to do so.
>
> http://code.google.com/p/google-web-toolkit/issues/detail?id=3888
>
> Add max-height and max-width support to Style
>
> http://code.google.com/p/google-web-toolkit/issues/detail?id=7905
>
>  
>  
> I don't necessarily care about this one but it is just a documentation 
> fix...
>  
> Documentation for TabBar doesn't list gwt-TabBarItem-disabled
>
> *http://code.google.com/p/google-web-toolkit/issues/detail?id=4050*
>
>  
>  
>  
>  
>  
>
> On Thursday, October 17, 2013 1:22:56 PM UTC-4, Matthew Dempsky wrote:
>
>> Hi all,
>>
>> Just writing to remind everyone that the GWT 2.6 feature complete 
>> deadline is November 4th.  On that day I'll fork the GWT 2.6 release 
>> branch, and I'll only approve patches for release critical bug fixes.
>>
>> The GWT 2.6 Release 
>> Plan
>>  contains 
>> the handful of outstanding issues that I know we still want to get in for 
>> 2.6, and I'll be following up with people to try to make sure they're 
>> merged in time.  If there are other features you think should be included 
>> but aren't listed, please speak up now so I can add them and track their 
>> progress.
>>
>> Thanks
>>
>

-- 
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: Where is gwt-customchecks.jar?

2013-10-21 Thread Colin Alworth 
Tentative patch up at https://gwt-review.googlesource.com/5063 - can 
someone sanity check it for me? It looks like step 4 (now step 3) should 
have previously been pointing to step 3 (now step 2), so is now more 
correct.

On Sunday, October 20, 2013 2:12:17 PM UTC-5, Andrés Testi wrote:
>
> Thanks Thomas. I think it should be removed from eclipse/README.txt. 
>
> - Andrés Testi
>
> El domingo, 20 de octubre de 2013 13:25:24 UTC-3, Thomas Broyer escribió:
>>
>>
>> On Friday, October 18, 2013 5:30:25 PM UTC+2, Andrés Testi wrote:
>>>
>>> Where is the gwt-customchecks.jar file referred in eclipse/README.txt? 
>>> Is it no longer required to configure codecheck?
>>> Thanks in advance.
>>>
>>
>> It's gone, and no longer required.
>> See https://gwt-review.googlesource.com/1051
>>
>

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