<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p><font size="+1">Hi, <br>
</font></p>
<p><font size="+1">Cuis is documented with bits found there and
there, it is not easy for new comers. Several time, after
searching on Cuis or asking on the list, I felt like a want to
write a small documentation notes on a recent finding so it can
be useful for other. So far I didn't and it is a waste, pretty
sure the same occurred to you as well.<br>
</font></p>
<p><font size="+1">We already have <a class="moz-txt-link-freetext"
href="https://github.com/Cuis-Smalltalk/Learning-Cuis"
moz-do-not-send="true">https://github.com/Cuis-Smalltalk/Learning-Cuis</a>
and also <a class="moz-txt-link-freetext"
href="https://github.com/Cuis-Smalltalk/CodeExamples"
moz-do-not-send="true">https://github.com/Cuis-Smalltalk/CodeExamples</a>
with valuable contents! If I miss any, please tell.<br>
</font></p>
<p><font size="+1">What about more structured documentation, like a
book, (with content related to LeaningCuis and CodeExample). We
could each other insert our knowledge in documentation notes
into it. I think I could spend 30 min/day on such a project. <br>
</font></p>
<p><font size="+1">IMHO, on-line editing with capability to output
printed book, may be several ones, for Lulu will be a nice
achievement by the community. It will give more visibility to
Cuis too.</font><br>
<font size="+1"><font size="+1">Of course inserting documentation
notes does not make a book but it gives valuable <b>incentive</b><b>s</b>
and <b>directions</b> to expend in valuable documentation.</font></font></p>
<p><font size="+1">Bellow my suggestions for a table of contents.
We could insert into documentations note and expand it later as
documentation paragraphs (we can capitalize on the Squeak/Pharo
by Examples too, for some Smalltalk generic contents). <br>
</font></p>
<p><font size="+1"><font size="+1">Any opinion? Suggestion for the
table of contents? At which place could we do the effort?
Which tools to use?<br>
</font></font></p>
<p><font size="+1"><font size="+1">Hilaire<br>
</font></font></p>
<hr width="100%" size="2"><b>A. Basic Cuis-Smalltalk</b><br>
<blockquote><u>Getting started </u><br>
</blockquote>
<blockquote>
<blockquote> Installing Cuis-Smalltalk<br>
Starting Cuis-Smalltalk<br>
Configuring Cuis-Smalltalk environment<br>
Writing your first script<br>
Introduction to the system class<br>
</blockquote>
<u>Writing your first application</u><br>
An excuse for a tour in Cuis world (Browser, Inspector)<br>
</blockquote>
<blockquote><u>Understanding the basic Cuis' model</u><br>
<blockquote>Syntax<br>
<b>Statements as blocks and messages send</b><br>
Basic classes<br>
Collections<br>
</blockquote>
<u>Writing your second application<br>
</u>
<blockquote>A second excuse for a tour in Cuis World (Debugger,
Changset)<br>
</blockquote>
<u>Cuising with Style (aka best practices)</u><br>
<blockquote>Variable/Comments/Method/Scope/Refactoring...<br>
Common design patterns<br>
...<br>
</blockquote>
</blockquote>
<b>B. Advanced Cuis-Smalltalk</b>
<blockquote><u>Cuis-Smalltalk code management<br>
<br>
Going visual</u>
<blockquote>The Morph system<br>
Composing widget with layout<br>
Graphic vectors engine<br>
</blockquote>
<u>The object model</u><br>
<br>
<u>Testing your code</u><br>
<br>
<u>Streams</u><br>
<br>
<u>Reflection</u><br>
<br>
.../...<br>
</blockquote>
<p><font size="+1"><br>
</font></p>
<pre class="moz-signature" cols="72">--
GNU Dr. Geo
<a class="moz-txt-link-freetext" href="http://drgeo.eu" moz-do-not-send="true">http://drgeo.eu</a>
<a class="moz-txt-link-freetext" href="https://pouet.chapril.org/@hilaire" moz-do-not-send="true">https://pouet.chapril.org/@hilaire</a></pre>
</body>
</html>