Smalltalk › Pharo › Pharo Smalltalk Developers

Nautilus questions

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

42 messages Options

123

Peter Uhnak

Re: Nautilus questions

On Wed, Aug 19, 2015 at 4:58 PM, Thierry Goubier <[hidden email]> wrote:

2015-08-19 16:46 GMT+02:00 Sean P. DeNigris <[hidden email]>:

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?

I would like the coding area to expand a bit when a method is too long.

While QA did take perhaps too much space, I think that there is benefit in having relatively small coding area (by small I mean pre-QualityAssistant) since it forces me to write smaller methods (I want to be able to see it at once). But this is just personal experience.

On Thu, Aug 20, 2015 at 10:58 AM, Esteban Lorenzano <[hidden email]> wrote:

- groups (btw, current scoped button does not takes that into account)

I thought groups are being removed.

Ben Coman

Re: Nautilus questions

On Sat, Aug 22, 2015 at 12:19 AM, Peter Uhnák <[hidden email]> wrote:

>
> On Wed, Aug 19, 2015 at 4:58 PM, Thierry Goubier <[hidden email]>
> wrote:
>>
>>
>>
>> 2015-08-19 16:46 GMT+02:00 Sean P. DeNigris <[hidden email]>:
>>>
>>>
>>> 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

123