Le 08/11/2015 20:29, Ferlicot D. Cyril a écrit :
Le 08/11/2015 20:14, Thierry Goubier a écrit :
Stef,
I don't understand. I have never set a category in a class creation template for the last three years.
When I teach using Pharo, I allways tell students to create a package, select the package in the browser and add a class there.
Changing #category: for #package: (which is what the fix will be, I bet) is useless.
Thierry
I understand because when I explain a little Pharo to friends who only learned Java, I like to explain the advantage to have everything as an object and every action as a message. And one of the first message we encounter is the class template. We can explain «We send this message to "Object" and with this message we have arguments which areâ¦Â». But when it comes to the package we have to say «And for the category you pass the package name and don't care about the "category" name» because this is too much to explain the tags thing to beginners.
Which would mean the tags have added complexity in that regard.
I think that what is easily visible should be very explicit, and more advances feature should be in menu or things like that to help beginners.
I'm not sure. Power users use the template directly (saves you one, two, three mouse clicks and a few mouse mouvements) and I'd suggest using the menu for beginners (you can direct them to the menu and they will remember they are doing that 'action' of adding a class: a dialog probably also helps them to focus on it and the questions they have to answer when they are creating a class). Thierry