Updated the L&F of the buygiftform, has a thin gray border but white
background.  The buttons are at the top and are mini just like the
reserve button on viewitem.html - so it ends up looking like the same
line item is "expanded" when you click reserve.

Buy is now Buy Online and we're using a twitter bootstrap button
toolbar and button group for the Reserve, Buy Online and Cancel
buttons
x
Facebook login working here.

Had a lot of problems with logging in to FB.  You enter user/pass and
the fb dialog goes blank but doesn't go away.  You do get logged in to
fb, but the "success" callback never gets called - which totally
screws up everything downstream.

Saw a bug report that fb was having trouble with callbacks to port
8080 addresses.  So added a line to build.sbt that would make jetty
run on 80.  Got fb login to work on foo.html.  Then copied login.html
to foo.html - again, foo.html worked.  Copied foo.html back to
login.html - that also worked HUH?

Finally, changed jetty back to 8080 and all the app url's at
developers.facebook.com back to 8080...  and login.html works again.

Makes no sense, but committing here so I have something to refer back
to.

There is a lot of "test" code and pages that shouldn't be here, but
for now, I'm just trying to capture a working FB login.
FB login implementation: little by little

Don't know what's going on with fb.  Take foo.html - the fb login
button on that page works every time.  Copy foo.html over to
login.html and it only seems to work some of the time.

Thought it had something to do with the code in $scope.initfbuser()
(app-ConnectCtrl.js) because as soon as I would start uncommenting
code in that method, the fb login would start acting up again (the
dialog wouldn't dismiss and the "success" would stop being called).

The fix/hack:  So I would just re-copy (over and over again) foo.html,
overlaying it on top of login.html (but the 2 pages are identical
except for some "tagging" text in each page - "login.html" and
"foo.html" to let me know exactly which page I was looking at.)

At this point, I have $scope.initfbuser() working up to the point
where it will recognized that a fb user also has an LBB account and so
it will automatically send the person to his wishlist page.

Note the $routeChangeStart event that we listen for in app.js.  This
code fires on every request.  It is here that we determine if we let
the user through or redirect to /login.  One of the things we look for
is the presence of $rootScope.user.

$rootScope.user is new.  We used to just store $scope.user and $emit
"userchange" events.  But it sounds like it is better to keep shared
variables and functions in the $rootScope.
In the prior commit, I was logging in the fb - the 'person' record
already had a facebook_id value, so this was a "merged" account.

In this commit, I am able to login to fb where the 'person' record
does not yet have a facebook_id value.  After logging in to fb, I
checked the person table and verified that it got updated with the
facebook_id.

This is an example of "merging" fb and lbb accounts because the record
in the person table got updated with a facebook id!
removed the "tagging" text "login.html"
More testing of the fb login feature:  Verified I get sent to the "who
are you page" when the email address is shared by 2 or more people and
no one has the right facebook id.

Making sure $rootScope.user is now set whenever the user is logging in
via various fb login use cases (person record exists, person record
doesn't exist, person record exists but facebook id null, etc)
Added a troubleshooting doc.  First tip: How to fix it when the fb
login doesn't go away or call the "success" function.
updated tests
updated tests
Profile Pic centering:  Got nice centering of the profile pic in
profilepic.html.  See app-UserCtrl.js.  Notice how
$scope.adjustedheight and $scope.adjustedwidth conditionally calculate
margin-top and margin-left