Devlog 4
Control Layout
first i would like to define what i call a control layout, as i reliased i never relly defined it properly
Control Layout: It is a layout of buttons and other control elements like
For Example
- control layout for playback control will have button/controls like volume up/down, play/pause, fast forwarding and controling playback
- Maybe some specifi button to help while editing video
- Or controls for some particular Applications
So basically, these controls can trigger and functionality or a shortcut or a macro onto the computer that the client is connected with
Single click on the phone screen will be able to run a complex keyboard shortcut
User can map shortcuts based on particular applications, and he does not need to remember keyboard shortcut.
They don’t even need to click anywhere on their screen. The phone will act as a secondary keyboard or a small macropad.
Customizable Control Layout
The application contains some prebuilt control layouts
But different user user different application and have different workflow, so i created a featrure to let users
- create his own custom layouts where he can place different buttons anywhere on the screen and assign what work each button will be doing.
As of now the current active applicaiton detection is not present but i will add this feature soon.
Details
-
basically, I have an interface which tries to mimic a mobile screen, and I have divided that screen into grids with CSS
-
I can move the elements around and resize them.
-
I track the
position,heightandwidthof those elements and store them in aJSONconfig file upon saving these layouts. This JSON config is sent overlocal web socketto theRust server. -
Along with just the information about the UI, there is also working information, like name of button, its functionality etc
-
I have a component which is quite opposite of a
builderwhich is arenderer. -
This renderer takes up JSON config and renderes the different components and maps the functionality, in smple word it takes json and create UI.
Comments 0
No comments yet. Be the first!
Sign in to join the conversation.