The Cuis Cookbook - Revision history

Ssmith2112: Fix typos

2025-06-03T14:00:44Z

Fix typos

Nmingott: added link to new pages

2025-05-13T07:54:46Z

added link to new pages

← Older revision		Revision as of 07:54, 13 May 2025
Line 12:		Line 12:
	* [[Introduction]]. What you should expect from this book and the reason why I am writing it. STARTED.		* [[Introduction]]. What you should expect from this book and the reason why I am writing it. STARTED.
	* [[Why Smalltalk?]]. For what reason should you learn another programming language which is also not so popular? Read on, there are very good reasons. STARTED.		* [[Why Smalltalk?]]. For what reason should you learn another programming language which is also not so popular? Read on, there are very good reasons. STARTED.
			* [[Why Cuis Smalltalk?]] . TODO
			* [[MetaCookbook]]. Collection of things about this document.

	== Installation and start up ==		== Installation and start up ==

Nmingott: added link

2025-05-13T07:43:23Z

added link

← Older revision		Revision as of 07:43, 13 May 2025
Line 1:		Line 1:

	A programming language cookbook is something like ''StackOverflow'', without the digging part and the try&pray experience. For a gentle and structured introduction to Cuis-Smalltalk, you should start with the '''The Cuis Book''' and '''Learning-Cuis''' more about this on the [[CuisCoookBook-References\|References]]. This is intended to be a <u>resource for programmers</u>, in the sense that it answers questions that will naturally come up to programmers while exploring Smalltalk.		A programming language cookbook is something like ''[https://stackoverflow.com/ StackOverflow]'', without the digging part and the try&pray experience. For a gentle and structured introduction to Cuis-Smalltalk, you should start with the '''The Cuis Book''' and '''Learning-Cuis''' more about this on the [[CuisCoookBook-References\|References]]. This is intended to be a <u>resource for programmers</u>, in the sense that it answers questions that will naturally come up to programmers while exploring Smalltalk.

	'''Reliability'''. I am writing these notes while learning Cuis. Some of what I write may not be the best way to solve the problem, it may not even be correct. Be patient, double check. Since I use these recipes myself I am going to improve them in time.		'''Reliability'''. I am writing these notes while learning Cuis. Some of what I write may not be the best way to solve the problem, it may not even be correct. Be patient, double check. Since I use these recipes myself I am going to improve them in time.

Nmingott: typo

2025-05-13T07:31:40Z

typo

← Older revision		Revision as of 07:31, 13 May 2025
Line 11:		Line 11:

	* [[Introduction]]. What you should expect from this book and the reason why I am writing it. STARTED.		* [[Introduction]]. What you should expect from this book and the reason why I am writing it. STARTED.
	* [[Why Smalltalk?]]. For what reason should you learn another programming language which is also not so popular. Read on, there are very good reasons. STARTED.		* [[Why Smalltalk?]]. For what reason should you learn another programming language which is also not so popular? Read on, there are very good reasons. STARTED.

	== Installation and start up ==		== Installation and start up ==

Nmingott: added link

2025-05-13T06:58:59Z

added link

← Older revision		Revision as of 06:58, 13 May 2025
Line 6:		Line 6:
	'''Sorting principles'''. Topic order is intended to go from easy to difficult. From frequently necessary to rarely used. From needed at the beginning of the programming experience to needed by black belts. These three forces, as the 3 laws of robotics, regulate what chapter goes toward the top of the document. They hold also for sub-chapters and articles.		'''Sorting principles'''. Topic order is intended to go from easy to difficult. From frequently necessary to rarely used. From needed at the beginning of the programming experience to needed by black belts. These three forces, as the 3 laws of robotics, regulate what chapter goes toward the top of the document. They hold also for sub-chapters and articles.

	'''Contributions'''. I am trying to figure out ways to make contributions possible and fruitful, see [[contributions motivated guidelines]].		'''Contributions'''. I am trying to figure out ways to make contributions possible and fruitful, see [[contributions motivated guidelines]]. As a write I see that also important are [[format guidelines]].

	'''Copyright'''. You have the right to read, print for your own use and contribute to the document. You can make external links to this document. You can not copy the document and make it available somewhere else on the Internet. You can't claim ownership. You can't bring the document to an editor and publish it. I, as the author of more than 99% of the words here displayed retain all rights as well as the right to change these rules.		'''Copyright'''. You have the right to read, print for your own use and contribute to the document. You can make external links to this document. You can not copy the document and make it available somewhere else on the Internet. You can't claim ownership. You can't bring the document to an editor and publish it. I, as the author of more than 99% of the words here displayed retain all rights as well as the right to change these rules.

Nmingott: small variation

2025-05-13T06:47:29Z

small variation

← Older revision		Revision as of 06:47, 13 May 2025
Line 2:		Line 2:
	A programming language cookbook is something like ''StackOverflow'', without the digging part and the try&pray experience. For a gentle and structured introduction to Cuis-Smalltalk, you should start with the '''The Cuis Book''' and '''Learning-Cuis''' more about this on the [[CuisCoookBook-References\|References]]. This is intended to be a <u>resource for programmers</u>, in the sense that it answers questions that will naturally come up to programmers while exploring Smalltalk.		A programming language cookbook is something like ''StackOverflow'', without the digging part and the try&pray experience. For a gentle and structured introduction to Cuis-Smalltalk, you should start with the '''The Cuis Book''' and '''Learning-Cuis''' more about this on the [[CuisCoookBook-References\|References]]. This is intended to be a <u>resource for programmers</u>, in the sense that it answers questions that will naturally come up to programmers while exploring Smalltalk.

	'''Reliability'''. I am writing these notes while learning Cuis. Some of what I write may not be the best way to solve the problem, it may not even be correct. Be patient, double check! Since I use these recipes myself I am going to improve them in time.		'''Reliability'''. I am writing these notes while learning Cuis. Some of what I write may not be the best way to solve the problem, it may not even be correct. Be patient, double check. Since I use these recipes myself I am going to improve them in time.

	'''Sorting principles'''. Topic order is intended to go from easy to difficult. From frequently necessary to rarely used. From needed at the beginning of the programming experience to needed by black belts. These three forces, as the 3 laws of robotics, regulate what chapter goes toward the top of the document. They hold also for sub-chapters and articles.		'''Sorting principles'''. Topic order is intended to go from easy to difficult. From frequently necessary to rarely used. From needed at the beginning of the programming experience to needed by black belts. These three forces, as the 3 laws of robotics, regulate what chapter goes toward the top of the document. They hold also for sub-chapters and articles.

Nmingott: /* Applications built on Cuis */

2025-05-12T21:27:11Z

Applications built on Cuis

← Older revision		Revision as of 21:27, 12 May 2025
Line 255:		Line 255:
	= Applications built on Cuis =		= Applications built on Cuis =

	* DrGeo		* DrGeo.
			* Borghi DataStreamer.

	== TODO ==		== TODO ==

Nmingott at 21:25, 12 May 2025

2025-05-12T21:25:37Z

← Older revision		Revision as of 21:25, 12 May 2025
Line 168:		Line 168:
	* ... these and thousands of other things are possible once you are able to leverage the power of Unix from Cuis.		* ... these and thousands of other things are possible once you are able to leverage the power of Unix from Cuis.

	You can perform these kind of operations with the module <code>OSProcess</code> included in Cuis or with the external package <code>CommandShell</code>. The second is easier, the first is lower level.		You can perform these kind of operations with the module <code>OSProcess</code> included in Cuis or with the external package <code>CommandShell</code>. The second is easier, the first is lower level => more difficult but more flexible.

	* [[Traps and pitfalls specific to running external programs]]		* [[Traps and pitfalls specific to running external programs]]

Nmingott: /* The Sound system */

2025-05-12T21:23:36Z

The Sound system

← Older revision		Revision as of 21:23, 12 May 2025
Line 226:		Line 226:
	= The Sound system =		= The Sound system =
	To some people doing programming is manipulating sounds. As for some other people it is building a nice graphical user interface or some one else does networks services. For this reason the sound system chapter is placed after Morphic.		To some people doing programming is manipulating sounds. As for some other people it is building a nice graphical user interface or some one else does networks services. For this reason the sound system chapter is placed after Morphic.


			All this chapter requires you to load the sound module. <syntaxhighlight lang="smalltalk">
			Feature require: 'Sound'.
			</syntaxhighlight>
	* [[First experiments with sound]] . Collecting knowledge here, when ready will be split into topics		* [[First experiments with sound]] . Collecting knowledge here, when ready will be split into topics
	* [[Play a melody writing a list of note names and their duration]] . Ok for note in the format C,D,E... TODO for notes with Italian names: Do, Re, Mi...		* [[Play a melody writing a list of note names and their duration]] . Ok for note in the format C,D,E... TODO for notes with Italian names: Do, Re, Mi...

Nmingott: /* The Sound system */

2025-05-12T21:13:47Z

The Sound system

← Older revision		Revision as of 21:13, 12 May 2025
Line 226:		Line 226:
	= The Sound system =		= The Sound system =
	To some people doing programming is manipulating sounds. As for some other people it is building a nice graphical user interface or some one else does networks services. For this reason the sound system chapter is placed after Morphic.		To some people doing programming is manipulating sounds. As for some other people it is building a nice graphical user interface or some one else does networks services. For this reason the sound system chapter is placed after Morphic.

	* [[First experiments with sound]] . Collecting knowledge here, when ready will be split into topics		* [[First experiments with sound]] . Collecting knowledge here, when ready will be split into topics
			* [[Play a melody writing a list of note names and their duration]] . Ok for note in the format C,D,E... TODO for notes with Italian names: Do, Re, Mi...
			* TODO. Realtime sound playing. On event play immediately a sound, simulate and instrument typing on your computer keyboard
			* [[Create and play *.wav files]].
			* [[References to the Sound system]] . for further study

	= Introspection and The compiler =		= Introspection and The compiler =

← Older revision		Revision as of 14:00, 3 June 2025
Line 1:		Line 1:

	A programming language cookbook is something like ''[https://stackoverflow.com/ StackOverflow]'', without the digging part and the try&pray experience. For a gentle and structured introduction to Cuis-Smalltalk, you should start with the '''The Cuis Book''' and '''Learning-Cuis''' more about this ~~on the~~ [[CuisCoookBook-References\|References]]. This is intended to be a <u>resource for programmers</u>, in the sense that it answers questions that will naturally come up to programmers while exploring Smalltalk.		A programming language cookbook is something like ''[https://stackoverflow.com/ StackOverflow]'', without the digging part and the try&pray experience. For a gentle and structured introduction to Cuis-Smalltalk, you should start with the '''The Cuis Book''' and '''Learning-Cuis''' more about this in [[CuisCoookBook-References\|References]]. This is intended to be a <u>resource for programmers</u>, in the sense that it answers questions that will naturally come up to programmers while exploring Smalltalk.

	'''Reliability'''. I am writing these notes while learning Cuis. Some of what I write may not be the best way to solve the problem, it may not even be correct. Be patient, double check. Since I use these recipes myself I am going to improve them in time.		'''Reliability'''. I am writing these notes while learning Cuis. Some of what I write may not be the best way to solve the problem, it may not even be correct. Be patient, double check. Since I use these recipes myself I am going to improve them in time.

	'''Sorting principles'''. Topic order is intended to go from easy to difficult. From frequently necessary to rarely used. From needed at the beginning of the programming experience to needed by black belts. These three forces, as the 3 laws of robotics, regulate what chapter goes toward the top of the document. They hold also for sub-chapters and articles.		'''Sorting principles'''. Topic order is intended to go from easy to difficult. From frequently necessary to rarely used. From needed at the beginning of the programming experience to needed by black belts. These three forces, as with the 3 laws of robotics, regulate what chapter goes toward the top of the document. They hold also for sub-chapters and articles.

	'''Contributions'''. I am trying to figure out ways to make contributions possible and fruitful, see [[contributions motivated guidelines]]. As a write I see that ~~also important are~~ [[format guidelines]].		'''Contributions'''. I am trying to figure out ways to make contributions possible and fruitful, see [[contributions motivated guidelines]]. As a write I see that [[format guidelines\|format guidelines are also important]].

	'''Copyright'''. You have the right to read, print for your own use and contribute to the document. You can make external links to this document. You can not copy the document and make it available somewhere else on the Internet. You can't claim ownership. You can't bring the document to an editor and publish it. I, as the author of more than 99% of the words ~~here~~ displayed retain all rights as well as the right to change these rules.		'''Copyright'''. You have the right to read, print for your own use, and contribute to the document. You can make external links to this document. You can not copy the document and make it available somewhere else on the Internet. You can't claim ownership. You can't bring the document to an editor and publish it. I, as the author of more than 99% of the words displayed here, retain all rights as well as the right to change these rules.

	* [[Introduction]]. What you should expect from this book and the reason why I am writing it. STARTED.		* [[Introduction]]. What you should expect from this book and the reason why I am writing it. STARTED.
Line 18:		Line 18:

	* Install and run Cuis in Windows		* Install and run Cuis in Windows
	* Install and run Cuis in ~~the Mac~~		* Install and run Cuis in MacOS
	* [[Install and run Cuis in Linux]]		* [[Install and run Cuis in Linux]]
	* [[Run Cuis in the Web Browser. (SqueakJS)]]		* [[Run Cuis in the Web Browser. (SqueakJS)]]
	* [[Run Cuis in a ARM platform, RPi, BeagleBone and similar. (Linux)]]		* [[Run Cuis in a ARM platform, RPi, BeagleBone and similar. (Linux)\|Run Cuis in an ARM platform, RPi, BeagleBone and similar. (Linux)]]
	* Run Cuis in a remote server. (Linux)		* Run Cuis on a remote server. (Linux)
	* Run Cuis on the metal: without Operating System		* Run Cuis on the metal: without an Operating System
	* How to keep Cuis updated		* How to keep Cuis updated
	* [[How to load the most recent changes Juan made to Cuis-Smalltalk-Dev]]		* [[How to load the most recent changes Juan made to Cuis-Smalltalk-Dev]]
Line 36:		Line 36:

	== Things unique to Cuis and/or Smalltalk ==		== Things unique to Cuis and/or Smalltalk ==
	Here are all the things that are totally unknown for anybody who never programmed in any Smalltalk.		Here are all the things that are totally unknown for anybody who has never programmed in any Smalltalk.

	* [[How can I make X? Learn to fish in Smalltalk\|How can I make X ? Learn to fish in Smalltalk]]		* [[How can I make X? Learn to fish in Smalltalk\|How can I make X ? Learn to fish in Smalltalk]]
Line 47:		Line 47:
	* [[My project needs to add a method to somebody else Class, how do I do it?\|My project needs to add a method to somebody else Class, how do I do it ?]]		* [[My project needs to add a method to somebody else Class, how do I do it?\|My project needs to add a method to somebody else Class, how do I do it ?]]
	* [[How to use Class variables]]. STARTED		* [[How to use Class variables]]. STARTED
	* [[Learn how to use the Transcript]] . This is really important, ~~better~~ you take a peek.		* [[Learn how to use the Transcript]] . This is really important, you should take a peek.
	* [[Tips & tricks]] . Those little keyboard/mouse shortcuts or little code snippets that may improve your programmer life.		* [[Tips & tricks]] . Those little keyboard/mouse shortcuts or little code snippets that may improve your programmer life.
	* [[Traps and pitfalls for polyglot developers]] . If you know more programming languages this page is for you.		* [[Traps and pitfalls for polyglot developers]] . If you know more programming languages this page is for you.