Master's Thesis - Computer Graphics and Visualization - TU Delft

More documents

Recommendations

Info

users. The creation includes checking the validation of the module specification, initializing the parameters of this module and drawing the icons of this module. This creation supports dynamic changes. If a module specification is changed or a new module specification is created during the run time of the system, the users can see the modification immediately without restarting the whole Culgi-GPE system. • Delete module: Delete a module in all data structures which record some information about this module. Destroy this module. • Run a user’s program: Run the modules one by one in a specified order. 4.5 The user interface Chapter 3 suggests three models, which are the network editor, the sequence editor, and the concept editor. It also points out that the combination of sequence editor and concept editor will be the solution for the Culgi GPE. Those two models both take modules as the basic building blocks, but different in the processes of user programming. This difference lies in the user interface. This section mainly introduces the implementation of the user interface part. It particularly describes the implementation on the sequence editor and the concept editor. Although the network model is not chosen as the solution, its prototype was also implemented in the beginning of this project. So this chapter introduces a little on implementation of the network model as well. The architecture of the user interface consists of two parts. One is the component Culgi-GPE. It mainly creates the interface for the whole system. The other one is component Model-Interface, which mainly creates the special widgets for different model, and satisfies the particular requirements for different model when executing the operations from users. This component has a class InterfaceBase as the base class of the three model classes: class SequenceInterface, class NetworkInterface and class ConceptInterface. The separation of the layout and the functions from the interface brings the advantage that a new layout can be designed and applied to the system easily. It is also easy to add new models of programming without change the layout of the interface. The function to export the end user applications is also implemented in component “Model-Interface”. Since the implementation about the mechanism described in section 3.6 is not difficult, we will not explain it in detail. In the rest of this section, component Culgi-GPE, SequenceInterface, ConceptInterface and Networkinterface are described separately. 4.5.1 The Component “Culgi-GPE” The role of component Culgi GPE is to build a framework of the user interface. This frame work includes menus, a widget for showing categories, a widget for showing modules, as well as a canvas. Meanwhile, this component also defines the actions of events, and binds these events to the - 34 -
corresponding operations. Figure 4-5 is the interface created by this class. Menu Bar 4.5.2 The Sequence View Module Category Modules Library Canvas Figure 4-5 User interface of the Culgi GPE Class SequenceInterface is used to implement the sequence model. In the sequence model, the canvas is divided into a number of rows, and each row only allows one module instance. This feature brings some new requirements to the system: 1) When a module is expanded or collapsed, the height of the row that this module lies in must be changed. For example, the appearance of a module is changed from view1 to view2, the height of the row should increase at the same time. 2) When a module is expanded, collapsed, or deleted, the position of the rows below this module should be changed as well. 3) If a user creates a new module in the row where another module already exists, the system should cancel the creation and inform the user about the rule of the sequence editor. - 35 -
Page 1: A Graphical Programming Environment
Page 5 and 6: Preface This project started in Sep
Page 7 and 8: Abstract Culgi stands for Chemistry
Page 9 and 10: Contents Abstract..................
Page 11 and 12: Chapter 1 Introduction Culgi stands
Page 13 and 14: elationship model (see Figure 1-3).
Page 15 and 16: Chapter 2 Requirement Analysis This
Page 17 and 18: loop in which users only need to sp
Page 19 and 20: Primary actor: -Simulation Program
Page 21 and 22: Req04 Select a module in the librar
Page 23 and 24: Chapter 3 Design Models In chapter
Page 25 and 26: also generates the same result as (
Page 27 and 28: 3.3 The Concept Editor 3.3.1 Descri
Page 29 and 30: (a) Step1 Build Box Step2 Create Vi
Page 31 and 32: 3.5.1 Multi view of modules In the
Page 33 and 34: 3.5.2 Various widgets to display a
Page 35 and 36: a correct order. These source codes
Page 37 and 38: Chapter 4 Implementation of the Cul
Page 39 and 40: library. Meanwhile, the interface p
Page 41 and 42: For example, in Figure 3-5(b), the
Page 43: The Module Editor is a tool for cre
Page 47 and 48: The second problem is about how to
Page 49 and 50: sequence. From these approaches, we
Page 51 and 52: Chapter 5 Results and Test The prev
Page 53 and 54: (a) Before click. (b) After an item
Page 55 and 56: instance of the module setDPDEnviro
Page 57 and 58: (a) Make only “Oil” visible (b)
Page 59 and 60: Feedbacks from the novices of Culgi
Page 61 and 62: Chapter 6 Conclusion The goal of th
Page 63 and 64: Chapter 7 Bibliography [1] Craig La
Page 65 and 66: Appendix A. Class Diagrams Figure A
Page 67 and 68: Figure A-4 Class Diagram of “Sequ
Page 69 and 70: Appendix B. Tables Table B-1 Functi
Page 71 and 72: Table B-3 Functionalities of Class
Page 73 and 74: Table B-5 Functionalities of class
Page 75 and 76: Table B-7 Properties of input param
Page 77 and 78: Appendix C. DPD Simulation # DPD Si
Page 79: $plot SetSize 400 400 $plot Load My

Master's Thesis - Computer Graphics and Visualization - TU Delft

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?