1. Elvis Cardenas
  2. PowerBuilder
  3. Wednesday, 5 July 2017 21:15 PM UTC

Power Builder 2017 Include treatment json library?

 

Tanks

Elvis C.

Accepted Answer
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 6 July 2017 04:16 AM UTC
  2. PowerBuilder
  3. # Permalink

Hi Elvis;

1) No, native PB does not support JSON yet.

2) JSON is supported in PB 2017 Universal for Mobile Apps only.

3) As a workaround ... http://powerbuilder-world-tour.com/downloads/NCPBUG-Conference-balent-JSONparser.pdf

Note: JSON is planned for native PB in 2018  ...  https://www.appeon.com/developers/roadmap/json-support.html

HTH

Regards ... Chris

Comment
There are no comments made yet.
Roland Smith Accepted Answer Pending Moderation
  1. Thursday, 6 July 2017 00:45 AM UTC
  2. PowerBuilder
  3. # 1

Hopefully a future version will support JSON in a similar way to the existing XML support.

Comment
There are no comments made yet.
Arcady Abramov Accepted Answer Pending Moderation
  1. Thursday, 6 July 2017 07:26 AM UTC
  2. PowerBuilder
  3. # 2

Chris,

I hate to sound like a broken record, but it looks like trying to support all these third-party stuff is a major waste of resources, not to mention a futile one. There are miriads of them, you will never get them all and always be lugging behind.

You can get the PB Native to support all of them, both present and future by allowing easy consumption of .NET assemblies, which were designed specifically for those third-party stuff.

 

For example - all you have to do to convert a datastore to JSON or to XML, to anything else for that matter, is to convert it to a .NET class with some collections. There are widely-used .NET modules whose whole purpose in life is to take these classes and convert them to whatever. Let them do the heavy lifting, many of them are free and almost all very cheap, PB developers will not be burdened by the additional costs.

And it works vice-versa as well. If you could just expose a PB native datastore as a .NET DataTable, then there would be a much wider use of PB .NET assemblies in .NET solutions. It is a pain to write C# or VB.NET code for DB selections and updates, so people would gladly use PB for this purpose.

Yes, I know I sound like a broken record.... Sorry about that

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.