Comments on: Wicket TextileLabel

By: Dani from Poland

Dani from Poland — Thu, 01 Apr 2010 10:29:56 +0000

Great post. I was looking for an half an hour for solving to my problem and I have found it here. Great

cheers from Poland!:)

By: Daniel Spiewak

Daniel Spiewak — Thu, 01 Oct 2009 21:15:22 +0000

Unfortunately, I’m not sure I even have the source anymore. I’ll take a look to see if I can find it, but I can’t make any promises. Fortunately, it should be pretty easy to recreate the component from the info given in this article.

By: ReinoutS

ReinoutS — Wed, 30 Sep 2009 10:46:17 +0000

Hi Daniel,

The link to your TextileLabel is dead. Could you post it again, please?

By: Daniel Spiewak

Daniel Spiewak — Fri, 13 Jul 2007 02:15:54 +0000

With the latest version, I still have the same problems.

By: Daniel Spiewak

Daniel Spiewak — Fri, 13 Jul 2007 02:10:10 +0000

Incidentally, have you considered easing our adoption pain considerably by adding an Ant build file? Or at least a precompiled JAR file. I know it doesn’t take all that much to assemble the JAR ourselves, but it’s still a headache.

By: Daniel Spiewak

Daniel Spiewak — Fri, 13 Jul 2007 02:07:56 +0000

No real headway, unfortunately. My current working theory is that PLextile is handling the \n\r whitespaces wrong (since I can step through the text myself and see that those are the characters coming from the HTML element).

I’ll try that latest version and see if that solves it.

By: Ben

Ben — Thu, 12 Jul 2007 23:46:18 +0000

Any more headway on that whitespace issue?

I thought I’d leave a message and mention that a slightly newer version of PLextile is up on Sourceforge. I’ve been working on a website for an IEEE competition that uses PLextile, and have been finding/fixing quite a few bugs with it.

Ben.

By: Daniel Spiewak

Daniel Spiewak — Mon, 09 Jul 2007 18:48:48 +0000

Hmm, it does spit out the proper output on my end as well. (wrapped in paragraph tags) It’s sounding more and more like whitespace stuff, but that would be really odd.

Windows uses \n\r as the linebreak character. I was under the impression MacOS X followed the *nix standard of \n. It was MacOS 9 and lower which used the solo \r char.

By: Ben

Ben — Mon, 09 Jul 2007 18:30:53 +0000

Interesting, to keep you posted, my parse ends up with the proper HTML with H1, H2, P, etc. But when I posted it it stripped all the HTML — this might just be how your comments work, but could a similar thing be happening with the other data?

Good luck,

Ben.

By: Ben

Ben — Mon, 09 Jul 2007 18:28:06 +0000

PLextile looks for the occurrence of two newline characters in a row “\n\n” to represent a new block… It first strips all ‘\r’ characters though. so “\n\r” shouldn’t be a problem — I myself use a Macbook which uses both characters (if I recall doesn’t windows just use ‘\n’?)… The only thing I can think of that could be a problem is:

1) The characters are escaped in a weird way, like my previous post suggested.
2) There is some sort of whitespace between two ‘\n’s perhaps “\n \n”.

Try parsing this string as a test:

String test=”h1{color: red}. Hello World\n\np>.I’m a test paragraph.\nstill same paragraph.\n\nh2. Second level header.”;

I just tried it in the newest build of the parser and get:

Hello World
I’m a test paragraph.still same paragraph.
Second level header.

Ben.