Hi Danny,

��
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.

The GUI you write is great, it push ProfStef from an interactive tutorial to an integrated help system.

But :) I think we should keep the idea of the interactive tutorial (the basic LessonView) using ProfStef go. Because ProfStef go is a little game, it must be attractive, funny. I like the idea of ProfStef which talk to the user and interact. My inspiration was��http://tryruby.org/

So IMHO you should put all your changes in a new class, like TutorialBrowser. So we will have:
- "ProfStef go" for the interactive tutorial
- "TutorialBrowser open" for the pseudo-help system.

This way we can keep existing classes clean.

And take care of unit tests and class comments :) .


Cheers,

Laurent

��

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