Hi Johan,
Still I really do not understand what particular problem that is solved by
changing
the template from
MySuperclass subclass: #Foo
instanceVariableNames: ''
classVariableNames: ''
poolDictionaries: ''
category: 'Bar-Core'
to
MySuperclass subclass: #Foo
instanceVariableNames: ''
classVariableNames: ''
category: 'Bar-Core'
other than some of your student had problem not yet knowning what pool
dictionaries are
and you want to hide pools therefore. A weak argument since some students may
not yet
know about class variables - so why not hiding them in the first place too?
Another teacher may argue that his students got problems because the template
was changed
and nearly all ST, Seaside and Pharo books used for teaching include the
extended variant
of the message.
IMHO a class template is (as the name says) a "template" and a template should
be
something one just has to fill out. The idea of a template is to avoid too much
typing afterwards.
So the idea is one just should fill out the template without much hazzle.
If I require an ivar, a class variable, a pool or a category I just put it in.
By now reducing the template people who require pools have to do more typing
and
they have to remember the order of words in the keyword message...
I stand at my point I think there is not much real value in this change of the
default
template, but are fine if community agrees on the reduced version.
Thanks
T.
