﻿Mobile ASP.NET MVC Template v3
README
2012-02-23

Author: Eric G. Miller <emiller@dfg.ca.gov>

This template was adapted from the ASP.NET Webforms version of the
California Mobile Template v3.0 - Developer Preview.  I have attempted
to stay faithful to the source template.  However, due to the architectural
differences, many things had to be reorganized.

Rational: Fish and Game is already using the ASP.NET MVC platform to
provide mobile optimized content.  So, it will be easier to migrate
exiting code to the new template if one exists.  Additionally, others
might be interested in using ASP.NET MVC.  I believe it provides a
good way to build lightweight pages vs. ASP.NET Webforms.

Location management is handled via the MyLocation model class and the
BaseController controller class.  I made the decision to stuff the MyLocation
instance in a ViewBag variable in order to pass it to the views.  I also considered
creating a base model class that either included the MyLocation instance as a
property, or simply used MyLocation as the base class.  However, I decided I didn't
want to muck up any models with excess baggage if it wasn't needed.

The BaseController also has a property for the BackUrl that may be set.  And, I'm
passing it to views via a ViewBag variable.  Again, the BackUrl property could be
handled a a base model class property.

I'm not sure that there is much point in having the _HomeLayout.cshtml since it
only applies to the landing page.  But, there it is...

I changed the Latitude/Longitude range checks from the source template because the
source ranges cut off parts of California.

Outstanding Issues:

* FUSION TABLES
The Fusion Tables ZIP code lookup seems to be missing some valid ZIP codes.
For instance, Arcata/McKinleyville 95521. I didn't do an exhaustive search, but I
happened upon the Arcata example.

* CSS RULES
Some of the style rules in the mobile.css seem overly broad and make it difficult
to style other kinds of pages than the samples.  And there doesn't seem to be a
default rule for simple paragraphs of text.

The rule "#second ul li span" can capture a lot of spans for which it really
isn't intended.  Can't we have a simple class for a sub-title block?

And, I would like to see a default container for paragraph text that simply
applies the correct padding.  For instance:

.content { padding: 5px 10px; }
