JP1 Remotes

Sorry, I haven't had much time for RM/JP1 lately.

I'll see if I can find some time this week to look at this.

I don't want to make a big deal about this, but I have to say how disappointed I am that there hasn't been anyone come along to help with the RM development effort. RM is intentionally open source, and the tools needed to work on it are all free and cross platform, and I thought it was the JP1 community's goal that RM be the JP1 software tool, especially once much of the IR function was added. I know it isn't there yet, but with a bit of help it could be there fairly quickly.

KM and IR continue to be enhanced, which is fine, but with virtually no effort to keep RM in sync with them, or even to keep me in the loop about what changes are coming or have been made, or what's been figured out about new digit maps or new executors, so that I might have a chance to keep RM up to date before some incompatibilty crops up. When that happens I have to make an emergency release, which sometimes means I break something else and I end up having multiple releases.

Maybe I am wrong that we want RM to become the main tool, but under that assumption it seems to me we as a group should be enhancing RM first, then bringing KM and IR up to that level when we deem it important to do so.

Sorry for ranting.

gfb107 wrote:I don't want to make a big deal about this

Greg, you didn't but this is a very SAD post

gfb107 wrote:Sorry, I haven't had much time for RM/JP1 lately.

I know how that feels.

gfb107 wrote:I don't want to make a big deal about this, but I have to say how disappointed I am that there hasn't been anyone come along to help with the RM development effort. RM is intentionally open source, and the tools needed to work on it are all free and cross platform, and I thought it was the JP1 community's goal that RM be the JP1 software tool, especially once much of the IR function was added. I know it isn't there yet, but with a bit of help it could be there fairly quickly..

I don't know if disappointment is the right word but frustration is the right word for me. I do wish I could have helped you more with this. I know that you have made great strides with RM/IR and also agree that with a little more help it could get done. Or as done as IR tools ever get anyway.

gfb107 wrote:KM and IR continue to be enhanced, which is fine, but with virtually no effort to keep RM in sync with them, or even to keep me in the loop about what changes are coming or have been made, or what's been figured out about new digit maps or new executors, so that I might have a chance to keep RM up to date before some incompatibilty crops up. When that happens I have to make an emergency release, which sometimes means I break something else and I end up having multiple releases.

Maybe I am wrong that we want RM to become the main tool, but under that assumption it seems to me we as a group should be enhancing RM first, then bringing KM and IR up to that level when we deem it important to do so.

I raised this point awhile ago myself with the RM vs. KM. It just seemed like a lot of double effort and feel the same way about RM/IR especially if the committement is not there to move forward into the open source world.

I don't think we can stop working on IR and KM until we do get to a fully functional level between the two so, short of actual programming what can I do to help.

Maybe one approach is to maintain a common wish list or bug and only do something on either if it is on the list. Not much help I know but atleast in this fashion when the list is done or atleast match in functionality then one or the other can be functionally stabilized.

Just for the record, I do test every version of RM/IR you release I just have not had time to do much other than that.