Posts

Showing posts from August, 2020

Basic Oops Concepts

  Oops means Object Oriented Programming System           Object-oriented programming (OOP) is a programming paradigm that uses “Objects “and their interactions to design applications and computer programs. Basic Oops concept are: Object Class Data Abstraction & Encapsulation Inheritance Polymorphism Dynamic Binding Message Passing 1) Object : Object is the basic unit of object-oriented programming. Objects are identified by its unique name. An object represents a particular instance of a class. There can be more than one instance of an object. Each instance of an object can hold its own relevant data. An Object is a collection of data members and associated member functions also known as methods. For example whenever a class name is created according to the class an object should be created without creating object can’t able to use class. the class of Dog defines all possible dogs by listing the characteristics and behaviors they can have; the object Lassie is one particular dog,

Merge Adapter sequentially with Merge adapters

  Merge Adapter is a new feature introduced in recyclerview:1.2.0-alpha02, that allows us to sequentially club multiple adapters. This offers more encapsulation and reusability, rather than combining several data sources into one adapter. In this post, you can learn how to use Merge Adapter and some other useful stuff, such as how to make effective use of the view pool through adapters. Now the Android team has launched the latest recycle rview update. To use Merge Adapter, upgrade the version of the recyclerview library to 1.2.0-alpha02, or add the following line in the build.gradle file under the dependency tag: Addictions Using 'androidx.recyclerview: recyclerview:1.2.0-alpha02' } To support us android, a new concept for merging data adapters has been developed. They have recently launched a new Recyclerview package:1.2.0-alpha02. This kit has a new class called Merge Adapter as the name means that it enables you to combine multiple data adapters into a single recycl

Android Architecture: Communication between ViewModel and View

Image
  Introduction There’s been a lot of talk about MVVM architecture since Google announced architecture components last year at I/O and so many developers who preferred Presenters (including me) have started to accept the ViewModel world. Using ViewModels (over Presenters) reduces boilerplate code, manages data during configuration change, makes it easy to share data between multiple fragments. However, it does make communication with Views much harder. To learn complete android course visit: android online training Problem Let’s take an example of Edit Profile screen. User data must be validated before sending to server, which means Presenter/ViewModel should be able to show/hide progress indicator, send validation and server errors (if any) to the View. Also if city/gender dialog is visible during configuration change then View should be notified about that as well. Presenters and ViewModels shouldn’t hold references to Views. In case of Presenter we usually define some sort of Contrac

Android Animations and Explain with Example

  Animations can add visual hints to notify users of what's happening in your app. These are especially useful when the state of the UI changes , for example when new content loads or new actions become available. Animations also add a polished look to your app which gives it a look and feel of higher quality. Android includes various animation APIs depending on the type of animation you want, so this page provides an overview of how you can add movement to your UI,more info visit: android app development course Bitmaps animate You should use the drawable animation APIs when you want to animate a bitmap graphic like an icon or an illustration. Normally such animations are dynamically defined with a drawable tool, but at runtime you can also specify the actions of the animation. Animating a play button turning it into a pause button when pressed, for example, is a pleasant way to demonstrate to the user that the two actions are connected, and that pressing one makes the other visibl