How does RM list remotes?

Nils_Ekberg · Post by **Nils_Ekberg** » Thu Oct 09, 2003 8:10 pm

Mark Pierson wrote:
jamesgammel wrote:Could? Somehow? They can share the same rdf's(RM's)
I know that, and I do that myself. But, is it stated in any of the readme's, etc? Will newbies know to do this?

My point is that I think we need to start streamlining the distribution of these tools. I'm always thinking about the people who aren't tech-savvy when it comes to computers. Even some of the simplest things that we take for granted need to be explicitly spelled out to others.

What we really need is an common directory structure that would be used by all these tools. Without some sort of installer app, however, I'm not sure how we could easily accomplish that.

I was just going to start a new thread on software distribution and came back here to check on something and I am glad I did since you made exactly the point I started to make in the new thread.

At a minimum we could make all 3 zip files with the same folder names. Second, make a change to IR to allow a different folder for RDF's. This way we could set up a structure like a main folder of IR and sub folders of RDF, Upgrades, and Images (like RM supports). In the IR main folder would be RM, KM and IR and the sub folders are self explanatory.

I think the common directory structure is key and packaging becomes the next big question. I think IR, KM, and RM should still distribute seperately for now but RDF's and Images/Maps should be packaged seperately.

Just food for thought........

Mark Pierson · Post by **Mark Pierson** » Thu Oct 09, 2003 9:22 pm

Nils_Ekberg wrote:In the IR main folder would be RM, KM and IR and the sub folders are self explanatory.

IMHO, the main folder should be called JP1 8)

jamesgammel · Post by **jamesgammel** » Thu Oct 09, 2003 10:15 pm

Ditto

Jim

Nils_Ekberg · Post by **Nils_Ekberg** » Fri Oct 10, 2003 6:39 am

Mark Pierson wrote:
Nils_Ekberg wrote:In the IR main folder would be RM, KM and IR and the sub folders are self explanatory.
IMHO, the main folder should be called JP1 8)

I agree. I just went and renamed mine from IR to jp1.

I did a quick test last night and got a self extracting zip file to create directories and install all 3 products in the format I use. eg; c:\jp1 (programs, RDF's, and KM upgrades), c:\jp1\Upgrades (RM upgrades), c:\jp1\Images (maps and images). The problem is that the zip file is 2.2 Meg with the RDF's and 2.0 without. Then take away the maps and images it is 1.3 Meg's. If we package the maps, images and RDF's separately they are about 750k.

I need to figure out how the licensing works with the self extractor and test some more but before I do does anyone thinks it is worthwhile pursuing packaging IR, KM and RM together with a separate distribution for RDF's, Images and Maps?

jamesgammel · Post by **jamesgammel** » Fri Oct 10, 2003 6:54 am

actually, I was thinking more in terms of 2 basic packages, one with IR and KM bundled, another with RM and IR bundled.

Rationality: If someone already has Excel, he *may* not want to go thru the long process of getting Java before RM will work. If he doesn't have excel, then it would be more worthwhile to get Java, cuz it's free. Both groups would also need the rdf's, but only the second needs the images and maps.

Jim

gfb107 · Post by **gfb107** » Fri Oct 10, 2003 7:44 am

Mark Pierson wrote:But you're on the right track with your thinking.

Ok, I'm looking at the Buttons2 sheet, columns D and E, which provide a mapping between position/index and generic name.

The odd thing (to me) is the indexes jump from 42 to 51, skipping 43-50.
Are there no buttons with these positions, or have I missed something?

Also, the last index appears to be 84, but 2 remotes ("Dreambox v2" and "Toshiba CT-90047") seem to have buttons after the last generic name.
In the case of the "Dreambox v2", they are all shifted versions of other buttons, but I'm not sure how they should be handled.

gfb107 · Post by **gfb107** » Fri Oct 10, 2003 8:54 am

gfb107 wrote:The odd thing (to me) is the indexes jump from 42 to 51, skipping 43-50.

I think I've got his working. I just ignored column D, and created an array of strings that has the names from column E (starting a row 20).

Let's make those names the generic names. Here's the list, for completeness:
0
1
2
3
4
5
6
7
8
9
vol up
vol down
mute
channel up
channel down
power
enter
tv/vcr
prev ch
menu
guide
up arrow
down arrow
left arrow
right arrow
select
sleep
pip on/off
display
pip swap
pip move
play
pause
rewind
fast fwd
stop
record
exit
surround
input
+100
fav/scan
device button
next track
prev track
shift-left
shift-right
pip freeze
slow
eject
slow+
slow-
x2
center
rear
phantom1
phantom2
phantom3
phantom4
phantom5
phantom6
phantom7
phantom8
phantom9
phantom10
setup
light
theater
macro1
macro2
macro3
macro4
learn1
learn2
learn3
learn4

It may not be obvious what name to use for some buttons. In that case, just look at the buttons2 sheet to figure out what KM did.

Mark Pierson · Post by **Mark Pierson** » Fri Oct 10, 2003 9:15 am

gfb107 wrote:The odd thing (to me) is the indexes jump from 42 to 51, skipping 43-50.
Are there no buttons with these positions, or have I missed something?

There are no buttons in positions 42 to 51. I can't remember exactly why I did that, though it had something to do with another app I was working on.

Also, the last index appears to be 84

You're obviously using an older version of KM. Currently, the list goes to #136, though the Dreambox entry of #111 is the largest at the moment.

mr_d_p_gumby · Post by **mr_d_p_gumby** » Fri Oct 10, 2003 9:19 am

gfb107 wrote:Let's make those names the generic names. Here's the list, for completeness:
...
It may not be obvious what name to use for some buttons. In that case, just look at the buttons2 sheet to figure out what KM did.

One minor point to note:
The mapping of a specific button to the generic name may not always be static within KM. Take the case of the (un)Intuitive remote; it has no power button, but instead the device buttons act as power buttons. Within each keymap the corresponding device button is mapped. So, when the user is making a cable upgrade, the CBL button is mapped to the generic power button, while a VCR upgrade will have the VCR button mapped. This won't present a problem when importing a KM upgrade, since the data is static at that point, but I just wanted to let you know that RM would have to be able to handle this case somehow.

gfb107 · Post by **gfb107** » Fri Oct 10, 2003 9:58 am

Mark Pierson wrote:
gfb107 wrote:
Also, the last index appears to be 84
You're obviously using an older version of KM. Currently, the list goes to #136, though the Dreambox entry of #111 is the largest at the moment.
I am using 7.53. I'll download 7.54 and look.

What I should have said is that #84 is the last one with a generic name specified. Since others don't have generic names, does that simply mean they are general purpose, and there isn't necessarily any correspondence between the buttons on different remotes.

For example, #95 for the "Dreambox v2" is "shift-info" but for the "Toshiba CT-90047" it is "OEM vol+" These don't seem logically related.

Maybe what I should do is simply fill out the default names with "button85" - "button136", just so there we have something.

Another question: what about the device buttons?

gfb107 · Post by **gfb107** » Fri Oct 10, 2003 10:10 am

mr_d_p_gumby wrote:One minor point to note:
The mapping of a specific button to the generic name may not always be static within KM. Take the case of the (un)Intuitive remote; it has no power button, but instead the device buttons act as power buttons. Within each keymap the corresponding device button is mapped. So, when the user is making a cable upgrade, the CBL button is mapped to the generic power button, while a VCR upgrade will have the VCR button mapped. This won't present a problem when importing a KM upgrade, since the data is static at that point, but I just wanted to let you know that RM would have to be able to handle this case somehow.

Interesting. Does KM support the Intuitive? I couldn't find it in v7.54, but maybe I just missed it.

Mark Pierson · Post by **Mark Pierson** » Fri Oct 10, 2003 12:09 pm

gfb107 wrote:Does KM support the Intuitive? I couldn't find it in v7.54, but maybe I just missed it.

It'll be in 7.55

Mark Pierson · Post by **Mark Pierson** » Fri Oct 10, 2003 12:13 pm

gfb107 wrote: I am using 7.53. I'll download 7.54 and look.

My bad... I misunderstood you.

For example, #95 for the "Dreambox v2" is "shift-info" but for the "Toshiba CT-90047" it is "OEM vol+" These don't seem logically related.

I haven't done anything to further define the generic list since adding the Dreambox and Toshiba.

Maybe what I should do is simply fill out the default names with "button85" - "button136", just so there we have something.

That'll probably do for now.

Another question: what about the device buttons?

What about 'em? They can't be assigned anything by KM on the Buttons sheet, so they're not an issue in this context.

gfb107 · Post by **gfb107** » Fri Oct 10, 2003 1:41 pm

Mark Pierson wrote:
Another question: what about the device buttons?
What about 'em? They can't be assigned anything by KM on the Buttons sheet, so they're not an issue in this context.

I was thinking in terms of Mike's point about the Intuitive remote, where the device key is present in the button map, and the normal use is to assign the power function to it, since there is no power button on the remote.

Mark Pierson · Post by **Mark Pierson** » Fri Oct 10, 2003 3:09 pm

gfb107 wrote:I was thinking in terms of Mike's point about the Intuitive remote...

Depending on the selected device type, the location of the generic Power button becomes "CBL", "TV", or "VCR". The Intuitive is the only case like this that I'm aware of.