1 / 13

Lab 9: Code Organization

This lab session focuses on effectively organizing code and designing user interfaces, emphasizing modularity and object-oriented principles. Key announcements include the completion of Homework 2 and submission of project proposals, with feedback expected by Saturday. We delve into the separation of concerns and the benefits of modular code, explaining how to utilize ActionScript and MXML components in your projects. Additionally, we cover the importance of class diagrams for visualizing module design and dependencies, providing a foundation for creating well-structured software applications.

hisoki
Télécharger la présentation

Lab 9: Code Organization

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Lab 9: Code Organization User Interface Lab: GUI Lab October 23rd, 2013

  2. Class Announcements • Hw2- Finished! • Project Proposals- Submitted! • Feedback by Saturday • Project Design Documents- due next week

  3. Code organization • Making your code modular • Allows for: • Code reuse • Clearer and cleaner code • Separation of concerns

  4. Code organization • Separating your project into modules • actionscript classes, MXML components • Should be able to swap out one module for another • Key: figuring out which module to write

  5. Organization of Modules • Object-oriented programming • Think of classes as real-world objects • MXML vs. Actionscript • MXML components are items on the screen • Actionscript files define interactivity in the app

  6. Example: Angry Birds

  7. Class diagrams • Describe the design of the modules (classes) and the dependencies between them • Very useful for communicating your program design to others • Also helps you finalize the structure of your program

  8. Class diagram • Rectangles represent classes • Important variables, functions • Some class diagrams use plus and minus sign to represent accessibility • Arrow lines represent inheritance • CheckingAccountextends BankAccount • Dash arrow lines represent implementation • GUI_SmileyimplementsGUI_Shape

  9. Design pattern • Reusable software strategy that can help solve common problems in software design • Not a solution, but a guide • A description or template for how to solve a problem • Many design pattern help create modular code

  10. MVC (model-view-controller) • Model: store the data & state and let components know when something changes • View: show the Model’s data to user in a visual form (UI components on the screen) • Controller: interpret the user actions on the view and update model (usually an event handler) • Separate application logic from the interface

  11. controller select view update model based on user input user input model view data & state changes http://cookbooks.adobe.com/post_Simple_MVC_for_Flex_and_AIR-16199.html

  12. MXML vs. actionscript • When do you write an actionscript class versus an MXML component? • MXML for visual components • Actionscript for non-visual components

More Related