re and using supersourcing for the tests.
>>> In the long run, as JDK9+ tests grow, supersourcing might become
>>> unsustainable, but the impact on the CI server et al. is non-negligible. We
>>> could still possibly, at least temporarily, build only with JDK8, and only
&
nished, landed.
* Update Javadoc to support >8 only, update build to skip any doc tasks when
on Java 8
On Wed, Jul 1, 2020, at 11:34 AM, Thomas Broyer wrote:
>
>
> On Wednesday, July 1, 2020 at 3:32:34 AM UTC+2, Colin Alworth wrote:
>> Thanks Goktug for clarifying - I am pers
We're going to try recording tomorrow, just for the specific 'sessions'
that are planned, so the video should be available afterward, I'll link in
a follow up post when they are ready.
Three planned topics to record:
* Ahmad Bawaneh presenting domino-history, a simple routing tool to
manipulat
Meeting link is at https://meet.google.com/jbs-wier-ywp - we will start
recording in about an hour, and will only publish the three talks listed
below.
On Wednesday, July 1, 2020 at 12:58:15 PM UTC-5, Colin Alworth wrote:
>
> We're going to try recording tomorrow, just for t
We have a shorter itinerary this week - I'll record a short piece on
j2cl-maven-plugin and how to start a project with it, try using pieces from
the ecosystem.
Dmitrii, Ahmad and I will continue our brainstorming about efficiently
producing both optimized output and minimizing the work the comp
d=MXVmcmw1czU5cHMxYm5lcHEzZWQ0MjR2ODUgY29saW5AdmVydGlzcGFuLmNvbQ&tmsrc=colin%40vertispan.com
--
Colin Alworth
co...@colinalworth.com
On Tue, Jul 21, 2020, at 8:24 AM, Michael Conrad wrote:
> How did it go?
>
>
> On 7/15/20 5:02 PM, Colin Alworth wrote:
>> We have a sh
GWT itself hasn't changed substantially in many years - improvements have
mostly been language features, adding support for incremental compilation,
the jsinterop system, etc, so for the most part the optimizations haven't
changed.
That said, the best way is almost certainly to take a look at t
I've just filed https://github.com/gwtproject/gwt/issues/9739, where a
workaround exists in java.util.Date that nearly doubles the time it takes
to parse date strings and build date objects. This workaround exists for
IE8 and IE9, as all more recent browsers implement the same behavior as we
al
We've got a few changes that have been brewing or waiting to be made
available, and it sounds like it is about time to collectively push to make
these things happen. Given the nature of some of these, I am suggesting
that they not be folded into a bugfix release, but instead that the next
relea
Note that it appears I'm mistaken, Runtime.java polyfilled Date.now()
(though code in JsDate and others still believed that this method might not
exist), so GWT 2.8.2 and 2.9.0 likely function properly in IE8.
On Thursday, September 30, 2021 at 11:49:56 AM UTC-5 Colin Alworth wrote:
&
I'm looking for reviewers and help for the above issues so I can finalize
them and begin testing. There are a few dependency chains here - I have
IE8/9/10 removal just about complete, but before that can merge we need the
apichecker updated, and after that merges, we can remove the poorly
perfo
hing
>> else is treated the same.
>>
>> -- J.
>>
>> ManfredTremmel schrieb am Montag, 4. Oktober 2021 um 11:07:11 UTC+2:
>>
>>> Am Donnerstag, 30. September 2021, 18:49:56 CEST schrieb Colin Alworth:
>>>
>>> > So, is there any objection a
We've successfully migrated the gwtproject.org website to a new domain name
server and new hosting, at Google's request. There are a few small
differences from the old hosting:
- HTTPS is now supported and enabled, though not yet mandatory, to allow
a period of migration, and making sure
See the question raised at
https://github.com/gwtproject/gwt-site/issues/328.
While gwtproject explicitly licenses all "software and sample code" as
under the Apache License 2.0, it appears that we don't have a license
specified for the contents of the gwtproject website
(https://gwtproject.or
TL;DR: If you have the capability to do so, now would be an excellent time
to help us test GWT in anticipation of a release, especially around the
groupId change we're going to make.
--
We think that we're one merge away from being ready for a GWT 2.10 release,
so I'm starting the release proc
nges been made through gerrit and did require a CLA?
>
> --J.
>
> Colin Alworth schrieb am Donnerstag, 21. April 2022 um 17:34:49 UTC+2:
>
>> See the question raised at
>> https://github.com/gwtproject/gwt-site/issues/328.
>>
>> While gwtproject explicitly
type
> DefaultDocumentEventRouter is not applicable for the arguments
> (ObservableMutableDocument)
> [ERROR] Line 928: The method
> create(ObservableMutableDocument) in the type
> DefaultDocumentEventRouter is not applicable for the arguments
> (ObservableMutableDo
I've pushed a new build with version 2.10.0-new-groupid-3 that has several
@SuppressWarnings("deprecation")s added, and hopefully will solve the WARN
logging issue.
--
You received this message because you are subscribed to the Google Groups "GWT
Contributors" group.
To unsubscribe from this g
Thanks
>>
>> Le dimanche 24 avril 2022 à 21:34:23 UTC+2, juan_pablo_gardella a écrit :
>>
>>> Tried with Maven 3.8.5 and still fails with same issue. Reported at
>>> https://github.com/tbroyer/gwt-maven-plugin/issues/152
>>>
>>> On Sun, Apr 2
Hello all,
All of the preliminary testing that I'm aware of for the upcoming release
is complete, leaving us with a decent level of confidence in the changes.
We have a document that outlines the release plan (with a link to the
standard release steps and the testing process) that has undergone
The last step of the release process is under way, Google's 2.10.0 release
is underway, we're just waiting for the release to be performed and
synchronized to Maven Central. When that has finished we can formally
announce the release.
I've created an issue for next steps to finish our transitio
If there’s one thing that GWT has tried to be consistent about, it is
retaining support for technologies past their “best by” dates. This is a
sore point from time to time, as it makes the tooling feel dated even right
after a release, but it has some specific advantages with regards to
enabl
maybe
> it will finally force people to move on faster. They tend to complain that
> we are using old technology (GWT) but at the same time they stick with Java
> 8.
> On 4 Aug 2022, 06:05 +0300, Colin Alworth , wrote:
>
>
>
> If there’s one thing that GWT has tried to be c
I'd welcome a separate discussion about a backward compatibility contract,
but clearly we have to contrast the "technically Java 8 is supported" with
"realistically, any project that uses standard up-to-date tools can't use
Java 8 by the end of 2023". We support _end users_ to the extreme, as so
The GWT Eclipse Plugin has become unmaintained, and over the last several
months several community members have stepped up to update it to run on
recent Eclipse versions, and support the new GWT groupId.
As part of that process, we've created a new marketplace entry, and while
it is still point
ger with password
> sharing between trustworthy community members. I appreciate the commitment
> of Vertispan but there should be a backup plan in case something unexpected
> happens.
>
> -- J.
>
> Colin Alworth schrieb am Samstag, 28. Januar 2023 um 03:45:13 UTC+1:
>
>>
That patch is delayed since it turns out there are some tests that rely on
specific behavior from the JVM - a few JPMS violations in legacy dev mode,
and apparently Annotation.toString() changed slightly breaking a few other
tests. I think it is just about ready, but each round of testing takes
There have been a few suggestions of making a release in the near future,
and it seemed like it might be a good idea to summarize pending
development, ask for help to land these, and see if anything else needs to
be addressed before shipping.
- There is a pending branch (not yet a PR for GW
; Hi Colin,
>
> if you need some help, I'm feeling to help.
> Specially the jakarta stuff is important for us.
> Do you find the time to have a look to the open PR?
>
> BR
> Rocco
>
> Colin Alworth schrieb am Mittwoch, 17. Mai 2023 um 16:44:58 UTC+2:
>
>> Th
dows with Java 11 and Chrome/Edge/Firefox.
> Will the jars for testing be available in some Maven repo?
>
> Cheers,
> Zbynek
>
> On Wednesday, November 15, 2023 at 3:37:38 AM UTC+1 Colin Alworth wrote:
>
>> It has taken longer than we had hoped, but I think we're just
since the
APIs we now use are not compatible there.
On Thursday, November 23, 2023 at 7:36:55 AM UTC-6 Juan Pablo Gardella
wrote:
> Hello, is gwt-2.11 artifacts available somewhere for testing against the
> applications I am currently working on?
>
> On Tue, Nov 14, 2023, 11:37 PM Colin A
Thanks for reporting - perhaps better for the bug tracker, and indeed we do
this (or something like it) filed already, see
https://github.com/gwtproject/gwt/issues/9840.
Your email title says that this is a compile time infinite loop, but then
the body suggests that it was a runtime error. If i
The 2.12 release seems to be almost ready - we're trying to do releases a
little more frequently when we have changes to be made, and this is going
to end up being about nine months after the 2.11 release.
Considerations for this release:
* *Java 8 support is formally dropped* for running the c
the gwt head snapshot? I cannot find it at
> https://s01.oss.sonatype.org/content/repositories/snapshots/org/.
>
> On Sun, Aug 11, 2024 at 5:48 PM Juan Pablo Gardella
> wrote:
>
>> I will help with testing Colin! Thanks a lot for all your effort
>>
>>
>
Colin Alworth has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 1:
(1 comment)
The ServerSerializationStreamWriter will also need
Colin Alworth has posted comments on this change.
Change subject: Add hasClassName method in com.google.gwt.dom.client.Element
..
Patch Set 3: Code-Review-1
As an idea, looks good, but remember that JSOs are a particularly
What are we looking at having in these interfaces? The discussion that
Goktug and I had a few months ago got stalled around the concept that these
interfaces were trying to both be a) implementation independent but also b)
rich enough to be useful. Doing both is hard/meaningless.
To pick an exampl
Slight follow up to both Stephen's comments here and my own prev post - If
the interfaces are for existing, standard, built-in GWT widgets, type 2
makes a lot more sense, whereas for type 1, we really seem to need a
general, ideal button that can be replaced by any implementation (with
possibly any
Colin Alworth has posted comments on this change.
Change subject: Add hasClassName method in com.google.gwt.dom.client.Element
..
Patch Set 6: Code-Review+1
Nope, we can work with it - a wrapper isn't really an option,
Colin Alworth has posted comments on this change.
Change subject: Add hasClassName method in com.google.gwt.dom.client.Element
..
Patch Set 6:
Thanks Goktug - one of the distinct advantages of extending Element is that
we
Colin Alworth has posted comments on this change.
Change subject: Add interfaces for widgets.
..
Patch Set 6:
(4 comments)
File user/src/com/google/gwt/dom/client
Colin Alworth has uploaded a new change for review.
https://gwt-review.googlesource.com/3361
Change subject: Ensure clinits get called for JSO instance methods.
..
Ensure clinits get called for JSO instance methods.
In
Colin Alworth has posted comments on this change.
Change subject: Ensure clinits get called for JSO instance methods.
..
Patch Set 1:
Afraid not, this is the exact same patch we looked at - only difference was
that I pulled
Gerrit-PatchSet: 2
Gerrit-Project: gwt
Gerrit-Branch: master
Gerrit-Owner: Colin Alworth
Gerrit-Reviewer: Colin Alworth
Gerrit-Reviewer: John A. Tamplin
Gerrit-Reviewer: Leeroy Jenkins
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
---
You received this message because you are
Colin Alworth has posted comments on this change.
Change subject: Ensure clinits get called for JSO instance methods.
..
Patch Set 2:
(2 comments)
File user/test/com
Colin Alworth has posted comments on this change.
Change subject: Ensure clinits get called for JSO instance methods.
..
Patch Set 2:
(1 comment)
File dev/core/src/com
Colin Alworth has posted comments on this change.
Change subject: Add interfaces for widgets.
..
Patch Set 8:
What is the thinking for the remaining 10%-ish of widgets - all of the cell
widgets (except CellPanel), remaining
Nice writeup. Comments/questions (since comments seem disabled in the docs):
* @Entry looks great - there has been some discussion in IRC about some
way to do this for easier library wrapping code, but every direction we
looked at with JSOs ended up with a little more cruft than we really wante
I got a tweet from you asking for a donation (or rather a 'partner', which
apparently means 'money'), but couldn't frame a useful response in 140
chars, so since this thread is coming back, I thought to do so here
instead.
What license are you offering these code samples under - if it isn't
someth
Shortly after 2.5.1, the Benchmark classes were removed from GWT
(https://gwt.googlesource.com/gwt/+/39eb6001a037fd8b6580a73a2540e6e9c04e54c2
and
https://gwt.googlesource.com/gwt/+/00c7ce43df3a629b7302ab902a07431db7224e2b)
- what are folks using for low-level performance testing these days?
I'
I'd be interested in helping with either approach. The phloc-css project
looks interesting if we are only trying to add support for newer CSS
features, while integration with Closure Stylesheets seems geared more
toward extending the CssResource featureset. Much of the existing
functionality in
ing in this
>> route and will definitely help you along the way, and also provide you
>> additional contact points from the team for support.
>>
>>
>>
>> On Tue, Aug 27, 2013 at 3:24 AM, Thomas Broyer
>>
>> > wrote:
>>
>>>
>>&
When I run that command it doesn't run all of the tests, but it does run
*other* tests. The parameter used specifies which gwt tests to run, but
there is also a batch of non-gwt tests (i.e. traditional JUnit test cases)
that get kicked off as part of the 'test' target.
One option is to specify *ex
I've got to second Thomas on this point - adding a new user.agent is very
non-trivial at least without an overhaul of CssResource generation. In GXT
3 we took the route of providing our own PropertyProviderGenerator and
adding a few new user agents (ie7, ie10 for a start), but quickly found
that do
e-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 optio
forward; it's not
> worth fixing older plugins. However, I believe Firefox 24 will be an ESR
> release so I think it's worth rebuilding that version.
>
>
>
> On Tue, Sep 24, 2013 at 4:31 PM, Colin Alworth
> > wrote:
>
>> I spent a little time this wee
; user/src/com/google/gwt/user/client/impl/WindowImpl.java line 32 where it
> can install an onunload handler. It does preserve the old one but it still
> seems kind of fragile to install one in the devmode.js. I wonder if there's
> some way to detect the unload event in C++?
>
&g
Its never too late - I don't know how far Julien has gotten, but I've been
distracted by other work, as well as trying to nail down conceptually where
GSS meets ClientBundle.
For my part, SASS or LESS are a major step down from what we already have -
the purpose of GWT in general is to let you
It looks like a recent commit that removed some deprecated methods may not
have gone far enough, as there is still code that makes use of those
methods - the
https://gwt.googlesource.com/gwt/+/f9630059081921b195ee4f7014e1a78c4b570f79
commit dropped several methods from Tree and TreeItem, but th
According to the the gwt-site git repo (at
https://gwt.googlesource.com/gwt-site/+/master/src/main/site/javadoc/latest),
the package-list file is present, but it can't be downloaded from
http://www.gwtproject.org/javadoc/latest/package-list. It *is* still
available from
http://google-web-toolk
Just wandered by https://gwt-review.googlesource.com/#/c/1040/ and noticed
that with this change, any downstream generator/linker using the static
helper methods in Name will no longer build across 2.5.1 to 2.6.0. With the
other discussions going on about JRE and browser support, perhaps we coul
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
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
easie
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:
>
> Thank
If only *all* of my changes were that easy to make...
On Tuesday, October 22, 2013 8:15:12 AM UTC-5, Andrés Testi wrote:
>
> Thanks Colin! I'm glad to see the power of the community in action :-)
>
> - Andrés Testi
>
> El lunes, 21 de octubre de 2013 19:59:53 UTC-3,
Amazingly, it still works great in the IE11 preview too! Only gotcha is
that the missing plugin page thinks you are running firefox, so you need to
manually grab the right copy of the IE plugin.
On Tuesday, October 22, 2013 12:58:57 PM UTC-5, Brian Slesinsky wrote:
>
> I expect that by next summ
I've just put up a patch that seems to resolve a current issue in deploying
snapshots to a maven repository: https://gwt-review.googlesource.com/5192
The basis of the problem requiring this patch is that maven (at least maven
3, possibly not maven 2) expects unique snapshots, and that each call
I can't reproduce this, we're also running ant clean elemental dist on our
teamcity build. We're also running ubuntu 12, python 2.7.3. Last confirmed
building as of 0d6a865556ca56840114e8397a1f2be522e83361 (current HEAD).
On Monday, October 28, 2013 5:43:04 AM UTC-5, Jens wrote:
>
> I just tried
Good thought, I tried that too to confirm that teamcity wasn't setting
anything funny. Still passed, not sure what is up.
Other details that may or may not help:
$ java -version
java version "1.6.0_35"
Java(TM) SE Runtime Environment (build 1.6.0_35-b10)
Java HotSpot(TM) Server VM (build 20.10-b0
It looks like while I can get maven from the command line to get along with
that repo, IntelliJ isn't having it - it is getting confused by the fact
that the latest gwt-user snapshot 2.6.0-20131105.081128-3 only has a
sources jar and a pom, no actual jar with compiled code in it. The -1 jar
is
ot; wrote:
> Thanks for testing, Colin! I'll try another push tonight using your
> scripts.
>
>
> On Tue, Nov 5, 2013 at 5:14 PM, Colin Alworth wrote:
>
>> It looks like while I can get maven from the command line to get along
>> with that repo, IntelliJ isn't havi
v 06 15:47:54 PST 2013
>>> [INFO] Final Memory: 8M/112M
>>> [INFO]
>>>
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file (default-
s released. Snapshots are the
other way around, you are allowed to update snapshots, as well as remove
stale ones.
On the plus side, the -SNAPSHOT build looks to be working great from my
testing.
On Wed, Nov 6, 2013 at 7:07 PM, Matthew Dempsky wrote:
> On Wed, Nov 6, 2013 at 4:54 PM, Colin A
6.0-rc1.zip
>
> (Next up the Maven 2.6.0-rc1 artifacts.)
>
>
> On Wed, Nov 6, 2013 at 5:07 PM, Matthew Dempsky wrote:
>
>> On Wed, Nov 6, 2013 at 4:54 PM, Colin Alworth wrote:
>>
>>> My vote is 2.6.0-SNAPSHOT and 2.6.0-rc1, in case we need a bug fix
>>> re
I'm not yet convinced that this isn't either a) a workspace issue or b) a
decision the community reached and I missed, but I figured I should stick
it out there and see if someone can correct me.
I've just brought our project up to date with GWT 2.6.0-rc1 from maven, and
I can verify that the c
ogle.com
> | 408-500-9148
>
>
> On Fri, Nov 8, 2013 at 3:31 PM, Colin Alworth
> > wrote:
>
>> I'm not yet convinced that this isn't either a) a workspace issue or b) a
>> decision the community reached and I missed, but I figured I should stick
>>
t; On Nov 8, 2013, at 17:47, Colin Alworth wrote:
>
> Thanks Roberto, I'll give that a shot. I normally work with Java 7, but we
> want our code to work with anyone who chooses to use Java 6 as well - and I
> surmised that GWT had the same goal.
>
> Would it make sense to consi
There is a workaround - I'm on my phone now, but I posted it in the bug
report. Essentially you can tell the plugin to not worry about "invalid"
SDKs, and either mark then as merely errors, or just ignore it entirely.
With that set, we've noticed no other I'll effects so far.
On Nov 17, 2013 12:29
Just to confirm, the plan is to set this in master as well as releases/2.6,
and this will go out in 2.6.0-rc2?
--
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
What's the current thinking on removing ImageResource.isStandalone from
2.6.0 final, as in the https://gwt-review.googlesource.com/#/c/5504/ review?
It isn't in GWT 2.5.x, and isn't in master, but is present in both
2.6.0-rc1 and 2. If it was an oversight to add this the first time around,
shou
I'm still running into trouble with the major version of the compiled
classes being 51, so I'm unable to gwt 2.6.0-rc3 to work under jdk 1.6. As
before, I was able to confirm that the actual .class files are compiled
correctly, but yet I get fatal errors in attempting to run dev mode.
Testing s
if Impl was precompiled by him (and in that case
> probably is consistent that the version is 51.0).
>
> I build from scratch in my laptop (only has java 1.6) and builds and tests
> run fine. Is there a specific application that you are trying to build?
>
>
>
>
> On T
gt; It seems that we need to build the release with -sourceLevel 6 for it to
> work with Java 6.
>
>
> On Thu, Dec 5, 2013 at 10:43 PM, Colin Alworth
> > wrote:
>
>> Sorry for being unclear - I'm building/testing an application that makes
>> use of GWT wh
This system property isn't listed when either dev mode or the compiler runs
because it is a system property, not a program arg. It should be provided
with the other VM args when you start Java. These aren't listed as part of
the normal properties, but are documented here:
http://code.google.com/p/g
Another thought: Christian Sedilek, Dan Kurka, and myself can also be found
pretty frequently in ##gwt on irc.freenode.net for a more informal
discussion - I'd love to see more steering committee members hang out
there, even if just idling most of the time, and chatting once in a while.
Keeping
Something funny has happened to the dont-reload-the-page code on
gwtproject.org, but I'm not seeing any obvious commit that should have done
this.
Steps to repro:
1) visit http://gwtproject.org/, or any *top level* document
2) observe that any link you hover looks to be correct, and visiting any
The concern I've heard expressed during in-person discussions about how to
do this is that a written document of answers 'feels' more real and
concrete than a group of people answer questions live, since they clearly
have no chance to vet their answers from their own organization or with
each other
Another set of dangerous code to look for would be any SafeHtmlUtils or
SafeHtmlBuilder (and their uri/style conterparts) call that should take
'constant' or 'trusted' but instead takes untrusted user data. Custom
implementions of SafeHtml should also be treated as suspect.
These all fall under
For JSON, you'd have go pretty far out of your way to get attacked, like
loading something untrusted via JSONP, or manually parsing your own json
with eval (rather than any of the safe built-in tools), or, ya know,
forgetting to run SSL and having someone intercept your server
communication. Th
If you know enough to start writing generators, it almost certainly is not
a concern - you are probably also careful with which GWT version you are
using as well as which gwt-m-p version. A problem can occur if more than
one version of gwt-dev is present on the classpath, such as a mistakenly
d
Just watched https://gwt-review.googlesource.com/#/c/6342/ wander by, but
I've also seen this trying to understand the general compiler changes that
are happening in trunk gwt - is the CompilerContext really an essential
part of ModuleDefLoader in general? From what I can see it is tracked as a
UTC-8, John Stalcup wrote:
>
>
>
>
> On Mon, Feb 10, 2014 at 2:57 PM, Colin Alworth
> > wrote:
>
>> Just watched https://gwt-review.googlesource.com/#/c/6342/ wander by,
>> but I've also seen this trying to understand the general compiler changes
>> that are
In CrossSiteIframeTemplate.js this is handled by assigning
__MODULE_FUNC__.__softPermutationId to 0 to begin with, and then only
change that value if : was present in the permutation string. I'm not
seeing any other js files that init __softPermutationId to 0, and only
permutations.js assigns i
Only note to add here is that the AngularJS project does require a CLA also
(see https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#cla)
- it looks like they either have a bot which complains about missing CLAs
on file (and so some associated between username and real name), or a
I haven't noticed the bit about restarting sdm, but at least a recompile is
certainly required to switch to a new property value. SDM does definitely
(and deliberately?) build based on exactly the set of properties coming
back from the last compile request, to avoid generating/compiling
unneces
This seems to be a pretty quiet discussion so far, with mostly Zied
responding to himself and Thomas’s one initial reply, but it is a holiday
weekend here in the US, so that might be contributing to the lack of
additional responses. I haven’t had the chance to even look at the initial
proposal
I've just opened https://gwt-review.googlesource.com/7780 to make it
possible to specify a fallback for any/all useragents that don't match one
of the built-in rules, via a rule like:
This example rule treats any unknown useragent as if it were webkit, rather
than the non-existent 'unknow
Sorry, that first line should say 'safari' (or any other valid user.agent
value), not 'webkit'. Wishful thinking perhaps...
--
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,
Currently SafeHtml &co live in gwt-user, though they are for the most part
listed in a shared package, implying that a server can use them. However,
gwt-user.jar also includes javax packages as well as hibernate, w3c, etc,
so can't reasonably be imported to a server which already uses any of tho
asses like AutoBeanFactorySource also made it in there) - does that
seem like a reasonable step?
On Mon, Jun 9, 2014 at 6:22 PM, John A. Tamplin wrote:
> On Mon, Jun 9, 2014 at 6:33 PM, Colin Alworth wrote:
>
>> Currently SafeHtml &co live in gwt-user, though they are for the most
101 - 200 of 261 matches
Mail list logo
