cool, sounds good to me.
Quote: Originally Posted by
sama 
The idea I had there was that using a button would cycle through the gestures top to bottom. but then I wasn't sure how the user would keep track of the context they're currently in. I then thought that a mechanism is required to inform the user, like perhaps an overlay bit of text.
The text overlay is an idea, it would have to fade away or go away and not be persistent though. Maybe a gesture that shows you what context you are in?
Quote: Originally Posted by
sama Interesting approch and I like it. However what of contexts that do not have an app window title? I mean, skins within RR say that do not embed an app? Does RR change it's title based on the skin page it's on?
No RR keeps the same window title, but the only time you would need to change the context for RR to something different would be when you have an embedded application running, like GPS or the webbrowser. I really cant think of anything else you would really need to have a different set of commands.
RR is pretty easy to control as far as keyboard goes, LEFT, RIGHT, UP, DOWN and ENTER will navigate the whole app. I dont think in practice you with need to have different context on different standard screens in RR as they all can be controlled with those 5 keys. Only embedded apps would need a different context. If the driver app would accept commands from RR to switch the context everything would be golden on RoadRunner side of things.
Quote: Originally Posted by
sama This is the approach I had in mind. Also, inh mentioned above that RR uses keyTBL and execTBL to allow context switching. So for RR, it looks like just pumping out some key presses from the driver may allow this to integrate with RR
Yup, pretty much thats all thats needed and the ability to run an application with command line options.
Quote: Originally Posted by
sama Another way is to write a file somewhere, which tells the current context. This would allow many apps to get that info, but for FE's, this would require additional code.
I guess the ultimate way of making this work, is to request integration from FE writers.
I think all the top 3 FE's, RR, CF and SD (is there really anything else on the same level) all have some sort of keyboard control for all its functions. So i dont think this would even be necessary.
will there be a mouse mode?