JP1 Remotes Forum Index JP1 Remotes


FAQFAQ SearchSearch 7 days of topics7 Days MemberlistMemberlist UsergroupsUsergroups RegisterRegister
ProfileProfile Log in to check your private messagesLog in to check your private messages Log inLog in

New 6805 RDF's
Goto page Previous  1, 2, 3, 4  Next
 
Post new topic   Reply to topic    JP1 Remotes Forum Index -> JP1 - New Remotes & RDFs
View previous topic :: View next topic  
Author Message
Nils_Ekberg
Expert


Joined: 02 Aug 2003
Posts: 1689
Location: Near Albany, NY

                    
PostPosted: Mon Oct 13, 2003 3:44 pm    Post subject: Reply with quote

The Robman wrote:
I have just re-bundled IR.exe together with all the current RDFs (as v3.21b). I have also bundled all the current RDFs together in their own zip and called it version 1.00

These include the 6805 RDFs from Mike's zip and the two Mil4 RDFs that Jim put in the RDF folder.


Rob, the RDF's in Mike's zip were not RM compliant plus the Mil4 that Jim had put in the RDF folder have been updated a few times. I just submitted to Greg additional updates to them plus more in the jp1-km files/RMImages and maps folder. See this thread: RM Updates

I believe the full set of RDF's that come out later today with the next release of RM is more up to date.

If we are in fact going to maintain the RDF's seperate from IR, KM, and RM we may also want to consider putting the RM maps and images in the same distribution zip file with the RDF's since they are so closely related. JUST A THOUGHT............
_________________
Nils
Files Section
Diagnosis File Section
Back to top
View user's profile Send private message Send e-mail
Mark Pierson
Expert


Joined: 03 Aug 2003
Posts: 3017
Location: Connecticut, USA

                    
PostPosted: Mon Oct 13, 2003 4:19 pm    Post subject: Reply with quote

Nils_Ekberg wrote:
If we are in fact going to maintain the RDF's seperate from IR, KM, and RM we may also want to consider putting the RM maps and images in the same distribution zip file with the RDF's since they are so closely related.

IMHO, the maps and images are only related to RM and should be included with it, not as part of the RDF archive.
_________________
Mark
Back to top
View user's profile Send private message Send e-mail Visit poster's website
The Robman
Site Owner


Joined: 01 Aug 2003
Posts: 21237
Location: Chicago, IL

                    
PostPosted: Mon Oct 13, 2003 4:24 pm    Post subject: Reply with quote

My goal was to establish a starting point and version number and to try and bring the multiplying RDFs back to where they belong. I know that I've totally lost track of where all the various versions are.

Anyway, I just made you a moderator in the jp1-yahoo group, so you have the ability to replace the rdf zip file if you like.

I don't have a problem with including the maps and images in the same zip.
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
Back to top
View user's profile Send private message Visit poster's website
Nils_Ekberg
Expert


Joined: 02 Aug 2003
Posts: 1689
Location: Near Albany, NY

                    
PostPosted: Mon Oct 13, 2003 4:40 pm    Post subject: Reply with quote

Mark Pierson wrote:
Nils_Ekberg wrote:
If we are in fact going to maintain the RDF's seperate from IR, KM, and RM we may also want to consider putting the RM maps and images in the same distribution zip file with the RDF's since they are so closely related.

IMHO, the maps and images are only related to RM and should be included with it, not as part of the RDF archive.

I agree that they only relate to RM but I was looking at it from the point of view that if an RDF changes there is good odds the map will need to change. If we have to wait for an RM release for the maps we could get out of synch on the maps and RDF's quick. Maybe a compromise is to include the maps and not the images. The maps are small, 2k each, and could be included in a sub zip file within the RDF zip file or sorted with the RDF's at the top.

What do you think?
_________________
Nils
Files Section
Diagnosis File Section
Back to top
View user's profile Send private message Send e-mail
Nils_Ekberg
Expert


Joined: 02 Aug 2003
Posts: 1689
Location: Near Albany, NY

                    
PostPosted: Mon Oct 13, 2003 4:51 pm    Post subject: Reply with quote

The Robman wrote:
My goal was to establish a starting point and version number and to try and bring the multiplying RDFs back to where they belong. I know that I've totally lost track of where all the various versions are.

Anyway, I just made you a moderator in the jp1-yahoo group, so you have the ability to replace the rdf zip file if you like.

I don't have a problem with including the maps and images in the same zip.

I agree with the goal 100%. After Greg does his next release tonight I will upload the complete set of RDF's to jp1. I will not include the maps and/or images until we agree on a direction with them since Mark is not comfortable with it, Greg has not chimed in yet, and there are others to hear from..
_________________
Nils
Files Section
Diagnosis File Section
Back to top
View user's profile Send private message Send e-mail
jamesgammel
Exile Island Resident


Joined: 03 Aug 2003
Posts: 394
Location: Gillette, Wyoming

                    
PostPosted: Mon Oct 13, 2003 6:43 pm    Post subject: Reply with quote

Faster downloads, and reduction of duplicity is also part of the goals. Several of us have shown that an IR download can be reduced to IR.exe, and really jst a few other pretty small files. I haven't seen where inserting IR.exe, and the other related files "breaks" RM or IR.

Since maps very often get changed along with rdf's for RM they are essentially integral. Of course, the Images themselves are RM specific, and at some point Nils should be done with them, save a new model being added. I would think that the maps should be getting to a similar stable point.

What I don't know is if the images and maps can be contained in a sub-folder within the rdf folder. If so, and I'm guessing Greg will have to adjust the coding of RM to account for doing that, and possibly with less strictness to "versionating". IR should simply just ignore maps, images, etc. since they aren't "rdf extension files. Some testing should be done to confirm this.

If someone isn't using RM, but prefers KM for whatever reasons they may have, they do have the option to simply not extract the images and maps, or delete them if they do extract them. Or simply ignore that they are there, providing IR does as well.

If images can reach some stable point not requiring so many updates or upgrades, save a new model, then maybe images and maps can be it's own zip.

Everyone regardless of how they choose to make upgrades has to have IR. There's no requirement that they make upgrades. For some, maybe all they want is a way of preserving their configurations, installing extenders or special protocols, or an easier way than manually for doing keymoves and making macros. IR does require rdfs. So this person would only need to download the rdf file, and download IR and extract to the same folder, maybe renaming it "IR".
KM is a standalone, just requiring Excel. RM (Now) isn't a standalone. It requires downloading a specific Java program, and wioll now also require rdf's, which he may already have from getting IR and RDFs to use IR, as well as the Imaages and Maps.

Maybe the best solution is Tolls will contain IR (versionated), KM (versionated), RDF's (Versionated), and Images and maps (also versionated). Any change made in any, no matter how small or seemingly insignificant should be accompanied by a version change. A user should know right away from the version whether or not he needs to update. ALL updates need to be announced as well, and quote prominantly. Perhaps this site needs a bulletin board where the current version is posted, and should be something a user doesn't have to enter to see, but almost smack him in the face when he logs in. Of course, all the moderators should have the ability to change the version number. Rob and/or Mark would have to know if something like this could be set up.

<two cents off>

Jim
Back to top
View user's profile Send private message Send e-mail Yahoo Messenger
cdhixson



Joined: 04 Aug 2003
Posts: 48
Location: Charlotte, NC USA

                    
PostPosted: Tue Oct 14, 2003 7:43 am    Post subject: Reply with quote

What about rdf files that are not currently included in the IR distribution. The one I know of is for the RS 15-1994 Extender 5. This rdf has never been included in the IR package. I have kept my copy up to date with the changes needed for RM. Should we include these into the standard IR and rdf packages?
Back to top
View user's profile Send private message Send e-mail
Nils_Ekberg
Expert


Joined: 02 Aug 2003
Posts: 1689
Location: Near Albany, NY

                    
PostPosted: Tue Oct 14, 2003 8:16 am    Post subject: Reply with quote

cdhixson wrote:
What about rdf files that are not currently included in the IR distribution. The one I know of is for the RS 15-1994 Extender 5. This rdf has never been included in the IR package. I have kept my copy up to date with the changes needed for RM. Should we include these into the standard IR and rdf packages?

I don't see why not since it is still in use. Either post it or send it to me in e-mail and I will include it in the zip file.
_________________
Nils
Files Section
Diagnosis File Section
Back to top
View user's profile Send private message Send e-mail
gfb107
Expert


Joined: 03 Aug 2003
Posts: 3411
Location: Cary, NC

                    
PostPosted: Tue Oct 14, 2003 8:26 am    Post subject: Reply with quote

Nils_Ekberg wrote:
I will not include the maps and/or images until we agree on a direction with them since Mark is not comfortable with it, Greg has not chimed in yet, and there are others to hear from..

I think the images and maps should be bundled with RM, and the RDFs should be distributed by themselves.

There are 2 reasons that the map files are currently churning so much.
  1. The images are still changing. When this happens, all the button shapes need to be adjusted. This is independant of the RDFs.
  2. The buttons names in the RDFs are being modified, and since the maps tie the button shape to a button by name, the names need to be adjusted. I'm starting to think it might make sense to use the keycodes instead to avoid all the churn. It also allows remotes that use the same image but diffferent button names to use the same map file. It makes it a little harder for the map coder, but makes maintenance easier.

_________________
-- Greg
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)
Back to top
View user's profile Send private message Visit poster's website
cdhixson



Joined: 04 Aug 2003
Posts: 48
Location: Charlotte, NC USA

                    
PostPosted: Tue Oct 14, 2003 8:45 am    Post subject: Reply with quote

Nils,

We need to be careful about what you upload to the JP1 files area. Mark Pauker has not released a new official version of IR that can handle the generic button names. The ImageMap line won't break the current version of IR so that can be included. It would be nice to have the same rdf files for IR and RM, but we're not there just yet.

Chris
Back to top
View user's profile Send private message Send e-mail
Nils_Ekberg
Expert


Joined: 02 Aug 2003
Posts: 1689
Location: Near Albany, NY

                    
PostPosted: Tue Oct 14, 2003 9:01 am    Post subject: Reply with quote

gfb107 wrote:
I think the images and maps should be bundled with RM, and the RDFs should be distributed by themselves.

There are 2 reasons that the map files are currently churning so much.
  1. The images are still changing. When this happens, all the button shapes need to be adjusted. This is independant of the RDFs.
  2. The buttons names in the RDFs are being modified, and since the maps tie the button shape to a button by name, the names need to be adjusted. I'm starting to think it might make sense to use the keycodes instead to avoid all the churn. It also allows remotes that use the same image but diffferent button names to use the same map file. It makes it a little harder for the map coder, but makes maintenance easier.

  1. I am comfortable with bundling the maps and images with RM, Especially since we have them down to a reasonable size and we won't have to distribute the RDF's with RM.
  2. I actually like the idea of tying the map shape to the button code just not looking forward to making the change but that has been my biggest headache with RDF button names changing. For migration from text to number could you make it both ways or would it have to be all or nothing? I assume you would pick up the button name from the RDF based on the button code in the map.

_________________
Nils
Files Section
Diagnosis File Section
Back to top
View user's profile Send private message Send e-mail
gfb107
Expert


Joined: 03 Aug 2003
Posts: 3411
Location: Cary, NC

                    
PostPosted: Tue Oct 14, 2003 9:18 am    Post subject: Reply with quote

cdhixson wrote:
Nils,

We need to be careful about what you upload to the JP1 files area. Mark Pauker has not released a new official version of IR that can handle the generic button names. The ImageMap line won't break the current version of IR so that can be included. It would be nice to have the same rdf files for IR and RM, but we're not there just yet.

Chris

Good point, Chris!
_________________
-- Greg
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)
Back to top
View user's profile Send private message Visit poster's website
gfb107
Expert


Joined: 03 Aug 2003
Posts: 3411
Location: Cary, NC

                    
PostPosted: Tue Oct 14, 2003 9:27 am    Post subject: Reply with quote

Nils_Ekberg wrote:
I actually like the idea of tying the map shape to the button code just not looking forward to making the change but that has been my biggest headache with RDF button names changing. For migration from text to number could you make it both ways or would it have to be all or nothing?

I'll try to make it go either way. The only issue is the digit buttons. I'll assume that a single digit is a name. So, when using keycodes, either use HEX ($xx), or use more than 1 digit.
Quote:
I assume you would pick up the button name from the RDF based on the button code in the map.

Yes, the display name comes from the button after the match is found. The only exception is when the map file overrides the button name as in URC-43000B01.MAP
_________________
-- Greg
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)
Back to top
View user's profile Send private message Visit poster's website
Nils_Ekberg
Expert


Joined: 02 Aug 2003
Posts: 1689
Location: Near Albany, NY

                    
PostPosted: Tue Oct 14, 2003 9:36 am    Post subject: Reply with quote

gfb107 wrote:
cdhixson wrote:
Nils,

We need to be careful about what you upload to the JP1 files area. Mark Pauker has not released a new official version of IR that can handle the generic button names. The ImageMap line won't break the current version of IR so that can be included. It would be nice to have the same rdf files for IR and RM, but we're not there just yet.

Chris

Good point, Chris!


Really good point. I just tested the generic name changes with the beta version of IR and it works fine but the 321 version does not.

Any idea when the new version of IR will be released?

Greg, you better not distribute what I sent you last night as they were all with the generic names. For IR purposes what was in RM 72 is current with the exception of the new 6805 RDF's
_________________
Nils
Files Section
Diagnosis File Section
Back to top
View user's profile Send private message Send e-mail
The Robman
Site Owner


Joined: 01 Aug 2003
Posts: 21237
Location: Chicago, IL

                    
PostPosted: Tue Oct 14, 2003 9:42 am    Post subject: Reply with quote

gfb107 wrote:
The only issue is the digit buttons. I'll assume that a single digit is a name. So, when using keycodes, either use HEX ($xx), or use more than 1 digit.


I think you need to make it more intelligent than that. If there's no = sign, the entry is a button name and it's keycode is one higher than the previous button. If there is an = sign, the data before the sign is the button name and the data after it is the keycode. If the keycode data starts with a $ sign, it's hex code, otherwise it's decimal code.

Also, I know you're trying to make RM recognize shifted buttons automatically, are you also trying to make it recognize button codes that don't have an entry in the [Buttons] section? IR.exe handles these by calling the entry "Key86" (where 86 is the decimal keycode)
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic   Reply to topic       JP1 Remotes Forum Index -> JP1 - New Remotes & RDFs All times are GMT - 5 Hours
Goto page Previous  1, 2, 3, 4  Next
Page 3 of 4

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


 

Powered by phpBB © 2001, 2005 phpBB Group
Top 7 Advantages of Playing Online Slots The Evolution of Remote Control