Plugin Development Question

[spyork]

I'm currently developing a plugin for controlling X10 devices, and I have a question. The user will be able to setup as many devices as they wish using the GBPVR Config program. For each device the user will have to specify a name, house code, and unit code. Where is the best place to store this data? Should I have my own XML configuration file for the plugin? What method does GBPVR plugin developers usually use? Thanks...

Spyork

[Jeff]

You can store them in the plug-ins section of the gbvr config.xml file. If you look at the weather plug-in as an example it uses some utilities in the commongbpvrutilities.dll to make access to these easy.

Jeff

[habile]

I'm currently developing a plugin for controlling X10 devices, and I have a question. The user will be able to setup as many devices as they wish using the GBPVR Config program. For each device the user will have to specify a name, house code, and unit code. Where is the best place to store this data? Should I have my own XML configuration file for the plugin? What method does GBPVR plugin developers usually use? Thanks...

Spyork

Hi Spyork. I would be more than interested in this. I was considering creating some kind of hook into Homeseer's web interface as my X10 is controlled from a remote PC. What kind of communication transport did you have in mind?

Always happy to test

C.

[spyork]

You can store them in the plug-ins section of the gbvr config.xml file. If you look at the weather plug-in as an example it uses some utilities in the commongbpvrutilities.dll to make access to these easy.

Jeff

Since potentially one could setup alot of devices, I was afraid of polluting the gbpvr config.xml file. In the future, I am also planning to add scripting ability to the plugin where the user can define an action that will control multiple X10 devices at once (i.e. turn off lights in theater, lower screen, etc.). At what point should I worry about placing too much plugin configuration info in the config.xml file? Thanks...

Spyork

[sub]

You dont have to place it in config.xml if you dont want. You can create your own file if needed.

[spyork]

Hi Spyork. I would be more than interested in this. I was considering creating some kind of hook into Homeseer's web interface as my X10 is controlled from a remote PC. What kind of communication transport did you have in mind?

Always happy to test

C.

Hey habile, I'm currently using an X10 firecracker module to control devices. Initially I was planning to just support it, since this is the first plugin I have written for GBPVR. I'm more than willing to add support for other devices if there is a library available to talk to the device. I've found a couple of libraries people have written to control the firecracker, but I'll definitely look around and see what else I can find too. What kind of device are you using? Is it a serial or USB device?

Spyork

[spyork]

You dont have to place it in config.xml if you dont want. You can create your own file if needed.

Thanks sub, I might go ahead and do just that to prevent the config.xml file from becoming bloated.

[fering]

Just dug up an old Firecracker X10 and thought, somebody must have made this work with GBPVR.

Any progress with this plugin?

[nightwalker]

for those looking there is a very fine plug in to run homeseer events from the gbpvr screen as well as from an osd screen while watching a video or tv. I doesn't do plain x10 commands you of course need to have Homeseer installed somewhere on your network.
link below, if the link doesn't work just do a search for homeseer it'll come up

http://forums.nextpvr.com/showthread.php...t=homeseer

[spyork]

Just dug up an old Firecracker X10 and thought, somebody must have made this work with GBPVR.

Any progress with this plugin?

Hey fering, I started the X10 plugin back in January and got about 35-40% finished before I got sidetracked with things at work. Hopefully I'll be able to get back to this very soon. It shouldn't take more than a weekend to complete. I'll let you know as soon as I have something usable.