|
> From: "Hans Boldt" <boldt@xxxxxxxxxx> > This brings up another good point. Why are you trying > so hard to fit your application into a browser interface, > but then also work hard at getting around all the features > of the browser? Browser menus and toolbars cause problems for users and programmers, and by removing them, one retains 90% of browser features. Your question evoked a lengthly list of reasons in my mind for using browsers, but the one that I'd throw out for consideration is that they integrate so many best of breed technologies. In addition to HTML and JavaScript, you can download documents containing references to Word, Excel, PowerPoint, and PDF, XML and XSL, applets and ActiveX components, which might even implement 5250 interfaces. When integrating multple interfaces, one might consider task swapping between them. The following link illustrates the idea: http://www.relational-data.com/rdweb/taskswap.html This sample is far from robust or complete, but it may begin to illustrate the integration concept. Hyperlinks along the top of the window toggle the visibility of various panels underneath. One of the panels contains a 5250 ActiveX component from Mochasoft, but just as well could have contained a Java applet or some other rich component. This example does use JavaScript. Nathan M. Andelin www.relational-data.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.