a Rich Text library for LÖVE

[pekka]

You don't apparently think it necessary or interesting to see how the guys at Trolltech have solved these problems when designing Qt and its Rich Text facility. That's kind of unfortunate. But, you know, I don't really want to defend this idea. I'm perfectly fine with you not liking it. In fact, I assume you don't like it and won't continue this discussion.

I'm just not happy about letting really poor arguments stand. Let's just look at the facts here. Some people can use a SUBSET of HTML as a perfectly fine markup language in their apps. I've even seen people implement a light-weight browser in their games to browse the HTML documentation while the game is running. It can be done. It has been done.

If you choose to do something else, fine. Just try to make the decision sensibly.

I hope it's OK if I don't post to this thread anymore.

(The Argument Clinic sketch was there to suggest I am not getting angry or frustrated here. I just get the feeling I am not getting across to you, but I have no hard feelings about that. On to other things.)

[Robin]

You don't apparently think it necessary or interesting to see how the guys at Trolltech have solved these problems when designing Qt and its Rich Text facility.

No, it is interesting, just not relevant to what we're doing.

I hope it's OK if I don't post to this thread anymore.

That's OK, although I hoped you'd stick around for more fundamental and important discussions.

(The Argument Clinic sketch was there to suggest I am not getting angry or frustrated here. I just get the feeling I am not getting across to you, but I have no hard feelings about that. On to other things.)

Heh, I had exactly the same feeling. But yeah.

Now that I got my new laptop and put LÖVE on it etc., I can start implementing it. ^-^

[Robin]

Fear not! I have started implementing RichText. It doesn't do anything yet, hell, I don't even know whether the syntax is right, but it's a start.

You may now commence commenting on my coding style, implementation choices and any horrible mistakes I will have made.

[nevon]

OMG Robin, wtf did you do!?

[kikito]

I like how it looks.

Comments:

• Some of those methods are going to be transformed into private ones later on, right?
• That render method is huge. It might help splitting it into several smaller ones

[Robin]

• Some of those methods are going to be transformed into private ones later on, right?

I'm not entirely sure what you mean. Local functions?

• That render method is huge. It might help splitting it into several smaller ones

I know, this I absolutely intend to do soon.

Also: updated version.

I hope you folks want to help testing this once it reaches a testable state.

[kikito]

I'm not entirely sure what you mean. Local functions?

Yes, local functions. "parse" is probably something you want to keep private. I have not reviewed the latest code.

[Robin]

New version!

• Implements colors
• Implements PO2 fix
• Splits up the render function
• Checked for syntax errors

[Robin]

New version!

This time, it works! It really does! However, there are still some issues and edge cases. Example main.lua included, you can fool around with it to test more of the richtext lib.

Requires 0.7.0, just mentioning.

Code: Select all

-- issues/bugs: (*: open  /: probably fixed  ~: workaround found)
--  * still under-tested
--  * renderText() may be too monolithic
--  * word wrapping might not be optimal
--  * words keep their final space in wrapping, which may cause words to be wrapped too soon
--  ~ text doesn't seem to be aligned properly, found workaround by multiplying height by 1.5, might need to be fixed in LÖVE
--  * initial text color (other than white) has to be specified manually by starting text

[arquivista]

My humble opinion. Rich Text would be a nice addition indeed but I think basic html and basic css would bring more text benefits than rich text and nice way to include and present external info. And since Rich Text is still a proprietary system and HTML/CSS an open one I think LOVE that is a free-source/open systems adept should be more "oriented" to adopt another open system like HTML/CSS.
But to be honest first I would also love to see printf with justify option (probably hard to implement right?)