jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Felix Schumacher <felix.schumac...@internetallee.de>
Subject Re: Darklaf - A themeable swing Look and Feel based on Darcula-Laf
Date Tue, 04 May 2021 15:25:44 GMT

Am 01.04.20 um 18:30 schrieb Antonio Gomes Rodrigues:
> Hi
>
> Good job, JMeter is much more beautiful now
>
> I have tested the last nighty in a fresh Ubuntu linux and I have two
> warnings when I launch JMeter
>
> Apr 01, 2020 5:25:35 PM com.kitfox.svg.Text buildText
> WARNING: Could not create font Arial
> Apr 01, 2020 5:25:35 PM com.kitfox.svg.Text buildText
> WARNING: Could not create font Arial
> Apr 01, 2020 5:25:35 PM com.kitfox.svg.Text buildText
> WARNING: Could not create font Arial
> Apr 01, 2020 5:25:35 PM com.kitfox.svg.Text buildText
> WARNING: Could not create font Arial
> Apr 01, 2020 5:25:35 PM com.kitfox.svg.Text buildText
> WARNING: Could not create font Arial
> Apr 01, 2020 5:25:35 PM com.kitfox.svg.Text buildText
> WARNING: Could not create font Arial
>
> I need to install Arial font with:
> sudo apt install ttf-mscorefonts-installer
>
> Gtk-Message: 17:25:36.748: Failed to load module "canberra-gtk-module"
> I need to insyall the module with:
> sudo apt install libcanberra-gtk-module

And only about one year later, we got rid of the warnings ;)

The svg had some references to the Arial font embedded, which it didn't
need.

Felix

>
>
>
> Le dim. 8 mars 2020 à 14:27, sebb <sebbaz@gmail.com> a écrit :
>
>> On Thu, 5 Mar 2020 at 17:28, Vladimir Sitnikov
>> <sitnikov.vladimir@gmail.com> wrote:
>>>> Properties, XML, etc are not executed by the JVM; they are effectively
>>>> just data.
>>> BeanShell, JavaScript, and Groovy are not "just data", but it is code
>> which
>>> is a part of JMeter.
>>>
>>> So far I see no technical justification for requiring all transitive
>>> dependencies to be written in Java language only.
>> I'll try again.
>>
>> + The main reason is portability.
>>
>> Compiled Java source is portable to all systems that have a suitable JVM.
>>
>> Native code is inherently not portable.
>>
>> + Another reason is that compiled Java byte code cannot cause a JVM crash.
>> Native code can (and does) cause crashes, and these are generally very
>> difficult to debug.
>>
>> + A third reason is that Java source code only needs a JDK to compile it.
>> There is no need to install additional compilers.
>> Indeed you can compile the code on one OS and deploy on another.
>>
>> Native code usually means installing a C-compiler.
>> Unfortunately, there are lots of varieties of C-compilers with
>> incompatible options and syntax.
>> This make compiling native code rather difficult and error-prone
>> Also compilation generally has to be done on the same OS version.
>>
>> ===
>>
>> As far as JMeter is concerned, it is the first two reasons that are
>> most important.
>> The 3rd reason is of more concern to creators of distributions.
>>
>> ===
>>
>> Note that BeanShell, JavaScript (Rhino) and Groovy are themselves pure
>> Java - that is why the same jar can be used on all OSes.
>>
>> ===
>>
>> I hope you now understand what 100% Pure Java is about and why it is
>> important to JMeter?
>>
>>> Vladimir


Mime
View raw message