I apologize if some of this is repeated constantly but I have been searching and cant find any information between: I-just-need-it-to-work user and developer. I would consider these middle ground how-to instructions for someone who is willing to contribute and needs some direction.

Templates:

Is there a way to copy a template when creating a new device without altering the original? I often times need to adjust a few properties only (such as advanced IP camera) when setting up a non-recognized or improperly recognized device. Currently I am pen-and-paper writing down all the command groups etc. Though I am learning a lot about "how" these things work in doing it this way it is killing my productivity.

Sharing Templates, Device Data, etc. via sqlCVS?:

So I created a new device for my D-Link 930L (wired or wireless IP cam). I could use generic, advanced or tweak the existing D-Link cameras but I like things to be clean so I wanted my duck to be called a duck. In development, is the LMCE direction to catalog and create device data for each piece or to come up with fewer generic device schemes that cover groups of equipment?

In my sqlCVS area of the web-admin page I see where I can pull in using the no-pass account which is pre-populated. How do I go about uploading anything I create for review and possible inclusion?

Designer:

It's very clear that as the UI goes that the old program is no longer used and effort is going into new schemes and methods. What I am hunting for information on though is screen and object relationships. When setting up a new device such as a camera and I am asked the PK_Object or PK_Screen # and have to tab out to find another device that uses it and hope I am correct. I tried going into /usr/pluto/orbiter but the file names do not contain such numbers. Is there a list of screens with numbers I am overlooking?

Bug Reporting:

I think something is a bug, I reload several times, I search wiki/forums/google and try to get it going on my own. I could have screwed something up or it could be buggy. Nobody else seems to be complaining about it on wiki/forums/google. Would LMCE prefer rejecting tickets as user screw-up or not getting a ticket at all?

- Just a few questions I wanted to get posted before I tackle getting one IP cam, one A/V input and two streaming feeds into the Quad-Cam view.

I understand that because this system is so complex, it is hard to know where to start. Let me see if I can untangle some of this for you.

Templates: No there unfortunately isn't a way to easily duplicate a template. It needs to be made from scratch. We aren't averse to somebody writing a duplicate function in the web admin, however, this would be very useful, it's just nobody has done it yet.

Device Templates are typically tilted towards specific devices and models. Sometimes, one device template can handle many different devices, sometimes it is a single device to a template. This is of the contributor's discretion, in the end the user just cares that it works, and therefore that's our stance too. The system is very flexible as to where it comes to describing a device, so if a multiple devices can work with the same commands and command groups, it makes sense to combine them into one device template. We have the ability to have multiple plug and play records for this purpose (among others.)

Uploading: Device templates can be uploaded with the anonymous/nopass credentials. They are then put into an area where we can view them and subsequently approve their inclusion into the database. In order for this to work effectively, what we ask each contributor to do is:

(1) sqlCVS update your database before making your new template(2) make your new template(3) Go to trac (http://svn.linuxmce.org/) and create a new ticket, with the title being your new device, and an indication that this is a new device template. This will give you a TRAC ticket #. you will need it for the next step.(4) Go to sqlCVS->Diff in the web admin, and be sure to check all for the DCE and IR command groups, as this is where your device template will be stored (the metadata is in DCE, and any special commands, IR codes, Ruby code, will be in the IR repository), IN THE COMMENTS FIELD, PLEASE PUT THE TRAC TICKET # YOU WERE GIVEN. This will allow us to easily process your template and match things up.(5) We will look things over, and most likely approve. If we don't, either way...(6) You get a message indicating it was approved or not, and what device template # it was inserted into the database as. If you do an sqlCVS, you will see the revised device template #.

As for Designer: Designer is still used, because we haven't replaced Orbiter yet. While we ARE working on a new engine, and it is available for those who want to contribute and test, Orbiter is still used in most cases, therefore Designer is still relevant. For most things, you should not need to go out and design a new screen, but if you do need to make UI changes, we can walk you through them in the -devel IRC channel.

and finally, all bug reports are useful, don't be hesitant to file one. If it's a dupe, we will mark it as such. If it's a worksforme, we will try to offer an explanation or ask for further information.

Does anybody have or have the ability to generate such a thing? I mainly need the number for single cam view, I am looking at it now on 4 different orbiters but I cant gather the # that way to set up a response to event that uses it.