Danny: You don't have an idea of how much important this is for the Pharo community. Having good documentation, tutorials and so on, is a KEY aspect from my point of view. So thanks to Laurent for the initiative and you for the work too.

Regarding your changes, I like them. I have a couple of thoughts:

- I would revome the buttons to go next and return. Actually, I wouldn't just remove the "next" button until it was not first done by code. Then you can show it (for that lesson). There are some places where the author has to think to go to the text lesson. For example, in the double cascade method. So, if you have the button...that good trick has no sense.

- I really like the idea that when someone does a tool, it can register its own tutorial somewhere. Then you can browse all the tutorials. Take this 3 examples:
���� *� WorkingSets from Romain: there is a cool workspace that explains that. But....who see it ? nobody....
���� * Algernon. The same. It has a welcome workspace. Who see it ? nobody
���� * ScriptManager: the same

So...I would really love that each of those projects can define in a class side initialize method for example, something like this:

Algernon class >> initialize
ProfStef registerNewTutorial: self algernonTutorial.

ProfStef registerNewTutorial:� aTutorial
� self addTutorial: aTutorial

or something like that...

BTW, can someone create tutorials for that? the workspaces are already written, so maybe it is too much work.

- I found a little bug in the UI. If you double click on a lesson, a debugger comes. Can you reproduce it ?

- Maybe you can integrate this in "Tools -> More -> ProfStef Tutorials"

- For Pharo 1.0 release, I will include the workspace version (the old one) as I don't want to incorporate new stuff. Only IMPORTANT bug fixes. But of course, it will included in next images. Continue with your work!!!


Cheers

Mariano

2010/1/28 Danny Chan <chan_dhf@yahoo.de>
Hi all!
I have pushed a version to Monticello that has a bit of a GUI with nicer
navigation, see the screenshot. I did not find out how to place the buttons
better, and I don't know how to tell the tree morph to select another entry
when I navigate through the lessons using the buttons or the workspace
contents. Please tell me what you think about this. Since I know how little
Smalltalk I really know, I certainly managed to destroy something, so please
have a look and tell me what to do better.

Here are a few ideas I've had, which I as a relative beginner would find really
neat in an interactive tutorial application. As time allows, I would try to
implement at least some of the points below:

- Clickable items in the text window. So that a tutorial writer could for
example write something like this:
<code>SystemWindow new openInWorld</code>
, and the code together with a button saying 'doit' would appear. So in
principle a markup language for interactive tutorials which adds a bit of
interesting short cut functionality and eye candy to the tutorial.

- Tabbed browsing for having several tutorials opened at the same time

- A button saying 'save lesson', that overwrites the appropriate method with
the current state of the workspace; users can annotate the tutorial with their
own notes or experiments; also the ability to add additional lessons

- A button to push the current tutorial with all the additional annotations to
a Monticello repository, from which future versions for everyone can be
generated. Wiki for interactive tutorials!

- Some additional functionality to generate a whole new tutorial from within
the tutorial browser

- (Semi-)Automatic update of tutorials

- And, of course, many, many tutorials. Wouldn't it be great to have a
tutorial for all the important and interesting aspects of a system, and even
for every additional package you download? With the system Laurent designed,
writing a tutorial is only so very slightly harder than writing example
classes and methods, but so much more expressive and approacheable for someone
new.

Cheers, Danny


Am Mittwoch, 27. Januar 2010 19:00:25 schrieb laurent laffont:
> 2010/1/27 Mariano Martinez Peck <marianopeck@gmail.com>
>
> > I forgot to ask....
> >
> > Does the DEVImageWorkspaces openGettingStartedWorkspace � still make
> > sense having ProfStef �?
> >
> > Can you take a look and "merge" it to ProfStef if there is something cool
> > not included by Stef ? �:)
> >
> > I would like to have only one reference form the Pharo welcome workspace.
> >
> > Thanks
> >
> > Mariano
>
> I agree for merging
>
> I will put these snippets from getting started in ProfStef:
> 42 explore
> Date today explore
> 'abc' asUppercase.
> 'Hello World' reverse.
>
> There's cool comments too.
>
> I put global Read & Write on ProfStef so everybody can destroy it :)
>
>
> Laurent
>

_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project