Project Demo(Chrome): https://motion.michaelsault.ca/
uOttawa - Comp. Sci. Honours Project (Continued Consultation)
Supervised by: Dr. Wonsook Lee
Contributors: Talaal Mirza, Michael Sault
- User Interface to Load New Images (IMPORTANT)
- Users can move images into the "media" folder to be selected
- Without PHP users must manually add items to the list
- Offer to add more commonly used images to list by defult
- Change video type (OPTIONAL)
- If possible within the WebRTC library
- Fix video output size (IMPORTANT)
- Output is far to big on small screens.
- Also managed to fix the issue with animating along the path
- Fix bug where image won't resize. (IMPORTAT)
- May have to remove/limit mutiple images or keyframe implementation
- Generate User Manuals/Videos (OPTIONAL)
- Might have to meet with the profs one more time
- Completed a tutorial page demonstarting the basics of recording a path
~~## TODO (HONOURS PROJECT)
- User animation
- Allow user to create paths for images to follow using mouse input
- Animation/state saving
- Allow user to save travel paths as well as image configuration
- Create page
- Create more tasks
[ ] Create Trello board?It's just me now, no need.
- Implement moving images
- Implement scaling images
- Implement changing images
- Implement rotating images
- Map movement, scaling and rotations to key presses
- Verify installation/build process
- Verified that p5.js needs a "live" server for accessing the images; Updated README accordingly
-
Investigate standalone options From what I understand we will be providing this tool for WYSISWYG use so we should maybe look into creating a packaged solution that doesn't require the use of running a server. This might require moving to Processing java or Processing.pyMoving to Processing java/python too time consuming.
- Update README accordingly
- Investigate moving to a package manager?
- Document the code
- Organize the code better (less global vars, better scoping)
-
Develop proper task organizationWe shouldn't be just pushing to master. I propose that we create individual tasks; For each task that gets worked on individual branches; For each branch that has its task completed we create Pull requests and have the other collaborator review them. This way we can better organize the changes that get pushed throughWe were, but again it's just me here and if it's not ready, I won't push it.-
Added branch rule to master. Changes now require pull requests.Left over from before.
- Clone the repo and follow the instructions in side the
/lib/README.md - In order to run this code you will need a live server
- One option is to use visual studio code to open the code and use the extension Live Server
- Another option is to use browser apps/extensions to run a local server
- Chrome: Web Server for Chrome
- Some more involved options may require python or php. How-to's for those are available on: