Dean Roddey
05-09-2005, 04:38 PM
Charmed Quark Systems, Ltd (http://www.charmedquark.com) is proud to announce the 1.4 release of CQC (the Charmed Quark Controller), its software-based control and automation system.
Charmed Quark System's automation products provide robust, flexible, and cost effective control of lighting, HVAC, security, home theater, media data, and other systems. It is available in various configurations, which will scale to meet your needs, whether large or small, open or secure, a single room or the whole home. Build your own hardware, or use our pre-built systems. Do it yourself or take advantage of our reasonable consulting and customization services, whatever fits your needs and budget.
In the remainder of this document some screen shots will be provided. These are of the interfaces created for various CQC-based automation solutions. Please note that there is nothing, visually or functionality, about these images that is intrinsic to CQC. They were created using the CQC interface designer, using arbitrary images chosen for their asethetics and the functionality provided is purely a matter of design, so they are not 'skins' providing alternate looks for a fixed set of functionality, nor are you in any way limited to a particular visual style. they are pretty significantly reduced in size and quality in order to avoid download overhead
http://www.charmedquark.com/Web2/Downloads/CQC1_4BlurbImages/D1_HomeOverlay_Small.jpg
Click here for a full sized version (http://www.charmedquark.com/Web2/Downloads/CQC1_4BlurbImages/D1_HomeOverlay.jpg)
What's New Overview
---------------------------------------
This section will briefly introduce the major new features in this version, some of which will be discussed in more detail later in this document.
Media Management. The biggest ticket item in this release is CQC's first steps into the media management world. Our driver architecture has been extended to support 'media drivers'. This allows CQC to provide browsing of media repositories and control of media renderers, and to coordinate them into a coherent media system.
New Action System. The 'Action' system in CQC, which is how you configure CQC to carry out tasks in response to a button press, IR signal, scheduled event, and so forth, was vastly reworked in this version. It is now far more powerful, far more flexible, and has a simpler interface.
Graphical Interface Features. CQC's user interface designer/viewer system has been extensively improved in this release. Interface widgets were added to support the new media management features, to allow you to view cover art, to browse media categories and cover art. One of the improvements in the item above is that actions were extended to include the interface widgets themselves, allowing you to create very dynamic interfaces without any programming. The new toolbar widget is a very convenient way to provide access to more buttons than you have physical space for. And a new simple animation widget allows you to easily represent the active states of devices under control.
Elk M1 Support. A new driver is available for the Elk M1 and M1 Gold automation panels. It supports both the serial and Ethernet based connections. The M1 is a very popular automation panel that is very reasonably priced.
Escient Fireball Support. The first media repository device supported in our new media architecture is the Escient Fireball, which is a single zone, media repository and renderer for CDs and DVDs. You can browse the Escient cover art database and control it during playback.
Zoom Player Support. Zoom Player is now supported as a media renderer, and is a very powerful combination with a file-based media repository and CQC providing the coordination.
J.River Disk Repository Support. J.River Media Center 11's disk based media repository is now supported as a CQC media repository, so you can browse the repository via category and cover art and invoke a renderer to play selected media.
Undo in Interface Designer. The user interface designer tool now supports Undo, which allows you to safely experiment or to recover from accidental changes.
Z-Wave Driver Improvements. The Z-Wave driver was vastly improved in this release, and now is very quick and very reliable. Z-Wave automation via CQC now shows what Z-Wave is capable of.
JPEG Support. You can now import JPEG images into CQC for use in interfaces, in addition to the already supported PNG and bitmap formats.
New Command System
---------------------------------------
One of the core functions of an automation system is to allow you to set up sequences of events that will take place when you press this button or that IR remote button or some event takes place. 1.4 introduces a new command system that is far more powerful than before, allowing you to do much more without having to use our much more powerful (and more complex) CML language. So non-programmers can create much more powerful command sequences ('actions' in CQC parlance) in a purely dialog driven way.
The new command system is much more generic and therefore it can adapt easily to different applications that use it, and it allows for various 'command targets' to be plugged into it according to the needs of the containing application. So in the interface system interface elements (widgets in CQC-speak) can be the target of commands now. So, for instance, one widget can send a text widget a command telling it to display some new text, or to an image widget telling it to show a new image, or to hide or show itself, and so forth.
http://www.charmedquark.com/Web2/Downloads/CQC1_4BlurbImages/MA_SatTVOverlay_Small.jpg
Click here for a full sized version (http://www.charmedquark.com/Web2/Downloads/CQC1_4BlurbImages/MA_SatTVOverlay.jpg)
This has introduced a lot of flexibility into the interface system, allowing you to do a form of object oriented programming, by having objects on the interface send messages back and forth. An example of its power will be seen below in the media management discussion. CQC has just begun to scratch the surface of what this new command system will be able to do in the future.
Media Management
---------------------------------------
1.4 introduces CQC's new media management architecture, which extends CQC's flexible driver system to encompass media repositories and renderers (things that provide media to browse, and things that play media.) So CQC can encorporate various media systems just as easily as it can regular devices.
http://www.charmedquark.com/Web2/Downloads/CQC1_4BlurbImages/D1_MediaOverlay_Small.jpg
Click here for a full sized version (http://www.charmedquark.com/Web2/Downloads/CQC1_4BlurbImages/D1_MediaOverlay.jpg)
We've introduced interface elements that support the new media driver architecture, which allow you to browse categories, browse cover art, display track lists, display currently playing cover art and so forth. These widgets talk to the media drivers you associate them with, and handle all of the details behind the scenes. You just drop them on your interface and configure them to look and act the way you want them to. You can control the spacing and size of the browser's images slots so that you can position them over any background image you want and make them fit appropriately.
As mentioned above, interfaces can now send and receive commands, which is very useful in the new media widgets, and in fact they kind of drove the need for this new feature. For instance, in the interface above, the media category browser allows you to browse the categories available in the associated media repository. You can configure it to send a command to the cover art browser to start browsing that new category. The cover art browser in the above example is configured to set the text widget above it to show the name of the current category it is browsing. The list of letters across the button are just buttons that send 'first letter' commands to the cover art browser, asking it to scroll to the first item starting with that letter.
The buttons used to page back and forth through those browsers are just sending scrolling messages to them, to ask them to scroll back and forth. In this example above, when you click on a cover art item, it will start up Zoom Player, if it is not playing already, wait for the Zoom Player driver to come online, then sends the Zoom Player driver a command to start playing the title, then sends a command to the main interface (in which it is embedded) asking it to load the 'now playing' interface.
An important aspect of this new scheme is that you remain in full control of the look and feel. If we built a browser with the buttons built in, you couldn't control where they were placed or how they looked. This way, you can have them look like separate buttons as above, or you can place them over a common image so that they look like part of the thing they are controlling, as is the case in the toolbar widget at the top left. The buttons on either side of it are just buttons without any background so that they look like they are part of that visual element.
So it has the flexibility of a 'skinning' system, but is far more powerful because it can be applied far more broadly and doesn't assume any pre-existing set of functionality.
Charmed Quark System's automation products provide robust, flexible, and cost effective control of lighting, HVAC, security, home theater, media data, and other systems. It is available in various configurations, which will scale to meet your needs, whether large or small, open or secure, a single room or the whole home. Build your own hardware, or use our pre-built systems. Do it yourself or take advantage of our reasonable consulting and customization services, whatever fits your needs and budget.
In the remainder of this document some screen shots will be provided. These are of the interfaces created for various CQC-based automation solutions. Please note that there is nothing, visually or functionality, about these images that is intrinsic to CQC. They were created using the CQC interface designer, using arbitrary images chosen for their asethetics and the functionality provided is purely a matter of design, so they are not 'skins' providing alternate looks for a fixed set of functionality, nor are you in any way limited to a particular visual style. they are pretty significantly reduced in size and quality in order to avoid download overhead
http://www.charmedquark.com/Web2/Downloads/CQC1_4BlurbImages/D1_HomeOverlay_Small.jpg
Click here for a full sized version (http://www.charmedquark.com/Web2/Downloads/CQC1_4BlurbImages/D1_HomeOverlay.jpg)
What's New Overview
---------------------------------------
This section will briefly introduce the major new features in this version, some of which will be discussed in more detail later in this document.
Media Management. The biggest ticket item in this release is CQC's first steps into the media management world. Our driver architecture has been extended to support 'media drivers'. This allows CQC to provide browsing of media repositories and control of media renderers, and to coordinate them into a coherent media system.
New Action System. The 'Action' system in CQC, which is how you configure CQC to carry out tasks in response to a button press, IR signal, scheduled event, and so forth, was vastly reworked in this version. It is now far more powerful, far more flexible, and has a simpler interface.
Graphical Interface Features. CQC's user interface designer/viewer system has been extensively improved in this release. Interface widgets were added to support the new media management features, to allow you to view cover art, to browse media categories and cover art. One of the improvements in the item above is that actions were extended to include the interface widgets themselves, allowing you to create very dynamic interfaces without any programming. The new toolbar widget is a very convenient way to provide access to more buttons than you have physical space for. And a new simple animation widget allows you to easily represent the active states of devices under control.
Elk M1 Support. A new driver is available for the Elk M1 and M1 Gold automation panels. It supports both the serial and Ethernet based connections. The M1 is a very popular automation panel that is very reasonably priced.
Escient Fireball Support. The first media repository device supported in our new media architecture is the Escient Fireball, which is a single zone, media repository and renderer for CDs and DVDs. You can browse the Escient cover art database and control it during playback.
Zoom Player Support. Zoom Player is now supported as a media renderer, and is a very powerful combination with a file-based media repository and CQC providing the coordination.
J.River Disk Repository Support. J.River Media Center 11's disk based media repository is now supported as a CQC media repository, so you can browse the repository via category and cover art and invoke a renderer to play selected media.
Undo in Interface Designer. The user interface designer tool now supports Undo, which allows you to safely experiment or to recover from accidental changes.
Z-Wave Driver Improvements. The Z-Wave driver was vastly improved in this release, and now is very quick and very reliable. Z-Wave automation via CQC now shows what Z-Wave is capable of.
JPEG Support. You can now import JPEG images into CQC for use in interfaces, in addition to the already supported PNG and bitmap formats.
New Command System
---------------------------------------
One of the core functions of an automation system is to allow you to set up sequences of events that will take place when you press this button or that IR remote button or some event takes place. 1.4 introduces a new command system that is far more powerful than before, allowing you to do much more without having to use our much more powerful (and more complex) CML language. So non-programmers can create much more powerful command sequences ('actions' in CQC parlance) in a purely dialog driven way.
The new command system is much more generic and therefore it can adapt easily to different applications that use it, and it allows for various 'command targets' to be plugged into it according to the needs of the containing application. So in the interface system interface elements (widgets in CQC-speak) can be the target of commands now. So, for instance, one widget can send a text widget a command telling it to display some new text, or to an image widget telling it to show a new image, or to hide or show itself, and so forth.
http://www.charmedquark.com/Web2/Downloads/CQC1_4BlurbImages/MA_SatTVOverlay_Small.jpg
Click here for a full sized version (http://www.charmedquark.com/Web2/Downloads/CQC1_4BlurbImages/MA_SatTVOverlay.jpg)
This has introduced a lot of flexibility into the interface system, allowing you to do a form of object oriented programming, by having objects on the interface send messages back and forth. An example of its power will be seen below in the media management discussion. CQC has just begun to scratch the surface of what this new command system will be able to do in the future.
Media Management
---------------------------------------
1.4 introduces CQC's new media management architecture, which extends CQC's flexible driver system to encompass media repositories and renderers (things that provide media to browse, and things that play media.) So CQC can encorporate various media systems just as easily as it can regular devices.
http://www.charmedquark.com/Web2/Downloads/CQC1_4BlurbImages/D1_MediaOverlay_Small.jpg
Click here for a full sized version (http://www.charmedquark.com/Web2/Downloads/CQC1_4BlurbImages/D1_MediaOverlay.jpg)
We've introduced interface elements that support the new media driver architecture, which allow you to browse categories, browse cover art, display track lists, display currently playing cover art and so forth. These widgets talk to the media drivers you associate them with, and handle all of the details behind the scenes. You just drop them on your interface and configure them to look and act the way you want them to. You can control the spacing and size of the browser's images slots so that you can position them over any background image you want and make them fit appropriately.
As mentioned above, interfaces can now send and receive commands, which is very useful in the new media widgets, and in fact they kind of drove the need for this new feature. For instance, in the interface above, the media category browser allows you to browse the categories available in the associated media repository. You can configure it to send a command to the cover art browser to start browsing that new category. The cover art browser in the above example is configured to set the text widget above it to show the name of the current category it is browsing. The list of letters across the button are just buttons that send 'first letter' commands to the cover art browser, asking it to scroll to the first item starting with that letter.
The buttons used to page back and forth through those browsers are just sending scrolling messages to them, to ask them to scroll back and forth. In this example above, when you click on a cover art item, it will start up Zoom Player, if it is not playing already, wait for the Zoom Player driver to come online, then sends the Zoom Player driver a command to start playing the title, then sends a command to the main interface (in which it is embedded) asking it to load the 'now playing' interface.
An important aspect of this new scheme is that you remain in full control of the look and feel. If we built a browser with the buttons built in, you couldn't control where they were placed or how they looked. This way, you can have them look like separate buttons as above, or you can place them over a common image so that they look like part of the thing they are controlling, as is the case in the toolbar widget at the top left. The buttons on either side of it are just buttons without any background so that they look like they are part of that visual element.
So it has the flexibility of a 'skinning' system, but is far more powerful because it can be applied far more broadly and doesn't assume any pre-existing set of functionality.