Bowline updates and more!
Mar2
A lot of work has been going into Bowline recently. Here are the latest features:
- New desktop app framework using wxWidgets, WebKit and Ruby 1.9.
- Improved and faster binding API
- New API for asynchronous Ruby/JS callbacks
- Bundler support
- Background updating
- Loads of fixes and optimizations
There’s also a new JavaScript framework for Bowline which will be released soon. It’s designed to be fairly de-coupled from Bowline – so you can use it for web applications. The idea is that you can share a lot of code between your desktop apps and your web applications.
Additionally I’ve been working on a project for in-memory models called SuperModel.
SuperModel works particularly well inside Bowline apps. Here are the main features:
- Serialisation
- Validations
- Callbacks
- Observers
- Dirty (Changes)
- Ruby Marshaling to disk
- Redis support
I’ve also re-written SuperModel in JavaScript – it’ll be integral to the next Bowline release.
Syncro is another recent project – it’s like Juggernaut on steroids! Syncro let’s you easily synchronise Ruby classes and state between remote clients. It’s also has some fancy features like offline support. You can now make Bowline apps, that function fully offline, and then can synchronize up to your servers (and any other clients) when they come back online.
All that work has made Taskforce possible. Taskforce is a collaborative work manager. Think of it as a cross between Things.app and Google Wave. Here’s a recent screenshot of Taskforce working on top of Bowline on OSX.
If you’re interested, sign up.
Enjoy this article?
Consider subscribing to our RSS feed!
4:23 pm on May 6th, 2010
Hello.
I’ve been checking occasionally on the status and it’s great to hear the project is not dead. But it sounds like you abandoned Titanium, in favor of wxWidgets/webkit combination. Right? If you don’t mind I’m just curious – what prompted the change?
Are you planning to support Windows? ( I mean it says on github, that you are, but anything more definite? Like ” yeah maybe in a year or two, when bowline is stable” or ” we are working on it, so maybe in half a year or so?”)
5:00 pm on March 24th, 2011
I know this is old, but I would love to hear the reason as well. I’m currently debating whether to use Appcelerator or roll my own version of it (either something in Mono or Qt). There’s tons of posts arguing one way or another (titanium sucks!! titanium is great!!) but it would help to hear from someone working on an actual application as to what prompted the move away from Titanium.