Difference between revisions of "User:Jwmh/Class Drafts"

From FreekiWiki
Jump to navigation Jump to search
 
(21 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
=Link to Modules=
 +
 
==Class Proposal: "Living in a Technology World"==
 
==Class Proposal: "Living in a Technology World"==
−
This is a [[Class_Drafts|draft proposal for the class]], "Living in a Technology World"
+
This is a draft proposal for the class, "Living in a Technology World"<br/>
 
(title suggested by Darren - [[User:Dheiber]]).
 
(title suggested by Darren - [[User:Dheiber]]).
  
 
The idea for this class came from me, Joseph Herbert ([[User:Jwmh]]).
 
The idea for this class came from me, Joseph Herbert ([[User:Jwmh]]).
  
−
The basic premises are as follows:
+
The basic premises are as follows:<br/>
 
- What separates a "computer person" from a "non-computer person"?  (note: these are usually self-identified)
 
- What separates a "computer person" from a "non-computer person"?  (note: these are usually self-identified)
  
 
[[Category: Classes]]
 
[[Category: Classes]]
 
[[Category: Education]]
 
[[Category: Education]]
 +
 +
==Overview (draft)==
 +
As I continue to reflect, it occurs to me that this can(should?) be split into three (3) sections, another way:
 +
* i. Hardware
 +
* ii. Software Concepts (Non-UI)
 +
* iii. Software Visualization & Interaction (UI)
 +
 +
 +
Number 2 would include things like the filesystem: Files, Folders, and Applications; etc.<br/>
 +
Number 3 would be how you go about interacting with it.
 +
 +
But, eh... how to describe certain concepts without showing what they look like?<br/>
 +
And really, wouldn't the Login window (visual UI) come before other concepts...???
 +
 +
Or maybe it does make sense to teach concepts first, then show what they look like??<br/>
 +
If so, then... is it worthwhile to halt visual learning, to go back to discuss abstract concepts about files/folders, and *then* show what they look like?  (I really think the concept of this should be demonstrated with books, first....)
 +
 +
 +
==Volume I: Familiarization with the interface==
 +
===[or, "Getting to know the basics"]===
 +
This should entail only the *bare necessities* for operating a computer:
 +
* physical care (e.g. heat=bad, liquid=bad, grounded surge protector = good, ...)
 +
* poweron / login / poweroff
 +
* using the keyboard and mouse
 +
* understanding the folders, files, and applications
 +
 +
Note that this doesn't cover the use of any specific applications (such as a web browser or a word processor), but rather familiarization w/ the interface as a whole.
 +
 +
** NB: currently this below content seems only applicable to the WIMP / Desktop model.  Is this appropriate? (initial instinct is to respond, "yes, and necessary, at least in present-day").
 +
However, how do we expand / generalize for smartphones?
 +
... The usual case for teaching abstractions is, Start with specific cases, then the rest (generalized) can follow.
 +
So may not be possible to teach 'only' the abstract (which we knew as soon as we started talking about UI conventions:windows/menus/etc, didn't we?).
 +
 +
 +
====Hardware====
 +
<ol>
 +
<li>Module: [[/Module:electric|power/electric/heat (howto turn on; do's/don'ts)]]</li>
 +
<li>Module: [[/Module:needed_peripherals|hooking up a computer]]</li>
 +
<li>[[/Module:hardware interface|Module: hardware interface (mouse and keyboard)]]
 +
*get Mac keyboard/mouse also</li>
 +
</ol>
 +
 +
 +
====Software (UI)====
 +
<ol>
 +
<li>[[/Module:UI_login_screen|Module: (UI) Login screen]]</li>
 +
 +
<li>[/Module:UI_desktop|Module: UI desktop (environment - default at login)]</li>
 +
 +
<!-- <li>Module 6: panels, menus, pointer, icons, and "windows"
 +
** "windows" aren't really like a window -- they're more like a table -- or better yet, they're like a book....</li>
 +
-->
 +
 +
<li>
 +
[[/Module:Filesystem|Module: Filesystem ("filing system")]]
 +
</li>
 +
 +
<li>
 +
[[/UI Conventions|UI Conventions: cursor, dialogbox, and Window conventions]]
 +
</li>
 +
 +
</ol>
 +
 +
==Volume II - Beyond the Basics: Knowing How to Explore==
 +
(even if you don't know what you're looking for)
 +
 +
<ol>
 +
<li>
 +
[[/Module: Risktaking, Exploring, Changing|Module: Risktaking, Exploring, Changing]]
 +
</li>
 +
</ol>
 +
 +
==Volume III - How to deal with unexpected behavior==
 +
[or, Section 4: solving problems; basic 'troubleshooting']<br/>
 +
(assuming something is not actually 'broken' as req's fixing by a technician..(?)
 +
 +
 +
 +
=====(temporary) notes:=====
 +
This is actually being covered by a new class someone else started:<br/>
 +
http://www.google.com/calendar/event?eid=Z3FoazMyNmJpMHZxMWJtMTc5aTkzMTgwNGsgcDNjYmdwcjAzb2ZxMmxuZ2Zma24zMzN1MjBAZw&ctz=America/Los_Angeles<br/>
 +
======.**** NEGATIVE, that class covers advanced Linux-specific troubleshooting (mostly, w/ some generalities)======
 +
-- need to get PDF, slideshow that's used in his class...<br/>
 +
.* Taught by Ben of Ubuntu Oregon<br/>
 +
 +
 +
Full list of classes here: http://wiki.freegeek.org/images/c/c1/Current_Classes_Trifold.pdf
 +
 +
and also here: http://www.freegeek.org/about/classes/
 +
 +
==(editor shortcut; stays at bottom)==

Latest revision as of 14:28, 27 February 2013

Link to Modules

Class Proposal: "Living in a Technology World"

This is a draft proposal for the class, "Living in a Technology World"
(title suggested by Darren - User:Dheiber).

The idea for this class came from me, Joseph Herbert (User:Jwmh).

The basic premises are as follows:
- What separates a "computer person" from a "non-computer person"? (note: these are usually self-identified)

Overview (draft)

As I continue to reflect, it occurs to me that this can(should?) be split into three (3) sections, another way:

  • i. Hardware
  • ii. Software Concepts (Non-UI)
  • iii. Software Visualization & Interaction (UI)


Number 2 would include things like the filesystem: Files, Folders, and Applications; etc.
Number 3 would be how you go about interacting with it.

But, eh... how to describe certain concepts without showing what they look like?
And really, wouldn't the Login window (visual UI) come before other concepts...???

Or maybe it does make sense to teach concepts first, then show what they look like??
If so, then... is it worthwhile to halt visual learning, to go back to discuss abstract concepts about files/folders, and *then* show what they look like? (I really think the concept of this should be demonstrated with books, first....)


Volume I: Familiarization with the interface

[or, "Getting to know the basics"]

This should entail only the *bare necessities* for operating a computer:

  • physical care (e.g. heat=bad, liquid=bad, grounded surge protector = good, ...)
  • poweron / login / poweroff
  • using the keyboard and mouse
  • understanding the folders, files, and applications

Note that this doesn't cover the use of any specific applications (such as a web browser or a word processor), but rather familiarization w/ the interface as a whole.

    • NB: currently this below content seems only applicable to the WIMP / Desktop model. Is this appropriate? (initial instinct is to respond, "yes, and necessary, at least in present-day").

However, how do we expand / generalize for smartphones? ... The usual case for teaching abstractions is, Start with specific cases, then the rest (generalized) can follow. So may not be possible to teach 'only' the abstract (which we knew as soon as we started talking about UI conventions:windows/menus/etc, didn't we?).


Hardware

  1. Module: power/electric/heat (howto turn on; do's/don'ts)
  2. Module: hooking up a computer
  3. Module: hardware interface (mouse and keyboard)
    • get Mac keyboard/mouse also


Software (UI)

  1. Module: (UI) Login screen
  2. [/Module:UI_desktop|Module: UI desktop (environment - default at login)]
  3. Module: Filesystem ("filing system")
  4. UI Conventions: cursor, dialogbox, and Window conventions

Volume II - Beyond the Basics: Knowing How to Explore

(even if you don't know what you're looking for)

  1. Module: Risktaking, Exploring, Changing

Volume III - How to deal with unexpected behavior

[or, Section 4: solving problems; basic 'troubleshooting']
(assuming something is not actually 'broken' as req's fixing by a technician..(?)


(temporary) notes:

This is actually being covered by a new class someone else started:
http://www.google.com/calendar/event?eid=Z3FoazMyNmJpMHZxMWJtMTc5aTkzMTgwNGsgcDNjYmdwcjAzb2ZxMmxuZ2Zma24zMzN1MjBAZw&ctz=America/Los_Angeles

.**** NEGATIVE, that class covers advanced Linux-specific troubleshooting (mostly, w/ some generalities)

-- need to get PDF, slideshow that's used in his class...
.* Taught by Ben of Ubuntu Oregon


Full list of classes here: http://wiki.freegeek.org/images/c/c1/Current_Classes_Trifold.pdf

and also here: http://www.freegeek.org/about/classes/

(editor shortcut; stays at bottom)

Retrieved from "http://wiki.freegeek.org/index.php?title=User:Jwmh/Class_Drafts&oldid=66384"