Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.java.programmer > #38852 > unrolled thread

more porting issues to Java 11

Back to article view | Back to comp.lang.java.programmer

Contents

  more porting issues to Java 11 Andreas Leitgeb <avl@logic.at> - 2019-04-03 17:21 +0000
    Re: more porting issues to Java 11 Arne Vajhøj <arne@vajhoej.dk> - 2019-04-03 14:28 -0400
      Re: more porting issues to Java 11 Arne Vajhøj <arne@vajhoej.dk> - 2019-04-03 14:32 -0400
        Re: more porting issues to Java 11 Andreas Leitgeb <avl@logic.at> - 2019-04-04 12:52 +0000
          Re: more porting issues to Java 11 Andreas Leitgeb <avl@logic.at> - 2019-04-04 14:11 +0000
            Re: more porting issues to Java 11 Arne Vajhøj <arne@vajhoej.dk> - 2019-04-04 20:08 -0400
    Re: more porting issues to Java 11 Arne Vajhøj <arne@vajhoej.dk> - 2019-04-03 14:37 -0400
      Re: more porting issues to Java 11 Andreas Leitgeb <avl@logic.at> - 2019-04-04 13:04 +0000
        Re: more porting issues to Java 11 Arne Vajhøj <arne@vajhoej.dk> - 2019-04-04 20:22 -0400
          Re: more porting issues to Java 11 Andreas Leitgeb <avl@logic.at> - 2019-04-08 16:40 +0000
            Re: more porting issues to Java 11 Andreas Leitgeb <avl@logic.at> - 2019-04-08 17:14 +0000
              Re: more porting issues to Java 11 Andreas Leitgeb <avl@logic.at> - 2019-04-10 18:08 +0000
                Re: more porting issues to Java 11 Andreas Leitgeb <avl@logic.at> - 2019-04-10 18:32 +0000
                Re: more porting issues to Java 11 Sebastian <nowhere@nirvana.org> - 2019-04-11 11:05 +0200
                  Re: more porting issues to Java 11 Andreas Leitgeb <avl@logic.at> - 2019-04-29 08:23 +0000
                Re: more porting issues to Java 11 Arne Vajhøj <arne@vajhoej.dk> - 2019-04-12 10:08 -0400
                  Re: more porting issues to Java 11 Eric Douglas <e.d.programmer@gmail.com> - 2019-04-12 07:35 -0700
                Re: more porting issues to Java 11 Andreas Leitgeb <avl@logic.at> - 2019-04-29 08:39 +0000
                  Re: more porting issues to Java 11 Andreas Leitgeb <avl@logic.at> - 2019-05-03 13:10 +0000
                    Re: more porting issues to Java 11 Knute Johnson <groups@585ranch.com> - 2019-05-04 11:24 -0500
                      Re: more porting issues to Java 11 Andreas Leitgeb <avl@logic.at> - 2019-05-04 21:58 +0000
                        Re: more porting issues to Java 11 Knute Johnson <nospam@rabbitbrush.frazmtn.com> - 2019-05-06 11:25 -0500
                          Re: more porting issues to Java 11 Andreas Leitgeb <avl@logic.at> - 2019-05-29 12:20 +0000
                            Re: more porting issues to Java 11 Andreas Leitgeb <avl@logic.at> - 2020-01-30 15:07 +0000
            Re: more porting issues to Java 11 Arne Vajhøj <arne@vajhoej.dk> - 2019-04-08 18:41 -0400
              Re: more porting issues to Java 11 Sebastian <nowhere@nirvana.org> - 2019-04-10 15:46 +0200
                Re: more porting issues to Java 11 Arne Vajhøj <arne@vajhoej.dk> - 2019-04-10 12:31 -0400
              Re: more porting issues to Java 11 Andreas Leitgeb <avl@logic.at> - 2019-04-10 18:13 +0000
                Re: more porting issues to Java 11 Arne Vajhøj <arne@vajhoej.dk> - 2019-04-13 20:39 -0400

Page 2 of 2 — ← Prev page 1 [2]

#38944

Knute Johnson <groups@585ranch.com> wrote:
> On 5/3/2019 8:10 AM, Andreas Leitgeb wrote:
>> Andreas Leitgeb <avl@logic.at> wrote:
>>> The application uses awt & swing components for the GUI, and all
>>> windows look distorted, fonts are a bit larger, even images look
>>> a bit stretched and moving another window over the jdk 11 application
>>> window leaves behind some spurious lines, as if the refresh had off-
>>> by-one-pixel inaccuracies.
>> In the settings dialog for "Screen Resolution", there is an option
>> labelled "Make text and other items larger or smaller", which on my
>> desktop was set to 125%.
>> Java up to 8 totally ignored that setting.
>> Java 11 tries to follow it (which is arguably an improvement), but
>>     does so in a somewhat broken way.
> I think that change actually came with Java 9.

Ouch, that makes it seem pretty unlikely that the visual bugs would
get fixed any time soon :-(

But thanks for the information.

> It is really a big improvement for high dpi screens.

I'd wholeheartedly agree, if it weren't for the pixel bugs.


I'd really appreciate some triaging help per email or here - either 
about you seeing problems in this or other setups, or about you not
seeing problems despite similar setup. "Problems" means for example,
that if another window is moved over the jdk11 app, or even just a
combo/dropdown box or popup window closing (and thereby unobscuring 
only parts of the jdk-11 window), then some spurious lines remain
visible.

Myself, I see it on my two-heads setup, each 1280x1024 (apparrently
no high-dpi) scaled at 125% "default" and a colleague's machine (likely
same scaling, but didn't yet think of checking his scaling those few
days ago).  Both machines run Windows 7.  No other applications show
these symptoms, not even those that also adhere to the scaling).

[toc] | [prev] | [next] | [standalone]

#38950

On 5/4/2019 16:58, Andreas Leitgeb wrote:
> Knute Johnson <groups@585ranch.com> wrote:
>> On 5/3/2019 8:10 AM, Andreas Leitgeb wrote:
>>> Andreas Leitgeb <avl@logic.at> wrote:
>>>> The application uses awt & swing components for the GUI, and all
>>>> windows look distorted, fonts are a bit larger, even images look
>>>> a bit stretched and moving another window over the jdk 11 application
>>>> window leaves behind some spurious lines, as if the refresh had off-
>>>> by-one-pixel inaccuracies.
>>> In the settings dialog for "Screen Resolution", there is an option
>>> labelled "Make text and other items larger or smaller", which on my
>>> desktop was set to 125%.
>>> Java up to 8 totally ignored that setting.
>>> Java 11 tries to follow it (which is arguably an improvement), but
>>>      does so in a somewhat broken way.
>> I think that change actually came with Java 9.
> 
> Ouch, that makes it seem pretty unlikely that the visual bugs would
> get fixed any time soon :-(
> 
> But thanks for the information.
> 
>> It is really a big improvement for high dpi screens.
> 
> I'd wholeheartedly agree, if it weren't for the pixel bugs.
> 
> 
> I'd really appreciate some triaging help per email or here - either
> about you seeing problems in this or other setups, or about you not
> seeing problems despite similar setup. "Problems" means for example,
> that if another window is moved over the jdk11 app, or even just a
> combo/dropdown box or popup window closing (and thereby unobscuring
> only parts of the jdk-11 window), then some spurious lines remain
> visible.
> 
> Myself, I see it on my two-heads setup, each 1280x1024 (apparrently
> no high-dpi) scaled at 125% "default" and a colleague's machine (likely
> same scaling, but didn't yet think of checking his scaling those few
> days ago).  Both machines run Windows 7.  No other applications show
> these symptoms, not even those that also adhere to the scaling).
> 

I'm happy to help you out with that.  Can you make an SSCCE that 
demonstrates the problem?  I know that mixing AWT and Swing components 
can get tricky.

If you want to email,  knute 2019 at 585 ranch dot com

-- 

Knute Johnson

[toc] | [prev] | [next] | [standalone]

#38968

Knute Johnson <nospam@rabbitbrush.frazmtn.com> wrote:
> On 5/4/2019 16:58, Andreas Leitgeb wrote:
>> Myself, I see it on my two-heads setup, each 1280x1024 (apparrently
>> no high-dpi) scaled at 125% "default" and a colleague's machine (likely
>> same scaling, but didn't yet think of checking his scaling those few
>> days ago).  Both machines run Windows 7.  No other applications show
>> these symptoms, not even those that also adhere to the scaling).
> I'm happy to help you out with that.  Can you make an SSCCE that 
> demonstrates the problem?

It'll take some time, but I'll eventually get back to your offer.

> I know that mixing AWT and Swing components can get tricky.

I didn't know that, but it might help me find the relevant
ingredients for the SSCCE. We do indeed have some mixture 
of these.

> If you want to email,  knute 2019 at 585 ranch dot com

Once I get it together, I'll likely post it here, but also Cc: you.

For now, we switched off the scaling (set to 100%), to be able to get
other tasks done, but we'll pretty surely have to deal with it again.
It's not solved yet, just a bit postponed.

[toc] | [prev] | [next] | [standalone]

#39282

We were able to let that case "rest" a bit (clients still on Java 8),
and in the meantime all the test-clients with "Java > 8" are on
Windows 10, and the problem no longer seems to show up.

With Java 11.0.* the window now just stays small, whereas with
Java 13.02 it now seems to respect the desktop magnification
setting and still shows none of the artifacts seen on Windows 7.

Thanks for all offered help.

Of course, there is now a new problem with Java 13.0.2 (with the same
mixture of JacORB and glassfish-ORB as works fine for 11.0.2 & 11.0.6)
It advertises a wrong encoding to the Corba-server, and all the umlauts 
get hosed during transfer. I'm still on the start with this one,
and will come back once I know more (or the problem dissolves again).

On Linux I had that problem already with Java 8, and a workaround was
to set LANG to an 8bit locale for the java client process.


Andreas Leitgeb <avl@logic.at> wrote:
> Knute Johnson <nospam@rabbitbrush.frazmtn.com> wrote:
>> On 5/4/2019 16:58, Andreas Leitgeb wrote:
>>> Myself, I see it on my two-heads setup, each 1280x1024 (apparrently
>>> no high-dpi) scaled at 125% "default" and a colleague's machine (likely
>>> same scaling, but didn't yet think of checking his scaling those few
>>> days ago).  Both machines run Windows 7.  No other applications show
>>> these symptoms, not even those that also adhere to the scaling).
>> I'm happy to help you out with that.  Can you make an SSCCE that 
>> demonstrates the problem?
>
> It'll take some time, but I'll eventually get back to your offer.
>
>> I know that mixing AWT and Swing components can get tricky.
>
> I didn't know that, but it might help me find the relevant
> ingredients for the SSCCE. We do indeed have some mixture 
> of these.
>
>> If you want to email,  knute 2019 at 585 ranch dot com
>
> Once I get it together, I'll likely post it here, but also Cc: you.
>
> For now, we switched off the scaling (set to 100%), to be able to get
> other tasks done, but we'll pretty surely have to deal with it again.
> It's not solved yet, just a bit postponed.
>

[toc] | [prev] | [next] | [standalone]

#38885

On 4/8/2019 12:40 PM, Andreas Leitgeb wrote:
> PS: I'd also appreciate hints about what people are *supposed* to use
>   instead of corba nowadays. (Server is in C++ and client in Java, and
>   getting them into the same language is infeasible.)

Most obvious: use web service.

If you really want a binary protocol and an IDL then look at
Thrift or gRPC.

Many like gRPC better but I actually like Thrift better.

Arne

[toc] | [prev] | [next] | [standalone]

#38890

Am 09.04.2019 um 00:41 schrieb Arne Vajhøj:
> On 4/8/2019 12:40 PM, Andreas Leitgeb wrote:
>> PS: I'd also appreciate hints about what people are *supposed* to use
>>   instead of corba nowadays. (Server is in C++ and client in Java, and
>>   getting them into the same language is infeasible.)
> 
> Most obvious: use web service.
> 
> If you really want a binary protocol and an IDL then look at
> Thrift or gRPC.
> 
> Many like gRPC better but I actually like Thrift better.
> 
> Arne
> 
> 
> 
> 
Or if you want a text-based protocol that can be used over any sort of 
transport, look at Google Protocol Buffers.
-- Sebastian

[toc] | [prev] | [next] | [standalone]

#38894

On 4/10/2019 9:46 AM, Sebastian wrote:
> Am 09.04.2019 um 00:41 schrieb Arne Vajhøj:
>> On 4/8/2019 12:40 PM, Andreas Leitgeb wrote:
>>> PS: I'd also appreciate hints about what people are *supposed* to use
>>>   instead of corba nowadays. (Server is in C++ and client in Java, and
>>>   getting them into the same language is infeasible.)
>>
>> Most obvious: use web service.
>>
>> If you really want a binary protocol and an IDL then look at
>> Thrift or gRPC.
>>
>> Many like gRPC better but I actually like Thrift better.

> Or if you want a text-based protocol that can be used over any sort of 
> transport, look at Google Protocol Buffers.

gRPC is Google ProtoBuf over HTTP.

But ProtoBuf is as far as I know a binary format.

Arne

[toc] | [prev] | [next] | [standalone]

#38897

Arne Vajhøj <arne@vajhoej.dk> wrote:
> On 4/8/2019 12:40 PM, Andreas Leitgeb wrote:
>> PS: I'd also appreciate hints about what people are *supposed* to use
>>   instead of corba nowadays. (Server is in C++ and client in Java, and
>>   getting them into the same language is infeasible.)
> Most obvious: use web service.
> If you really want a binary protocol and an IDL then look at
> Thrift or gRPC.
> Many like gRPC better but I actually like Thrift better.

I'll keep that in my backhead... Thanks!

For now, the glassfish-orb finally looks promising enough, to not
actively pursue the alternatives.

[toc] | [prev] | [next] | [standalone]

#38916

On 4/10/2019 2:13 PM, Andreas Leitgeb wrote:
> Arne Vajhøj <arne@vajhoej.dk> wrote:
>> On 4/8/2019 12:40 PM, Andreas Leitgeb wrote:
>>> PS: I'd also appreciate hints about what people are *supposed* to use
>>>    instead of corba nowadays. (Server is in C++ and client in Java, and
>>>    getting them into the same language is infeasible.)
>> Most obvious: use web service.
>> If you really want a binary protocol and an IDL then look at
>> Thrift or gRPC.
>> Many like gRPC better but I actually like Thrift better.
> 
> I'll keep that in my backhead... Thanks!
> 
> For now, the glassfish-orb finally looks promising enough, to not
> actively pursue the alternatives.

If you want to look at CORBA vs Thrift then you could
start at:

http://www.vajhoej.dk/arne/articles/binrpc2.html
http://www.vajhoej.dk/arne/articles/binrpc3.html

that shows the same code in CORBA and Thrift in various
languages.

Disclaimer: I am not really an expert in neither CORBA
nor Thrift, so the above should be seen as very
introductory.

Arne

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | comp.lang.java.programmer

csiph-web