design: Start thinking about the GUI

I still have some back-end work to do first, but I should start thinking
out what users will see.

Signed-off-by: Anna Schumaker <schumaker.anna@gmail.com>

design.txt

@@ -28,6 +28,8 @@ Files:
 	/usr/lib/ocarina/
 	ocarina/
 		design.txt
+	ocarina/gui/
+		*
 	ocarina/include/
 		audio.h
 		database.h
@@ -743,6 +745,22 @@ Preferences: (lib/prefs.cpp)
 
 
 
+Gui: (ocarina/*)
+	The GUI will be written in C++ using gtkmm3 for (hopefully) cleaner code.
+
+- Design requirements:
+	- gtkmm3
+	- Front-end for the library to add, remove and modify paths
+	  - This can be hidden since it's not a common task
+	- Double-click to play songs
+	- Front-end for groups to add and remove tracks
+	  - This is a common task and should not be hidden
+	- Don't save / restore window size
+	  - Some window managers already do this automatically
+	  - Set reasonable defaults
+
+
+
 Future work:
 	I want to set reasonable expectations for Ocarina 6 so that I don't
 	have to spend a large amount of time coding before releasing something

design/gui.txt

@@ -0,0 +1,20 @@
+== Files ==
+	ocarina/gui/
+		*
+
+== Depends ==
+idle file prefs
+
+Gui: (ocarina/*)
+	The GUI will be written in C++ using gtkmm3 for (hopefully) cleaner code.
+
+- Design requirements:
+	- gtkmm3
+	- Front-end for the library to add, remove and modify paths
+	  - This can be hidden since it's not a common task
+	- Double-click to play songs
+	- Front-end for groups to add and remove tracks
+	  - This is a common task and should not be hidden
+	- Don't save / restore window size
+	  - Some window managers already do this automatically
+	  - Set reasonable defaults