View this PageEdit this PageUploads to this PageVersions of this PageHomeRecent ChangesSearchHelp Guide

notes-3-09

Proposed Outline:

  1. cover the board with a topic, skill, and squeak feature listing
  2. break into groups to hash out possible orders of coverage, models of what tutorial materials, examples, explorations, should be like.
  3. reconvene for group reports, discussion, and consensus
  4. break into small working groups with concrete assignments to begin an initial collection of lessons that should come right after the basic tutorials, with the hope of having a handful of first-pass materials created by next Wednesday.

Today is for the book people

Question from the physics people: what age group are we aiming at, because the math could be a bit complicated for younger people. Perhaps a change in focus is needed
Book, squeak in the classroom -Lenny will bring in
Look for high school physics lessons, to get an idea of what is age approriate
Premade scripts for complicated behaviours are alright for now (hiding infrastructure)
Keep asking yourself "What is the point?" "What will people learn that's they didn't know before about Squeak?"

A few places to look for resources

Book Coverage and Ideas
  • First pass of where tools exist
  • Mechanics of Squeak
  • Demos wanted
  • Topical coverage of ideas
  • places to go
Squeak How-To
  • skills
  • programming constructs
    • supplies
    • squeakplaces
  • Basic CS knowledge (not really the purpose)
  • points back to #1
A Squeaky Introduction to Programming
  • Chapters (probably reorded, reorganized)
Pedagogy Place
  • conversations
  • what is a good order
  • what types of projects
  • general learning issues

Book Computer Science Logo Style - Teaches programming at HS level
Book The most complex machines - incomplete breadth course on cs

Level 2 standards - CS Background and concepts ideas other sciences and mathes as vehicles of expression
Resources/attributes that all lessons should try to have
  • Link to stndards
  • printable guide
  • animation
  • explanation/text to intro
  • exploration w/anim before write script
  • offline actvity
  • assessment tools
  • skill level? (length, difficulty, building upon other projects)
  • if game
    • type of squeak things in it
    • what squeak tools does it use?
  • MJ: show need and motivation for each construct
  • Consistent and coherent style and organization Navigation through 1) whole book 2) project/unit/module/lesson
  • KH: See a finished project in layers

Help bubbles for comments, Open script editor, click on objectbox go to "edit ballon help for this script"

Break out to make concept maps
Figure out what is core CS vs peripheral vs other "look and feel"
classify eveything not just squeak stuff- how to program knowledge