Update README

therajanmaurya · Mar 21, 2018 · 7d65e64 · 7d65e64
1 parent 8911283
commit 7d65e64
Showing 1 changed file with 51 additions and 45 deletions.
diff --git a/README.md b/README.md
@@ -100,47 +100,53 @@ public class SweetErrorInActivity extends AppCompatActivity {
                         getString(R.string.sweet), R.drawable.ic_adb_black_24dp,
                         llSweet, layoutError);
 
-	# Empty UI (1.2)
-        // Need to pass the feature(s) name that is empty and icon image of the feature that you want to show
-	// and your child view that you want hide and layoutError UI to visible. It will handle everything.
-	// See 2nd screenshot above as an example
-         sweetUIErrorHandler.showSweetEmptyUI(getString(R.string.sweets), R.drawable.ic_adb_black_24dp,
-                        llSweet, layoutError);
-
-
-	# Error UI (1.1)
-        // Need to pass the feature name in which error occured and
-	// your child view that you want hide and layoutError UI to visible. It will handle everything.
-        sweetUIErrorHandler.showSweetErrorUI(getString(R.string.sweets), llSweet, layoutError);
-
-	# Error UI (1.2)
-        // Need to pass the feature name in which error occured and image that you want to show like 
-	// bad internet connection image etc.
-	// your child view that you want hide and layoutError UI to visible. It will handle everything.
-        sweetUIErrorHandler.showSweetErrorUI(getString(R.string.sweets), R.drawable.ic_no_network llSweet, layoutError);
-
-	// Use this button click to refresh UI if any error occured or any Network issue occured.
-	Button btnTryAgain = findViewById(R.id.btn_try_again);
-
-	# No Network I UI (1.1)
-        // Need to pass your child view that you want hide and layoutError UI to visible. It will handle everything.
-	// It will look like above 4th screenshot.
-        sweetUIErrorHandler.showSweetNoInternetUI(llSweet, layoutError);
-
-	# Custom Error UI (1.1)
-        // Need to pass Image that will show up at the top of title and
-	// the title text that will show bottom to the image and subtext that will show in bottom of title text.
-	// and your child view that you want hide and layoutError UI to visible. It will handle everything.
-         sweetUIErrorHandler.showSweetCustomErrorUI(getString(R.string.no_sweets_found),
-                        getString(R.string.come_later_again), R.drawable.ic_adb_black_24dp,
-                        llSweet, layoutError);	
-
-	# Custom Error UI (1.2)
-        // Need to pass Image that will show up at the top of title and subtitle of error message.
-	// the title text that will show bottom to the image and there will be no subtext, only image and error text.
-	// and your child view that you want hide and layoutError UI to visible. It will handle everything.
-         sweetUIErrorHandler.showSweetCustomErrorUI(getString(R.string.no_sweets_found), R.drawable.ic_adb_black_24dp,
-                        llSweet, layoutError);	
+
+		# Empty UI (1.2)
+		// Need to pass the feature(s) name that is empty and icon image of the feature that you want to show
+		// and your child view that you want hide and layoutError UI to visible. It will handle everything.
+		// See 2nd screenshot above as an example
+		 sweetUIErrorHandler.showSweetEmptyUI(getString(R.string.sweets), R.drawable.ic_adb_black_24dp,
+				llSweet, layoutError);
+
+
+		# Error UI (1.1)
+		// Need to pass the feature name in which error occured and
+		// your child view that you want hide and layoutError UI to visible. It will handle everything.
+		sweetUIErrorHandler.showSweetErrorUI(getString(R.string.sweets), llSweet, layoutError);
+
+
+		# Error UI (1.2)
+		// Need to pass the feature name in which error occured and image that you want to show like 
+		// bad internet connection image etc.
+		// your child view that you want hide and layoutError UI to visible. It will handle everything.
+		sweetUIErrorHandler.showSweetErrorUI(getString(R.string.sweets), R.drawable.ic_no_network llSweet, layoutError);
+
+
+		// Use this button click to refresh UI if any error occured or any Network issue occured.
+		Button btnTryAgain = findViewById(R.id.btn_try_again);
+
+
+		# No Network I UI (1.1)
+		// Need to pass your child view that you want hide and layoutError UI to visible. It will handle everything.
+		// It will look like above 4th screenshot.
+		sweetUIErrorHandler.showSweetNoInternetUI(llSweet, layoutError);
+
+
+		# Custom Error UI (1.1)
+		// Need to pass Image that will show up at the top of title and
+		// the title text that will show bottom to the image and subtext that will show in bottom of title text.
+		// and your child view that you want hide and layoutError UI to visible. It will handle everything.
+		 sweetUIErrorHandler.showSweetCustomErrorUI(getString(R.string.no_sweets_found),
+				getString(R.string.come_later_again), R.drawable.ic_adb_black_24dp,
+				llSweet, layoutError);	
+
+
+		# Custom Error UI (1.2)
+		// Need to pass Image that will show up at the top of title and subtitle of error message.
+		// the title text that will show bottom to the image and there will be no subtext, only image and error text.
+		// and your child view that you want hide and layoutError UI to visible. It will handle everything.
+		 sweetUIErrorHandler.showSweetCustomErrorUI(getString(R.string.no_sweets_found), R.drawable.ic_adb_black_24dp,
+				llSweet, layoutError);	
     }
 ```
 
@@ -168,10 +174,10 @@ public class SweetErrorInFragment extends Fragment {
         justiceUIErrorHandler = new JusticeUIErrorHandler(getActivity(), rootView);
 
         // Now you are all set. Whatever error UI you want to show according to condition like
-	// you can use rest of things as we are using in above activity.
-	
-	// Use this button click to refresh UI if any error occured or any Network issue occured.
-	Button btnTryAgain = rootView.findViewById(R.id.btn_try_again);
+		// you can use rest of things as we are using in above activity.
+
+		// Use this button click to refresh UI if any error occured or any Network issue occured.
+		Button btnTryAgain = rootView.findViewById(R.id.btn_try_again);
 
         return rootView;
     }