= Chapter 14 Notes =

Title: '''Absolute Layouts'''

== Summary ==

So much ado about Labels and the text in them.

=== Programming Concepts Summary ===

|| '''Concept''' || '''Page''' ||

== Programs ==

=== Program AbsoluteDemo ===

Page 339.

Concepts:

The {{{AbsoluteLayout}}} class redefines its Children property to be of type {{{AbsoluteLayout.IAbsoluteList<View>}}}, which includes two additional Add methods that allow you to specify the position of the child relative to the upper-left corner of the Absolute-Layout. You can optionally specify the child’s size.

Sizes are in device independent coordinates..

Classes: 

 1. {{{AbsoluteLayout}}} is demonstrated.

Action: It's simple, just show it.

=== Program ChessboardFixed ===

Page 342 

Concepts: Demonstrates how to calculate the location of views.

No New classes.

Action: Check out the calculations.

=== Program ChessboardDynamic ===

Page 344 

Concepts:

 1. dynamically sizes the board and layout on the changing of the size...
 1. {{{AbsoluteLayout.SetLayoutBounds(view,rect)}}} this is much ado about nothing! Who cares if {{{SetLayoutBounds}}} is static, view is not!
 1. {{{AbsoluteLayout.LayoutBoundsProperty}}} is a {{{BindableProperty}}} - Hence this is a demo of Attached bindable properties.

Action: Walk through the program ans show the calculations. Briefly!!! The next one is more important.

=== ChessBoardProportional ===

Page 349, 

Concepts:
 1. Automating child view sizes based on {{{AbsoluteLayout}}} size. 

Action: Just show it, its pretty self explanatory, but there is a lot of talk about "Attached Bindable Properties" leading up to it. 

=== ProportianalCoordinateCalc ===

Page 352.

Action: Although this may be useful, we are skipping it for now. GOTO PAGE 355 ({{{AbsoluteLayout}}} and XAML)

=== AbsoluteXamlDemo ===

Page 355.

Concepts: 
 1. The XAML way of doing things is unique so look at the program.

Action: See concepts.

=== SimpleOverlay ===

Page 359. 

Concepts: 

 1. Overlaying objects. 

Action: Quick Demo! It's simple, but it is very cool! 

=== DotMatrixClock ===

Page 362 

Concepts: 

 1. Just an implementation of something cool - uses timers of course. 

Action: Gloss over - this is for students to do something similar!

=== BouncingText ===

Page 368

Concepts:

 1. Using timers again to move things around this time. 

Action: Gloss over - this is for students to examine.