Prefinals

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/24

encourage image

There's no tags or description

Looks like no tags are added yet.

25 Terms

1
New cards

Framework

  • is a well defined environment that exposes toolkit, functions or algorithms that can be used to develop new applications.

  • contains specific structure for creating applications, building executable versions of applications, and sometimes includes mechanism for deploying/running an application.


2
New cards

Toolkit

  • is a library of precomposed UI objects and predefined set of events or routines that are composed from the lower level UI software layer.

  • also promotes the creation of an interface with a consistent look, feel, and mechanism.


3
New cards

Widget

  • essential part of a graphical user interface (GUI) that displays information or provide a specific way for users to interact with the operating system or application

  • includes icons, menus, buttons, selection , and text boxes, and etc.


4
New cards

Android UI execution Framework and Toolkit

  • is based on java

  • event processing model and programming toolkit are mostly the same as Java AWT


5
New cards

What Android UI execution Framework and Toolkit provides

  • rich and extensive view system that is used in building an application user interface

  • resource manager which provides access to non code resources such as localized strings, graphics, and layout files.

  • Notification manager that enables all applications to display custom alerts in the status bar

  • activity manager that manages the lifecycle of applications

  • content provider that enables applications to access data from other applications.


6
New cards

iOS UIKit Framework and Toolkit

  • has 3 types of discrete events for iOS

    • multi-touch, motion, and remote control

  • other feature offered are animation support, document support, drawing and painting support, information about the current device, text management and display, search support, accessibility support, app extension support, and research management.


7
New cards

what the iOS UIKit Framework and Toolkit provides the following required infrastructure

  • implementing interfaces

  • event handling infrastructure for delivering multi-touch and other types of input to the applicaiton

  • main run loop needed to manage interactions among the user, system, and application


8
New cards

JavaServer Faces (JSF) (Web UI Framework)

  • supported by Oracle

  • comes with in-depth and complex documentation features and plays an important part in the Java Enterprise Edition


9
New cards

Struts (Web UI Framework)

  • open-source framework that is used to create elegant, aesthetically pleasing Java applications.

  • functions are based on the Model-View-Controller (MVC) approach

  • made for fast development and testing but is not flexible due to a set of coding and designing rules


10
New cards

Wicket (Web UI Framework)

  • supported by Apache Software foundation

  • lightweight web framework built for designing simple but elegant application in a component-based language that is useful and responsive

  • HTML can be easily integrated


11
New cards

Spool UI Kit (Mobile UI Kits iOS and Android)

  • free mobile toolkit designed by Sergey Melnik that contains 6 screen designs in Photoshop Document (PSD) format.


12
New cards

Travel UI Kit (Mobile UI Kits iOS and Android)

  • free mobile toolkit designed by Ena Bacanovic that contains 50 different screen designs in Sketch format


13
New cards

Splash UI Kit (Mobile UI Kits iOS and Android)

  • powered by Envato Elements Pty Ltd.

  • one of the best toolkits in creating iOS mobile application

  • contains more than 55-high quality, ready to use screen


14
New cards

Java Abstract Window Toolkit (AWT)

  • includes useful classes creating two-dimensional user interface and graphical objects.

  • also a part of the UI execution framework for java that handles a large subset of interaction events called AWTEvents.


15
New cards

AWTEvents

  • descendants of EventObjects which cover most of the useful UI events such as a mouse click and keyboard input


16
New cards

AWT support GUI with these features

  • set of native user interface components

  • robust event-handling model

  • Graphics and imaging tools, including shape, color, and font classes

  • Data transfer classes for cut-and-paste through native platform clipboard

  • layout managers for flexible window layouts that do not depend on a particular window size or screen resolution


17
New cards

Interactive System development framework

  • pertains to an established modular approach for interactive program development where the core computation and interface parts are developed in a modularization method and are combined flexibly

  • this kind of development is often based on the UI toolkit which provides the abstraction for the interface part


18
New cards

Model-view-controller (MVC) framework


  • also known as MVC architecture

  • a well known three-layer framework used in developing and implementing user interfaces especially web application.


19
New cards

Smalltalk

  • designers of a programming language, that proposed the MVC approach as a computational architecture for interactive programs, rather than a methodology.

  • one of the first object-oriented and modular languages in the programming history


20
New cards

Model: Data and Logic

  • specifies the logical structure of data and the associated high-level classes in software application

  • is a domain-specific representation of the data that describes the processes in an application.

  • when a model changes its state, the domain notifies its associated views to refresh.

  • ex. interactive banking application, maintains the balance, computes the interest, makes wire transfer.


21
New cards

View: Interface

  • involves all the UI logic in a software application, which also presents the application’s users interface as an output.

  • renders the model into a form that is suitable for user interaction

  • multiple views can also exist for a single model but for different purposes

  • for GUI implementation of views is commonly through widgets

  • ex. interactive banking, might be the windows and widgets that display the list of all possible transactions and the balance of a given account.


22
New cards

Controller: User Input

  • serves as an interface between the model and the view components

  • processes all the business logic and incoming requests and input, manipulates data using the model component and interacts with the views to render the final output of a software application.


23
New cards

Advantages of MVC Framework

  • faster development process through parallel development of all MVC component

  • Can provide multiple views for a single model because of the separation of data and business logic from the display

  • modification does not affect the entire framework because the model component does not depend on the views component

  • return data framework without applying any formatting so that components can be used many times for different interfaces

  • East to develop and SEO-freindly uniform resource locator (URL) to generate more visits from a specific application

  • supports the test-driven development approach


24
New cards

Disadvantages of MVC framework

  • inefficiency of data access in view because of minimal code duplication

  • difficulty of implementing MVC framework with mdoern user interface involving different modalities

  • Programmers/Developers must be knowledgeable about the business process linked to the application development for each MVC component


25
New cards

MVC implementation

Step 1: browser sends a request to the MVC application

Step 2: incoming request is directed to the controller

Step 3: Controller processes the request based on the data model of the application

Step 4: result of the model component is passed to the appropriate view

Step 5: view component renders the result into a form suitable for user interaction.


<p>Step 1: browser sends a request to the MVC application</p><p>Step 2: incoming request is directed to the controller </p><p>Step 3: Controller processes the request based on the data model of the application </p><p>Step 4: result of the model component is passed to the appropriate view</p><p>Step 5: view component renders the result into a form suitable for user interaction.</p><p></p>