On Sat, Aug 22, 2015 at 12:19 AM, Peter Uhnák <i.uhnak@gmail.com> wrote:
On Wed, Aug 19, 2015 at 4:58 PM, Thierry Goubier <thierry.goubier@gmail.com> wrote:
2015-08-19 16:46 GMT+02:00 Sean P. DeNigris <sean@clipperadams.com>:
kilon.alios wrote
I have to confess I was never and probably will never be a fan of the system browser
I agree. It was probably well-suited to the context in which it was invented, but I think we could do much better today. However: - IMHO there is value in having a really-great-old-thing that empowers us to create an entirely new thing - as mentioned, it's good to have a simple and robust fallback behind a revolutionary new tool
Yes!
This is confusing to me. How do you guys write/read code? I was under the impression that Nautilus (System Browser) is the go-to solution. Or is there some other tool/approach I don't know about?
Coding from within the debugger? - where you write methods making use of classes/methods that don't yet exist. When you invoke this from Playground, the expected debugger appears and you flesh out the missing methods (again making use of classes/methods that don't exist yet), then continue from the debugger and flesh out the next missing methods. cheers -ben