Background: #fff
Foreground: #000
PrimaryPale: #8cf
PrimaryLight: #18f
PrimaryMid: #04b
PrimaryDark: #014
SecondaryPale: #ffc
SecondaryLight: #fe8
SecondaryMid: #db4
SecondaryDark: #841
TertiaryPale: #eee
TertiaryLight: #ccc
TertiaryMid: #999
TertiaryDark: #666
Error: #f88
<div class='toolbar' macro='toolbar [[ToolbarCommands::EditToolbar]]'></div>
<div class='title' macro='view title'></div>
<div class='editor' macro='edit title'></div>
<div macro='annotations'></div>
<div class='editor' macro='edit text'></div>
<div class='editor' macro='edit tags'></div><div class='editorFooter'><span macro='message views.editor.tagPrompt'></span><span macro='tagChooser excludeLists'></span></div>
To get started with this blank [[TiddlyWiki]], you'll need to modify the following tiddlers:
* [[SiteTitle]] & [[SiteSubtitle]]: The title and subtitle of the site, as shown above (after saving, they will also appear in the browser title bar)
* [[MainMenu]]: The menu (usually on the left)
* [[DefaultTiddlers]]: Contains the names of the tiddlers that you want to appear when the TiddlyWiki is opened
You'll also need to enter your username for signing your edits: <<option txtUserName>>
<link rel='alternate' type='application/rss+xml' title='RSS' href='index.xml' />
These [[InterfaceOptions]] for customising [[TiddlyWiki]] are saved in your browser

Your username for signing your edits. Write it as a [[WikiWord]] (eg [[JoeBloggs]])

<<option txtUserName>>
<<option chkSaveBackups>> [[SaveBackups]]
<<option chkAutoSave>> [[AutoSave]]
<<option chkRegExpSearch>> [[RegExpSearch]]
<<option chkCaseSensitiveSearch>> [[CaseSensitiveSearch]]
<<option chkAnimate>> [[EnableAnimations]]

Also see [[AdvancedOptions]]
<div class='header' macro='gradient vert [[ColorPalette::PrimaryLight]] [[ColorPalette::PrimaryMid]]'>
<div class='headerShadow'>
<span class='siteTitle' refresh='content' tiddler='SiteTitle'></span>&nbsp;
<span class='siteSubtitle' refresh='content' tiddler='SiteSubtitle'></span>
<div class='headerForeground'>
<span class='siteTitle' refresh='content' tiddler='SiteTitle'></span>&nbsp;
<span class='siteSubtitle' refresh='content' tiddler='SiteSubtitle'></span>
<div id='mainMenu' refresh='content' tiddler='MainMenu'></div>
<div id='sidebar'>
<div id='sidebarOptions' refresh='content' tiddler='SideBarOptions'></div>
<div id='sidebarTabs' refresh='content' force='true' tiddler='SideBarTabs'></div>
<div id='displayArea'>
<div id='messageArea'></div>
<div id='tiddlerDisplay'></div>
body {background:[[ColorPalette::Background]]; color:[[ColorPalette::Foreground]];}

a {color:[[ColorPalette::PrimaryMid]];}
a:hover {background-color:[[ColorPalette::PrimaryMid]]; color:[[ColorPalette::Background]];}
a img {border:0;}

h1,h2,h3,h4,h5,h6 {color:[[ColorPalette::SecondaryDark]]; background:transparent;}
h1 {border-bottom:2px solid [[ColorPalette::TertiaryLight]];}
h2,h3 {border-bottom:1px solid [[ColorPalette::TertiaryLight]];}

.button {color:[[ColorPalette::PrimaryDark]]; border:1px solid [[ColorPalette::Background]];}
.button:hover {color:[[ColorPalette::PrimaryDark]]; background:[[ColorPalette::SecondaryLight]]; border-color:[[ColorPalette::SecondaryMid]];}
.button:active {color:[[ColorPalette::Background]]; background:[[ColorPalette::SecondaryMid]]; border:1px solid [[ColorPalette::SecondaryDark]];}

.header {background:[[ColorPalette::PrimaryMid]];}
.headerShadow {color:[[ColorPalette::Foreground]];}
.headerShadow a {font-weight:normal; color:[[ColorPalette::Foreground]];}
.headerForeground {color:[[ColorPalette::Background]];}
.headerForeground a {font-weight:normal; color:[[ColorPalette::PrimaryPale]];}

.tabSelected {color:[[ColorPalette::PrimaryDark]];
	border-left:1px solid [[ColorPalette::TertiaryLight]];
	border-top:1px solid [[ColorPalette::TertiaryLight]];
	border-right:1px solid [[ColorPalette::TertiaryLight]];
.tabUnselected {color:[[ColorPalette::Background]]; background:[[ColorPalette::TertiaryMid]];}
.tabContents {color:[[ColorPalette::PrimaryDark]]; background:[[ColorPalette::TertiaryPale]]; border:1px solid [[ColorPalette::TertiaryLight]];}
.tabContents .button {border:0;}

#sidebar {}
#sidebarOptions input {border:1px solid [[ColorPalette::PrimaryMid]];}
#sidebarOptions .sliderPanel {background:[[ColorPalette::PrimaryPale]];}
#sidebarOptions .sliderPanel a {border:none;color:[[ColorPalette::PrimaryMid]];}
#sidebarOptions .sliderPanel a:hover {color:[[ColorPalette::Background]]; background:[[ColorPalette::PrimaryMid]];}
#sidebarOptions .sliderPanel a:active {color:[[ColorPalette::PrimaryMid]]; background:[[ColorPalette::Background]];}

.wizard {background:[[ColorPalette::PrimaryPale]]; border:1px solid [[ColorPalette::PrimaryMid]];}
.wizard h1 {color:[[ColorPalette::PrimaryDark]]; border:none;}
.wizard h2 {color:[[ColorPalette::Foreground]]; border:none;}
.wizardStep {background:[[ColorPalette::Background]]; color:[[ColorPalette::Foreground]];
	border:1px solid [[ColorPalette::PrimaryMid]];}
.wizardStep.wizardStepDone {background:[[ColorPalette::TertiaryLight]];}
.wizardFooter {background:[[ColorPalette::PrimaryPale]];}
.wizardFooter .status {background:[[ColorPalette::PrimaryDark]]; color:[[ColorPalette::Background]];}
.wizard .button {color:[[ColorPalette::Foreground]]; background:[[ColorPalette::SecondaryLight]]; border: 1px solid;
	border-color:[[ColorPalette::SecondaryPale]] [[ColorPalette::SecondaryDark]] [[ColorPalette::SecondaryDark]] [[ColorPalette::SecondaryPale]];}
.wizard .button:hover {color:[[ColorPalette::Foreground]]; background:[[ColorPalette::Background]];}
.wizard .button:active {color:[[ColorPalette::Background]]; background:[[ColorPalette::Foreground]]; border: 1px solid;
	border-color:[[ColorPalette::PrimaryDark]] [[ColorPalette::PrimaryPale]] [[ColorPalette::PrimaryPale]] [[ColorPalette::PrimaryDark]];}

.wizard .notChanged {background:transparent;}
.wizard .changedLocally {background:#80ff80;}
.wizard .changedServer {background:#8080ff;}
.wizard .changedBoth {background:#ff8080;}
.wizard .notFound {background:#ffff80;}
.wizard .putToServer {background:#ff80ff;}
.wizard .gotFromServer {background:#80ffff;}

#messageArea {border:1px solid [[ColorPalette::SecondaryMid]]; background:[[ColorPalette::SecondaryLight]]; color:[[ColorPalette::Foreground]];}
#messageArea .button {color:[[ColorPalette::PrimaryMid]]; background:[[ColorPalette::SecondaryPale]]; border:none;}

.popupTiddler {background:[[ColorPalette::TertiaryPale]]; border:2px solid [[ColorPalette::TertiaryMid]];}

.popup {background:[[ColorPalette::TertiaryPale]]; color:[[ColorPalette::TertiaryDark]]; border-left:1px solid [[ColorPalette::TertiaryMid]]; border-top:1px solid [[ColorPalette::TertiaryMid]]; border-right:2px solid [[ColorPalette::TertiaryDark]]; border-bottom:2px solid [[ColorPalette::TertiaryDark]];}
.popup hr {color:[[ColorPalette::PrimaryDark]]; background:[[ColorPalette::PrimaryDark]]; border-bottom:1px;}
.popup li.disabled {color:[[ColorPalette::TertiaryMid]];}
.popup li a, .popup li a:visited {color:[[ColorPalette::Foreground]]; border: none;}
.popup li a:hover {background:[[ColorPalette::SecondaryLight]]; color:[[ColorPalette::Foreground]]; border: none;}
.popup li a:active {background:[[ColorPalette::SecondaryPale]]; color:[[ColorPalette::Foreground]]; border: none;}
.popupHighlight {background:[[ColorPalette::Background]]; color:[[ColorPalette::Foreground]];}
.listBreak div {border-bottom:1px solid [[ColorPalette::TertiaryDark]];}

.tiddler .defaultCommand {font-weight:bold;}

.shadow .title {color:[[ColorPalette::TertiaryDark]];}

.title {color:[[ColorPalette::SecondaryDark]];}
.subtitle {color:[[ColorPalette::TertiaryDark]];}

.toolbar {color:[[ColorPalette::PrimaryMid]];}
.toolbar a {color:[[ColorPalette::TertiaryLight]];}
.selected .toolbar a {color:[[ColorPalette::TertiaryMid]];}
.selected .toolbar a:hover {color:[[ColorPalette::Foreground]];}

.tagging, .tagged {border:1px solid [[ColorPalette::TertiaryPale]]; background-color:[[ColorPalette::TertiaryPale]];}
.selected .tagging, .selected .tagged {background-color:[[ColorPalette::TertiaryLight]]; border:1px solid [[ColorPalette::TertiaryMid]];}
.tagging .listTitle, .tagged .listTitle {color:[[ColorPalette::PrimaryDark]];}
.tagging .button, .tagged .button {border:none;}

.footer {color:[[ColorPalette::TertiaryLight]];}
.selected .footer {color:[[ColorPalette::TertiaryMid]];}

.error, .errorButton {color:[[ColorPalette::Foreground]]; background:[[ColorPalette::Error]];}
.warning {color:[[ColorPalette::Foreground]]; background:[[ColorPalette::SecondaryPale]];}
.lowlight {background:[[ColorPalette::TertiaryLight]];}

.zoomer {background:none; color:[[ColorPalette::TertiaryMid]]; border:3px solid [[ColorPalette::TertiaryMid]];}

.imageLink, #displayArea .imageLink {background:transparent;}

.annotation {background:[[ColorPalette::SecondaryLight]]; color:[[ColorPalette::Foreground]]; border:2px solid [[ColorPalette::SecondaryMid]];}

.viewer .listTitle {list-style-type:none; margin-left:-2em;}
.viewer .button {border:1px solid [[ColorPalette::SecondaryMid]];}
.viewer blockquote {border-left:3px solid [[ColorPalette::TertiaryDark]];}

.viewer table, table.twtable {border:2px solid [[ColorPalette::TertiaryDark]];}
.viewer th, .viewer thead td, .twtable th, .twtable thead td {background:[[ColorPalette::SecondaryMid]]; border:1px solid [[ColorPalette::TertiaryDark]]; color:[[ColorPalette::Background]];}
.viewer td, .viewer tr, .twtable td, .twtable tr {border:1px solid [[ColorPalette::TertiaryDark]];}

.viewer pre {border:1px solid [[ColorPalette::SecondaryLight]]; background:[[ColorPalette::SecondaryPale]];}
.viewer code {color:[[ColorPalette::SecondaryDark]];}
.viewer hr {border:0; border-top:dashed 1px [[ColorPalette::TertiaryDark]]; color:[[ColorPalette::TertiaryDark]];}

.highlight, .marked {background:[[ColorPalette::SecondaryLight]];}

.editor input {border:1px solid [[ColorPalette::PrimaryMid]];}
.editor textarea {border:1px solid [[ColorPalette::PrimaryMid]]; width:100%;}
.editorFooter {color:[[ColorPalette::TertiaryMid]];}
.readOnly {background:[[ColorPalette::TertiaryPale]];}

#backstageArea {background:[[ColorPalette::Foreground]]; color:[[ColorPalette::TertiaryMid]];}
#backstageArea a {background:[[ColorPalette::Foreground]]; color:[[ColorPalette::Background]]; border:none;}
#backstageArea a:hover {background:[[ColorPalette::SecondaryLight]]; color:[[ColorPalette::Foreground]]; }
#backstageArea a.backstageSelTab {background:[[ColorPalette::Background]]; color:[[ColorPalette::Foreground]];}
#backstageButton a {background:none; color:[[ColorPalette::Background]]; border:none;}
#backstageButton a:hover {background:[[ColorPalette::Foreground]]; color:[[ColorPalette::Background]]; border:none;}
#backstagePanel {background:[[ColorPalette::Background]]; border-color: [[ColorPalette::Background]] [[ColorPalette::TertiaryDark]] [[ColorPalette::TertiaryDark]] [[ColorPalette::TertiaryDark]];}
.backstagePanelFooter .button {border:none; color:[[ColorPalette::Background]];}
.backstagePanelFooter .button:hover {color:[[ColorPalette::Foreground]];}
#backstageCloak {background:[[ColorPalette::Foreground]]; opacity:0.6; filter:alpha(opacity=60);}
* html .tiddler {height:1%;}

body {font-size:.75em; font-family:arial,helvetica; margin:0; padding:0;}

h1,h2,h3,h4,h5,h6 {font-weight:bold; text-decoration:none;}
h1,h2,h3 {padding-bottom:1px; margin-top:1.2em;margin-bottom:0.3em;}
h4,h5,h6 {margin-top:1em;}
h1 {font-size:1.35em;}
h2 {font-size:1.25em;}
h3 {font-size:1.1em;}
h4 {font-size:1em;}
h5 {font-size:.9em;}

hr {height:1px;}

a {text-decoration:none;}

dt {font-weight:bold;}

ol {list-style-type:decimal;}
ol ol {list-style-type:lower-alpha;}
ol ol ol {list-style-type:lower-roman;}
ol ol ol ol {list-style-type:decimal;}
ol ol ol ol ol {list-style-type:lower-alpha;}
ol ol ol ol ol ol {list-style-type:lower-roman;}
ol ol ol ol ol ol ol {list-style-type:decimal;}

.txtOptionInput {width:11em;}

#contentWrapper .chkOptionInput {border:0;}

.externalLink {text-decoration:underline;}

.indent {margin-left:3em;}
.outdent {margin-left:3em; text-indent:-3em;}
code.escaped {white-space:nowrap;}

.tiddlyLinkExisting {font-weight:bold;}
.tiddlyLinkNonExisting {font-style:italic;}

/* the 'a' is required for IE, otherwise it renders the whole tiddler in bold */
a.tiddlyLinkNonExisting.shadow {font-weight:bold;}

#mainMenu .tiddlyLinkExisting,
	#mainMenu .tiddlyLinkNonExisting,
	#sidebarTabs .tiddlyLinkNonExisting {font-weight:normal; font-style:normal;}
#sidebarTabs .tiddlyLinkExisting {font-weight:bold; font-style:normal;}

.header {position:relative;}
.header a:hover {background:transparent;}
.headerShadow {position:relative; padding:4.5em 0 1em 1em; left:-1px; top:-1px;}
.headerForeground {position:absolute; padding:4.5em 0 1em 1em; left:0; top:0;}

.siteTitle {font-size:3em;}
.siteSubtitle {font-size:1.2em;}

#mainMenu {position:absolute; left:0; width:10em; text-align:right; line-height:1.6em; padding:1.5em 0.5em 0.5em 0.5em; font-size:1.1em;}

#sidebar {position:absolute; right:3px; width:16em; font-size:.9em;}
#sidebarOptions {padding-top:0.3em;}
#sidebarOptions a {margin:0 0.2em; padding:0.2em 0.3em; display:block;}
#sidebarOptions input {margin:0.4em 0.5em;}
#sidebarOptions .sliderPanel {margin-left:1em; padding:0.5em; font-size:.85em;}
#sidebarOptions .sliderPanel a {font-weight:bold; display:inline; padding:0;}
#sidebarOptions .sliderPanel input {margin:0 0 0.3em 0;}
#sidebarTabs .tabContents {width:15em; overflow:hidden;}

.wizard {padding:0.1em 1em 0 2em;}
.wizard h1 {font-size:2em; font-weight:bold; background:none; padding:0; margin:0.4em 0 0.2em;}
.wizard h2 {font-size:1.2em; font-weight:bold; background:none; padding:0; margin:0.4em 0 0.2em;}
.wizardStep {padding:1em 1em 1em 1em;}
.wizard .button {margin:0.5em 0 0; font-size:1.2em;}
.wizardFooter {padding:0.8em 0.4em 0.8em 0;}
.wizardFooter .status {padding:0 0.4em; margin-left:1em;}
.wizard .button {padding:0.1em 0.2em;}

#messageArea {position:fixed; top:2em; right:0; margin:0.5em; padding:0.5em; z-index:2000; _position:absolute;}
.messageToolbar {display:block; text-align:right; padding:0.2em;}
#messageArea a {text-decoration:underline;}

.tiddlerPopupButton {padding:0.2em;}
.popupTiddler {position: absolute; z-index:300; padding:1em; margin:0;}

.popup {position:absolute; z-index:300; font-size:.9em; padding:0; list-style:none; margin:0;}
.popup .popupMessage {padding:0.4em;}
.popup hr {display:block; height:1px; width:auto; padding:0; margin:0.2em 0;}
.popup li.disabled {padding:0.4em;}
.popup li a {display:block; padding:0.4em; font-weight:normal; cursor:pointer;}
.listBreak {font-size:1px; line-height:1px;}
.listBreak div {margin:2px 0;}

.tabset {padding:1em 0 0 0.5em;}
.tab {margin:0 0 0 0.25em; padding:2px;}
.tabContents {padding:0.5em;}
.tabContents ul, .tabContents ol {margin:0; padding:0;}
.txtMainTab .tabContents li {list-style:none;}
.tabContents li.listLink { margin-left:.75em;}

#contentWrapper {display:block;}
#splashScreen {display:none;}

#displayArea {margin:1em 17em 0 14em;}

.toolbar {text-align:right; font-size:.9em;}

.tiddler {padding:1em 1em 0;}

.missing .viewer,.missing .title {font-style:italic;}

.title {font-size:1.6em; font-weight:bold;}

.missing .subtitle {display:none;}
.subtitle {font-size:1.1em;}

.tiddler .button {padding:0.2em 0.4em;}

.tagging {margin:0.5em 0.5em 0.5em 0; float:left; display:none;}
.isTag .tagging {display:block;}
.tagged {margin:0.5em; float:right;}
.tagging, .tagged {font-size:0.9em; padding:0.25em;}
.tagging ul, .tagged ul {list-style:none; margin:0.25em; padding:0;}
.tagClear {clear:both;}

.footer {font-size:.9em;}
.footer li {display:inline;}

.annotation {padding:0.5em; margin:0.5em;}

* html .viewer pre {width:99%; padding:0 0 1em 0;}
.viewer {line-height:1.4em; padding-top:0.5em;}
.viewer .button {margin:0 0.25em; padding:0 0.25em;}
.viewer blockquote {line-height:1.5em; padding-left:0.8em;margin-left:2.5em;}
.viewer ul, .viewer ol {margin-left:0.5em; padding-left:1.5em;}

.viewer table, table.twtable {border-collapse:collapse; margin:0.8em 1.0em;}
.viewer th, .viewer td, .viewer tr,.viewer caption,.twtable th, .twtable td, .twtable tr,.twtable caption {padding:3px;}
table.listView {font-size:0.85em; margin:0.8em 1.0em;}
table.listView th, table.listView td, table.listView tr {padding:0 3px 0 3px;}

.viewer pre {padding:0.5em; margin-left:0.5em; font-size:1.2em; line-height:1.4em; overflow:auto;}
.viewer code {font-size:1.2em; line-height:1.4em;}

.editor {font-size:1.1em;}
.editor input, .editor textarea {display:block; width:100%; font:inherit;}
.editorFooter {padding:0.25em 0; font-size:.9em;}
.editorFooter .button {padding-top:0; padding-bottom:0;}

.fieldsetFix {border:0; padding:0; margin:1px 0px;}

.zoomer {font-size:1.1em; position:absolute; overflow:hidden;}
.zoomer div {padding:1em;}

* html #backstage {width:99%;}
* html #backstageArea {width:99%;}
#backstageArea {display:none; position:relative; overflow: hidden; z-index:150; padding:0.3em 0.5em;}
#backstageToolbar {position:relative;}
#backstageArea a {font-weight:bold; margin-left:0.5em; padding:0.3em 0.5em;}
#backstageButton {display:none; position:absolute; z-index:175; top:0; right:0;}
#backstageButton a {padding:0.1em 0.4em; margin:0.1em;}
#backstage {position:relative; width:100%; z-index:50;}
#backstagePanel {display:none; z-index:100; position:absolute; width:90%; margin-left:3em; padding:1em;}
.backstagePanelFooter {padding-top:0.2em; float:right;}
.backstagePanelFooter a {padding:0.2em 0.4em;}
#backstageCloak {display:none; z-index:20; position:absolute; width:100%; height:100px;}

.whenBackstage {display:none;}
.backstageVisible .whenBackstage {display:block;}
StyleSheet for use when a translation requires any css style changes.
This StyleSheet can be used directly by languages such as Chinese, Japanese and Korean which need larger font sizes.
body {font-size:0.8em;}
#sidebarOptions {font-size:1.05em;}
#sidebarOptions a {font-style:normal;}
#sidebarOptions .sliderPanel {font-size:0.95em;}
.subtitle {font-size:0.8em;}
.viewer table.listView {font-size:0.95em;}
@media print {
#mainMenu, #sidebar, #messageArea, .toolbar, #backstageButton, #backstageArea {display: none !important;}
#displayArea {margin: 1em 1em 0em;}
noscript {display:none;} /* Fixes a feature in Firefox where print preview displays the noscript content */
<div class='toolbar' macro='toolbar [[ToolbarCommands::ViewToolbar]]'></div>
<div class='title' macro='view title'></div>
<div class='subtitle'><span macro='view modifier link'></span>, <span macro='view modified date'></span> (<span macro='message views.wikified.createdPrompt'></span> <span macro='view created date'></span>)</div>
<div class='tagging' macro='tagging'></div>
<div class='tagged' macro='tags'></div>
<div class='viewer' macro='view text wikified'></div>
<div class='tagClear'></div>
This concept map is intended to closely follow the one presented by James J. Vagliardo in his paper found at
<iframe src="" width="600" height="400"></iframe>
You can also visit the site to view the [[concept map|]].
Examining the concept map makes it clear that there is a great deal going on. That said, true understanding of every component of logarithms in not necessary in Algebra II. While logarithms were conceptually complete by 1700, we have gone from using logarithms as the supercomputer of the age to using them to solve for an unknown exponent. While I do want my students to have at least superficial knowledge of the rules of logarithms and why logarithms were historically important, I want them to have a deep understanding of a different subset of the concept map. Namely:

# How to use logarithms to solve for an unknown exponent. This must include story problems and connections to other content areas.
# Be able to describe the graph of a logarithm and know key points on the graph.
## Asymptotic to the //y// axis as //x// approach 0 from the right. Nonpositive //x// values are outside the domain.
##The //x// intercept is at 1. Unless there is a transformation the graph always goes through (1,0) no matter the base.
##Be able to roughly sketch the graph without a table.
##Know that a logarithmic function grows much more slowly than a linear function.
##Connect the graph to a logarithmic scale and realize why we use logarithmic scales.
#Know that a logarithm is an inverse of the exponential function and why this fact is mathematically important.
##This again connects to logarithmic scales.
##The graph of exponential function and logarithm are reflections over //y//=//x//.

I am primarily a high school mathematics teacher at [[Bellevue Community Schools|]]. The schedule changes significantly every year. However, I’ve been mostly teaching Geometry and Algebra II the last few years. Bellevue Community Schools are located in the [[Village of Bellevue|]] and is surrounded by rural housing and farms. Like many other rural schools the district, and most families attending, are [[not affluent|]]. Many students have access to computers, a smartphone or a iPod like device; however, this is far from universal. High speed internet is simply not attainable from any carrier or not affordable in other cases. The school was blessed with a technology bond a few years back. [[Interactive Whiteboards|]] are installed in every classroom. There are two computer labs shared from 6th to 12th grade. A classroom set of netbooks is also available. There is also a set of graphing calculators that is mostly used with ~PreCalculus students. There are classroom sets of [[Scientific Calculators|]] for every math and science classroom.

[img[CalcVsToes_Web.png]] My name is Eric Fitton and I am working on getting my Masters Degree from [[MSU|]] in [[Education Technology|]]. If you want to see my teaching applets, view my resume or otherwise know more about me, please visit my main page at This particular subdomain is for a project where I look at students using GeoGebra in my classroom and being able to do that by flipping my classroom.
I am fortunate that I will have the same special education co-teacher with me for the third year in a row. The first year she did the same assignments as the students. We work together extremely well. She gives me feedback when her notes from the previous year show another approach. In addition to talking to me when an approach, strategy or thought process makes sense to her; she will also give mini-notes on how she makes sense of the material or how she took notes to the students in the class. I have no doubt that she will be watching video lectures at home and using them in her resource room hour. In short, I am blessed that I will get feedback from a teacher that I trust and have been working with for multiple years. I know that she will let me know what parts of flipping the class worked and which parts did not. This will not only include the “lectures” but will also include GeoGebra applets, story problem group work, concept maps and student reflections.

Math lends itself to post-tests and there will be formative and summative assessments through the unit and a summative assessment at the end of the unit. I believe that student reflections will be a useful formative assessment and should help me get a look at students understanding. Moreover, this will help guide what I do in the unit. I am not planning on a pre-test this unit as everything in this unit is absolutely new to students. It would be uninformative for me and could possibly hurt student confidence heading into the unit. That said, I should be able to compare how students did on the post-test this year compared to the previous two years. In addition to the actual numerical results, my co-teacher’s thoughts about how much better or worse students understood the material overall will be important.

Where the rubber really hits the road for me is how are students able to perform the following year or in a different subject. When students enter ~PreCalculus will they still be able to use a logarithm or will they have forgotten how? If there is a physics problem requiring a logarithm will they be able to work with the physics teacher or will fantasia or amnesia show themselves. The ~PreCalculus teacher gives a pre-test with logarithm problems at the start of the year. I will be interested in the following September if he sees a difference in how students perform.

!![[Next|Key Issues in Education Technology]]
<iframe width="560" height="315" src="" frameborder="0" allowfullscreen></iframe>

GeoGebra is wonderful dynamic software that connects Algebra, Geometry and Calculus. It can be found at Instructional [[screencasts|]] are available.
Logarithms are incredibly powerful idea and tool in mathematics. They are relatively old, used before exponents. They are a central tool in computer science and physics. However, while students might be able to use logarithms to solve drill problems, deeper applications and understanding frequently eludes students. Looking back at my own mathematical learning, true understanding of logarithms came slower to me than almost every other facet of math^^1^^.

While my students can apply logarithms for their Final Exam, ~PreCalculus students simply did not remember to use a logarithm to find //x// on their pretest four months later. My hope going forward is to increase students’ perspective of logarithms, help students interpret the context of logarithms and make students able to explain logarithms by the end of the unit. With this background I believe there will be a reduction in amnesia; students should be able to apply logarithms four months or four years later.
I believe this unit lends itself to being “flipped.” It is inordinately difficult to activate prior knowledge with logarithms. While students can explore logarithms during activities and make connections during discussions; inquiry based learning where students //discover// logarithms is unrealistic. The background of notation and basic calculations simply needs to be supplied first. Using video, screencasting software, youtube, my website, and ~DVDs I plan on supplying lectures and notes as the homework for students. This will allow time for group activities and class discussion helping students put logarithms in historical and mathematical perspective.[>img[log.jpg]]
Freeing class time will allow for different types of assessments where I will be able to talk to small groups or individuals. This will help with regards to both formative and summative assessments. I will also be seeking feedback from my co-teacher during and after this unit. This will certainly give me perspective if the unit was more successful flipped. The rubber ultimately will meet the road the following September when ~PreCalculus students take their pretest.

^^1^^ A discussion of eigenvectors can wait for another day.

!!Using Technology for Creativity and Critical Thinking
A great deal depends on how you use a tool. Many people cringe when then think of worksheets. A worksheet often is a great deal of practice problems. But a worksheet can also help students find patterns. Consider the following worksheet about the [[Triangle Inequality Theorem|]]. It should help students find patterns and reason out ''why'' the Triangle Inequality Theorem works. This is how I intend to use GeoGebra in my flipped classroom.

!!Professional Development and Leadership
GeoGebra has a user forum and a website called [[GeoGebraTube|]] for sharing applets, worksheets and other materials. I have always shared my applets at However, I plan on becoming more involved with the ~GeoGebra community through ~GeoGebraTube and their forum. Similarly I will be looking to participate in an online community dealing with flipped classrooms. One of the advantages to meeting face to face in the hybrid program is I now have met two different math teachers who have already flipped their classroom and I certainly consider them part of my ~PLN.

While ~GeoGebra is limited with how many teachers can realistically adopt it at my school, it is ultimately a math tool, the same is not true of the flipped classroom. Social Studies and English teachers have assigned reading to students well before anyone coined the phrase, "flipping a class." That said, if I have success with flipping lessons and units I am sure other teachers will adopt and adapt my approach at my school.

!!Social and Ethical Uses of Technology
While important (we use [[Common Sense Media|]] in our //Creativity and Computing// class), these are addressed in other areas of my districts curriculum rather than in this proposal.

!!Universal Design for Learning
GeoGebra again plays a staring role. Not only will we be representing a great deal of the content visually, they can be quickly and easily modified. This allows students to dig for patterns while watching the image change. In addition to set applets, graphs can also be created on the fly by either me, individual students or groups. The purpose of flipping the class is to increase student engagement. By having student reflect in writing and in concept maps they will be expressing how they are thinking on multiple platforms that are usually ignored in a math classroom.

!!Information Literacy and Technology Skills
This is not part of this proposal at this time.

!![[About Me|EricFitton]]
!!<<slider chkTPACK [[The Total PACKage]] "The Total PACKage" "Open TPACK">>
!![[Educational Technology|Key Issues in Education Technology]]
There is a great deal I love in this unit. Exponential Growth and Decay is spiraled back in. We find and use Euler’s number //e// and we really connect to the sciences. That said, the motivating question for the unit is to give students: 5^^//x//^^=2069 and ask them to solve it. Someone will eventually guess and check their way there; however, we do not have a workable approach other than logs. Given the plethora of exponential equations available from science and economics, being able to solve these problems is motivating and the goal is straightforward.

The pedagogy this unit will be wide ranging. There will be direct instruction in the form of videos for students to watch at home. Students will drill to make sure they can switch between logarithmic form and exponential form. Students will practice finding //x// no matter if it is the base, the exponent, or the answer. However, students will be asked to use higher order thinking skills as well. We will “discover” //e// by using the interest formula with an ever decreasing amount of time between compounding. There will be story problems that will be solved in groups. Students will make concept maps linking logarithms to different areas of math and science. And students will reflect on their understanding of logarithms and revise their understanding as we go through the unit.

A highly informative article that shows a number of ways logarithms can be thought of historically. This article is where I found some of the best concept maps.
How logarithms were historically used. Would fit well with the facet of perspective with an eye towards history.
This gives a nice history of logarithms. An table with relevant dates is laid out.
A logarithm "cheat sheet"
A substantial piece of writing and research. I actually used this article more several years ago. My Dream IT project focuses much more heavily on graphing than the historical aspect.

!!Flipping the Classroom
A look at flipping a classroom paying attention to UDL and conceptual understanding.
A social network of educators using screencasting and flipping their classrooms.

Home of all things GeoGebra. This is the website with the actual software. On this page you will also find an introduction, a user forum and classroom materials.
Screencasts, worksheets and scripts to learn GeoGebra. This is how I first learned how to use the software.
Logarithms with a flipped classroom and GeoGebra.
Dream IT
body {font-size:1em; font-family:arial,helvetica; margin:0; padding:0;}

.viewer table.borderless,
.viewer table.borderless * {
border: 0;
!!! Putting together Technology / Pedagogy / Content

While I make sure logarithms get a large share of time in Algebra II, there is still a limited amount of time to learn the material. Traditionally in my classroom for this unit I go over homework questions (usually story problems), followed by a lecture, followed by guided practice and students then have a book assignment or worksheet which is a combination of drill and story problem. I have made time for Newton’s Law of Cooling as a demonstration and always have had students “discover” //e//. That said, most days follow the same routine which misses students make deep connections or working out the story problems.

This unit is shaping up different in the coming year. Using screencasts and video with a variety of distribution mediums, the “lecture” is going to happen at home. The practice part of the assignments are not a large time commitment. While I still will have guided practice as a regular part of the day; how the end of the day looks can and will vary. Having groups work together on story problems rather than watching me will get students more involved. Having students concept map will get students thinking about connections. Introducing mini science labs will help students uncover what a logarithm is and how it works. Similarly, worksheets designed to get at understanding can be used and start a discussion. However, this would all be much more limited without being able to use technology to flip the classroom, making the lecture the homework.

There is an advantage to graphing using tables. It is universal and at times helps us uncover the material. A table can help us find slope, intercepts and connect to a story problem. Graphing point by point using a table is slow. When exploring a family of functions it is much faster to graph using a computer. A GeoGebra (similar to Geometers Sketchpad) applet can help students explore graphs of logarithmic functions and exponential functions. Changing variables with sliders helps clarify that an exponential function and a logarithmic function remain reflections. Connections can be made to the [[Graph-Translation Theorem|]] and students can again use sliders to look at horizontal shifts, vertical shifts and dilations. The graph also helps with the discussion about domain and range. That you simply cannot take the log of a negative number is an essential piece of understanding and a graph can help students with that understanding. A great deal can be done using an automatic grapher and this unit lends itself to a program like GeoGebra.

Here is an example of an applet that I wrote for this unit showing how GeoGebra works. When I mention creating a worksheet, it is intended to be an exploration worksheet for students to look for patterns and make connections.
<html><!-- copy and paste. Modify height and width if desired. --> <object id="scPlayer"  width="898" height="654" type="application/x-shockwave-flash" data="" > <param name="movie" value="" /> <param name="quality" value="high" /> <param name="bgcolor" value="#FFFFFF" /> <param name="flashVars" value="thumb=" /> <param name="allowFullScreen" value="true" /> <param name="scale" value="showall" /> <param name="allowScriptAccess" value="always" /> <param name="base" value="" /> Unable to display content. Adobe Flash is required.</object></html> 

There are actually two different ways I will need to make use of technology. The first component is the technology to “flip” the classroom. To create the videos I will be using a number of technologies. At times I may be using a flip camera, webcam, document camera, interactive whiteboard, a variety of microphones and an input tablet. Various software packages, including one to create screencast will be necessary. I also need to be able to distribute the videos. I will be uploading the videos to a personal website and to [[YouTube|]]. However, not all students have access to the internet or a data plan, I plan on using jump drives for these students. I will also need to burn ~DVDs for students who do not have access to a computer. This does limit the type of work I can send home to either book assignments, worksheets or video lecture. It is possible a grant would allow for netbooks or tablets with java for more experiential homework and ease the workload on distributing the lessons.

As a result of the flip, I will be using more technology in my classroom. Some of this technology might be relatively simple. A thermometer with either hot or cold water can have students using logarithms to estimate a future temperature using Newton’s Law of Cooling. I will plan on using GeoGebra both on my interactive whiteboard and in the computer lab for students to manipulate graphs of logarithmic functions. Additionally, students will be writing about their understanding of logarithms throughout the unit. There is also an opportunity to create concept maps using a Web 2.0 tool.

That said, GeoGebra will be playing a leading role in my classroom and in this unit this coming year. I have created two applets already to go with this unit, am willing and able to make more and am sure I will be able to find more on [[GeoGebraTube|]]. I have spent approximately two days each year with Geometry and Algebra II students teaching them how to create and use GeoGebra. While pre-written applets are wonderful, having students start working from scratch in GeoGebra brings an entirely new twist to the classroom and the computer lab. There is certainly a place for GeoGebra to be used with an entire class, with worksheets / applets prepared ahead of time and for students to create on their own.

[<img[construction_web.png]]In prior years I have focused almost entirely on two aspects of understanding in this unit. The largest focus was on applying logarithms. I wanted students to be able to apply logs to practice problems, story problems and to small projects. With the difficulty in activating prior knowledge I also tried to help students gain perspective understanding. We would connect examples with exponents, often reworking an entire example backwards using exponents. I would emphasize multiple times throughout the unit that logarithms are the only way to find an unknown exponent other than guess and check.

Clearly application matters. Logarithms are a building block of math and science. While I previously tried to incorporate perspective understanding, I believe I need to increase the amount of time spent on connections between the areas of mathematics and increase the quality of activities related to perspective understanding. I also think that class time will better be used having students manipulating models of logarithms; probably graphically, than how class time was used in previous years. Hopefully students will be able to interpret how logarithms work by adding this facet of understanding. Moreover by creating stories with thermometers and exploring Newton's Law of Cooling thoroughly, I expect to see greater understanding in the facet of interpretation. Where my instruction was most lacking; however, was dealing with the facet of explanation. Students never explained their thinking on logarithms. This is not only a vital assessment piece, it will also help students organize their thinking and help them make more connections. This can be gradually teased out to help students' with their self-knowledge. Are they aware of what they do and do not understand?

Technology can be an asset to my students understanding. While many of my “lectures” are interactive with students at the board, my lectures on logarithms are not. By moving the least interactive piece of instruction to the home we free up class time to not only work on drill assignments but engage in activities. We can solve story problems in groups and have group and class discussions. We can manipulate logarithms on graphing calculators and with GeoGebra. Students can explain their thinking by writing, and as we learn more, by revising. They can make sense on the material and demonstrate their connections between different aspects of logarithms and in math in general with concept maps. The writing can easily be a google document and there exist many Web 2.0 services to create concept maps.