lol, feels good, don’t it? And I liked yours better (simpler, cleaner) - mine was definately 0th gen.
But seeing them both go away in favor of NICE is super cool.
Color is only spelled “Colour” if you’re currently wearing “Armour”. But hey, wait - I thought you were Norwegian? Shouldn’t you be saying it should be spelled… “Farge”? Seriously - “setFarge()”. I can go for that. Hell, I like it better than Colour.
Yes, I can use google translate. I don’t speak a word of Norwegian. The internet is AWESOME.
Nei, jeg er ikke norsk. Jeg er en engelskman som bor i Norge.
But it should be “setteTekstfarge”. I’m pretty sure that the Norwegians would make “text colour” all one word (so your dislike of camel case would be satisfied).
Mind you, I shan’t consign my fonts to the trashcan just yet. Given how long Apple is taking to approve the current update of Codea then I think that our fonts have a little longer to live. Also, it might be good to have something to fall back on for custom fonts or for glyphs that aren’t in the iOS5 fonts (or is there full unicode support?).
England wasn’t cold enough for you already? ok - you have special dispensation for superfluous "u"s then. I still like doing it in Norwegian, just because.
I like to think of the current, soon to be obsolete font stuff, as … well, soon to be obsolete. If someone goes spelunking thru our code and gets something of value later, it’s all bonus. I don’t know about you, but I always considered my stuff as a placeholder, and maybe someplace to experiment (and to be totally truthful, a show-off stunt) - the concept that I will outlive the usefulness of my code makes me more tolerant of its many imperfections. (my pic() class is also largely irrelevant too, and good riddance. We still need a decent flood fill…)
I was gonna ask about Unicode, but I’d just be parroting the word - I’m very ASCII, thank you very much - you can keep your umlauts and such. But - you can insert emoji into the editor, so I suspect it’s supported from that angle at least, even if it comes out wonky in lua string manipulation.
Also the editor doesn’t correctly handle fonts that cause the line height to change (such as Kanji). So I’ll have to look at ways to fix that in the future.
but I always considered my stuff as a placeholder, and maybe someplace to experiment (and to be totally truthful, a show-off stunt)
Agree wholeheartedly (especially with the parenthetical bit).
I like unicode. With unicode, not only do I not have to worry when I switch to bokmål (f. eks. hvis jeg vil at studentene lærer å gjøre complekstallteori med Codea), I also don’t have to worry when I switch to maths and start writing things like ? ? ? ? ? ? E = ??.
Great work Simeon, this is the feature i am looking forward the most. And text input from keyboard. Then i am a happy man Hope Apple doesnt delay it for months.
@fred lol - that’s why I upgraded back in the day to a 1200 baud modem - 300 baud was slow enough I could read faster than it!
@simeon re. speed - I was actually surprised how fast my original draw-them-with-lines fonts worked; I’ll be very, very suprised if your stuff isn’t 1 or 2 orders of magnitude faster. Lua is all good and light, but it’s hard to beat compiling down to machine code.
I’m all excited about this, but let me ask since it was brought up - if we got a keyboard (just the system keyboard, toggle it on/off, get keys from it) along with the fonts, that would be doubleplus awesome. Not that I’d let it delay things.
Keyboards are easy! I’m not looking for having the OS keyboard simply because I want to be able to have more control over the keys than that would allow. For my kids, I want a keyboard with lowercase letters. Maybe I want some special characters (like the Codea keyboard) as well. Getting text into the app is a solved problem … I just haven’t written the code yet[1].
[1] I’m a mathematician. “I’ve bought the wood, I have the tools, so why are you looking at me as if we don’t have any shelves yet?”
Out of curiosity, does emoji work? It works with the print statement. Edit: Oh sorry. The images didn’t load before. AWSOME! (Sorry, I hit the character limit)
(Wrote this this morning in response to “keyboards are easy!” - just noticed it’s still in ‘draft’ status)
That’s the spirit!
I’m actually all for “roll your own keyboard” - the issue I have is that then someone has to get a copy of my library, and someone will make a different one, and blah blah blah and in the end, I’m lazy. (I actually have a working keyboard in my font library - it’s crap)
