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

Resolved Guidance for PowerBuilder 2019 and beyond

  1. Advice
0
Votes
Undo
  1. Bradley Schultz
    Bradley Schultz
  2. Beta Testing
  3. Wednesday, 27 February 2019 20:01 PM UTC

I want to clarify the recommended direction for PB applications moving forward. Is it correct to say that Appeon is recommending customers move away from using the PB Desktop functionality? It appears that the guidance moving forward will be to generate PowerBuilder .NET assemblies that can be aggregated into ASP.NET and or other .NET desktop technologies?

There will not be technology to utilize C#/.NET assembiles directly in PowerBuilder desktop applications(other than via COM/etc)? 

Slow start of pb 2019 ide
Publish RestFull Service
Responses (1)
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 27 February 2019 20:29 PM UTC
  2. Beta Testing
  3. # 1

Hi Bradley,

No, it is not that we are recommending customers to move away from PB desktop functionality.  In fact, the next major release of PowerBuilder (after PowerBuilder 2019) has planned to revamp the desktop functionality with a cloud-installable version: https://www.appeon.com/developers/roadmap/desktop-cloud-app.html And in this version we added UI Themes for PB desktop: https://youtu.be/AegyiYsjEqA We wouldn't invest to do these things if the plan is to move away from PB desktop.

But the new generation of PowerBuilder is all about open standards.  So when we designed the new C# Web API and assembly features we did so based on the open-source cross-OS .NET Core and ensuring that these features were compatible with not only a PB desktop app but also with ASP.NET pages and any other UI technology that follows open standards.  So surely you will see us promote the openness of what you can do now.

Also, we opened up the DataWindow control of a PB desktop app to the world of REST Web APIs... think of this as the new generation of the old SOAP Web Service DataWindow.  Specifically, we introduced a new RESTClient object to make it very easy (with very little coding) to call any REST Web API, including a REST Web API developed with PowerBuilder 2019.  And also, the RESTClient added support to directly pipe data in and out of the DataWindow control.  https://youtu.be/vdRmuarEnMk

And just to clarify, us putting a lot of focus on the middle tier (C#) in PowerBuilder 2019 is not to imply we are moving away from PowerScript or the desktop.  Rather, we were forced to put a lot of focus in this area because Sybase failed to deliver a popular solution for the middle tier - either they shipped expensive and proprietary solution (EAServer) or half-baked and proprietary solution (PB.NET).  These days most customers won't build a new enterprise system without a middle tier.

Hope this clarifies where PowerBuilder is heading, and of course please keep checking our roadmap page, which should be consistent with all that I said.  https://www.appeon.com/developers/roadmap

Regards,

Armeen Mazda
CEO, Appeon

 

 

Comment
Olan Knight
  1. Olan Knight
  2. Wednesday, 27 February 2019 21:44 PM UTC
Wonderful! Thanks for the clarity, Armeen!
  1. Helpful
Kevin Ridley
  1. Kevin Ridley
  2. Thursday, 28 February 2019 16:04 PM UTC
Too bad we couldn't fix EA Server. That was good stuff. I guess I'll just be like Chris when DPB went away! :(
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 28 February 2019 18:30 PM UTC
DPB ... Oooooo, Ahhhhhh ... stop teasing me Kevin - LOL!
  1. Helpful
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.