01-15-2010, 06:15 PM
Hey mrtae
Thanks for adding to the wishlist.
Anything is possible. Speech recognition sounds interesting; probably I\'d use the Microsoft SAPI SDK to add to floorplans and link at the floorplan (ie speech enabled \"ClickResponses\" as I call them) and at the system level too (ie say Tab 2 to switch views say).
For the next release I\'ve fixed a few issues so far and also added some new features so far including configurable positioning of Window Tabs; want them Top, Bottom, left or right of the main panel etc.
Currently I\'m developing something called \"Condition Manager\" for the Client for the next release which is a big piece of work. The Condition Editor is 95% complete and I\'m now going to start putting in hooks for where you can use (and more of these will be added over the subsequent releases if people or myself want). Conditions will be definable at Floorplan and System level with one overriding the other if the named condition appears in both. Havent quite decided yet which\'ll take precedence but siding on the Floorplan one.
Examples where I see conditions could be applied:
(1) Filtering what is displayed in monitor window. Poor Ingo with his regular polling counter which fills up the window with lots of records. Being able to say dont display if \"Counter XX is true\" for example.
(2) Only playing sounds during certain periods; ie if condition is currentTime (now) > x < Y. Or if say comfort Flag N = false. So for example being able to diosable sounds during nighttime.
(3) Setting floorplan objects visible/hidden depending on criteria. So have say images and show them depending on the attached condition; 0 - 10 shows Image 1, 11 - 50 shows Image 2 and 51 - 255 shows Image 3. So you can create ramp effects, gauges, traffic light effects etc. Initially we\'ll do with multiple objects but eventually try to create a composite object which has multiple image definitions linked to conditions.
Obviously lots more possibilities. The aim is not to duplicate what Comfort Responses do but to utilise them more creatively in the Client and to add new ones that arent possible in Comfort itself.
Relational operators will include: =, != , >, <, <=, >=
Logical operators include: AND, OR
Initial release will support Comfort Counters and Flags as the source. Later I\'ll add \"internal\" (system) ones specific to the client like \"DateTime\", \"LoggedOnUser\" etc etc. So for each fancy changing the UI look and feel when a user logs on?
The possibilities are endless if I can get it to work as I envisage.
Regards
Julian
Thanks for adding to the wishlist.
Anything is possible. Speech recognition sounds interesting; probably I\'d use the Microsoft SAPI SDK to add to floorplans and link at the floorplan (ie speech enabled \"ClickResponses\" as I call them) and at the system level too (ie say Tab 2 to switch views say).
For the next release I\'ve fixed a few issues so far and also added some new features so far including configurable positioning of Window Tabs; want them Top, Bottom, left or right of the main panel etc.
Currently I\'m developing something called \"Condition Manager\" for the Client for the next release which is a big piece of work. The Condition Editor is 95% complete and I\'m now going to start putting in hooks for where you can use (and more of these will be added over the subsequent releases if people or myself want). Conditions will be definable at Floorplan and System level with one overriding the other if the named condition appears in both. Havent quite decided yet which\'ll take precedence but siding on the Floorplan one.
Examples where I see conditions could be applied:
(1) Filtering what is displayed in monitor window. Poor Ingo with his regular polling counter which fills up the window with lots of records. Being able to say dont display if \"Counter XX is true\" for example.
(2) Only playing sounds during certain periods; ie if condition is currentTime (now) > x < Y. Or if say comfort Flag N = false. So for example being able to diosable sounds during nighttime.
(3) Setting floorplan objects visible/hidden depending on criteria. So have say images and show them depending on the attached condition; 0 - 10 shows Image 1, 11 - 50 shows Image 2 and 51 - 255 shows Image 3. So you can create ramp effects, gauges, traffic light effects etc. Initially we\'ll do with multiple objects but eventually try to create a composite object which has multiple image definitions linked to conditions.
Obviously lots more possibilities. The aim is not to duplicate what Comfort Responses do but to utilise them more creatively in the Client and to add new ones that arent possible in Comfort itself.
Relational operators will include: =, != , >, <, <=, >=
Logical operators include: AND, OR
Initial release will support Comfort Counters and Flags as the source. Later I\'ll add \"internal\" (system) ones specific to the client like \"DateTime\", \"LoggedOnUser\" etc etc. So for each fancy changing the UI look and feel when a user logs on?
The possibilities are endless if I can get it to work as I envisage.
Regards
Julian