… continued from Random Picture Thread.
Sssssweet. But why?
I mean… do you have particular functions, toggles or widgets in mind we could try stuffing into this toolbar / sectioned pane layout?
Also – any thoughts on controller mappings? Right now I’m thinking about rigging button presses (not pointer related) as a secondary/aimless way to switch between panes.
Cool, but keep in mind this is just a quick proof-of-concept. My advice is to wait for and probably run with what @james_hifi suggests – in part because it’s likely to have a longer shelf life.
Unfortunately, adding atp support to QtWebEngine doesn’t seem very practical, but the next version of Qt makes it easier (so there is hope for the future).
There are some ways to solve the problem entirely on the content side, but the ones I know of just complicate things.
What I think would work best for now is “simply” adding a lightweight http-atp proxy to Interface.exe itself – able to answer ATP requests on mapped URLs like:
and hashed URLs like:
Hmm, if you mean like jQuery, the stock qwebchannel.js include, stuff living under resources/ – then yes.
On the content side the image/nav is just vanilla HTML and jQuery. I literally unpacked its .zip file, edited the .html file to removing margins and padding (for a seamless display), and loaded into my “HTML5 UI toolbar” window.
OverlayWebWindow would have worked too – except I didn’t want the window title bar or frame icons.
So made my own “HTML5 UI toolbar” window out of two files: a Client Script and the custom .qml it loads into an
Not entirely sure what you mean, but it sounds interesting!
What would the AC script do in that case (and would the Node.js instance be behind the firewall)?