Mockingbird goes 1.0, introduces real-time collaboration using OT and Node
blog.gomockingbird.com
blog.gomockingbird.com
Really appreciated and heavily used the grid update from a few months ago -- well implemented with the minimum amount of UI, like the rest of the app.
Highly recommended.
I LOVE Balsamiq (another wireframing option), Peldi (balsamiq founder) is a really nice guy and one of my companies even hosts some of their website... but I've moved over to using Mockingbird for my own work. It's that good.
If you need to design wireframes, I encourage you to try Mockingbird.
Can you give us a sense about your work environment (IDEs, etc) and how you go about debugging Cappuccino apps? Do you even use Atlas? Any tips for a noob Cappuccino dev?
Thanks and nice work!
I work entirely in emacs and use OJTest to test my code as I write it. Sheena (my co-founder) uses TextMate though, and I think that might be a better environment for someone starting out.
The best debugging trick I think I've learned is to use index-debug.html and enable objj_msgSend_decorate(objj_backtrace_decorator); (it's commented out by default). Other than that, I think I've learned to just try testing my code early and often with OJTest to catch things. I do want to try to build out better testing and debugging tools for Capp though.
In general, just ask questions on the mailing list and don't be afraid of coming into IRC. The #cappuccino IRC channel is one of the most helpful ones I've been.
Ideally: I would like components to match their actual behaviour more closely, e.g. a tab container would actually contain views in the respective tabs that would be shown or hidden depending on the tab selected. I know this is no easy feat - I have yet to find a wireframing tool that lets you infuse interactivity as easily as one would like to, and I have been through a lot of them.
Have you evaluated causal trees against OT as the collaboration algorithm?
See:
bouillon.math.usu.ru/articles/ctre.pdf bouillon.math.usu.ru/articles/broth5.pdf
edit: updated link to saikat's suggestion
http://github.com/ajessup/pluto http://www.dontstopthesignal.com/2010/05/design-goals-for-pl...
I got the email notification about these upgrades this morning and it was poorly written. You might want to re-visit the text and look it over. I've deleted it now so can't quote you specifics but I remember seeing lines advising that services would be available until Jan 2010 etc.
It would have also helped having a line at the top simply stating what Mockingbird is for those of us who may have forgotten.
(great product though; I'll be trying it again now I've been reminded it exists)
The pain points in wireframing software are:
* organizing projects / groups of similar wireframes
* keeping track of versions
* allowing anyone on your team to get access to / update the latest file.
Give me this tiny horse and I'll abandon Balsamiq. Thanks!
Note: this is exactly like how 25% of AOL's support tickets involved issues with Windows. Remember, your users are always dumber than you are.