Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (4)

Resolved Alternatives for unsupported Inet object

  1. Advice
0
Votes
Undo
  1. S&F Datentechnik
    S&F Datentechnik
  2. PowerBuilder
  3. Monday, 22 November 2021 08:47 AM UTC

Hi,

 

on the obsolete features page from powerbuilder 2019 R3 there was written, that the inet object has no support anymore: https://www.appeon.com/developers/obsolete-features-in-powerbuilder-2019R3.html

What would be a feasible workaround for the hypertextToUrl method?

Will this inet object also be unsupported on powerserver mobile apps for the custom workspace? If so, what would be a workaround for the method above on powerserver apps?

 

Regards,

Jonas Schwartz

PBAccessibility.dll causing application to crash.
Jenkins Job and Orca script
Accepted Answer
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 24 November 2021 07:26 AM UTC
  2. PowerBuilder
  3. # Permalink
Hi Joans, For iOS/Android you should keep using INet. For Windows OS you can use the technique Rene mentioned if you want to use default Web browser if you don't want to use the new WebBrowser control inside your PB app.
Comment
There are no comments made yet.
Responses (4)
René Ullrich
René Ullrich Accepted Answer Pending Moderation
  1. Monday, 22 November 2021 09:17 AM UTC
  2. PowerBuilder
  3. # 1

Hi Jonas,

On Windows it should work to simply "run" the URL. But PBs run function seems not to do what you want. You could use "WScript.Shell" instead (see https://www.rgagnon.com/pbdetails/pb-0151.html).

I don't know how it works with mobile apps.

Regards,

René

 

Comment
Load more comments
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Monday, 22 November 2021 11:38 AM UTC
I think (not completely sure) that the ShellExecuteW API also works on powerserver. (at least I don't recall any problems in the past when having done some migration). Correct me if I'm wrong.
  1. Helpful
S&F Datentechnik
  1. S&F Datentechnik
  2. Monday, 22 November 2021 14:12 PM UTC
My goal on mobile devices is to open other apps via custom url calls. We are doing this by the hypertexttourl method currently. But I don't know how this could be done, if the inet object on mobile development also is unsupported by now.

Im just trying to prevent upcoming problems if we keep using a unsupported method on mobile devices also. But if only the inet object for desktop development is unsupported, using hypertexttourl on mobile devices shouldn't be a problem.
  1. Helpful
mike S
  1. mike S
  2. Monday, 22 November 2021 16:17 PM UTC
an unsupported method is the least of your worries to " prevent upcoming problems" on powerserver mobile.

  1. Helpful 3
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Monday, 22 November 2021 16:37 PM UTC
  2. PowerBuilder
  3. # 2

Hi Heino,

INet is still supported for PowerServer 2020.  It is in PowerServer 2021 that it is not supported (but still we kept the feature in the product in case customers don't want to migrate off of it yet).   So long story short, this is obsolete feature not discontinued feature.

For users of PowerBuilder 2019R3 and newer or PowerServer 2021 and newer, the recommended replacement of INet would be the new Chromium WebBrowser control.  

Best regards,
Armeen

 

Comment
S&F Datentechnik
  1. S&F Datentechnik
  2. Tuesday, 23 November 2021 14:13 PM UTC
Hi,



but how we can use the new chromium webbrowser control as alternative for inet.hyperlinktourl then? We don't wan't to use a visible webbrowser control to open an URL with the default web browser from the device.



And what about the mobile powerserver apps? We are using inet.hyperlinktourl ("tel ..." ) to let an ios or android device call a specific phone number. Also we use this to open other apps installed on the devices. How we should do this when we have to migrate off the inet object?



Regards,

Jonas Schwartz
  1. Helpful
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Wednesday, 24 November 2021 03:23 AM UTC
  2. PowerBuilder
  3. # 3

On a side note: The reason why I'm mentioning the ShellExecuteW API, is that not all users might have Powershell enabled (especially on servers), which is a requirement for the "WShell.Script" method to work, if I'm not mistaken.

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.