Re: Tutorial, how to improve it? (was Vision for Aida)
Posted by
bobcalco on
Feb 10, 2012; 7:00pm
URL: https://forum.world.st/Vision-for-Aida-tp4376327p4377237.html
Hi Janko,
As I have a lot of opinions about this, I'll volunteer to work on it with you. :)
1. It should implement a non-trivial data model. At least one each of a many-to-many, one-to-many, and one-to-one relationship in the domain.
2. It should be iterative, where we start with a 'traditional' site, layer in unobtrusive JavaScript, and then get fancy with Ajax, WebSocket, etc. On the domain model side, it should first implement in-image persistence, then move onto GLORP and then GemStone as alternate back-ends when you need to run more than one image, possibly on different machines. It *must* cover deployment well. I personally can't stand when that very difficult part of correctly using a framework is 'left as an exercise for the reader'... ;)
3. It should explain the core internals and cover styling in detail. Assume you're talking to experienced engineers coming from a Rails, Symfony, Django, or Grails background. Do not assume they're seasoned Smalltalkers.
4. It should touch on things that are unique to Aida... hosting multiple sites... the way apps get layered onto sites to create systems... being able to run scheduled one-off or periodic processes in the background... really show Aida's breadth while going deep only into domain models, UI, and deployment issues.
5. It must be follow-along-as-you-go, leaving nothing really assumed and easy for someone to bookmark where they are, close their image for the night, and pick up first thing in the afternoon when they wake up... ;)
- Bob
2012/2/10 Janko Mivšek
<[hidden email]>
S, Robert Calco piše:
> I think Aida needs a much better, much more in-depth tutorial, that
> really highlights its best parts, and suggests where it's going to get
> better over time.
Ok, let we start improving documentation by improving a tutorial. So far
we have two articles:
1. Tutorial for a "traditional" Aida [1]
2. ToDo example in-depth description [2]
Tutorial has now at the bottom a link to the ToDo description.
Tutorial is probably not attractive enough for a first impression,
because it shows so called traditional web application in a sense that
there we have classical web pages and navigation between them
(graph-like control flow) but not more recent ajaxified style of
'single-page' web app development, which is shown in the ToDo example.
One solution would be to introduce another tutorial for a simple
ajaxified web app, with widgets, realtime form validation etc. then
continue with current one to shows the traditional Aida as well. and
then ToDo example description.
Any ideas, how to proceed?
Janko
[1] http://www.aidaweb.si/tutorial.html
[2] http://www.aidaweb.si/todo-description
--
Janko Mivšek
Aida/Web
Smalltalk Web Application Server
http://www.aidaweb.si
_______________________________________________
Aida mailing list
[hidden email]
http://lists.aidaweb.si/mailman/listinfo/aida
_______________________________________________
Aida mailing list
[hidden email]
http://lists.aidaweb.si/mailman/listinfo/aida