This page last changed on Jan 20, 2012 by ebariaux.

Let's use this post to list the desired functionality that would need to be added in future iterations of the modeler.
This will not cover adding new widget types, see this thread instead.

  • possibility to re-import back an exported configuration
  • fix issues with content in non US locale (in current version accentuated characters do not make it to the XML files)
Building modeler
  • when a protocol has a finite set of values for a field, use a dropdown instead of a free text field
UI Designer
  • cut/copy/paste of UI elements
  • possibility to select multiple elements
  • some form of help on alignment (e.g. guides being displayed to show alignment of different elements or functions to align multiply selected elements or space them evenly)
  • re-use of images (both internally when the same image is assigned to multiple elements it should only be included once in the generated configuration and from a user point of view so that he/she should only have to upload an image once and be able to use it on multiple elements)
  • keyboard shortcuts for certain operations. For instance, move the graphical elements using the arrow keys
  • graphical editor for rules

The first improvement is great!, when will it be available?

Posted by pakojones at Sep 29, 2011 16:24
  • re-use uploaded images
Posted by mredeker at Sep 29, 2011 17:15

though i am not a developer of OR i'd like to suggest something

  • Support foreign characters
  • Subgroups of a device to put i.e. commands, sensors, switches and sliders of one room into one group
Posted by obelix at Sep 30, 2011 23:23

An option if the uploaded image should be private or public for everybody to use would be nice.
This way, if people want to share their created graphical assets, it's just a checkbox and the graphics are available for everybody.

Posted by mredeker at Oct 06, 2011 09:41

The problem being that we will get a ton of porn shared on the designer.

Posted by juha at Oct 10, 2011 02:56

Agreed on both. And both items are on the todo list either to be tested/implemented or being designed at the moment.

Posted by juha at Oct 10, 2011 02:57

If a protocol only supports certain strings as commands it would be nice if we could give these strings within protocol.xml and the designer would create a dropdown for the command where the user just selects the string, eg. KNX switch command only supports "on", "off", "status"

Posted by mredeker at Oct 11, 2011 09:53

That could be a problem. On the other hand we might not know about some really cool designs.

Posted by mredeker at Oct 11, 2011 09:55

When you enter

for CR/LF modeler does not pass this corectly to the XML output file.

It would be helpfull if it did.

Posted by pjmm at Oct 11, 2011 21:44

Option to create command templates :
I'm using Global Cache iTach to control devices, for all commands I have to define protocol TCP/IP, the host and port.
As all commands are sent by the same emitter all of this fields are same for them.

Posted by ivanfm at Nov 19, 2011 10:25

REST API to add devices, commands, etc.
I have created a simple learner for iTach, will be very nice if it can upload the IR commands to the designer.
I will create an Android interface for my Learner and publish in Android Market in a few weeks.

Posted by ivanfm at Nov 19, 2011 10:27

While command template do not exist, if you use the "Submit and Continue" button on the command creation panel, it will create the command and keep the panel open with the previously entered value. You can then change the command name and the parameters that vary. And so on. This saves you from entering the same values all over again.

Posted by ebariaux at Nov 19, 2011 16:28

We're working on bringing this functionality. The REST API will be on beehive (that is anyway the backend for the designer). So you'll be able to do all you do in the designer but through an API.

Posted by ebariaux at Nov 19, 2011 16:29

BTW, you might also want to check this thread.

The wizard allows the create all the commands required for the GC based on IR codes coming from an XCF file (from Pronto Edit Professional tool).

Posted by ebariaux at Nov 19, 2011 16:31

Additionnal improvements from this thread:

  • sub pages widget reusable and dynamically parametrized
  • graphical Rules designer
Posted by yannph at Jan 20, 2012 08:52

Agreed on both. Added the second to the list here but the first 1 will required change to the XML / console / ... so does not fit in this thread.
Will be covered in

Posted by ebariaux at Jan 20, 2012 12:25
Document generated by Confluence on Jun 05, 2016 09:31