Touch Screen Navigation...
One of the fundamental aspects of a touch screen is how it navigates between pages .. where the logic sits that performs that function.
At the moment there is some basic page navigation with page toggle, show and hide (beta4 only has toggle implemented). There is also the additional <group> tag that either button or pages can belong to which automatically enforces only one page/button is enabled/visible at any one time.
Beta 5 will add more possibilities with Martyns <parent> tag implementation plus a new way of controlling page navigation - via xAP Page visibility and button clicks will be 'evented' over xAP and I intend to allow the visibility of both buttons and pages to be controlled via xAP. I may allow buttons to be 'clicked' via a xAP BSC command too.
The leading players like AMX and Crestron typically implement a touch screen interface by loading all the graphics onto the screen and feeding back finger presses. Then they have a control program running on a standalone processor that decides what should be displayed at any given time so there is minimal navigation logic actually implemented within the touchscreens. This has an additional benefit that multiple identical screens share one piece of code and can be all updated at once. Generally any displayed data is acquired by the processor and then pushed (via joins) to the touchscreens for display if needed. This keeps the touch screen clients light in terms of processing. It does however mean the screens require a separate processor to function, rather than being standalone.
So I'm intending to keep the Joggler internal navigation to a minimum - possibly as it is now which seems pretty adequate for most needs, and that the xAP BSC schema will mimic the joins. Joins are actually binary, analog or text - which is nicely analogous to xAP BSC.
Those wanting very sophisticated screen navigation or features would then either use a xAP capable controller / PC software or alter the Flash AS3 code directly.
So if there are other page/button navigation functions that people do feel should be included within the Joggler itself and configured via the XML do shout up now... !! I already intend a 'display a page for n secs' that seems sensible and will be useful as I deprecate the inbuilt CallerID screen to allow you to create your own from within the XML.
K
One of the fundamental aspects of a touch screen is how it navigates between pages .. where the logic sits that performs that function.
At the moment there is some basic page navigation with page toggle, show and hide (beta4 only has toggle implemented). There is also the additional <group> tag that either button or pages can belong to which automatically enforces only one page/button is enabled/visible at any one time.
Beta 5 will add more possibilities with Martyns <parent> tag implementation plus a new way of controlling page navigation - via xAP Page visibility and button clicks will be 'evented' over xAP and I intend to allow the visibility of both buttons and pages to be controlled via xAP. I may allow buttons to be 'clicked' via a xAP BSC command too.
The leading players like AMX and Crestron typically implement a touch screen interface by loading all the graphics onto the screen and feeding back finger presses. Then they have a control program running on a standalone processor that decides what should be displayed at any given time so there is minimal navigation logic actually implemented within the touchscreens. This has an additional benefit that multiple identical screens share one piece of code and can be all updated at once. Generally any displayed data is acquired by the processor and then pushed (via joins) to the touchscreens for display if needed. This keeps the touch screen clients light in terms of processing. It does however mean the screens require a separate processor to function, rather than being standalone.
So I'm intending to keep the Joggler internal navigation to a minimum - possibly as it is now which seems pretty adequate for most needs, and that the xAP BSC schema will mimic the joins. Joins are actually binary, analog or text - which is nicely analogous to xAP BSC.
Those wanting very sophisticated screen navigation or features would then either use a xAP capable controller / PC software or alter the Flash AS3 code directly.
So if there are other page/button navigation functions that people do feel should be included within the Joggler itself and configured via the XML do shout up now... !! I already intend a 'display a page for n secs' that seems sensible and will be useful as I deprecate the inbuilt CallerID screen to allow you to create your own from within the XML.
K
Comment