Smalltalk › Pharo › Pharo Smalltalk Users

Thanks.

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

2 messages Options

Hans Schueren

Thanks.

Thank you Kion Alios !

As a beginner of smalltalk i have realized two things.

1. The main view in smalltalk language is on the " Programming System"
( functions of the Pharo system at all )

You could say : " Open the IDE - check the functions for many days
: then start to write Objects with minimal code"

2. In other languages the main view is on the "Syntax and code structure
only" ( the systems IDE is minimal styled )

You could say : " Open the IDE - check the function for one day :
and start to write code for many days "

My next aim is to write a simple program from a practical task. a
storage program for items

The only information are " what the worker in the company would do with
the items ".

Therfore i try to make a FLOW CHART with an additional software tool to
see the whole Tasks in one view.

Then i add the Object names and class names that are corresponding to
that tasks ( same name as real ).

I would see in practice if this flow chart is a good method for
overview. ( Brainstorming - Flowchart ).

I dont care of the many functions of the system at this beginning point.

Just make ONE simple program , and compile it to an .exe to check on
another PC.

Regards

Hans

kilon.alios

Re: Thanks.

I assume here you mean that Smalltalk emphasises on the existence of the IDE and the close integration of the IDE with the language. I will say yes you are correct.

In other languages the IDE is simply not there, so the language cannot rely on it the same way Smalltalk relies on its own IDE. But then it also depends. Smalltalk and Pharo are dynamic languages but so are Python , Ruby, Javascript and much more. Even static type languages have integrated some type of dynamism. So the differnces are not as massive as you may assume. For example Ruby is actually very close to Smalltalk. So language wise Smalltalk does not really offer anything out of the ordinary.

But yes the close integration with the IDE and live coding itself set Pharo and Smalltalk apart from all other languages.

Now if you imply that you need to understand many methods in Pharo because the methods are small, generally that is not the case. As a matter of fact Pharo is quite small system, Python, Java , Ruby , Javascript they come with tons more libraries and code. But you dont need to understand all these things. You learn as much you need to move to the next step, as much you need to write the next line of code. At least that is how I work.

So dont try to figure out Pharo structure just yet, start with very small tasks, very simple problems , concetrate only on one line of code and then go back to learning as much you need to code the next line and continue in this loop. Dont waste your time with reading chapters or prining out code and tying to understand diagrams and complex structures. Trust me its a waste of time, because in a month you will forget all that.

This is not how our brain works.

The brain wants small chunks, small things to learn, one step of time and always code. Dont stop coding. Practice is everything.

So yes dont care about learning many functions, stick to only a few of them, do small tasks and you will be fine. Pharo is easy to learn anyway.

On Thu, Oct 23, 2014 at 8:18 PM, Hans Schueren <[hidden email]> wrote:

Thank you Kion Alios !

As a beginner of smalltalk i have realized two things.

1. The main view in smalltalk language is on the " Programming System" ( functions of the Pharo system at all )

You could say : " Open the IDE - check the functions for many days : then start to write Objects with minimal code"

2. In other languages the main view is on the "Syntax and code structure only" ( the systems IDE is minimal styled )

You could say : " Open the IDE - check the function for one day : and start to write code for many days "

My next aim is to write a simple program from a practical task. a storage program for items

The only information are " what the worker in the company would do with the items ".

Therfore i try to make a FLOW CHART with an additional software tool to see the whole Tasks in one view.

Then i add the Object names and class names that are corresponding to that tasks ( same name as real ).

I would see in practice if this flow chart is a good method for overview. ( Brainstorming - Flowchart ).

I dont care of the many functions of the system at this beginning point.

Just make ONE simple program , and compile it to an .exe to check on another PC.

Regards

Hans