On 08 Nov 2015, at 20:14, Thierry Goubier <thierry.goubier@gmail.com> wrote:
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.
Because what written there is not a package, itâs a package + tag. So it would make sense to have ⦠package: âPacakgeNameâ tag: âTagNameâ But what Iâd really enjoy is to have a dedicated UI there. Because we really use class templates as templates. 90% of a time I just change the Superclass, Class and instance variables. And 9% more I also add a tag to the package. So why we cannot have a UI with text fields for this values? Later it can be fancier e.g. classVariables are hidden by default and can be expanded on demand or if the are defined (I donât like explaining class vars to people and I donât like them from design point of view). Then also superclass field can have autocompletion only from the defined classes prioritizing the ones from the same package. Instance variables can be converted to slots really fast by lookup, etc⦠I mean, itâs nice that we can subclass by sending a message, but we donât develop methods in a template like: compile: âmethodCodeâ classified: âprotocolNameâ So maybe we make use of special UI for classes instead of plain code. Uko
Thierry
Le 08/11/2015 19:55, stepharo a écrit :
https://pharo.fogbugz.com/f/cases/16952/Change-class-template-creation
Stef
Hi guys
I think that not enough of us are teaching... we are so used to jump around "DETAILS" that we do not have a clue how newcomers see our system.
For example I hate that I have to explain that we should enter a package name as argument of a category????
Object subclass: #NameOfSubclass instanceVariableNames: ââ classVariableNames: ââ category: âPackageNameâ
I will change the template because I do not want to have to explain that and that our Mooc refers to such crap. And you will have the right to complain but in that case I will tell you: "give a lecture and come back to"
We are trapped in our way of thinking and we are trapped in the glitches of our system
We should not accept glitches and we should kill them.
Stef