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