https://bz.apache.org/bugzilla/show_bug.cgi?id=63620
--- Comment #13 from Vladimir Sitnikov <sitnikov.vladi...@gmail.com> --- > Right, but it is in the calculation of the width of lines to break them > apart, so it would still be helpful to try to pretty print the large json > structure (if it shortens the lines), don't you think? 1) An option to pretty-print based on the content type makes sense. However it might "defeat" regular expressions because "user-visible" json would be different from the one that came from the network. However I do support the idea of pretty-printing by default 2) Even though we have content type, it is not always right. For instance, they might sent the data as text/plain, and we have very little clue on how to pretty-print. 3) We might want to implement an option to "forcibly add newlines" for lines exceeding N characters. A plus would be to put that newlines in-between word breaks so it won't tear words. That might be a decent workaround. 4) It might be a Java-related issue. For instance, they say https://bugs.openjdk.java.net/browse/JDK-4202291 is fixed in Java 6 So it might be JMeter code is doing something wrong. We might want to analyze what is causing that slowness. For instance, what if we limit "the maximum width" of the textview? Would it influence text wrapping algorithm? -- You are receiving this mail because: You are the assignee for the bug.
