phil at pgpotter.co.uk
Mon Feb 14 09:28:13 UTC 2022
Omnis seems to think, what appears to be a remote task, is a remote
form, and is looking for the remote task to link with it...
I don't think that could work with an ultra thin solution?
Seems you need to just open a specially crafted web page, that will act
like the ultra thin form, but I guess does not need the login, or has it
incorporated within it, or needs a bunch of settings to open the
specific page you are hoping to display in oBrowser...
Or failing that, just open the same login page as a user would have in
Based in Chester in the UK.
On 14/02/2022 00:19, Rob Mostyn wrote:
> Hi $All,
> I have a conundrum… We have an ultra thin web app which has been working well for years.
> As our web app requirements have evolved and become more sophisticated, the complexity of the code has become greater.
> The content of web pages is managed through a window in a fat client app (same library opened in different contexts).
> What I want to do is from the window class instance to kick off a remote task that will run the desired web object and return the page content back to the window to be displayed in an oBrowser window so I can see the result. I created a remote task, subclassed from the remote task in the web app and then I try to to this:
> Do $classes.rtPageDisplayTest.$open()
> When I do this I get the error message:
> To use a remote form class, you must set the design task of the remote form class to a remote task
> $open is not a method normally available to the remote task but when it is typed in, Omnis syntactically resolves it and applies the coda-chroming to suggest it is a legal statement.
> This message does not surprise me. I am trying to open a remote task from a regular task and I know I am “breaking the rules”. Has anyone figured out a way to trick Omnis in doing this?
> Rob Mostyn
More information about the omnisdev-en