On Sat, Jun 13, 2020 at 11:11 AM Colin Alworth wrote:
> If I understand you, that is what I'm doing - I only the required 18 classes
> (with some members removed so that I don't need more than that), and am just
> seeking an opinion other than my own as to whether it is better to checked
> them
If I understand you, that is what I'm doing - I only the required 18 classes
(with some members removed so that I don't need more than that), and am just
seeking an opinion other than my own as to whether it is better to checked them
straight into gwt as com.google.gwt.thirdparty.ant... classes,
Even IE11 is not needed anymore for my projects, there is Edge for Windows
7+, so all my customers are already upgraded.
--
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
I would love to see just ie11 supported.
--
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.
To vi
Possibly a dumb question ... but isn't it possible to just manually
vendor in the source files to GWT? I can't imagine there is a whole
lot of dependencies that would need to be maintained. Just strip out
the gunk you don't need.
On Sat, Jun 13, 2020 at 7:05 AM Colin Alworth wrote:
>
> So, given
So, given either "make a git repo on gwtproject/ and add a jar to
gwtproject/tools" with the minimal history, or a single commit adding all
already-modified classes to gwt in one go? I should be able to turn out either
change fairly quickly, once we decide.
Adding to GWT directly would be somew
Regarding the ie support: We have really a lot of large customers
(https://resources.softwareag.com/customers) in all business sectors and
also a lot of customers in the financial sector which are normally very
slow updating software. Last year we removed the support for ie8, ie9 and
ie10 for a
Fwiw: IE11 will be EOL for mainstream in October this year:
https://www.swyx.io/writing/ie11-eol/ (of course, for enterprise customers
this will be longer; my opinion is that those companies that have enough
money to pay for special Microsoft support contract could also pay a
company to fork an
To minimize the work, and because 1.6.5 works well for us without known
vulnerability, I would either copy/paste the code into gwtproject/gwt or
provide it in a JAR in gwtproject/tools and call it a day. We already have
a copy of Rhino (with changes for JSNI), and a slimmed down version of
jsil
Yep, sounds like the test stuff I had in mind - for a quick demo I'll set up a
repo, put some "libraries" and "gwt" jars/boms into it, and then make a bunch
of sample projects. The "gwt jars" will have some service loader wiring, and
the sample projects will check to see which jars they end up w
I fully agree. Based on my experience, I'd suggest, for IE, to set the
minimum supported version at IE11.
Il giorno venerdì 12 giugno 2020 17:48:48 UTC+2, Colin Alworth ha scritto:
>
> Agreed that this fix only requires dropping IE8, but I'm suggesting that
> we go a bit further and either a)
Agreed that this fix only requires dropping IE8, but I'm suggesting that we go
a bit further and either a) also drop other dead browsers, or b) have a
plan/timeline for when we can drop those browsers - at least officially. We
might still leave in support for them (as we did for IE6 for some yea
Some frameworks can support IE8 polyfilling the application. In my opinion
the IE 8 support could be dropped.
Don't forget that the proposal (the* Object.defineProperty()*usage) is
available from IE9, therefore we are not saying that we raise the GWT
requirement to IE11 or Edge, but only 1 vers
Most of our cliensts dropped support for ancient IEs, and we now only
support IE11 and edge.
On Thursday, June 11, 2020 at 10:18:18 PM UTC+3, Colin Alworth wrote:
>
> Since the existing code is very similar to J2CL's code, it seems like a
> reasonable change, provided it is indeed safe to drop s
On Thursday, June 11, 2020 at 10:19:00 PM UTC+2, Colin Alworth wrote:
>
> @Thomas, it sounds like you think relocation should be well supported
> then? My primary concern was the quote on the linked page, but if this is
> well supported, then I think we're on the same page. From the linked page
We have two issues tracking the dependency that GWT has on Ant,
https://github.com/gwtproject/gwt/issues/9690 and
https://github.com/gwtproject/gwt/issues/9677. I've taken a little time and
produced a minimal set of classes copied from ant which appear to provide a
working ZipScanner. For the m
16 matches
Mail list logo