After using Dashcode for almost a year now, this is the bottom line:
“Don’t make any big projects with it.”
– A random Dashcode user
Then, debugger stops working. The Dashcode’s small embedded fake HTTP server can’t handle the simultaneous requests made by the main page to load all the scripts. You might circumvent this by making a script loader that somehow loads them gradually, one by one. I tried it but it didn’t work, instead started giving way more exotic error messages.
This is until the project grows even bigger and you reach the point where Dashcode crashes when autoloading your project.
It didn’t happen on Snow Leopard, though, so I guess this is some random incompatibility problem with OSX Lion. Even choosing the setting “Do nothing when Dashcode starts” doesn’t disable the autoload completely. This is probably because closing the big project on Dashcode crashes it and it reloads the last project when starting again.
I found a workaround for that:
- Open Dashcode
- Quickly press CMD-W when the project loads up
- Quickly press CMD-Q when the project is closed
- Open Dashcode again
- Open the project from the Recent projects menu
Handy and easy.
Anyway, it’s a shame that it seems this program has been neglected by Apple for some time now. Hope they’ll get more active on it one day again.
One thought on “Dashcode, part II”
I agree with you. Dashcode could certainly be what jquery mobile has become to the world and more. I moved on primarily because I just couldn’t get good information on how to add to the stacks. Bought Dashcode for Dummies and even took a class from the same author via VTC, both left a lot to be desired. I did manage to cobble together one program, but found it to run slowly due to the images that I included.
LOVE the way that you use databases in Dashcode. I’m so challenged when it comes to all of this stuff.
Would appreciate any information that you are willing to post to help me find more information on Dashcode. I keep hoping that I can get proficient enough to use it.