>That doesn't sound simple to me, at all. The server interface is a 5250
stream!
I guess I was basing my simple comment on the below FOR loop that is
processing the screen character by character. What if there was an
integer handler of some sort that when encountered would cause a call to
an custom API that would retrieve the values to generate a drop down. Not
saying mine is the best of ideas, but sometimes throwing something out
there will trigger somebody else's brain to think of something way better.
for i= 2 to 24;
%><pre style="position:absolute; margin-left:0; margin-top:<%=
%char((i-1) * 22 + 4) %>"><%
for j=1 to 80;
c = %subst(vts.scn80x24(i):j:1);
select;
when c = x'20';
responseWrite('</b> ');
when c = x'22';
responseWrite('<b> ');
when c < ' ';
responseWrite(' ');
other ;
responseWrite(c);
endsl;
endfor;
%></pre><%
endfor;
>It would be a pity to extend the scope of this interface to an
unreasonable extreme.
Do you feel that drop-downs are a waste of time? I sure do think they
have use and believe users would request/expect them to be a part of any
web initiative.
Aaron Bartell
http://mowyourlawn.com
Nathan Andelin wrote:
From: Aaron Bartell
The one thing that comes to mind is simply having an "indicator" in
the stream that would tell a custom ExtJS script to render the data
elements as a drop down and also specify how to map the data to
the correct input field when it gets back to the server.
That doesn't sound simple to me, at all. The server interface is a 5250 stream! It's not like you can modify the WRKSPLF command to insert "an indicator" or have an IBM command respond to a request to fill in a drop-down. IBM controls that part of the interface.
And even if you were dealing with an RPG program, and had access to the DDS and RPG source, you'd still be dealing with the 5250 protocol.
It would be a pity to extend the scope of this interface to an unreasonable extreme.
Zend and IBM partnered on a 5250 bridge that exchanges XML between PHP and IBM's Webfacing server. What Niels has come up with is already a lot more efficient than that; and Niels can simplify the messaging between the client and server even further, using ExtJS with JSON and some kind of protocol. That's where I'd suggest he focus his efforts.
Nathan.
As an Amazon Associate we earn from qualifying purchases.