Mon, Dec 24
made a bigger update.
Sat, Dec 22
Wed, Dec 19
Adjustments to the daemon are done, see comm packet. Also added digital gain and reworked analog gain.
Made today a update:
- Iconfont is now generated
- slider in the modal window
Dec 11 2018
Just a quick update, tested the daemon with web UI and it works great. Of course current setup is still not finalized and daemon runs as app, so it can be killed directly, but "analog gain" setting works fine (done some test snapshots). Next step will be some adjustments to the comm packet, so we have dedicated command parameter for get/set (a bit like REST), so the part of splitting "set_gain" to check the command will become obsolete and the code easier.
Dec 2 2018
@sebastian i think it doesn't make much sense for me. I don't know the backend so i could only see if the web-remote works.
Nov 28 2018
@Francis do you want a remote Beta account? https://wiki.apertus.org/index.php/AXIOM_Beta_Remote_Access
I think the code is in a stage where it's good for testing on the Camera. There are surly some functions missing but that can be added when the test gives some results.
Nov 22 2018
small progress can now make a desktop app :-)
Nov 18 2018
Will check it in the next days, have no time as another work travel is on tomorrow.
@BAndiT1983 made some small updates is it for you now better?
Nov 12 2018
just checked for slide control and seen some solutions but i need to investigate more into it. what i have done is a autoupdate so you don't need to close the modal window and it should be possible to use the arrow keys for change the values (up/down).
Nov 10 2018
i changed on the end from the IRC Meeting the data.json for your requirements.
Did just few adjustments to web-remote, it communicated almost right away with the WSServer and daemon. Noticed 2 things which should be adjusted:
Nov 1 2018
Maybe this one is better -> https://github.com/ygoe/msgpack.js also consider gzipped versions, where your 50kb file is only 14kb big.
Oct 25 2018
Just as a reference for the future: Usually our JSON packets will be very small, but if we consider to sent larger packs in the future, like restoring some user profiles (no point to sent individual settings, if there are a lot of cahnges) or when receiving the response with all available stuff in the camera (which i expect to be rather big), then we could consider to use MessagePack, to reduce the size -> https://msgpack.org
Oct 24 2018
Okey thanks i will check that when i have more time.
Have added simple eslint config with settings i'Ve already mentioned before. Don't have any other special preference at the moment.
the riot.js compiler is not required can be replaced with riot.min.js (~12KB less) i will do that when i have done the new widgets.
Is the riot compiler JS still required? As currently pre-compilation is done by gulp.
Dev VM is planned for UI development in first place, then i hope to move daemon to another repo and also place it there, for comm tests.
When there is a code style guide that you prefer or has been defined it's no problem to adapt it. I'm new in terms of code development and it's my first real code project i'm happy to get inputs to reach a better result.
Nothing to be sorry about, just normal development cycle. Preparing the VM currently, which will hold the web UI dev environment. It consists of Manjaro (XFCE) and Atom.io mainly. Will try to add some plugins, like eslint, after that we have to do a short discussion about code style, e.g. semicolon yes/no, single ' or double " quotation marks for strings and so on. Have my own preferences, but wanted to talk to majority about it.
@BAndiT1983 strage bug the precompile for the .tag files didn't see the end correctly i removed emty space's and it works againe. sorry for that.
Please check the code, getting unexpected token "<" in browser.
made the upload, i will also delete my repo in some days.
Oct 23 2018
Then a new repo please, with commit rights for us all. You could upload latest version, so Francis can commit his changes over it, then we can inspect the differences. I've adjusted his code a bit, as showcase for Browsersync stuff, but not very much.
Whatever you prefer.
Should we start separate repo for it, and add as submodule to beta-software one later? This would allow to do things in parallel, like independent CI builds.
Great to see things flowing so steadily here!
Shall I give you commit access to github so you can more easily commit/collaborate on code?
i made a update my stuff is still under development but the other part hasn't been changed so gulp should work.
made also all component tag's to a single js file so it looks slowly better in the index.html file and less stuff to load.
Oct 22 2018
Here is the version with browsersync support. Lost my websocket adjustments, but there were only few, which is not that tragic.
Nah, not gulp serve, but browsersync. It reloads HTML page on the fly, when it detects changes to HTML or JS files. Also you can stream CSS changes, without reloading the page, which saves time. Also you can adjust it to compile and then reload on changes to Tag files, as an example. Really nice stuff, using it when i can for web development, latest one was development of a Drupal theme, done with this live preview. See pcb-aoi apertus repo on Github for an example.
Sound's good and take it easy 😉...
For the UI my view was to have for each data type a own widget and the module maker defines the widget for his module.
Adjusted UI code a bit, so it would send correct message on reload, to get available params. Also adjusted websocket server processing, so the response will come back with real data from daemon. Will try to do final tests today, before uploading it.
Oct 21 2018
We can for sure embed it in a JSON file on the camera and send it together with other stuff back. Will resume to inspect your code in a moment, as i want to get exactly this part of comms done, before proceeding with adding parameters.
My target is to use indexedDB from the browser to store the data. There shouldn't be a big task to go over daemon (it takes maybe 20-40 LOC to make it happen) .
Oct 20 2018
No problem, adjust it to your liking, just assisting with some infrastructure. Websocket has connected, after my adjustments, see the code, but haven't got much further, as it expects the JSON database. Will try to adjust it, so it actually tries to retrieve it from websocket server, as i'm not sure, if we should maintain separate JSON config file or not. Current plan is to provide it dynamically by daemon, on request.
@BAndiT1983 thank you! i didn't invest a lot in gulp yet but it looks very simple. thanks
Oct 19 2018
Improved a bit and fixed small problems, also added build.sh.
My proposal for GULP adjustments, started to implement, as i wasn't sure how to debug riot.js without precompiling:
Oct 16 2018
I agree that its important to familiarize yourself with the technology but still we cannot punish users who didn't.
@sebastian the others don't know that is important to test and understand the equipment. (could tell storys about that! a good hint this was a reason why i support apertus! we lost nearly customer data because we haven't test the memory cards before shooting)
i'm sure most user will test first there setup at a location that has internet.