removed titles from the app & challenge lessons as they are fetched from the db now

pocha · pocha · commit d0ffb3931d4f · 2014-06-11T22:57:43.000+05:30
diff --git a/twitter-client-tutorial/_android_list_view_intro.html.md b/twitter-client-tutorial/_android_list_view_intro.html.md
@@ -1,4 +1,3 @@
-# Designing List of Tweet Screen
 
 We successfully hooked 'No Tweet Found' screen after the login screen in the previous lesson. In this lesson, we will remove the 'No Tweet Found' message & populate the screen with a dummy tweet list. As usual, we will use some placeholder data to show some dummy list content.
 
diff --git a/twitter-client-tutorial/_android_login_button_listener.html.md b/twitter-client-tutorial/_android_login_button_listener.html.md
@@ -1,4 +1,3 @@
-# Adding Listener to Login Button 
 
 So far, we just have the interface of the login screen. As per plan, we will simply move to the next Activity when Login button is pressed. We will not capture any login information for now. Once we are done with our first iteration, we will revisit the Login Activity & add capturing of login information & validation of the user. 
 
diff --git a/twitter-client-tutorial/_android_login_password_and_button.html.md b/twitter-client-tutorial/_android_login_password_and_button.html.md
@@ -1,4 +1,3 @@
-# Add Password & Login button
 
 In the previous lesson, we added Username label & input field. For the password, we will simply replicate the LinearLayout for the Password label & input field. 
 
diff --git a/twitter-client-tutorial/_android_login_screen_add_username_password.html.md b/twitter-client-tutorial/_android_login_screen_add_username_password.html.md
@@ -1,4 +1,3 @@
-# Adding Username label & input field
 
 In the previous lesson, we got the header in place. In this lesson, we will add the input fields namely username & password. 
 
diff --git a/twitter-client-tutorial/_android_login_screen_layout.html.md b/twitter-client-tutorial/_android_login_screen_layout.html.md
@@ -1,4 +1,3 @@
-# Login Screen Layout
 
 So far, we already have a hello world application. In the earlier lesson, we have seen how the control starts from the `onCreate` method of the **MainActivity.java** file and how it renders the layout defined in **activity_main.xml** . 
 
diff --git a/twitter-client-tutorial/_android_login_style_elements.html.md b/twitter-client-tutorial/_android_login_style_elements.html.md
@@ -1,4 +1,3 @@
-# Styling Login Screen Elements
 
 So far we have focussed on positioning the elements but ignored the width & height of the elements. We will address those issues in this lesson.
 
diff --git a/twitter-client-tutorial/_android_tweet_detail_activity.html.md b/twitter-client-tutorial/_android_tweet_detail_activity.html.md
@@ -1,4 +1,3 @@
-# Tweet Detail Activity Screen
 
 In the previous lesson, we implemented click listener for each tweet. Ideally, clicking on a tweet should show the tweet detail screen. In this lesson, we will be creating new Activity TweetDetailActivity & show the Activity on click of tweet item through intent. 
 
diff --git a/twitter-client-tutorial/_android_tweet_item_click.html.md b/twitter-client-tutorial/_android_tweet_item_click.html.md
@@ -1,4 +1,3 @@
-# Click Listener for individual tweet item
 
 In the previous lesson, we integrated the custom layout row_tweet.xml with the ListView. The next step is to view each tweet in detail when the tweet item is clicked. For the detail screen, we will need a new Activity. We'll do that in a subsequent lesson. In this lesson, we'll see how to enable & capture click event for each item in a ListView. 
 
diff --git a/twitter-client-tutorial/_android_tweet_list_activity.html.md b/twitter-client-tutorial/_android_tweet_list_activity.html.md
@@ -1,4 +1,3 @@
-# Layout for Tweet
 
 In last lesson, we learnt how to show up a ListView with dummy data. We need the tweet list to look like as below 
 
diff --git a/twitter-client-tutorial/_android_tweet_list_custom_layout.html.md b/twitter-client-tutorial/_android_tweet_list_custom_layout.html.md
@@ -1,4 +1,3 @@
-# Custom Layout for individual tweet
 
 In the last lesson, we learnt how to show a basic ListView with one line data. We need the tweet list to look like the image below 
 
diff --git a/twitter-client-tutorial/_android_tweet_list_hooking_custom_layout.html.md b/twitter-client-tutorial/_android_tweet_list_hooking_custom_layout.html.md
@@ -1,4 +1,3 @@
-# Hooking Custom Layout to Tweet List View
 
 In the last lesson, we created a custom layout for a Tweet but our Tweet List will still show up as a basic list with one entry per line.
 
diff --git a/twitter-client-tutorial/_android_tweet_list_item_click.html.md b/twitter-client-tutorial/_android_tweet_list_item_click.html.md
@@ -1,4 +1,3 @@
-# Attaching click listener to individual tweets
 
 In previous lesson, we are able to get the kind of layout we designed for the list of tweet screen. Clicking on a tweet item should show the tweet detail in a new Activity. In this lesson, we will put the click listener on each tweet item. 
 
diff --git a/twitter-client-tutorial/_android_tweet_list_layout_part_2.html.md b/twitter-client-tutorial/_android_tweet_list_layout_part_2.html.md
@@ -1,4 +1,3 @@
-# Layout for Tweet List - Part 2
 
 In last lesson we added just the ImageView in the row_tweet.xml . We need to add child LinearLayout with its own children. 
 
diff --git a/twitter-client-tutorial/_asynctask_intro_networkcall.html.md b/twitter-client-tutorial/_asynctask_intro_networkcall.html.md
@@ -1,4 +1,3 @@
-# AsyncTask intro
 
 AsyncTask class lets us execute things in parallel. It is like spawning a new thread which does things in parallel & exits silently when the tasks are done. It is important not to *block* the main Activity thread. 
 
diff --git a/twitter-client-tutorial/_asynctask_show_new_tweets.html.md b/twitter-client-tutorial/_asynctask_show_new_tweets.html.md
@@ -1,4 +1,3 @@
-# Show tweets after AsyncTask
 
 The AsyncTask we created in previous lesson is simply simulating a network call to fetch new tweets. In case of an actual network call, new tweets will be fetched and we should update the tweet list screen to show them.
 
diff --git a/twitter-client-tutorial/_asynctask_tweets_write_new_asynctask.html.md b/twitter-client-tutorial/_asynctask_tweets_write_new_asynctask.html.md
@@ -1,4 +1,3 @@
-# Moving writing of tweets to new AsyncTask
 
 As mentioned earlier, reading & writing from files are slightly elaborate tasks & should be done in a separate thread to avoid affecting the main Activity flow. 
 
diff --git a/twitter-client-tutorial/_button_click_listener_module.html.md b/twitter-client-tutorial/_button_click_listener_module.html.md
@@ -1,4 +1,3 @@
-# Implementing Login Button Click Listener
 
 If you have followed our Twitter App tutorial so far, you have built a login screen with some basic Layouts & View elements. You have added a login button but it does nothing. 
 
diff --git a/twitter-client-tutorial/_hello_world.html.md b/twitter-client-tutorial/_hello_world.html.md
@@ -1,4 +1,3 @@
-# Hello World
 
 If you have not setup our Virtual Assistant so far, kindly click the *Go to setup* button on the right. In the setup steps, you would be created a new **CodelearnTwitterApp** which has an Android Hello World app running. The app is similar to the default Android Hello World app that would create from Android ADT. Let's understand the Android app control flow a bit. We have created a screencast for you to help you understand the flow faster.
 
diff --git a/twitter-client-tutorial/_hello_world_module.html.md b/twitter-client-tutorial/_hello_world_module.html.md
@@ -1,18 +1,32 @@
-# Welcome to Codelearn Android Twitter App Tutorial
 
-In this tutorial, you will build a Twitter App from scratch. Our intent is to show the lifecycle of an app from scratch to production. The unique thing about this tutorial is - you learn by building an app rather reading about the concepts. We tried to keep the flow as close as possible to how real developers develop real apps.   
+In this tutorial, **you will build a Twitter App from scratch**. Our intent is to show the complete lifecycle of an app from scratch to production. The unique thing about this tutorial is - *you learn by building an app rather reading about the concepts*. We tried to keep the flow as close as possible to how real developers develop real apps.   
+
+## Why you should learn from us 
 
 It could be daunting for a total newbie to get into Android app development from day 1. To keep things simple & progressive, our App Tutorial flow is created such that :-
 
-* Features required easier concepts are built earlier while the features requiring difficult concepts are pushed later. For example, we start with building the UI as it involves basic concepts like Activity & Layout, while pushing features like new tweet notification for later (work in progress).
+1. **Easier concepts first, difficult concepts later **
+
+	Features required easier concepts are built earlier while the features requiring difficult concepts are pushed later. For example, we start with building the UI as it involves basic concepts like Activity & Layout, while pushing features like new tweet notification for later (work in progress).
+
+
+2. **App features tweaked for optimal & gradual learning**
+
+	If a feature is combination of multiple concepts involving some of the advanced ones, we break down the feature such that we do a sub-optimal build of the feature. For example, while introducing AsyncTask for network calls, we ask users to simulate the network call using a `Thread.sleep(..)` so that users can focus on just AsyncTask. 
+
+3. **Small learning per lesson to avoid information overload**
+
+	Each module is broken down into lessons such that the lessons has just enough feature for you to focus only on one concept (or part of concept) at a time. This is also done to ensure that we are able to test the feature & pin-point you of the exact error which we would probably not able to do if it is a bigger feature involving multiple concepts. 
+
+4. **Get your app evaluated at every lesson ** 
 
-* If a feature is combination of multiple concepts involving some of the advanced ones, we break down the feature such that we do a sub-optimal build of the feature. For example, while introducing AsyncTask for network calls, we ask users to simulate the network call using a `Thread.sleep(..)` so that users can focus on just AsyncTask. 
+	You get to build & get your app tested at every lesson through our Eclipse plugin which we also call Virtual Assistant. So you dont just learn by doing, you learn by building a real app with instant app evaluation. Our aim is to enhance our Virtual Assistant to the level that it should be able to hint & guide you based on your learning capabilities. As for now, it simply tells you the error message of the test that fails when it evaluates your app. 
 
-* Each module is broken down into lessons such that the lessons has just enough feature for you to focus only on one concept (or part of concept) at a time. This is also done to ensure that we are able to test the feature & pin-point you of the exact error which we would probably not able to do if it is a bigger feature involving multiple concepts. 
+5. **Newbie friendly language. Tutorial structured by experts but worded by learners**
 
-* Lastly, you get to build & get your app tested at every lesson through our Eclipse plugin which we also call **Virtual Assistant**. So you dont just learn by doing, **you learn by building a real app**. Our aim is to enhance our Virtual Assistant to the level that it should be able to hint & guide you based on your learning capabilities. As for now, it simply tells you the error message of the test that fails when it evaluates your app. 
+	The language of our tutorial is very beginner friendly. **A lot of our users have told us this point**. Most of the tutorials are created by experts. Our tutorial structure is created by experts but the actual tutorial content is created by newbies who learn from this tutorial & then replace the complex statements with easier to understand lines & also fill in any newbie friendly information which experts have missed.
 
+6. **Want to be a good developer ? Develop a lot of apps & not just your own**
 
-Lastly, the language of our tutorial is very beginner friendly. A lot of our users have told us the same. Most of the tutorials are created by experts. Our tutorial structure is created by experts but the actual tutorial content is created by newbies who learn from this tutorial & then replace the complex statements with easier to understand lines & also fill in any newbie friendly information which experts have missed.
+	We understand that you have your own app ideas that you like to work on & probably not like to build *yet another Twitter app*. The only way you can become a decent developer is by creating a lot of apps. This way, **you not only understand Android concepts, but also the engineering behind app creation** like how to conceptualize an app, how to break a big feature into smaller features etc. Going through complete app development lifecycle is an important learning which you can use in your own Android app.
 
-We understand that you have your own app ideas that you like to work on & probably not like to build *yet another Twitter app*. The only way you can become a decent developer is by creating a lot of apps. That way, you not only understand Android concepts, but also the engineering behind app creation like how to conceptualize an app, how to break a big feature into smaller features etc. Going through complete app development lifecycle is an important learning which you can use in your own Android app.
diff --git a/twitter-client-tutorial/_import_codelearn_project.html.md b/twitter-client-tutorial/_import_codelearn_project.html.md
@@ -1,4 +1,3 @@
-# Import Codelearn Twitter Challenge Project
 
 In the previous level, we installed Codelearn Eclipse Plugin.
 
diff --git a/twitter-client-tutorial/_iteration_1_plan.html.md b/twitter-client-tutorial/_iteration_1_plan.html.md
@@ -1,4 +1,3 @@
-# Planning the app
 
 The first thing an app developer does before he starts building the app is to plan it. The first step is to create [mockups](http://en.wikipedia.org/wiki/Mockup#Software_Engineering). But since we are replicating an already existing app, we know how it will look. So we can bypass the mockup creation step.
 
diff --git a/twitter-client-tutorial/_lesson_group_async_task.html.md b/twitter-client-tutorial/_lesson_group_async_task.html.md
@@ -1,4 +1,3 @@
-# Reading/Writing tweets with AsyncTask
 
 Reading and writing tweets from/to file are time consuming tasks. These tasks should not be handled in the main thread so as not to give a *hung app* experience to the user.
 
diff --git a/twitter-client-tutorial/_lesson_group_shared_preference.html.md b/twitter-client-tutorial/_lesson_group_shared_preference.html.md
@@ -1,4 +1,3 @@
-# Storing login data in Shared Preference
 
 In the real Twitter client, once you log in successfully, you will not see the login screen again. The app sends the username password information to the server, receives an authentication token & stores it locally in the phone. The next time you open the app, it checks for the authentication token & directly takes you to the tweet list screen.
 
diff --git a/twitter-client-tutorial/_lesson_group_tweets_from_file.html.md b/twitter-client-tutorial/_lesson_group_tweets_from_file.html.md
@@ -1,4 +1,3 @@
-# Fetching/Writing tweets from/to local files
 
 Now that we know how to show dynamic list of tweets, we are now going to go to the next level of storing the tweets in a local file & showing tweets from it.
 
diff --git a/twitter-client-tutorial/_login_page_intent_module.html.md b/twitter-client-tutorial/_login_page_intent_module.html.md
@@ -1,4 +1,3 @@
-# Loading TweetList Screen from Login Screen through Intent
 
 In the last module, you implemented **Click Listener** on login page button which simply updated the button text. In this module, you will learn how you can load a new Activity on the button click using **Intents**.
 
diff --git a/twitter-client-tutorial/_new_codelearn_project.html.md b/twitter-client-tutorial/_new_codelearn_project.html.md
@@ -1,4 +1,3 @@
-# Creating A New Codelearn Twitter Project
 
 In the previous lesson, we installed Codelearn Eclipse Plugin. Instead of following the regular process of creating a New Android project, the plugin comes with a **Codelearn Twitter App** project pre-bundled. **When you create a new Android project, it asks for quite a few parameters which is confusing for a newbie. We have condensed all those steps by providing default values.** 
 
diff --git a/twitter-client-tutorial/_no_tweet_activity_after_login.html.md b/twitter-client-tutorial/_no_tweet_activity_after_login.html.md
@@ -1,4 +1,3 @@
-# Hooking up Login to 'No Tweet Found' Activity
 
 We created a login button listener which simply updated the button label to 'I am Clicked' from 'Login'. Ideally, post login, the user should be able to see the tweets. We need to create a new Activity for that. Let us just create an empty Activity which showed 'No Tweets found'. 
 
diff --git a/twitter-client-tutorial/_plugin_installation.html.md b/twitter-client-tutorial/_plugin_installation.html.md
@@ -1,4 +1,3 @@
-# Setup Virtual Assistant in 5 minutes
 
 To assist you better during the development cycle, we have created an Eclipse plugin that tests your app at every step to ensure you are doing it right. Our intent is to be able to show you very relevant error messages (& possible solution).
 
diff --git a/twitter-client-tutorial/_reading_tweets_from_file.html.md b/twitter-client-tutorial/_reading_tweets_from_file.html.md
@@ -1,4 +1,3 @@
-# Reading tweets from local file
 
 There are only three lines that are different while reading from a local file as against writing. 
 
diff --git a/twitter-client-tutorial/_shared_pref_modify_login_flow.html.md b/twitter-client-tutorial/_shared_pref_modify_login_flow.html.md
@@ -1,4 +1,3 @@
-# Do not show login screen again
 
 A real twitter app does not show login screen after you have already logged in. On subsequent visits, it directly takes you to the tweet list screen as soon as you open the app.
 
diff --git a/twitter-client-tutorial/_shared_pref_reading_login_data.html.md b/twitter-client-tutorial/_shared_pref_reading_login_data.html.md
@@ -1,4 +1,3 @@
-# Reading Login data from the View 
 
 ## Recap from module 1
 
diff --git a/twitter-client-tutorial/_shared_pref_writing_login_data.html.md b/twitter-client-tutorial/_shared_pref_writing_login_data.html.md
@@ -1,4 +1,3 @@
-# Writing login data to Shared Preference
 
 Shared Preference is a good place to store app-specific data. It is the easiest form of local storage available in an Android app. SharedPreference uses a simple key-value pair format to store and retrieve data. Because it is meant for simple data, SharedPreference does not support storing complex Objects.
 
diff --git a/twitter-client-tutorial/_tweet_detail_data_from_intent.html.md b/twitter-client-tutorial/_tweet_detail_data_from_intent.html.md
@@ -1,4 +1,3 @@
-# Passing data over Intent to Tweet Detail Screen
 
 Each tweet item shows different tweet data. But clicking on a tweet item still shows the same old **activity_tweet_detail.xml** with the data hardcoded in the XML. 
 
diff --git a/twitter-client-tutorial/_tweet_list_dynamic_data.html.md b/twitter-client-tutorial/_tweet_list_dynamic_data.html.md
@@ -1,4 +1,3 @@
-# Dynamic Data for Tweet List Screen
 
 We are done storing login data from previous lessons. It is time to handle data for Tweet List Screen. 
 
diff --git a/twitter-client-tutorial/_tweet_list_dynamic_data_tweet_model.html.md b/twitter-client-tutorial/_tweet_list_dynamic_data_tweet_model.html.md
@@ -1,4 +1,3 @@
-# Creating Tweet Model
 
 ##Recap from module 1
 
diff --git a/twitter-client-tutorial/_tweet_list_dynamic_data_use_tweet_model.html.md b/twitter-client-tutorial/_tweet_list_dynamic_data_use_tweet_model.html.md
@@ -1,4 +1,3 @@
-# Using Tweet Model in ListView
 
 In the previous lesson, we created a Tweet Model. In this lesson, we are going to populate it with dummy data & then use its content to show up on TweetListActivity. 
 
diff --git a/twitter-client-tutorial/_tweetdetail_intent_module.html.md b/twitter-client-tutorial/_tweetdetail_intent_module.html.md
@@ -1,4 +1,3 @@
-# Loading Tweet Detail Activity using Intent
 
 So far you have built a basic Tweet List screen. You also learnt how to attach Click Listener to each List item. As per our plan, you need to load a new Activity with details of the tweet when the tweet item is clicked on the ListView. 
 
diff --git a/twitter-client-tutorial/_tweetdetail_intent_with_data_module.html.md b/twitter-client-tutorial/_tweetdetail_intent_with_data_module.html.md
@@ -1,4 +1,3 @@
-# Passing data to Tweet Detail Activity over Intent
 
 In one of the previous modules, we were simply opening TweetDetail Activity on List item click in TweetList Activity. In this module, we will be passing tweet object over the Intent which is then used to popuplate the TweetDetail Activity.
 
diff --git a/twitter-client-tutorial/_tweetlist_listview_module.html.md b/twitter-client-tutorial/_tweetlist_listview_module.html.md
@@ -1,4 +1,3 @@
-# Implementing TweetList screen using ListView
 
 So far, you learnt to work with relatively simple View elements like LinearLayout, RelativeLayout, TextView, EditText & Button. For building the list of tweet screen, we would be needing a different View element called **ListView**.
 
diff --git a/twitter-client-tutorial/_twitter_data_handling.html.md b/twitter-client-tutorial/_twitter_data_handling.html.md
@@ -1,4 +1,3 @@
-# Twitter Data Handling & Local Storage
 
 We have built a Twitter app with three screens so far. It is just the User Interface. As we mentioned earlier, the first step of app development is to design the interface. We could add more screens, but let's just stick to the three screens - Login, Tweet List & Tweet Detail - that we have built & focus on handling data, storing it locally & updating it as & when needed. 
 
diff --git a/twitter-client-tutorial/_writing_tweets_to_file.html.md b/twitter-client-tutorial/_writing_tweets_to_file.html.md
@@ -1,4 +1,3 @@
-# Serializing & writing to local file
 
 ** Writing to a local file **
 
diff --git a/twitter-http-challenge/_import_codelearn_project.html.md b/twitter-http-challenge/_import_codelearn_project.html.md
@@ -1,4 +1,3 @@
-# Import Codelearn Twitter Challenge Project
 
 In the previous level, we installed Codelearn Eclipse Plugin.
 
