Format guidelines - Revision history

Ssmith2112: Fix typos

2025-06-03T13:51:01Z

Fix typos

← Older revision		Revision as of 13:51, 3 June 2025
Line 1:		Line 1:
	* Accumulating material		* Accumulating material
	* '''variable assignment syntax'''. Use <code>':='</code> instead of <code>'-'</code>. Ratios. I like ~~more~~ <code>'_'</code>, when it is rendered in Cuis XXX-SHOW-IT-UNICODE-XXX but there is a problem. (1) If we use the backward directed arrow the new user will be in trouble since he will not know how to type in that thing. (2) In other ~~Smalltalk~~ <code>':='</code> is more ~~used~~, as far as I know.		* '''variable assignment syntax'''. Use <code>':='</code> instead of <code>'-'</code>. Ratios. I like <code>'_'</code> more, when it is rendered in Cuis XXX-SHOW-IT-UNICODE-XXX but there is a problem. (1) If we use the backward directed arrow the new user will be in trouble since he will not know how to type in that thing. (2) In other Smalltalks <code>':='</code> is used more often, as far as I know.
	* '''Syntax ~~highlight~~ in big code chunks''' . It is much easier to read. The automatic highlighter in Mediawiki does a good job. To insert code you need to do <u>Insert -> More -> Code Block</u>.		* '''Syntax highlighting in big code chunks'''. It is much easier to read. The automatic highlighter in Mediawiki does a good job. To insert code you need to do <u>Insert -> More -> Code Block</u>.
	* '''Typing in small code chunks (inlined code)'''. At the moment i haven't ~~fund~~ a way to ~~hilight~~ ~~iniled~~ code. To type in inlined code for the moment do: <u>(1) select a code chunk (2) Click '''A''' -> Computer Code</u> .		* '''Typing in small code chunks (inlined code)'''. At the moment I haven't found a way to highlight inlined code. To type in inlined code for the moment do: <u>(1) select a code chunk (2) Click '''A''' -> Computer Code</u> .
	* '''~~Muse~~ button name by left-right order'''. Always use the convention first, second, third button. The ordering is left to right. ~~Mouser~~ are supposed to have 3 buttons. If people have strange mice (see Apple) they know already how to simulate the 3 buttons. Don't use the button color names as it is done in Squeak. As of today naming mouse ~~button~~ by color just adds to the complexity and perplexity of the new user.		* '''Mouse button name by left-right order'''. Always use the convention first, second, third button. The ordering is left to right. Mice are supposed to have 3 buttons. If people have strange mice (see Apple) they know already how to simulate the 3 buttons. Don't use the button color names as it is done in Squeak. As of today naming mouse buttons by color just adds to the complexity and perplexity of the new user.
	* aaa		* aaa

Nmingott: add something to quit the edit stat (strange)

2025-05-13T07:25:39Z

add something to quit the edit stat (strange)

← Older revision		Revision as of 07:25, 13 May 2025
Line 4:		Line 4:
	* '''Typing in small code chunks (inlined code)'''. At the moment i haven't fund a way to hilight iniled code. To type in inlined code for the moment do: <u>(1) select a code chunk (2) Click '''A''' -> Computer Code</u> .		* '''Typing in small code chunks (inlined code)'''. At the moment i haven't fund a way to hilight iniled code. To type in inlined code for the moment do: <u>(1) select a code chunk (2) Click '''A''' -> Computer Code</u> .
	* '''Muse button name by left-right order'''. Always use the convention first, second, third button. The ordering is left to right. Mouser are supposed to have 3 buttons. If people have strange mice (see Apple) they know already how to simulate the 3 buttons. Don't use the button color names as it is done in Squeak. As of today naming mouse button by color just adds to the complexity and perplexity of the new user.		* '''Muse button name by left-right order'''. Always use the convention first, second, third button. The ordering is left to right. Mouser are supposed to have 3 buttons. If people have strange mice (see Apple) they know already how to simulate the 3 buttons. Don't use the button color names as it is done in Squeak. As of today naming mouse button by color just adds to the complexity and perplexity of the new user.
			* aaa

Nmingott: started new page

2025-05-13T07:18:59Z

started new page

New page

* Accumulating material
* '''variable assignment syntax'''. Use <code>':='</code> instead of <code>'-'</code>. Ratios. I like more <code>'_'</code>, when it is rendered in Cuis XXX-SHOW-IT-UNICODE-XXX but there is a problem. (1) If we use the backward directed arrow the new user will be in trouble since he will not know how to type in that thing. (2) In other Smalltalk <code>':='</code> is more used, as far as I know.
* '''Syntax highlight in big code chunks''' . It is much easier to read. The automatic highlighter in Mediawiki does a good job. To insert code you need to do <u>Insert -> More -> Code Block</u>.
* '''Typing in small code chunks (inlined code)'''. At the moment i haven't fund a way to hilight iniled code. To type in inlined code for the moment do: <u>(1) select a code chunk (2) Click '''A''' -> Computer Code</u> .
* '''Muse button name by left-right order'''. Always use the convention first, second, third button. The ordering is left to right. Mouser are supposed to have 3 buttons. If people have strange mice (see Apple) they know already how to simulate the 3 buttons. Don't use the button color names as it is done in Squeak. As of today naming mouse button by color just adds to the complexity and perplexity of the new user.