Re: Jacada Seagull and the like

>
> Even so, your approach and mine differ in a significant point: with PSC400,
> programs do not have to use any special "uniform API", because the PSC400
> tool will convert standard RPG I/O opcodes to calls to the PSC400 API.
This
> is done automatically, in under a minute.
>
> I agree that once you have a common API, the web side of things is
> possible - in fact it's relatively easy.  The hard part is to take an
> existing program - one that uses indicators on attributes, and subfiles,
and
> ERRMSGID, and message subfiles - and convert it to a program that can be
web
> enabled.

but you have an underlying screen description: DDS and the things you tie
into
a screen, e.g. subfiles. Even if you are using a user-defined datastream. The
datastream itself is a description of the screen. Both DDS and the datastream
can be used to build an internal "image" of the screen, which you then
generate
the HTML from. There are actually people that do that (I helped them). E.g.
http://www.twincentric.com.

This is not meant to belittle your product or effort (it is great). Just to
point
out that you are not quite alone.

Keep it up!
Leif