I cloned the FAQ page and converted it to the new design: https://www.apertus.org/node/552
Needs Triage (15)
- No repositories found for this query.
Tue, Nov 13
Thanks. While we're at it can we make the same allowances on the Wiki please?
Mon, Nov 12
just checked for slide control and seen some solutions but i need to investigate more into it. what i have done is a have 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).
Should be fixed now, please check.
Sun, Nov 11
Sat, Nov 10
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:
Fri, Nov 9
Agreed on the internal ND filter. Whether it's an electronic, variable, or rotary disk style, it's incredibly handy to have. Especially on cranes and gimbals. It could also breed greater functionality and cause for use of the remote control in those situations. Lack of behind the lens ND has made some RED rigs much larger than what would be preferable in some tighter scenarios as well.
Wed, Nov 7
Yeah the landing page is an issue. Unfortunately the key people who're in the process of its reformatting are currently engaged with the camera's UI and it's pretty important that they're not disturbed.
The reason it is hard to join the Apertus community in a way that is meaningful to being beneficial in any way is not the lack of a CoC.
Drawing attention and doing meaningful things with it fails because there is no landing page explaining why the project is different.
For what little impact I have had, I really want to avoid contributing anything to a CoC-project. Also making that landing page and
trying to reorganize the wiki turned out to be unwanted effort, so maybe I am wrong and this CoC is the sign of a project that really
knows what it is doing, and there is a real community behind it.
"people express interest in joining our community and wanting to contribute but it does not work out in the end, they disappear again - often soon after making first contact. We never know the reasons and don't have the resources to follow up with all of them." - SP.
Tue, Nov 6
CHANGES TO TASK DESCRIPTION
Mon, Nov 5
So I am answering in a context where this CoC already applies?
I don't really care to read it extremely carefully, for the same reason I think it fails already in general at this point of entry.
Why is this needed, and what does it do?
Sun, Nov 4
First version done: https://www.apertus.org/code-of-conduct
Thu, Nov 1
Maybe this one is better -> https://github.com/ygoe/msgpack.js also consider gzipped versions, where your 50kb file is only 14kb big.
Mon, Oct 29
It's lovely all around. Note how they deal with a large sitemap on mobile.
Thu, Oct 25
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
Wed, Oct 24
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.