309 Project Presentation (1st Week) We should talk about ...

looneyvillestaticSoftware and s/w Development

Aug 15, 2012 (5 years and 2 days ago)

251 views

309
Project Presentation (1
st

Week)

We should t
alk about the following:

Walkthrough

(X minutes)

1.

High level explanation of how there are two main “views”

of the program

o

E
ach
“view”
has
o
wn supplemental view tied to it (Document Options,
Palette/
QuestionEditor combo)

o

Each “view” loosely defined by a single Netbeans RCP Module



Generally contains all of the logic about that view.

2.

Also have 2 other

3.

Load up program (have it on a laptop, have already loaded it up before)

4.

Open up Student Crisis Quiz or

whatever

5.

Two views


Doc and Design

o

Start in Design view


I’m sure you’re all familiar with ilt

o

List of questions to add (we use a palette, groom will talk about that later)

o

Question editor is filled with a panel depending on what question type you want
to
make



Daniel will talk about how that’s done

o

Questions added go into the central JTable

o

Exam Elements (generalized form of questions and design elements) are fully editable

o

Randomize, drag and drop movements, even d
-
n
-
d from Palette (that was a bitch)

o

Re
sizable everything


boundary b/w QEditor, Pallete, JTable



Also movable


check it out!

o

Now, we have some questions here
, some design elements, they interact nicely, but
how do they show up in the PDF?

6.

Design view time, bichez.

o

First off, the PDF



This uses

a couple of different libraries, Daniel is going to talk about those later



The PDF renders quickly, and renders all changes made to the exam



All of the styling you see here is done with CSS magic, courtesy of Justin and
Daniel



Document Options allows for
changes to how the questions are displayed



These change the CSS rules, and make it so that they saved file is as
small as possible by only storing the necessary CSS rules

Modular Structure

(X minutes)

-

Justin

Class Diagrams

(X minutes)



Daniel


Refactori
ng Plans

(X minutes)

-

Design view should be default

-

Split up DesignView module

-

Document Options GUI needs to be refactored to be more easily modifiable.

APIs

(X minutes)

Walkthrough/demo

Modular design

APIs used

Class designs of each module

Specific topics
we need to hit: (while we’re in class diagrams)


Properties to CSS mapping


Singleton Exam class


Palette


Question Editor “framework”


Observer/Observable


Font Formatting


XML/PDF storage, usage

Design Rationales


Everything based around XML/CSS/PDF


Document Options


Persistence of Exam


Exam storage


toXML in specific modules

Refactoring Plans


M
-
VC to M
-
V
-
C


DesignView module needs to be split


XMLUtility class is a god class


DesignViewTopComponent is a god class