Merge branch 'master' of github.com:codelearn-org/android-tutorial-views

Author: pocha

twitter-client-tutorial/_import_codelearn_project.html.md

@@ -3,7 +3,7 @@ In the previous level, we installed Codelearn Eclipse Plugin.
 
 Follow the steps below to import an Android project, which will be used by you for the rest of the challenge.
 
-1. <%= link_to "Download CodelearnTwitterChallenge Eclipe project", "/android-tutorial/#{@current.lesson_module.import_file}" %> and import it in Eclipse.
+1. <%= link_to "Download CodelearnTwitterChallenge Eclipe project", download_import_project_zip_path(@current.lesson_module.lesson.token, @current.lesson.token) %> and import it in Eclipse.
 
 2. From next lesson onwards you will be building your application on this imported project. So to run it from next lesson you can either choose to **[right click on CodelearnTwitterApp] -> Run As -> Android App Codelearn ** or simply hit the **Run button** on the top of Eclipse which will show the popup below. *Remember to choose 'Android App Codelearn' option as against 'Android Application'*. Now you can go to the next lesson.
 <p>

twitter-client-tutorial/_lesson_group_async_task.html.md

@@ -4,3 +4,4 @@ Reading and writing tweets from/to file are time consuming tasks. These tasks sh
 You can always compensate the delay by showing a loading/spinner but that is a bad app design. It is like blocking the app flow. The code should be written in such a way that blocking the app flow should only happen if the user's next action is dependent on the current action. The choice is personal on the part of programmer too. For example - fetching tweets from network should never be blocking but publishing a tweet can be. The user might or might not want to wait till the tweet is published. If you do not block the app, you should show some kind of notification which will let user come back to the publish tweet screen to publish it again. 
 
 In the last lesson, we were reading & writing the tweets in the same thread. In this lesson, we are going to move the steps of creating new tweets & overwriting the cached file into a separate thread using **AsyncTask**.
+

twitter-client-tutorial/_lesson_group_shared_preference.html.md

@@ -4,5 +4,3 @@ In the real Twitter client, once you log in successfully, you will not see the l
 We are introducing data handling in this module. The network calls will be introduced in the subsequent module. We make things a little sub-optmial. Instead of sending data to the server & getting an authentication token, we will simply store the username password from the login screen. 
 
 <div class="alert alert-warning"><b>Warning</b>: It is never a good idea to store passwords locally, plaintext or otherwise. But for the sake of this module, we overlook best practices to get a better understanding of SharedPreferences</div>
-<div>
-

twitter-client-tutorial/_lesson_group_tweets_from_file.html.md

@@ -7,3 +7,4 @@ In a mobile app, use of local storage is important for a better user experience.
 
 For now, we are simply going to write the dummy tweets that we created in the previous lesson into a local cache file, read from it & show it to the user when the Tweet List screen loads. In subsequent lesson, we are going to move the writing tweets part to an asynchronous process using AsyncTask. 
 
+

twitter-client-tutorial/_tweet_list_dynamic_data.html.md

@@ -5,3 +5,4 @@ In this module, we will add the feature - each tweet item should have different
 
 > In this module, you will going to learn how to access & modify data in a ListView & best practices of storing data using models in Java/Android. 
 
+