Post has attachment
Hey, it was nice working with you all. I plan on going through this book next. If there's interest in collaboration, and maybe splitting the cost of an e-book, let me know.

I was asked to upload a file of the audio from the previous meeting.  This forum requires upload to YouTube, which requires a file format I have not been ale to create yet.

I will be at Church this Thursday for Maundy Thursday, part of Holy Week leading to Easter.  Back to the Jam the next Thursday.

As second prize, here are some notes from 3/19.  It would be great if someone could take and post the best possible notes for this Thursday.  An audio tape would be even better.

745 Atlantic Ave
We Work/South Station
Informal Android meetup
Mon 30th
see page for our meetup

Self intros
Who we are
Why there
What working on.

connection -- 4G v wifi
structure the data and ops to be fast and effic 
synch adapter

In Studio, go to VCS tools and then to diff to compare files.

Use Hierarchy Viewer to fix UI problems

Employers look for:
Code store with samples that work
PlayStore entries
Bring in tablet and show your app

Tim in class for publishing apps
He is creating an LLC to limit his liability

Beth is the new additional teacher

Suggestion that we will find Kayak or KIAC.  [Spelling uncertain.  Sounds like KIAK.]

Check how projections work

Select * may have a security problem.
If get error ms it will include the tabledef so cracker can play with those indiv fields.

Support Libraries let you access and run newest features even if running an older version of o.s.
Android SDK mgr.
"support library features" into Google to find documentation
loader stuff requires bringing in V4
V13 import is difficult or can be
V7 has material for action bar

Google captures good data about who is using what version of Android
--> which api to target app to
Developer counsole user --- Kitkat to make fit into smaller versions
Majority of developers currently writing in Jellybean and Kitcat. 41% developing on Kitcat.
Seems should currently go with api 15 or 16 at conclusion of the discussion.

swiping is expensive in terms of resources
Therefore use newer device with more power

7:57 Swipe somewhat replaces action bar:
Try Navigation Drawer
Leaves more screen real estate.
Goes in layout folder rather than xml
8:03 Contacts menus pop up when hold finger to a a particular spot on screen.
double taps, 2-fingers, combinations for gestural choosing.
guidelines for Android change and are enforced very flexibly
mandatory for iPhone.

Naimi Djouhri had a lot of good questions and comments

Beth says Android has the most market share in US

ISPs control the market for iPhone and Android phones
Limitations on data transmission a problem
Blackberry opened the door for ISPs to share data openly
In India they pay per byte for data trnasmission. 
Leads to a completely different user psychology re data.

Bada is low end O.S. by Samsung popular in W.Europe
Google wants more bandwidth, because more ads --> more revenue


Google and FB have bought solar drone netwoerks to stay in air a year at a time
LTE network using weather balloons
For mesh networks

"Cardboard" for virtual reality

Do half of lesson 5 for next week.

I am having a hard time with the "Action Bar" step of lesson 5.

First, I was not able to use "@style/Theme.AppCompat.Light.DarkActionBar". So I included the library '' and downgraded the target SDK to 20. 

But now I am not able to define the node '<item name="colorPrimary">@color/sunshine_blue</item>', as I get an error which states: "Error:(5, 21) No resource found that matches the given name: attr 'colorPrimary'".

Perhaps I need to update my SDK? Has anybody else run into this issue? I'm sure it's not a huge deal, but it is frustrating none-the-less.

I am jarred by the shortfall in consistency in the videos.  Here is an example. originally has this line:
 double high = cursor.getDouble(ForecastFragment.COL_WEATHER_MAX_TEMP);
Then in "Modify ForecastAdapter-Solution"
it changes to 
 float high = cursor.getFloat(ForecastFragment.COL_WEATHER_MAX_TEMP);

It then returns to double here:!/c-ud853/l-1623168625/e-1667758593/m-1667758594

Which are they proposing to teach us that we use, and on what basis?

One line of pedagogical logic is that these kinds of changes without explanation or warning force the student to learn the material better.  Valid point. We do a lot of debugging of our own typing, and we can also debug Udacity.  Another holds that time is precious and we are attempting to process a lot of material per week, so seeming glitches in the teaching material poses a problem.  This would argue that Udacity needs to put some more effort into debugging its materials.

I think that the other half of why to type in our code is that it gets us used to using Android Studio which has awesome features for reducing typos and making sure as much as possible is consistent across the application, thus helping to free our attention to the substance of coding.

Thinking about the apps that I have, human factor design is essential, but the functionality is more important.  I refuse to use Facebook app because it downloads way too much data, making it costly and slow.  I really like apps that give me some arcane pieces of information, such as arcane gps info.  I get very irritated when one of my errant fingers brushes against some part of the screen and creates major damage.  I find the android typing function primitive and cumbersome.  I itch for Droids to reach their full promise.

Post has attachment
It's beyond the scope of this course, but I found an interesting tutorial on building a RESTful web service using Spring. I haven't actually tried this out yet, but I'm sure that as with all things it's easy when simple and difficult when the use case becomes more complex:

Hi Folks - here-s what +Jinn Kim  has outlined for tonight's Study group meetup.

here is an outline of what i plan on talking about.

app can be killed anytime for resouces

activity lifecycle
onCreate -> created
onStart -> visible
onResume -> active

onPaused -> Paused
onStop -> Stopped
onDestroy > Destroyed

foreground and infoocus

active -> visible -> background

app roatation
onPause, onStop is where resources should be released
sensors, location, broadcast recievers, heavy CPU/GPU (games)

exit and quit dont' do anything

onCreate -> onRestoreInstanceState -> Active ->
onSaveInstanceState -> onpaause -> terminated

key value pairs of primatives
SQlite DB
DB helper
Junit asserts

+burc oral 

Post has attachment
Check out some useful Android Studio shortcuts.

Post has attachment
How many of you folks completed Lesson 2.
votes visible to Public
I completed
I am working on it.
Wait while more posts are being loaded