Yes (the tinting inline now works as well). Thanks for those. They are hangovers - originally I converted the .fnt to a file so I can require it, but now it just scans the .font file, it wasn't multiline compatible originally.
The .x,.y can be set for the view group.
It is a bit confusing. This is partly deliberate - I wanted to be able to have something like the display.newText() call because that's how Corona is designed, so the display.newBitmapText is a wrapper.
The problem with that is, what it returns isn't any sort of display object - hence there is the getView() call - all the transitions refer to getView(). It can't be treated like a displayObject, you can insert it into groups and things but you have to be careful.
It tends to have two of everything because of this. It's a good idea to move it either with transition.to or setting x,y on the viewGroup, which works as normal, or to use the :moveTo() classes which also works, but if you try to do both it can get confusing as one ends up offsetting the other.
The driver is actually the singleton FontManager class, which updates the strings and does the animations, this maintains a list of the strings and updates them if necessary.
It is not best to use it in complex code but to use the strings as individual objects in a scene - this isn't really a problem, because it would normally be used for title screens or scores (this is why it does vertical text as well), and use the clear call to clean up (or remove() them manually).
Because it's not a proper display object it can't clear itself up with string:getView():removeSelf() - it doesn't work, it will leave the string behind because there is a lot of support stuff in there besides the display objects. Hence it has its own string:remove() method which clears everything up. It can't be integrated in quite the same way as Corona Objects can be.
I don't think it's practical (unfortunately) to implement it as a pure Corona extension, it is doable but it would be extremely vulnerable to changes in the way Corona works.
The OO doesn't really matter - it's much the same as Corona in many ways. I do like chaining stuff which Corona doesn't support but it's just shorthand for multiple calls
you just have
which is neater