This is fun because I was thinking that we should add to the main page a videos of the counter coding in the debugger and GTInspector.
We have the mooc videos showing ProfStef so we have nearly everything we need and now they are available (should upload them with english voice). Stef On Fri, Oct 6, 2017 at 5:39 PM, Ben Coman <b...@openinworld.com> wrote: > I saw this comment, and wonder if we might have an intro video (or cartoon) > of how to run the ProfStef tutorial in the first few minutes of opening your > first image. > >> They need to work on the presentation. How do you get started ? How does >> the code look like ? etc. Not just "download this program and buy this book" > reply > > yes, time, resources, someoneHasToDoIt all apply. > just a random thought, > cheers -ben > > On Fri, Oct 6, 2017 at 9:47 PM, horrido <horrido.hobb...@gmail.com> wrote: >> >> Thanks. I gave your answer verbatim. I also added the following paragraph: >> >> The problem I find with today’s developers is that they are rather >> closed-minded. They are rigid and inflexible, and not willing to adapt to >> new and different ways of doing things. In my generation (circa >> 1980–1990), >> people didn’t have a problem with trying different technologies. That’s >> why >> I had no issue with learning Smalltalk 10 years ago, after I had retired >> from a 20-year-long career in C systems programming and FORTRAN scientific >> programming. >> >> >> >> Sven Van Caekenberghe-2 wrote >> >> On 6 Oct 2017, at 14:54, horrido < >> >> > horrido.hobbies@ >> >> > > wrote: >> >> >> >> I received this comment from someone who complained: >> >> >> >> *What about the lack of documentation? From time to time I’ve checked >> >> some >> >> SmallTalk implementations like Squeak, GNU-Smalltalk and now Pharo. Of >> >> these, only GNU-SmallTalk appears to have a free, official programming >> >> guide >> >> and core library reference that any serious programmer expects from a >> >> language. >> >> >> >> https://www.gnu.org/software/smalltalk/manual-base/html_node/* >> >> >> >> I pointed to Pharo's documentation but then he came back with: >> >> >> >> *Then show me a link of the free, maintained reference documentation >> >> for >> >> the >> >> classes that form “the core library”, like this one for Python >> >> (https://docs.python.org/3/library/index.html)* >> >> >> >> It's true, most Smalltalks do not have a core library reference, not >> >> even >> >> VisualWorks! So what is the proper response to this complaint? >> > >> > The first answer is that Pharo/Smalltalk is unique in that a running >> > system/IDE contains _all_ source code, _all_ documentation (class, >> > method, >> > help, tutorial), _all_ unit tests and _all_ runnable examples in a very >> > easy, accessible way. It takes some getting used to, but this is >> > actually >> > better and much more powerful than any alternative. >> > >> > The second answer is that there are lots of books and articles that take >> > the classic/structured book/paper approach. There is >> > http://books.pharo.org, http://themoosebook.org, >> > http://book.seaside.st/book, http://medium.com/concerning-pharo and many >> > more. >> > >> >> Thanks. >> >> >> >> >> >> >> >> -- >> >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> >> >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >
