Reply to thread

Message: <blockquote data-quote="hallergard" data-source="post: 507940" data-attributes="member: 97639">Thanks, zunixnuz.  We have problems understanding eachother, but we are getting there.   I think that the FirefoxIntegrator is a very interesting concept.  Today computers and TV:s are merging technologies.  The first TV:s with internet are in my opinion approaching this from the wrong side - they are adding a mobile phone operating system rather than a proper system.  So be it, but they run into the problem of how to surf the internet with a remote controller.  What they have so far come up with is getting partners (YouTube & Picasa) to write special sites that are easy to tab with the direction keys - but it means you don't get their full service.  Best so far is Panasonic, but not good enough in my opinion.  I believe the the TV should become just a very good one montior on the home network at least as far as internet goes.  But you have to be able to use the remote as a mouse and be able to text (sms) your searches.  I am surprised that Philips doesn´t push their Pronto concept with their Net-TV.  Anyway, this is why I am trying to understand how FirefoxIntegrator works.When I configured MP to use the Hauppauge remote, the MP itself works perfectly with the remote without any mapping whatsoever, but starting the FFI there is nothing the remote can do.  I have concluded that the FFI is written to work exclusively with MCE codes.  So I changed the MP config to using the MCE remote.The first problem I encountered is that MP does not work anymore with my remote, not even up, down, and enter the menu.  I am sure that's rather easy to fix, at least the essentials, but this is not my priority right now.Then starting FFI the remote of course doesn't work with my old (Haupauge) mappings.  My remote has 45 buttons, problem areas:a.  0-9 and VolUp and VolDown do have the same codes!b.  12 of the buttons send codes that MCE doesn't recognise, eg the OK button sends code59 which is not recognized by MCE (which uses code34 for OK - and H cannot send code 34) - so I cannot use the OK button.c.  22 of the codes are in common with MCE, but for different buttons - so quite some remapping has to be done.  Believe that I will be able to keep the most important navigation commands, but this requires the mouse to function - otherwise I will loose to much of the Firefox capabilities.d.  The 22 buttons in c) will not be good enough to manage my (non internet, non-FFI) multimedia menus written in simple HTML.  E.g. I have to use F6 to move to next frame but FFI recognizes F6 only as Zoom in.  Using the H mode command I am hopeful to create a [firefox] mapping for FFI and a [mozilla] mapping for my family videos.I just managed to get the mouse to function with the remote - so I feel quite optimistic about this right now, though I have a lot to do to wrap it up.</blockquote>

Verification