- () set REVISION const in constants.js set to 'x_dev'
- () I will want a window-main-javascript html file for using a threejs revision by way of three.min.js
- () I will want a window-main-jsm html file for using three.module.js
- () add r91, r146, and r149 (or r150 if out ) for additional threejs revision options
- () add three.min.js for all revision where available
- () add three.module.js for all revisions where available
- () update README to reflect changes made in R9
- () REVISION in constants.js, and package.json set to 9 and commit with message '0.9.0'
- () set REVISION const in constants.js set to 'x_dev'
- () start an plugin system so that I have a way to start creating built in, and optional features
- () see about turning the export by frame feature the first built in plugin
- () start a new repo videoground-plugins that will work as a way to pull down optional plugins
- () have a diolog that can be used to pull up an index of plugins for this repo
- () have it so that more than one github url can be given
- () the first option plugin can be something like a javaScript formatter
- () update README to reflect changes made in R10
- () REVISION in constants.js, and package.json set to 10 and commit with message '0.10.0'
- () set REVISION const in constants.js set to 'x_dev'
- () This might need to be an optional plug in actually
- () see about having a file > Open Recent menu option
I would like remove the old DAE loader that I have in the core ov videoground in favor of having this kind of functionaly as an optional user space module.
- () remove dae loading feature
- () I will see need a way to make sure legacy videos will work if I have a decent plugin system as this time
- () I will need to turn client.js into a module that returns a public API like clientMod
- () have a clientMod.createSM method
- () have a clientMod.setup method
- () have a createSM method in client.js
- () have a clean sm object on each call of
- () set REVISION const in constants.js set to '13_dev'
- () start a /lib/logger/index.js that will be the main logger lib used by all javaScript files
- () have a videoAPI.createLogger funciton that can be used to create a logger for each of the client files
- () I would still like to have an export to frames dialog
- () can click a browse button as a way to set/change export folder
- () see about starting a dialog in menu.js, just getting all the info there and being done with it.
- () use settings.json to store a default folder for exporting frames
- () make the default location in the user data folder
- () create the folder if it is not there
- () set REVISION const in constants.js set to '12_dev'
- () start a file > new option in menu.js
- () use the hard coded start video as the start point for the new video
- () when creating a new file the fileName and filePath vm data object values should be null
- () use videoAPI.saveAsDialog in save event when fileName and filePath vm data object values are null
- () start a file > new from template option
- () have a way to set a templates location in settings.json
- I can add ffmpeg binaries as part of the over all end product and then write scripts to automate work
- I will want bins for each supported os kernal and arch (armhf and i368 Linux, and i386 Win 10)
https://johnvansickle.com/ffmpeg/
- the size of an ffmpeg bin is about 30mb, so I might want to just have one bin for each final os package
- start an export menu that will be the new home for 'export to images' in the File menu
- rename 'export to images' to just simply 'to images'
- I will want to start a 'to video' option
- the 'to video' export will still use 'to images' but will also call ffmpeg to create a video, and delete frames when done
- have an 'options' menu item that can be used to set a location for an ffmpeg bin to use