A note about the view binding feature (Android Studio 3.6+) Since Developing Android Apps with Kotlin has launched, a new feature, view binding, has been introduced and is available in Android Studio 3.6 and higher. We don't use view binding because it came out after the course, but it's a feature to be aware of. View binding replaces findViewById . View binding generates a binding object for each XML layout. You use this binding object to reference views, using their resource ids as the name: // Creating a binding object for the main_activity.xml layout binding = ActivityMainBinding . inflate ( layoutInflater ) // Referencing a view with the ID roll_button binding . rollButton View binding has the following benefits over findViewById : Type safety - findViewById requires you to specify the type of view you expect to be returned. For example, if you accidentally specify that you expect an ImageButton to be returned when the a...
Goals: Learn about: - What reliability and availability are? - How device faults can result in failures? - What can we do to make a computer work fine even when parts of it have failed? Dependability : It's the quality of delivered service, meaning a characteristic of delivered service that justifies relying on the system to provide that service. Specified Service: what is the behavior of the system should look like Delivered Service: Actual behavior. The behavior that we actually got out of the system. System has components (modules): Each module has an ideal specified behavior that should be ideally getting. So each module has some sort of ideal behavior that we will want to expect for it, but of course, real modules maybe not always exhibit this ideal behavior. So when we talk about things that make the system not be dependable, we're really taking about modules deviating from specified behavior and that causing the system to deviate, so that the delivered ser...
Comments
Post a Comment