159.407 - Object-Oriented Software Engineering
Group Projects 2009JUF - A User Interface Framework for JavaDale Halliwell & Parul Sharma
IntroductionThe aim of these projects is to design and implement either a relative complex framework, or a component based system. The focus is on reuse. This means two things:
Produce a piece of software to be used by other software. Reuse other software.
Objectives:The framework support the generation of (client side) user interfaces for Java. The framework should work for all objects that follow the Java Bean Specification (so-called Plojos – plain old Java objects). In particular, the framework should be able to build forms “on the fly” that can be used to visualize and edit sets of objects and individual objects. AbstractionsAreas can be arranged in different constellations (fixed, separated by slider, list as list, tree or combobox on top, editor as pop-up, ..). Different containers are possible (plain list, tree). The Look and Feel can be configured. Persistent adapter – how changes are stored (and whether they are stored at all). Whether the form is display only or an editor. Events updating the model can be configured. The list can hold objects of different types. ChallengesFields must be validated (e.g., whether the value in a text field can be parsed into an int). Actions must be disabled/enabled if the become available/unavailable. If there are multiple action triggers (toolbars, menus, popups, keystrokes etc ), they must be kept consistent. Forms must be customised (e.g., if a property is edited in a text field, what is the size of this text field), but strong dependencies should be avoided. What does copy and sort mean for arbitrary objects?