You must be one of the "one mouse button" folks from days of yore. The schema I presented is in NO WAY complex, it's very intuitive. Also, the screen border can be dynamically calculated to contrast with whatever color the rest of the page is.
That fact that you have to keep coming up with new exceptions and rules—and a tutorial to tell users how to use a Web browser--makes it complex by nature.
And if the “use Flash gestures here" border is different on every page, then it’s even less intuitive to tell it apart from all the other borders on pages.
However, I have a better plan:
How about Apple letting Adobe make a Flash app in the store, they can even sell it for $9.99 and MANY would buy it. If you click on a flash on a website, the flash app opens with the touchscreen rules I defined above (which WILL work for most of the flash sites just fine by the way) sort of like clicking on a video file and the video player opening up in the iphone. If Apple isn't truly afraid of Flash apps bypassing their store, they'll let Adobe put a flash player app in the app store.
That IS a good plan for some things (and probably doable: Adobe is working on Flash executable tools for iPhone). I like it! But Flash has to talk to the rest of the page much of the time, so even that is not a catch-all solution. Good for games, though. (But games need more complex mouseover actions, and they need them quicker. And they often need a keyboard!)
And a solution that only works “sometimes” is, again, Flash done BADLY.
(BTW we already DO have some Flash apps in the app store. Individual self-contained Flash games. Adobe has yet to put the next version of Flash on sale, but when they do, this is another tool for app developers. Nice to have options! And Apple allows it.)
I've been developing in Flash since version 2, prior I used director. With ActionScript 3 and how it handles mouse event, and the fact I know how to program, is why I say it's really simple for me to adjust a mouse's behavior. I can see if you're one of those timeline only Flash guys that has scripts vomited all over the place that it might be an issue, but if you build everything in AS3 and keep it organize, adjusting a button's listener is a simple matter.
I’m not a timeline programmer, I’m an ActionScript programmer, and it is NOT really simple to adjust the mouse’s behavior if doing so requires that you ALSO change the function of the app you’re making. One line of code changes a roll to a click. A LOT more than that is needed to make the change make any sense. Look at some Flash games and video players—I’m not talking about really simple menu buttons.
Say you have a video player where controls pop up on mouseover, but you pause on click. So—you remove the click-to-pause (annoying your users) and then you change it to a click to make the controls appear. But then the controls start hidden! So you make them visible by default. And then they stay in the way, instead of auto-vanishing the way they normally would on mouse-out. So then you add a timer so they go away even if the mouse IS over them. And then that annoys someone who clicks at the moment it vanishes. So then you try maybe changing the size of the Flash app (affecting the whole surrounding page) so that the controls are below the video instead of over it. Your designers don’t like the look and they don’t like the wasted space. And all of it requires decisions and meetings and approvals from tons of people. And testing. And maybe trying a couple options to see which looks best. And now your one line of code is not so simple. If you’re a commercial Flash developer, you know what I’m talking about
And my point was,
even if it IS really simple to reprogram a Flash app (and if the original source file and programmer are always readily available) it is STILL not going to happen.
You could tell every Flash site to type an asterisk on the page—one second of HTML work—and it still wouldn’t get done Web-wide because we’re talking about thousands of sites.
And if only “some” Flash sites work, then that’s Flash done BADLY.