Good to hear from you. Hope all is well with you. In answer to your questions:
1. Yes. While code can be executed on the jsClient, you can also execute code on the Omnis server that the jsClient is connected to.
2. Yes. It’s not the preferred setup – Code Classes are considered to be “not good Object-Oriented design”. That being said, if you’re converting your app to a more modern setup, code classes can be a stepping stone into the Object-Oriented world.
3. No. No copy/paste from thick client window objects to remote forms. You have to remake your interface using the objects specifically made for the remote form. You could consider writing some code to do the work for you, and create an equivalent of each field in the remote form, but what you find is that the remote forms don’t work quite the same way as a window would. Depending on how your thick-client application works, there could be huge differences between the two.
4. No. There is a “Background object”, which can be set to be a line, or a circle, rectangle, image etc.
5. Yes. Keep in mind, unless you’re deploying a “serverless client”, you need an Omnis Server running somewhere that your jsClient connects to. That’s where the externals etc are installed.
6. I suspect the mailing list 🙂
A man rushed into the doctor’s office and shouted, “Doctor! I think I’m shrinking!”
The doctor calmly responded, “Now, settle down. You’ll just have to be a little patient.”
Paul W. Mulroney
We Don't Do Simple Pty Ltd
ACN 161 009 374
Bentley Western Australia 6102