Am 04.03.2015 09:43, schrieb Andrey Pokhilko:
The rule I think is common for all pages.

Choise of optimum width is a bit arbitrary. From my experience,
screenshots should not be more than 800px width, 600px is even better.
It is good to take screenshots with window minimized to desired size, to
keep the image from scaling and having maximum detail.

The problem of the big images is not a new one. The patch for https://bz.apache.org/bugzilla/show_bug.cgi?id=53764 adresses part of this problem. The big images don't look nice, but they will
not keep the paragraphs from wrapping.

I think we should use ant to make thumbnails from all images with maximum size of about 800 px width and use those inside the documentation. Those thumbnails
should then link to the original ones, just like Andrey suggested.

If a screenshot can be cropped to a size of the thumbnail it would be even better,
but I suspect that it will not always work.

I will try to get the thumbnail generation and linking into to the patch for bug 53764.

Regards
 Felix


Andrey Pokhilko

On 03/04/2015 11:26 AM, Milamber wrote:
On 04/03/2015 07:13, Andrey Pokhilko wrote:
Hi,

I think having too big screenshots on doc pages makes it difficult to
read because of horizontal scrollbar, it prevents text from wrapping.
I'd recommend limit width of images (just by setting width attribute)
and provide hyperlinks to full-size images.

The doc pages is the user manual or another(s) page(s) ?

What will be the maximum width for the best view?


Andrey Pokhilko

On 03/04/2015 02:57 AM, Milamber wrote:
Hello,

The first release candidate for JMeter 2.13 (r1663807) has been
prepared, and your votes are solicited.

This release brings some new features and fixes
some bugs.

If you can, some tests of this release candidate (load tests and/or
functional tests) with Java 6/7/8 on Linux/Windows/Mac OS on changes are
welcome.

You can read the New and Noteworthy section with some screenshots to
illustrate improvements and full list of changes at:
http://people.apache.org/~milamber/jmeter-2.13RC1/docs/changes.html

JMeter is a Java desktop application designed to load test functional
behavior and measure performance. The current version is targeted at
Java 6+.

Archives/hashes/sigs:

https://dist.apache.org/repos/dist/dev/jmeter/v2.13_RC1/

RAT report:

http://people.apache.org/~milamber/jmeter-2.13RC1/dist/rat-report-jmeter-2.13RC1.txt

(please note: you need build the latest version of RAT: 0.12-SNAPSHOT to
generate the report. Reason unknown, but the version 0.11 don't work
(loop running indefinitely))

MD5 hashes of archives for this vote:

15ddc74560f71118a6afdaef41a800a6 *apache-jmeter-2.13.tgz
d4280b12bea9e09769075fb3d4861deb *apache-jmeter-2.13.zip
45723fba94479016a14e9834817ec2d4 *apache-jmeter-2.13_src.tgz
f04c55fa5c12b281b8060248d4437325 *apache-jmeter-2.13_src.zip

Site Docs are here:
http://people.apache.org/~milamber/jmeter-2.13RC1/docs/

Maven staging repo is accessible here:
https://repository.apache.org/content/repositories/orgapachejmeter-1004/org/apache/jmeter/

Tag:
http://svn.apache.org/repos/asf/jmeter/tags/v2_13_RC1/

Keys are here:
http://www.apache.org/dist/jmeter/KEYS

N.B.
To download the dependencies: "ant download_jars"

To create the jars and test JMeter: "ant package test".

JMeter 2.13 requires Java 6 or later to run.

Some known issues and incompatible changes are listed on changes page.
http://people.apache.org/~milamber/jmeter-2.13RC1/docs/changes.html


All feedback and vote are welcome.

[  ] +1  I support this release
[  ] +0  I am OK with this release
[  ] -0   OK, but....
[  ] -1   I do not support this release (please indicate why)

The vote will remain open for at least 72 hours.

The PMC members please indicate the mention "(binding)" with your vote.


Note: If the vote passes, the intention is to release the archive files
and rename the RC tag as the release tag.

Thanks in advance!

Milamber





Reply via email to