-> Simone It doesn't answer your question about debugging, but just to say I start from the other angle, of writing a trivial Shoes.app that DOES start (perhaps based on something in the samples folder) and then adding things to it to bend it to my will. That way, the last thing to be added is the thing that has stopped it working...
The other thing to do, if the code lends itself to it, is create 'checkpoints' with calls to Alert - then you can see what method or block you are in when it fails. On 27/02/2008, Simone D. <[EMAIL PROTECTED]> wrote: > Hi all, > I'm trying to create anything using Shoes but I have some troubles > with some require. > Which is the best way to debug Shoes to understand what is not working > (meaning that Shoes.app doesn't start)? > > Thank you > Simone >
