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

More documents

Recommendations

Info

4.1.2 Architecture The whole system consists of four components: the user interface, the kernel, modules, and the module library, as shown in Figure F4-1(a). The main functions of each component are explained below. • A module is a building block of a program. Each module is declared in a specification file. • The module Library is a library that contains all modules’ specification files. • The kernel is the core of Culgi GPE. The main tasks of the Culgi GPE are done in the kernel. The kernel receives the commands from interface and operates on the modules including create a module instance, delete a module instance, run a user’s programs and so on. • The user interface is the GUI of the whole system. It shows all the commands, functionalities, the useful entities in a visual way for the users. Meanwhile, it waits for the events from users, and then responds to the events by passing the corresponding commands to the kernel. Users The Culgi GPE User Interface Tcl Interpreter Module Library Kernel Module (a) (b) Figure 4-1 Diagram of the high-level architecture of the Culgi GPE Culgi.D LL From this architecture, the whole system can be divided into three packages, as can be seen from figure F4-1(b).When the whole system is running; the user interface is waiting for actions from the user. If the action is a defined event, the user interface will call the corresponding operation. Most operations can not be done only at the interface level. The user interface will pass a command to the kernel. The kernel has the connection with the Tcl Interpreter, the module as well as the module library. It will pass a command to a specific component. With this architecture, the whole system can be extended to another library if modules are made on that - 28 -
library. Meanwhile, the interface part can be changed without changes in the functions of the kernel and the module. That is to say, a whole new interface can be designed for the system freely without the consideration on the internal structure of the kernel. The rest of this chapter introduces these four components individually. 4.2 Module This section introduces Component Module in the architecture. It first introduces the basic components and functions of a module in section 4.2.1. Then it shows the module specification in 4.2.2. 4.2.1 Module implementation A module is a primitive building block, consisting of a user program. It has two main properties. One is that the content of this module contains several lines or only one line of Tcl script. This script usually needs arguments as input, and returns a value as the output. The other property is that it must have a GUI so that users can see the module and can manipulate it. That is to say, this GUI will not only be a visible widget but also be able to interact with users. To support these two properties, a module should be designed to have four components: input parameters, output, the source code container, and the GUI, as shown in Figure 4-2. The input parameters record the arguments of the source code in this module; the output records the return value after the execution of the source code in this module; the source code container keeps the source code; and the GUI is an interface with which users can manipulate this module. Meanwhile operations on these parts are also needed for users to control the module, such as setting the values of the parameters and executing the source code of this module. Input parameters Output Source Code GUI A Module Figure 4-2 Necessary parts of a module Vary in different modules Same in different modules In different modules, only the contents of the input parameters, the output and the source code container should be different from each other (because the source codes of modules are different); the GUIs for each module and the operations on these components should be the same. For example, the operation of executing the source code of a module is independent to the content of the source code. - 29 -
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: Chapter 4 Implementation of the Cul
Page 41 and 42: For example, in Figure 3-5(b), the
Page 43 and 44: The Module Editor is a tool for cre
Page 45 and 46: corresponding operations. Figure 4-
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

Create successful ePaper yourself

Delete template?

Save as template?