Tim,

And all Squeakers who take the time to update Wiki pages - Thank You!

When you are investing time in this valuable effort, please keep in mind the audience of beginners and (#('CS' 'CP' 'CIS' 'MIS' 'EE' 'ETC') includes: myDegree) not when writing things up. Since I have a very small amount of formal education in IT,  I have been updating pages lately and trying to rewrite or add language that makes more sense to me. Using MorphicModel as an example, when i encountered the word "sensitize", I had no idea what it meant, but a bit of web poking surfaced some information that made some sense to me and I added it to the page(sans footnote). Part of what I added included another term, callback, which I don't understand and is not defined in the Swiki. The word "callback" is referenced in 20+ pages, but never defined.

I also have trouble with "used to represent structures with state and behavior as well as graphical structure" and "The tree is constructed concretely by adding its constituent morphs to a world." I think, I may get the meaning of these phrases, but I am not sure:

Is a structure, in the context of a MorphicModel, an instance of the class to which one or more submorphs have been added and (optionally) sensitized? Are constituent morphs added to a world (World?) or and instance of MorphModel or perhaps as an instance of PastUpMorph?

Now back out of this Rabbit Hole and return to the one where I am trying to update my project which has gotten badly out of sync from working on too many OSes and Images :-(

-jrm




On Thu, Apr 5, 2018 at 10:47 PM, tim Rowledge <tim@rowledge.org> wrote:


> On 05-04-2018, at 10:13 AM, K K Subbu <kksubbu.ml@gmail.com> wrote:
>
> wiki.squeak.org/squeak is an excellent resource for Squeakers. However, it's interface is a bit dated and could do with some improvements.

I agree that the UI is a bit blah (and your suggestions are interesting) but far more worrying is the out of date state of so many pages.  Every now and then I go on a minor rampage to mark obviously obsolete pages, delete clearly ridiculous one, recycle those pages, update stuff where I know what can be improved and so on. We suffer from a colossal swathe of effectively empty pages generated by some long-gone process/project that appeared to consider that dumping class name as page and (maybe) sticking class comments in was a good idea. There are strings of pages forming the promising beginnings of tutorials that simply fade out to.........{crickets}

Almost anyone can help to clean up the swiki. Pick some page from the front page, follow it down the rabbit-hole a bit, look at the pages that link to a duff page, clean them up a bit, recycle bad pages, rewrite poorly thought out explanations, maybe replace ancient screenshots with ones taken from a current Squeak.  (as an example, take a look at http://wiki.squeak.org/squeak/3480 - lots of very out of date examples there). Even simple things like organising into proper lists and editing text into proper paragraphs can help a lot in readability. You don't need to be a great expert to provide a valuable service here - but I bet that spending some time in the swiki will start to make you an expert, even if it's only by making you look up the real state of something!

If everyone on the squeak-dev list edited a swiki page once a week we'd very quickly see big improvements.

tim
--
tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim
I'm so skeptical that I'm not sure I'm really a skeptic