Pegasus for Cocoa Touch - Framework to build UIKit view hierarchies in XML

It seems like a neat project, but I don't really hate Interface Builder that much.<p>Getting rid of all the glue code is a <i>really</i> nice part of interface builder and this makes it so every UI element I want to use requires at least a couple lines of code.<p>I also don't like the idea of randomly tweaking numbers and rebuilding to see my whole interface.

Just to add: I'm seeing a lot of click-thrus from Ycombinator onto my site.<p>This is fantastic and I'm glad people are checking it out. I'm also looking to gather requests and feedback for how it can be improved further.<p>Right now it's little more than a proof-of-concept with a handful of adapters for the most basic UIKit classes (UILabel, UITextField, etc. but support for UITableView, UIPickerView, etc. is still in the works).<p>If anyone has any feedback, suggestions and/or criticisms please do leave a comment on the site or post here and I will look into it.

Developer of Pegasus here:<p>I hear what you say. The idea is not to necessary replace IB, but to provide an alternative.<p>Next step is to include layout managers (similar to Android/Swing) which will automatically lay out views based on some pre-defined templates (e.g. i*j grid, horizontal, vertical, etc.) which will remove the need for randomly tweaking numbers as you say ;-)<p>(Said so, this is how a lot of developers tend to work already...)

I'll bite.. why describe your UI in XML when interface builder does it for you? How does pegasus deal with localizing your UI in different languages? This seems a bit like reinventing the wheel for very little benefit.<p>Who is the target developer? A new developer to the platform or an experienced one?

Interesting. Have you thought about using JSON to describe views (like in QML)?

How stable is Pegasus now? Is anyone using it for realworld applications yet?