Get 'no' example working with Weblua

[ghoulsblade]

Get 'no' example working with Weblua

[campadrenalin]

I'm going to try to fix the TTF font issue, using the Font.js library. This lets us measure font metrics for a given text at any size, which lets us cache metrics for individual characters, and render text to canvas directly with fillText, rather than as glyphs.

[ghoulsblade]

awesome progress overall =) sorry i've been inactive, was away from home on a business trip.
ttf with canvas draw : hmm sounds like a potential performance bottleneck,
if it's not much effort a caching of the canvas for the same text would be good,
i suspect love loads the glyphs into a texture and blits from there or something,
rather than rendering the same text 30+ times per second using a ttf lib.
But not top priority i guess.

[campadrenalin]

Heh. After writing that, I figured out that fillText only works on 2D contexts. So while we can use it to populate textures, it's useless for directly rendering to the canvas. So the two different font types will share a common architecture after all.

They will differ a bit in that the TTF fonts will use an array of textures, and render characters to them as needed, striking a balance between preallocation and being able to add an arbitrary number of glyphs to the cache on demand. All the common code will be in cLoveFont, but thanks to the way Weblua supports handles, I'm able to do image fonts and TTF fonts separately as the cLoveImageFont and cLoveFontFace classes. This allows a nice, straightforward separation between common code, image-specific code, and fontface-specific code.

[campadrenalin]

Font.js turned out to be a bust, but I was able to get equivalent functionality from canvas.measureText. TTF fonts are now working with Weblua as demonstrated by the demo page. In case I haven't already made enough warnings about this, I seriously overhauled the entire love.font.js library. It's better but will probably take some getting used to.