TextKit a2 Available
January 29th, 2008 by Jonathan JohnsonWe’ve made alpha 2 of TextKit available which includes several features and fixes that you’ve requested.
- TKTextRenderer does not recalculate line heights when setting an attribute. This bug would cause any assignment to font or text size to cause the lines to overwrap and draw offset (if aligned).
- Style of inserted text is now based on the previous character. This bug is hard to describe, but essentially what was seen before is on Mac OS X, the style of the inserted text would be applied correctly, but as soon as you selected some text, the inserted text would flip back to the style of the text after the insertion point. On Windows, there was no flipping: it just took the style from the next character, rather than the previous character. Now, styles are properly applied using the previous character.
- Added some field measurement methods. We’ve added three new methods: ObjectAtXY, LineAtY, and LineTop. Read the documentation for more information about these methods.
We’re excited to see how much interest there is in this product. Please let us know if there’s anything you would love to see this field do by either commenting here or filing a new ticket.
Visit the product page to download and learn more about TextKit.
Thanks everyone!
January 30th, 2008 at 7:20 pm
waou just been playing with it, with large text and large pictures, this is great
so many questions bumped into mind :
- will it support exporting/importing something like rtf ?
- how is this possible ? linux too. you used some kind of lib like QT or else ?!
thanks very much for making this !
January 30th, 2008 at 9:55 pm
It will support a binary serialization, which will support custom objects, in the next alpha or two. This will be used for styled cut, copy, and paste. I plan on having RTF supported before version 1.0, but it’s a little bit further back on my list of priority.
It will be supported on Linux as well. It’s completely custom written, and that’s for speed and all of the wonderful features that we couldn’t do if we tried to use a native control.
However, our goal is that by version 1.0, it will be indistinguishable from the native fields on all platforms. This means even for little nitpicky issues, so be sure to let us know about every issue you find, no matter how mundane
January 31st, 2008 at 6:05 pm
oki sounds great! thanks a lot a good luck for the rest of it
February 4th, 2008 at 11:25 am
I haven’t had much time to digest this, but I had two feature-related questions. First, do you plan on implementing a full justification (since the metrics for it are such a pain)? Also, while thinking about your off-screen renderer object, it occurred to me that this could potentially be a fix for ugly rotated text on Windows. Do you plan on implementing a rotational method(s) on it?
Thanks again for your efforts.
February 5th, 2008 at 7:04 am
Sorry for the delay in responding, out on vacation this week. Full justification may or may not be in version 1.0. It’s still a tricky problem to solve, but we certainly can solve it. I’m wanting to get a lot of the more lower-hanging fruit taken care of first, and then see what our customers really want at that point in time.
I don’t plan on adding any text rotation explicitly in TextKit. However, it will be integrated with this soon, which should solve the rotated text problem on Windows.