-
Notifications
You must be signed in to change notification settings - Fork 7
Alpha Release Task List
Roger B. Dannenberg edited this page Jul 1, 2020
·
81 revisions
The following are what we decided are necessary for an initial release:
- Owner: Ziyi, Manuel
- Requirements:
- Working Icons only
- If you create a project without logging in, then log in, your project is deleted. That's just rude. Either
- disable project creation unless you are logged in, OR
- preserve project while unlogged-in user registers or logs in, then allow the project to be saved
- Project is deleted if you move off the project edit page. That's rude. Require confirmation to exit the page if project has been modified.
- Projects page has "Import" button. Do we have an "Export" button? If not, remove the "Import" button.
- Floating view editing region should not have such large margins; maximum width should expand to width allowed by window.
- See issue #47 - Project Editor GUI
- Owner: ?
- Requirement:
- Projects tab should open a drop-down menu:
- New (DONE) -- creates an empty editor window
- Open (DONE) -- opens what is currently called "ProjectMenu," a list of projects with Actions choices of Edit, Share, Copy, and Delete
- Note the addition of "Copy" - this should prompt for a name and description. Equivalent to "Open" followed by "Save As...", but the project is not actually opened in the editor.
- Save (DONE) -- saves the current project from the editor. If user is not editing a saved project, the user is prompted for a name and description.
- Save As... (NOT DONE) -- prompts for a name and description (default to current name with " copy 1", " copy 2", etc. appended) and then saves under the new name.
- Export -- allows user to download a .json representation of the project. This can be imported using the Import menu item.
- Import (NOT DONE) -- prompts to upload a .json file representation of a project and adds it to the list of projects.
- Use Floating View/Use Column View -- changes the view mode to/from floating or columns. (works, but confusing labels)
- (NOT DONE) It would be nice to have recent projects appear in the drop-down menu to allow a single selection to open a recently edited project.
- Projects tab should open a drop-down menu:
- Owner: Amit, Roger
- OSC does not seem to work now. See also Issue #84 for additional work.
- Owner: Kristin + Amit
- Requirement:
- patching should work -- Try hooking up a player to Mixer input.
- patching should be saved and should restore
- delete buttons should all work
- Owner: Kristin
- x0, x1, x2 buttons need outline to show they are buttons.
- Status: Modules Status Table
- Owner: Kristin
- Status: Modules Status Table
- Owner: Roger
- Status: needs outline around speaker icon to show it is a button.
- Status: Needs to be tested to confirm it is complete.
- Audio Configuration: nothing required for Alpha, Ankit looking into what's possible within Web Audio. UPDATE: not much is possible. Probably we want to fix sample rate to 44100. Devices cannot be selected. One thing we could control is suggested latency. The semantics are implementation-dependent, so let's wait and see if we have any high-latency problems or low-latency glitches before trying to "fix" it with user control.
- Owner: none
- Status: This is complete when everything else is complete. It's mentioned here just to remind everyone that we are not implementing a cloud service (yet).
- Owner: Amit & Roger
- Status: ?
- Requirements:
- package that installs monolithic binary to run Soundcool server on local host
- scripts and documentation for Roger to check out and document
- verify_requirments_linux.sh: It will check if the system is missing any requirements
- setup.sh: It covers the complete setup of soundcool project(e.g. mysql,.env, node_modules, etc.)
- launch.sh: It launches the soundcool application
Note: Make sure that the system meets the requirements before running setup.sh Everyone, please use the script and report the errors or improvements it can have. Also, Let me know if you think that we need a script for other functionalities. IMO a script to automatically clean and update the database is necessary.
- Owner: Roger
- Status: Roger wants to test and review documentation. Maybe we're done.
- Owner: Saul
- Status: Do we know of any problems that are particular to Lliurex? Have we tried running on Lliurex?