from:"Alberto Mancini"

Re: [gwt-contrib] Re: Goodbye IE 8–9 

2021-10-04 Thread Alberto Mancini

+1 for dropping support for all IE versions.

Thanks.

On Fri, Oct 1, 2021 at 8:32 PM mcmi...@gmail.com  wrote:

> +1 for remove IE
> If really needed deprecate IE11 elso drop full IE versions
>
> miha...@gmail.com schrieb am Freitag, 1. Oktober 2021 um 08:15:26 UTC+2:
>
>> My preference would still be to keep IE11, for one more year, if possible.
>>
>> https://blogs.windows.com/windowsexperience/2021/05/19/the-future-of-internet-explorer-on-windows-10-is-in-microsoft-edge/
>> MS official suport ends on June 15, 2022.
>>
>> Is there some new feature to be added, into GWT core that require removal
>> of IE11?
>>
>> +1 removal of  ie8-10.
>> +1 deprecate ie11 for gwt 2.10
>>
>> On Thursday, September 30, 2021 at 7:49:56 PM UTC+3 nilo...@gmail.com
>> wrote:
>>
>>> 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
>>> already would expect. Dropping support for those two browsers would
>>> simplify the code required here
>>>
>>> From the age of this thread and the discussion so far, it sounds like
>>> there is interest in keeping IE11 still, but no one has spoke up about IE10
>>> or below.
>>>
>>> Additionally, java.util.Random emulation was changed to require
>>> Date.now(), which isn't available in IE8, so neither GWT 2.8.2 nor GWT
>>> 2.9.0 are apparently compatible with IE8 anyway, at least in this small
>>> way. This should give us some confidence (along with the lack of opposition
>>> in this thread) that at least IE8 is definitely safe to drop.
>>>
>>> So, is there any objection at this time to dropping what remains of IE8,
>>> IE9, and IE10 support from GWT? Then, we can reevaluate IE11 at some later
>>> date, for GWT itself? Various migrated GWT modules have focused their
>>> efforts on well-supported browsers, and are likely to only support IE11 by
>>> accident anyway.
>>>
>>> On Friday, March 12, 2021 at 1:20:02 AM UTC-6 stuckagain wrote:
>>>
 We still need IE11 support in the banking sector. We still have a
 majority of customers that use IE11 due to technical reasons (plugins
 needed for accessing secure token don’t install properly in Chrome without
 internet access amongst others).

 What do you mean with “next version of GWT” if that is 3.x then I don’t
 care at this point. We have been waiting for that release for a few years
 now. But 2.x releases should not drop IE11 support it is supposed to be a
 long-term supported version.
 On 12 Mar 2021, 07:54 +0100, bernhar...@schubec.com <
 bernhar...@schubec.com>, wrote:

 Hi all!

 I think IE11 support should be dropped soon if it blocks (or makes it
 difficult) to implement new features in the next version of GWT.
 I understand, that there are enterprises who still use IE11 internally,
 but developers who service such enterprises should use the current version
 of GWT, which is not going away. Nobody is forced to upgrade to the next
 version of GWT.

 Thanks,
 Berni

 tony.be...@gmail.com schrieb am Donnerstag, 11. März 2021 um 22:26:21
 UTC+1:

> IE 11 is still widely used inside corporations, because it is the only
> browser that supports Java applets, and applications such as Oracle
> e-Business Suite still use applets extensively (for Oracle forms). While
> that segment does not move very fast, it does not mean other unrelated
> groups within the same corporation are not updating GWT regularly. It is
> hard to generalize In a multinational company  with tens of thousands of
> employees.
>
> Regards
>
> Tony
>
> On Thu, Mar 11, 2021 at 9:49 AM Jens  wrote:
>
>> Dropping IE 8-10 shouldn't really hurt. Companies that require it are
>> probably not upgrading GWT in a fast pace anyways.
>>
>> However I wouldn't drop IE 11 anytime soon. IE 11 itself is tied to
>> the lifecycle of Microsoft's operating systems, which means for Windows 
>> 10
>> it is supported until 2025 (for now). So just because MS and Google drop
>> support for IE 11 in some/all of their products, the browser itself is
>> still generally supported by MS. So we should think twice before removing
>> IE 11 from a library such as GWT, even if it means to decline/revert
>> certain commits if they break IE 11. From own experience I have usually
>> seen something around 8% of IE 11 usage in GWT based apps.
>>
>> However I am pretty sure more and more companies will announce
>> dropping IE 11 this year or next year. With MS and Google starting, this
>> could easily have a domino effect. However GWT also also strongly used
>> internally inside companies so it might not have that much of an effect 
>> in

Re: [gwt-contrib] Re: HashCode H$ property should be not enumerable

2020-06-13 Thread Alberto Mancini

Hi,
I think that keeping just IE11 is ok.

Thanks,
   Alberto

On Sun, Jun 14, 2020 at 5:30 AM Freddy Boucher 
wrote:

> Hi,
> On our side, an enterprise GWT webapp, 14% of our Users still use IE11 (we
> already dropped prior IE versions).
> And unfortunately we still have to support IE11 for some time.
> Regards
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/8bb390c7-855e-455e-bb34-16b6d18f6452o%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAGv30Vmb7%2BHwMr%2BkZfS72ZPSSi%2BQ8DXLy%3DtR-ib-zda_-Bi%3DPQ%40mail.gmail.com.

Re: [gwt-contrib] Re: The elusive J2CL

2018-06-01 Thread Alberto Mancini

Hello Goktug,
thanks a lot for the opportunity.
Actually seems that the address j2cl-exter...@googlegroups.com does not
exist.
 mailer-dae...@google.com 
We're writing to let you know that the group you tried to contact
(j2cl-external) may not exist, or you may not have permission to post
messages to the group. A few more details on why you weren't able to post:

 * You might have spelled or formatted the group name incorrectly.
 * The owner of the group may have removed this group.
 * You may need to join the group before receiving permission to post.
 * This group may not be open to posting.
- -

It is just me, I'm not autrorized or actually the address is spelled
incorrectly?

Thanks,
   Alberto.


On Thu, May 31, 2018 at 11:51 PM 'Goktug Gokdogan' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> Hi all.
>
> Sorry for the delays in getting J2CL work for opensource. Some of the
> delays were out of our control but this is something we actively working on
> in the last few months and having progress. In the meantime plenty of
> active GWT contributors already has access to it for a long time and
> working on getting GWT 3 ready. Also a while back, I said "if there are
> more people who needs access to J2CL for GWT 3 porting, we can give them
> access" but it is not usable for average developer.
>
> If you think you need earlier access to J2CL in as-is state (which
> partially builds with plenty of workarounds), pls send a message to
> j2cl-exter...@googlegroups.com; and pls make your case (e.g. porting X
> from GWT 2 SDK to GWT 3) and we will give access. However we cannot help
> you a lot at the moment when you hit problems (you will) so pls set your
> expectations accordingly.
>
>
> On Thu, May 31, 2018 at 6:02 AM Ivan Markov  wrote:
>
>> Don't you think there could've been 2x or even 3x as much people working
>> on porting GWT2 stuff over to J2CL if J2CL was released in the first place?
>> For one, releasing J2CL could've made me reconsider how much time I invest
>> in my own SDBG pet project. Which - at the current situation is exactly
>> zero. Or whether to invest time in the abandoned typescript2java effort,
>> which would bring seamless JSInterop with gazillions of .d.ts'd JS
>> libraries without the need to manually code JSInterop bindings...
>>
>> Say what you want, but 3 months since my original rant that at the top of
>> this thread, the "basic Bazel building issues" of Goktug seem still to be a
>> roadblock and J2CL is still nowhere to be seen.
>>
>> ... and then we had Daniel planning to write a book on J2CL end of 2016,
>> remember? Come on guys, it is Q3 2018 now... I might now agree with Learner
>> Evermore on his points 2) to 5), but with point 1) he nailed it:
>> "1. The backing company backed off but kept the crucial new piece secret
>> - J2CL."
>>
>>
>> On Wednesday, May 30, 2018 at 6:07:25 PM UTC+3, Frank Hossfeld wrote:
>>>
>>> That's not really true. There are a lot of people working on the GWT
>>> module, getting them out of GWT and moving them to standalone artifacts.
>>> Doing that, they replace JSNI with JsInterop, replace generators, etc. This
>>> is all done, to get GWT 2 ready for GWT 3. And if you want to see something
>>> existing in GWT 3, you can ask vertispan to do the job.
>>>
>>> With the knowledge about the things, that will change with GWT 3 / J2CL,
>>> I was able to make mvp4g ready for GWT 3 / J2CL. I replaced the generator
>>> with APT and remove the dependency to any GWT classes. I created a sample
>>> application based on the new version (mvp4g2) and Elemental 2. And yes, it
>>> works with J2CL.
>>>
>>> And, keep in mind, applications written in GWT in 2010 still work. What
>>> was the favorite JS framework at that time? I don't remember.
>>>
>> --
>> 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 view this discussion on the web visit
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/03d79d23-11e5-423b-9009-d439a569c512%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA2Z333EfYXk-RAD_%3DPJkrXV62JkfWHJFrwTdUsj%3DZ_StA%40mail.gmail.com
>

Re: [gwt-contrib] The elusive J2CL

2018-03-08 Thread Alberto Mancini

Hello,
yes, definitely I would like to be in.
I am really interested.

Cheers,
   Alberto.


On Thu, Mar 8, 2018 at 2:21 PM Nándor Előd Fekete 
wrote:

> I am *really* interested. Can you sign me up?
>
>
> On Thursday, March 8, 2018 at 9:13:01 AM UTC+1, Goktug Gokdogan wrote:
>>
>> The main blocker for releasing J2CL for wider audience is even basic
>> missing functionalities around building it in open-source and seeing at
>> least some output for your compilations. That is blocked on missing
>> functionalities in bazel. After that we can probably finished in more
>> timely manner.
>> There is still tone of work to do for a polished open source experience
>> but at least we can give access to more people who is really interested.
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/8de62b64-4bc8-4158-80d4-b15ef688f523%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAGv30V%3DfWDpwQ45u9mPVuXY%3D62PJZ%2B9uxearZk5Lq_a0j2yjaA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Voice of the GWT Committee???

2015-10-16 Thread Alberto Mancini

>
>
>
>> There is no promotion on the main GWT site of the only currently
>> scheduled GWT conference and the normally already scheduled GWT.create
>> conference, there is no chatter about.
>>
>
> Conference organizers are probably the ones who should promote their
> conference; GWT core contributors don't have time for that. But anyone can
> promote the conferences, anywhere.
> The web site is open to contributions <
> http://www.gwtproject.org/makinggwtbetter.html#webpage> and it just
> happens that nobody (organizers, or anyone in the community) proposed (pull
> request or even just an issue) to promote the conference on the site.
>

This point is my fault probably, or at least something that matter me
firsthand being one of the organizers of GWTcon2015.

I Never minded to ask for a note in the site, actually there's not a
section for news on gwtproject and asking for a note on the front page was
too much promotional.
GWTcon has been promoted at our best actually trough all the channels we
can reach but any help is definitely appreciated.

Last but not least, any info on GWTcon is available at: www.gwtcon.org and
there's a Q organized by Arcbees scheduled for
October 28th https://plus.google.com/+ChristianGoudreau/posts/SNMUJbF2jha

and, well, just ask me if you want informations.

Cheers,
Alberto

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAGv30Vn06uTZ2nSbLZbCZQN5p0zyvo7xAHJpCXC2W5yHQ_9gLg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 3 info on GWT CON?

2015-09-29 Thread Alberto Mancini

Hello Brian,
sorry for the long delay but actually I waited  the (almost) definitive
agenda of GWTcon2015 before telling something about the talks.

Cannot state so much about the the keynote cause the abstract is still in
flux but right now there are at least 3 confirmed talks on 'life after GWT
2'.

Check:  http://www.gwtcon.org/#agenda_top


Cheers,
   Alberto.


On Tue, Sep 15, 2015 at 7:19 AM Brian Pedersen 
wrote:

> I am really looking forward to GWT CON in November, but so far no talks
> has been announced on GWT 3 related topics.
>
> I know that the blueprint are still in flux, but I also have a feeling
> that the core team knows exactly which direction they are pushing GWT.
>
> My biggest wish is to see a continuation of the GWT meetup talk Modernizing
> GWT Applications
> ,
> going even more in to details on how we can use GWT 2.8 and JsInterop to
> prepare for GWT 3.0.
>
> See you there ... :)
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/4789c00b-0caf-4b5e-93df-f32e7760b17e%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAGv30Vm7Mr2%2BE%2B2Oo2Zp7Fpov_eC9b0QeGrOGh7C%3D3AsjEhZNQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 2.7 requiring Java7 for development - Action needed

2014-09-11 Thread Alberto Mancini

Hi,
IMHO, java 7 for development more than OK.

Thank you !

Alberto.

On Thu, Sep 11, 2014 at 7:50 PM, 'Daniel Kurka' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

Hi all,

while bringing GSS support into GWT, I discovered that the closure
styleheets compiler actually requires Java7.
This means that we either have to do a back port of the compiler (I
haven't looked at it seriously) or require Java7 for development with GWT
(probably only if you are using CssResource).

I really like your input on this and if I do not hear any strong
objections, I will go ahead with using the Java7 version of closure
stylesheets and thus we will require Java7 for GWT development.

Note: This does not impact deployment of any GWT apps. You can still run a
GWT app on a Java6 container, this will only affect developers on their
machines.

-Daniel

--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujip-hsvuE7-NghZGJ0HL007yjCaE5mMX2126Gag4KUJ7Ug%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujip-hsvuE7-NghZGJ0HL007yjCaE5mMX2126Gag4KUJ7Ug%40mail.gmail.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAGv30V%3D0oNv%3DgmG7UfZhfXJ%3DoWDbqxjOJdeKEDY8tR%3DeT6LK%2BQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Should GWT support WebGL without Elemental ? (or should Elemental be extended to support more browsers ?)

2013-07-29 Thread Alberto Mancini

Hi,
hope this is the right list for this discussion.

WebGL is today supported at least  by FF and, according to 
http://caniuse.com/webgl, also the next release of IE will support it so I 
wonder if
should GWT support WebGL (without Elemental).

As i see in previous mails in this group, and in other GWT related groups, 
the direction of the community is to move code 'out' of the core
but in my opinion the support of browser-related-features has to be 
provided by GWT and not by external libraries, comments ?  

Elemental seems to me the right place where to have non-so-standard 
features but supporting just chrome is not enough and I can't imagine alone 
the work needed to 
extend it to ff  co.  
I remember a post, that I cannot find anymore actually, about extending 
Elemental to support at least ff, there is any work in that direction or 
is better to leave generating-code-from-webidl just for chrome ? 


Thank you,
   Alberto

-- 
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] Should GWT support WebGL without Elemental ? (or should Elemental be extended to support more browsers ?)