Very good idea, thought about checkbox styling for that, also because of states, but haven't thought about searching for examples.

Original SVG file:

Also added here -> https://wiki.apertus.org/index.php/OpenCine.Diagrams

To tihs one -> https://wiki.apertus.org

Let me take a look, have got a bit of experience by now. See intern chat.

He told me yesterday that it is 1366x768 (see IRC log). We have to add new area to the theme or move current footer area out of the main container, then the shrinking works again.

Hi. OC hierarchy consists of (currently) 2 main shared libs OCcore and OCui. OCBackup, OCLauncher and ProcessingTest are building upon this libs. Idea is to have a suite of tools, which have same look and feel (provided by OCui).

Install script is already in repo. One for RESTServer will follow at some point.

Moved related parts of code and started adding unit tests.

Added install_daemon.sh script.

Added Main.cpp, adjusted RESTServer code accordingly.

And this one is more to the point maybe: https://www.mediawiki.org/wiki/Manual:Tag_extensions/Example

Maybe like examples from this page: https://www.mediawiki.org/wiki/Manual:Tag_extensions

Or we can add just a simple script/plugin which looks for some special marker and replaces the HTML code for the section. Like $ for bash commands.

Added the test code from sandbox, please check if it's better suited.

Please remove the prototype page, as i'm at work right now and can't do it without my credentials.

Adjusted like requested.

Just a small thing: Header 5 should possibly be a bit bigger or bolder than normal text. But all in all we can close this task, if current adjustments are sufficient.

Looks very nice, but we should think of some concept which is not copying same behaviour, as it could cause us a lot of (legal) trouble. UI is not the big problem for OC, but the backup logic and verification is very important. We can think of some web UI in the future, if you want to have fancy stuff like animations.

In my opinion, no. This would just multiply number of repos, which increases difficulty of maintenance afterwards.

REST has a license in "develop" branch, but Github does not recognize it. Possibly .txt is missing as extension (see OC repo and the license info in the top-right corner).

Currently reworking to more flexible solution, in QML:

@maltefiala What about Meteor or Dart for the client side? I'm not that deep into web development jungle and if one searches the web, then thousands of frameworks can be found.

Reference for golang REST service, required for basic testing at the moment: https://thenewstack.io/make-a-restful-json-api-go/
Used JS REST lib (client side): https://github.com/marmelab/restful.js/tree/master

Looks very nice.

Needs a bit of investigation, but feel free to go to BlackMagic site to see their mobile navigation.

Nice demo of the inline menu -> http://output.jsbin.com/rusup/1/

Maybe we can show sub-menus underneath the navigation, similar to this -> https://i.stack.imgur.com/vmI0M.jpg

Something like this? -> https://bootsnipp.com/snippets/featured/multi-level-dropdown-menu-bs3

Yes, the breadcrumbs were positioned just below the navbar, but are not there at the moment. Have to investigate it, maybe it has to do with the left shift of the middle section of the navbar. When they are available again, we can discuss where the should be positioned for final version, but currently i've tried to add them similar to BM ones.

Done. Please check if the setup is ok for you.

Added breadcrumbs through plug-in as core ones were not working. They are not adjusted yet! -> http://apertus-d8-dev.w4f.eu/drupal8/products

Done.

Changed background to #e1e1e1 for now, but i prefer the previous lighter gray (#f4f4f4) better.

See comments.

Modified the page a bit, so the buttons are positioned right. What is the intention after all?

Another reference: http://getbootstrap.com/migration/

".row-fluid has been removed from Bootstrap 3 onwards. The above question refers to versions of Bootstrap prior to 3" -> http://stackoverflow.com/questions/16158176/twitter-bootstrap-how-to-use-row-fluid-class-properly

Bootstrap theme was installed as-is, apertus° theme is just derived from it, no modifications were done to original classes. Have to investigate it.

MOV thumbnails are generated by QtAV/FFMPEG.

Charts: Maybe we can really use http://www.chartjs.org or similar and re-style it to our needs, e.g. rotate bars at 45 degrees, like the first image (second one gives 404 now) in my previous answer. Advantage is the usage of small dataset to drive it, as image editing can become very tedious over time.

Implemented.and adjusted.

Wasn't the maker faire in Chemnitz?

Added black level subtraction (hard-coded at the moment), some colored pixel artifacts appeared, will be fixed later. Source code will follow soon.

First visual output:

See comment at T757.

Source as always here: https://github.com/apertus-open-source-cinema/beta-software
Yesterday i've found what the cause of exception was and will upload real communication part today which encodes settings, sends them to daemon and decodes them. Afterwards the client test project will be converted to a library, shared or static one, but that needs a discussion of needs.

Every manufacturer has different protocol for their lenses.

Sebastian, if there's need at some point in time then i can translate the article natively, if machine translation is not clear enough.

Yes, if we extend it a bit, just creating a simple daemon for now. The log is written to /var/log/syslog in my VM. You can see the init for log in the source i've uploaded yesterday, jsut take a look at main.cpp. Thanks for reminding me of return values, as we also want to request set values to display/verify them.