On Nov 5, 2010, at 2:52 AM, Matthew Farwell wrote: > For me, the main advantage of using a browser for RIA is you don't need to > install anything on client machines. However, there are a couple things that > always irritate me when I'm doing RIA for clients, as opposed to a > traditional application. > > Please note that I'm not talking about public web sites, I'm talking about > internal applications that are not exposed to the public. So please don't > respond 'I wouldn't want this to happen on my browser', it's not going to > happen on your browser. You will never see this application, you won't even > know it exists. > > 1) Disabling navigation/back button functionality. This gets me every time. I > NEED to be able to prevent the user from going back a page. No discussion, no > 'You should educate the user not to do that'. Taking firefox as an example, > you can go back a page in (at least) three ways: backspace, click on the back > button, right click on the page. That means I have to somehow prevent the > user from doing these three things. And not counting refresh, multiple > submits and preventing them from entering a different URL. What is needed is > the option to disable navigation. Full stop.
No, you are doing it wrong. This is NOT how a web page is supposed to work, whether on a corporate LAN or via the Internet at large. I ** HATE ** it when web apps try to get around the fact that they are web apps by playing little tricks like hiding the menu or trying to disable the back button. I'd suggest if you *really* need to do this, HTML is the wrong tool for the job you are trying to do. Write a real desktop application for god's sake, in Swing for example. Not every problem can be solved by HTML! Rob -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
