Recent changes to Program Structure Planning

WikiPage Program Structure Planning modified by Samuel Jaeschke

Samuel Jaeschke — Thu, 01 Mar 2012 15:43:24 -0000

--- v5 
+++ v6 
@@ -27,13 +27,17 @@
 ---
 Using objects, just one possibility:
 
-- `Realm = Vector` (this vector is the top parent)
-    + `Courses = Vector` (the 4 or so selected by the user)
+- `Realm = Vector`
+    + `Courses = Vector` *(the 4 or so selected by the user)*
         * `Title`
         * `Classes = Vector`
-            -`Times = Vector` (timeslot options for each class)
+            -`Times = Vector` *(timeslot options for each class)*
 - `Workspace = Vector
-    + `Timetables_Generated = Vector` (possible timetables available)
-        * `Rank` (index)
-        * `Class_List = Vector<*Time>` (class times that make up the timetable)
-    + `Timetable = *Timetable` (pointer to selected timetable)
+    + `Timetables_Generated = Vector` *(possible timetables available)*
+        * `Rank` *(index)*
+        * `Class_List = Vector<*Time>` *(class times that make up the timetable)*
+    + `Timetable = *Timetable` *(pointer to selected timetable)*
+
+Language
+---
+I'm thinking C++ is a good idea, since it'll be most versatile. Once we have the binary we can compile it as a library for practically anything else. Also probably the most portable between architectures, without assuming a particular interpreter. And just generally most solid and stable and what we're all familiar with.

WikiPage Program Structure Planning modified by Samuel Jaeschke

Samuel Jaeschke — Thu, 01 Mar 2012 15:37:39 -0000

--- v4 
+++ v5 
@@ -7,33 +7,33 @@
 
 - Scraper
 - Timetabler
-    - Enumerator
-    - Evaluator (discard any that contain clashes)
-    - Ranker
+    + Enumerator
+    + Evaluator (discard any that contain clashes)
+    + Ranker
 - Interface
-    - CLI
-    - GUI (Qt?)
-    - ncurses?
-    - PHP? (even if it is simply a frontend interfacing with a C++ binary)
+    + CLI
+    + GUI (Qt?)
+    + ncurses?
+    + PHP? (even if it is simply a frontend interfacing with a C++ binary)
 - Output (just a thought, if we want to get fancy)
-    - Print
-    - iCal
-    - Email
-    - Applicator (automatically enter into Access Adelaide; Rob's code will help)
+    + Print
+    + iCal
+    + Email
+    + Applicator (automatically enter into Access Adelaide; Rob's code will help)
 
 Ideally we'll keep these very modular, in which case we'll practically need an API between each. That way we can potentially develop multiple enumerator algorithms for example (better optimised ones later on) and easily swap them in. Also leaves the possibility to add scrapers for other unis (one of my Software Engineering mates at UniSA would be keen), and different interfaces (as above).
 
 Data Structure
 ---
 Using objects, just one possibility:
 
 - `Realm = Vector` (this vector is the top parent)
-    - `Courses = Vector` (the 4 or so selected by the user)
-        - `Title`
-        - `Classes = Vector`
+    + `Courses = Vector` (the 4 or so selected by the user)
+        * `Title`
+        * `Classes = Vector`
             -`Times = Vector` (timeslot options for each class)
 - `Workspace = Vector
-    - `Timetables_Generated = Vector` (possible timetables available)
-        - `Rank` (index)
-        - `Class_List = Vector<*Time>` (class times that make up the timetable)
-    - `Timetable = *Timetable` (pointer to selected timetable)
+    + `Timetables_Generated = Vector` (possible timetables available)
+        * `Rank` (index)
+        * `Class_List = Vector<*Time>` (class times that make up the timetable)
+    + `Timetable = *Timetable` (pointer to selected timetable)

WikiPage Program Structure Planning modified by Samuel Jaeschke

Samuel Jaeschke — Thu, 01 Mar 2012 15:35:29 -0000

--- v3 
+++ v4 
@@ -1,4 +1,4 @@
-Thought i'd get down some comments and elementary structure (largely based on [Jacob's ideas](http://www.facebook.com/jacob.shearer/posts/3489558763508)).
+Thought i'd get down some thoughts and elementary structure (largely based on [Jacob's ideas](http://www.facebook.com/jacob.shearer/posts/3489558763508)). Please comment :)
 
 Program Components
 ---

WikiPage Program Structure Planning modified by Samuel Jaeschke

Samuel Jaeschke — Thu, 01 Mar 2012 15:35:03 -0000

WikiPage Program Structure Planning modified by Samuel Jaeschke

Samuel Jaeschke — Thu, 01 Mar 2012 15:34:37 -0000

--- v1 
+++ v2 
@@ -1,30 +1,32 @@
-Thought i'd get down some comments and elementary structure (largely based on [Jacob's ideas](http://www.facebook.com/jacob.shearer/posts/3489558763508)
-
+Thought i'd get down some comments and elementary structure (largely based on [Jacob's ideas](http://www.facebook.com/jacob.shearer/posts/3489558763508)).
+
 Program Components
 ---
 
 We will need:
+
 - Scraper
 - Timetabler
     - Enumerator
     - Evaluator (discard any that contain clashes)
     - Ranker
 - Interface
     - CLI
     - GUI (Qt?)
     - ncurses?
     - PHP? (even if it is simply a frontend interfacing with a C++ binary)
 - Output (just a thought, if we want to get fancy)
     - Print
     - iCal
     - Email
     - Applicator (automatically enter into Access Adelaide; Rob's code will help)
 
 Ideally we'll keep these very modular, in which case we'll practically need an API between each. That way we can potentially develop multiple enumerator algorithms for example (better optimised ones later on) and easily swap them in. Also leaves the possibility to add scrapers for other unis (one of my Software Engineering mates at UniSA would be keen), and different interfaces (as above).
 
 Data Structure
 ---
 Using objects, just one possibility:
+
 - `Realm = Vector` (this vector is the top parent)
     - `Courses = Vector` (the 4 or so selected by the user)
         - `Title`

WikiPage Program Structure Planning modified by Samuel Jaeschke

Samuel Jaeschke — Thu, 01 Mar 2012 15:31:03 -0000

Thought i'd get down some comments and elementary structure (largely based on [Jacob's ideas](http://www.facebook.com/jacob.shearer/posts/3489558763508) Program Components --- We will need: - Scraper - Timetabler - Enumerator - Evaluator (discard any that contain clashes) - Ranker - Interface - CLI - GUI (Qt?) - ncurses? - PHP? (even if it is simply a frontend interfacing with a C++ binary) - Output (just a thought, if we want to get fancy) - Print - iCal - Email - Applicator (automatically enter into Access Adelaide; Rob's code will help) Ideally we'll keep these very modular, in which case we'll practically need an API between each. That way we can potentially develop multiple enumerator algorithms for example (better optimised ones later on) and easily swap them in. Also leaves the possibility to add scrapers for other unis (one of my Software Engineering mates at UniSA would be keen), and different interfaces (as above). Data Structure --- Using objects, just one possibility: - `Realm = Vector` (this vector is the top parent) - `Courses = Vector` (the 4 or so selected by the user) - `Title` - `Classes = Vector` -`Times = Vector` (timeslot options for each class) - `Workspace = Vector - `Timetables_Generated = Vector` (possible timetables available) - `Rank` (index) - `Class_List = Vector<*Time>` (class times that make up the timetable) - `Timetable = *Timetable` (pointer to selected timetable)