It’s a major undertaking with a long timeline and its final form isn’t fully settled. I am taking measures: I have enlisted a technical writer to help bring this blog back to life, and I’ll try to communicate more of TextMate’s status and direction through him.īigger than either of those problems though, as I mentioned, is that TextMate 2 is no minor facelift. So while I started a lot of posts, I end up unhappy with them halfway through, and they don’t get finished or published. I am more into informal conversations, for instance over mailing lists or on IRC. Hopefully an alpha version will be ready before too long, but I can’t make any promises about dates.Īnd why haven’t I been better about keeping the world informed? It is a combination of many things really, but the main issue is that I am not good at writing for a large audience. While I use 2.0 for my own work, day-to-day, and the basic infrastructure is pretty solid, much of the front-end still needs work, and for now it’s all lacking the spit and polish of a finished app. But as they say, on the horizon, mountains look small. So where does development stand for 2.0? It feels to me like most of the modules are getting close, say 90%. In the coming months, I’ll try to describe some of these new abstractions, but for now, know that I am excited about the new ideas involved. Not only are the low-level data structures chosen for increased flexibility, but the abstractions on which TextMate is built-snippets, scope-based language grammars, context-dependent settings-have been rethought and are more powerful than ever. Every part has been completely rewritten to take advantage of the lessons learned from the years of version 1.
But TextMate 2 is about more than new surface features. The requests for TextMate 1 have mostly been incremental additions such as split views, chunked undo, and editing over SFTP.
#TEXTMATE 2 BINARY SERIES#
While I am not writing to announce a release date for TextMate 2, I do hope that this post will be the first in a series showing a bit more transparency. Moreover, the community continues to churn out new bundles and features for TextMate 1.5, and I’ve been building up a backlog of posts describing them. I hope to publicly describe some new abstractions in the coming weeks and months. The rewrite has been a slow and careful process, but the ideas behind it are exciting. In short, TextMate development is going strong: TextMate 2 isn’t done yet, but progress is steady, it is starting to take shape, and the end is in sight. This blog post, the first I’ve written here in a long time, is an attempt to assuage those concerns and answer some of the most frequent questions. Over the past two years, posts on this blog have slowed to just a trickle, and a number of TextMate users have asked about TextMate’s status, or publicly worried about its future.
The author, Allan Odgaard, has updated the TextMate blog with this post: Working on It Allan stresses that no release is "around the corner" yet.)
If this text is still here, that is still the case. Q: Is TextMate 2 still in development, or has it been abandoned?
0 kommentar(er)
