tag:blogger.com,1999:blog-7655425.post3636736417268433972..comments2020-04-25T08:41:45.452-04:00Comments on e-venture: Dashcode Browser Back Button IssueErik Loehfelmhttp://www.blogger.com/profile/00442820836647805543noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7655425.post-40777757163255609672009-04-12T23:25:00.000-04:002009-04-12T23:25:00.000-04:00Thanks for the props!I've pretty much abandoned th...Thanks for the props!<BR/><BR/>I've pretty much abandoned the Dashcode tools and have jumped right into XCode and native iPhone application development. It's been tough but rewarding.<BR/><BR/>- eErik Loehfelmhttps://www.blogger.com/profile/00442820836647805543noreply@blogger.comtag:blogger.com,1999:blog-7655425.post-12390871600980835122009-04-11T11:17:00.000-04:002009-04-11T11:17:00.000-04:00Great looking app, Erik!Not that it helps at all, ...Great looking app, Erik!<BR/><BR/>Not that it helps at all, but I too struggle with Dashcode in many ways. The lack of documentation is one. Another is that something in the way I have put everything together causes Safari on both the iPhone and iPhone Simulator to become completely unresponsive. I have to reload in Safari on my iPhone or shutdown and restart Dashcode. There's no way to diagnose the problem and nothing in the documentation discusses such pitfalls. I have a feeling it is a memory issue, but without analysis tools, there's no way of knowing. Have you run into such issues?<BR/><BR/>I feel like I have taken Dashcode to the limit. I'm considering abandoning it. But seeing your app makes me at least aware that others are trying to implement serious apps in it. Maybe it's worth continuing to wrestle with it.Anonymousnoreply@blogger.com