The chat screen in the RSDC scheduler is a persistent view.
Comments are stored in the database. Anybody can log in
and see all the past messages, as well as stay logged in and
watch realtime messaging.

True, but I'm introducing the idea of starting with a screen design using HTML, pulling in light-weight JavaScript libraries which you might use across many of your applications, then adding a little bit of "glue script" to make an interactive prototype. When that's done, implement calls to the server.

That's sort of my point. This is a real applications, with real
business logic. Sure, you can make something that looks like
a chat screen, but can you actually add the business logic that
makes it work?

Of course. But that's the final step.

And now you're writing JavaScript as well as RPG; as the amount
of JavaScript grows, then at some point you're not really doing
RPG-CGI, are you?

I don't advocate writing a lot of JavaScript. But I do advocate using JavaScript libraries when an application calls for it.

Nathan.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.