Tasking for next milestone!
Big milestones:
1. Ability to edit music
Data structure
Drag notes around staff
Saving and opening from server
2. Conductor (network and local)
Line up beats (not pitches) – synching and threading
Save to MIDI on server
3. Jam session of doom!!!!
How to break this down into smaller, more manageable milestones?
- For the view group, need to have an idea of how the GUI will be laid out
- For the model group, to be able to load a midi file, mess with it, and save it back
oDr. Wong’s suggestion – “Google, midi, C#, I already have code to do that
that I DID NOT write.”
- for the networking group, getting the basic client-server protocols working,
sending data, etc, like the chat program
osome of the interfaces from the chat program need to be changed
owants to take a different approach from the Java design patterns we used
o“Chat program has sockets with raw data going through, that’s about as
fast as you can get”
oMap out the different networking subsystems, client-to-server vs. client-
to-client
o“Test the smallest pieces possible, as soon as possible.”
oNeed to think about multicasting, even though it involves working with
the IT department
Need to be aware of little issues like running at slowest available
speed
- networking & model group need to have short-term research tasks so they can
come up with milestone for next Friday.
oWill be meeting in the next few days
- hopefully, by Sunday, milestone tasks will be set
-need to have a spec for what we are going to deliver, since that’s what the
customer wants on Monday
owould give us some idea of what we are researching
owill be putting this together on SUNDAY 3pm
othese are the main features of the program:
play
record
edit
stylus gesture input for composition, but not for a live jam session
– have keyboard shortcuts instead
