![]() Since Activity represents an interactive screen, it must gracefully handle a variety of events that affect the screen. When we click on a contact’s name, we load a new Activity that shows a history of our conversation with the contact. A messaging app, for example, will probably have an Activity that lists each contact that we have texted. We define each screenful of user interaction in our app as a subclass of Android’s Activity class. Let’s get started by introducing two key actors in every Android app: the Activity class and layout resources. On a quarter sheet of paper to be turned in at the beginning of the next class, write down 3-4 questions, concerns, or observations you encountered during your reading, watching, and project planning.If you want to claim this achievement, the post must appear on Slack before Saturday. One possible achievement is to share a post on Slack describing a plan for your app, with hand-drawn or wireframe mockups of your screens. Marks on this project are based on achievements rather than as a percentage of some ideal performance. In the near future-but at your convenience-watch some tutorials on ConstraintLayout, starting with Build a Responsive UI with ConstraintLayout. We won’t be going into exhaustive detail on ConstraintLayout during lecture.Run the example on a real device if you have one, but the emulator is fine too. Work through the Build Your First App tutorial.We will write a few today: one to emit Morse code’s dots and dashes and one to show the time in two different timezones.īefore we forget, here’s your TODO list for next time: Now that we’ve examined Kotlin as a standalone language, it’s time to write our first Android apps. Filed under lectures, semester1-2019, seng440. SENG 440: Lecture 3 – Activities and Layoutsįebruby Chris Johnson. » SENG 440: Lecture 3 – Activities and Layouts teaching machines ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |