|
From: Jon Paris <Jon.Paris@partner400.com> > What I am trying to do is to build a new app with completely separated UI > logic. > > So - it seemed to me that defining the data in XML and using XSL to do the > browser transforms was a reasonable approach to this. What I wanted to do > was apply the same principals to the 5250 users. Since using conventional > DDS based screens does not offer the required flexibility, the notion was to > generate the 5250 XSL (or some internal equivalent) by working with some > kind of design tool to determine where on the screen each piece of the data > should be displayed etc. etc. The XML would then be transformed into 5250 > datastream (and back) by the UI handler. > > > So - does this work? If not - what is the alternative? > Jon, I have worked on a project where we did this, but no special tool was used. Maybe somebody knows what magic dust to sprinkle over the screen. We didn't, but it was not hard to do in the first place, so we stopped looking for tools.
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.