Hi Mariano,

2010/1/21 laurent laffont <laurent.laffont@gmail.com>

...

I've just released in MetacelloRepository the milestone I've wanted to reach. Now you can create your own interactive tutorial with ProfStef. How ? There's a ProfStef interactive tutorial for that :D

ProfStef goOn: HowToMakeYourOwnTutorial

Laurent: Adrian has a good idea. What about adding lessons (at the end) of the ProfStef that calls directly to ProfStef goOn: HowToMakeYourOwnTutorial

For example, in the last lesson con can put something like:

"Do you want to create your own interactive tutorial with ProfStef ? That's very easy!! How ? There's a ProfStef interactive tutorial for that :D Jus evaluate the following code: ProfStef goOn: HowToMakeYourOwnTutorial"

With this, I don't need to link to both codes from the welcome workspace to pharo image and also it would be also seen by more people. More people do the tutorial than those who had read this email ;)

What do you think ?

Yes, we are thinking about listing all tutorials in a sexy way. Danny Chan has just started to contribute to ProfStef and he's working on this. I can add you and/or Adrian as developper if you want. I have less time now so I may concentrate on pharocasts.

BTW, I found a problem with ProfStef. I select a piece of code, right button, and if I press extended search, the same popup raise again instead of going to the "extended search" popup. Can you reproduce it ?

I will try. Thank you. Cheers, Laurent

Cheers

Mariano

...

It was real fun to write this !

Cheers,

Laurent

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

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

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 On Wed, Jan 27, 2010 at 6:07 PM, Mariano Martinez Peck < marianopeck@gmail.com> wrote:

2010/1/27 laurent laffont <laurent.laffont@gmail.com>

Hi Mariano,

...

...

2010/1/21 laurent laffont <laurent.laffont@gmail.com>

...

I've just released in MetacelloRepository the milestone I've wanted to reach. Now you can create your own interactive tutorial with ProfStef. How ? There's a ProfStef interactive tutorial for that :D

ProfStef goOn: HowToMakeYourOwnTutorial

Laurent: Adrian has a good idea. What about adding lessons (at the end) of the ProfStef that calls directly to ProfStef goOn: HowToMakeYourOwnTutorial

For example, in the last lesson con can put something like:

"Do you want to create your own interactive tutorial with ProfStef ? That's very easy!! How ? There's a ProfStef interactive tutorial for that :D Jus evaluate the following code: ProfStef goOn: HowToMakeYourOwnTutorial"

With this, I don't need to link to both codes from the welcome workspace to pharo image and also it would be also seen by more people. More people do the tutorial than those who had read this email ;)

What do you think ?

Yes, we are thinking about listing all tutorials in a sexy way. Danny Chan has just started to contribute to ProfStef and he's working on this.

Cool!! What I will do for the next image is to remove that little text to build your own tutorial, from the welcome workspace. I will only link to the ProfStef go.

If you release a new version, please let me know so that I can include it in the image.

...

I can add you and/or Adrian as developper if you want.

No problem. I won't have too much time to contribute, sorry :(

...

I have less time now so I may concentrate on pharocasts.

good luck with you new job :)

...

...

BTW, I found a problem with ProfStef. I select a piece of code, right button, and if I press extended search, the same popup raise again instead of going to the "extended search" popup. Can you reproduce it ?

I will try. Thank you.

I reported a similar problem to Frederic in the NewInspector. Maybe you can fix it in the same way:

http://n4.nabble.com/bug-with-Extended-Search-of-low-panel-of-new-inspector-...

Cheers

Mariano

...

Cheers,

Laurent

...

Cheers

Mariano

...

It was real fun to write this !

Cheers,

Laurent

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

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

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

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

Mariano, you can download last ProfTest package: - contextual menu simplified, IMHO better for a tutorial - I've added "Pharo environment" lesson - updated some examples + last slide from getting started workspace. Cheers, Laurent 2010/1/27 Mariano Martinez Peck <marianopeck@gmail.com>

2010/1/27 laurent laffont <laurent.laffont@gmail.com>

...

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.

Excellent. I will remove then the invocation to that workspace from the next dev image :)

...

I put global Read & Write on ProfStef so everybody can destroy it :)

Ok...

...

Laurent

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

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

2010/1/27 Mariano Martinez Peck <marianopeck@gmail.com>

2010/1/27 laurent laffont <laurent.laffont@gmail.com>

...

Mariano,

you can download last ProfTest package: - contextual menu simplified, IMHO better for a tutorial

I agree.

...

- I've added "Pharo environment" lesson

Cool. Maybe in this lesson (23) yo can add to the contextual menu also the inspect it and browse it. what do you think ? This is cool because they see that the same they are doing from code, you can do it from UI. There is no difference at all. Both send the same message :)

It's a good idea. I'll try it.

...

- updated some examples + last slide from getting started workspace.

Excellent. Little detail. You forgot to let the code as code color (without the comments)

BTW, where do you keep this workspaces (the text) information ? Just in case I want to commit something

You haven't do the HowToMakeYourOwnTutorial ?!?!?! :D Take a look at SmalltalkSyntaxTutorial, lessons category methods. Laurent.

Thanks!!!

Mariano

...

Cheers,

Laurent

2010/1/27 Mariano Martinez Peck <marianopeck@gmail.com>

...

2010/1/27 laurent laffont <laurent.laffont@gmail.com>

...

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.

Excellent. I will remove then the invocation to that workspace from the next dev image :)

...

I put global Read & Write on ProfStef so everybody can destroy it :)

Ok...

...

Laurent

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

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

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

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

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

Hi Laurent! I see your point. It is definitely a good idea to keep the core ProfStef as simple as possible. Right now ProfStef itself can serve as a simple application to begin exploring the language, so that even a dummy like me has a chance to understand it. Maybe it is a good idea to create a new package that builds on the ProfStef core application you wrote, call it ProfStefCenter or something, and add additional functionality there? That way ProfStef itself would stay simple and be in the spirit of a playful introduction to Smalltalk, and a full fledged interactive help and tutorial system could evolve from there. Cheers, Danny Am Donnerstag, 28. Januar 2010 20:45:35 schrieb laurent laffont:

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

2010/1/28 laurent laffont <laurent.laffont@gmail.com>

On Thu, Jan 28, 2010 at 10:13 PM, Danny Chan <chan_dhf@yahoo.de> wrote:

...

Hi Laurent!

I see your point. It is definitely a good idea to keep the core ProfStef as simple as possible. Right now ProfStef itself can serve as a simple application to begin exploring the language, so that even a dummy like me has a chance to understand it. Maybe it is a good idea to create a new package that builds on the ProfStef core application you wrote, call it ProfStefCenter or something, and add additional functionality there? That way ProfStef itself would stay simple and be in the spirit of a playful introduction to Smalltalk, and a full fledged interactive help and tutorial system could evolve from there.

Cheers, Danny

Mariano has just suggested to create 3 separate packages 1) ProfStefBrowser 2) ProfStefCore 3) ProfStenTests

so 2 + 3 = current stable version, and put all the GUI stuff in 1.

Yes, what I suggested is that the "text" and lessons should be totally decouple from how they are shown: if a worksapce, a UI, etc. I would even reify the concept of lesson, which is almost text. With this -both "UIs" can coexist: the workspace version and the browser version- -merge would be easy Of course that names are just the ones that came first to my mind. You can put better names if you want. Even more, I would like to load only "some" of them. For example, just core, or core and tests. Maybe other person wants the browser...etc. All this should be defined in a Metacello configuration. This will let us define stable versions and let us choose what we want. Cheers Mariano

Would you like to create ProfStefBrowser ?

Laurent

...

Am Donnerstag, 28. Januar 2010 20:45:35 schrieb laurent laffont:

...

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

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

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

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

Now, a ProfStef tutorial must subclass AbstractTutorial. Danny has written a simple method to find all tutorials: AbstractTutorial class >> tutorials ^self subclasses sortBy: [:a :b | a name < b name]. Note that the class name is used to generate the tutorial title (like in Rails). So: HowToMakeYourOwnTutorial title ==> 'How To Make Your Own Tutorial' Laurent

Each package can define each own tutorial entry point method like this: AlgernonTutorial class>>MyCooooolTutorial <tutorial> bla bla bla

then with: (PragmaCollector filter: [:pragma | pragma keyword = 'tutorial']) reset

you get all existing methods with a <tutorial> pragma.

And no need to manage any registration/unregistration.

Cheers Alain

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

Am Donnerstag, 28. Januar 2010 21:20:00 schrieb Mariano Martinez Peck:

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.

I have a secret (well, now not so secret) agenda. I want a help system that allows me to learn all the cool stuff I don't know, and where developers of great software are asked immediately 'Hey, sounds great, but where is the tutorial?'. So that people like me, who are not really software developers, can start using this stuff, too.

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

Yes, I am still learning how to work with Morphic in general and this TreeMorph in particular

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

How?

- For Pharo 1.0 release, I will include the workspace version (the old one) as I don't want to incorporate new stuff.

Very wise. I wouldn't want to include new stuff by someone who committed himself to really learn Smalltalk only a few weeks ago for my welcome screen. Cheers, Danny

Hi! As discussed I've added a new repository ProfStefBrowser and uploaded a version which builds on top of the current ProfStef version from Laurent without touching the code in the ProfStef package.

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

I think I found out why this happens. Apparently, when you double click on an item, the item is deselected. The callback that is called in this case receives as the item which was clicked nil. I added a workaround, but since the callback is set using a message 'setSelectedSelector:' I personally feel that this behaviour is not intuitive and that this callback shouldn't be called at all when deselecting items. Who are the guys to talk to for this behaviour? Danny

Am Freitag, 29. Januar 2010 15:38:58 schrieb Mariano Martinez Peck:

On Fri, Jan 29, 2010 at 3:33 PM, Danny Chan <chan_dhf@yahoo.de> wrote:

...

Hi!

As discussed I've added a new repository ProfStefBrowser and uploaded a version which builds on top of the current ProfStef version from Laurent without touching the code in the ProfStef package.

Cool. Just be aware that you don't need to create a separete repository for that. You can have more than 1 package in a repository. Then, you can have the ProStef repository, where inside you have different packages like ProfStef core (Laurent) and ProfStefBrowser. This is easier because you have all together in the same repository.

Ah, understand. I was confused by packages vs repositories. I will copy the packages to the ProfStef repository. Danny

Welcome ProfStef-Core and ProfStef-Tests !

Cool !! Now you can update the ConfigurationOfProfStef so that I can link correctly from ConfigurationOfPharo ;) You can look as an example in ConfigurationOfShout or OCompletion ! cheers Mariano

Looks cool! Stef On Jan 28, 2010, at 8:27 PM, Danny Chan wrote:

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

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