Create and deliver personalized experiences across digital properties at scale
Build engaging websites with intuitive web content management
Leverage a complete UI toolbox for web, mobile and desktop development
Build, protect and deploy apps across any platform and mobile device
Build mobile apps for iOS, Android and Windows Phone
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Automate UI, load and performance testing for web, desktop and mobile
Host, deploy and scale Node.js, Java and .NET Core apps on premise or in the cloud
Optimize data integration with high-performance connectivity
Automate decision processes with a no-code business rules engine
Globally scale websites with innovative content management and infrastructure approaches
Content-focused web and mobile solution for empowering marketers
Faster, tailored mobile experiences for any device and data source
UX and app modernization to powerfully navigate today's digital landscape
Fuel agility with ever-ready applications, built in the cloud
It’s been a while since I posted Part Two of the series on support for mobility in OpenEdge and I’m sure many of you have been on the (Open)edge of your seats in anticipation of the next thrilling installment. Well the wait is over!
The recently released OpenEdge 11.2 ESAP contains many of the bits that will ultimately be available in the GA version of OpenEdge 11.2 scheduled for February 2013.
Let’s take a poke around: In Progress Developer Studio for OpenEdge (PSDOE) we now have support for a Project of type ‘Mobile’.
And there’s a brand new visual designer in PDSOE integrated into the IDE: The OpenEdge Mobile App Builder is a cloud-based service, thus supporting collaboration, and has extensive support for jQuery Mobile components. Although cloud-based, the Mobile App Builder allows developers to copy source files to the local workspace providing support for any source control mechanisms which may be in place. The Mobile App Builder also supports incremental test and development with a range of device emulators (iOS, Android and various form factors) baked into the facility. We’ll take a deeper dive into the App Builder in a future blog post, exploring how simple it is to hook up events in the UI to back-end, OpenEdge-based services and ship data over the wire.
But what use would a Mobile App be without data from the OpenEdge database?
The OpenEdge Reference Architecture defines a Business Entity (BE) and we’ve integrated this metaphor into PDSOE. The BE leverages the notion of an abstract schema i.e. a ProDataSet or a TempTable as a convenient way to automatically generate reusable ABL classes.
The PDSOE wizard will optionally create “CRUD” operations against the BE. In our generated code, we can typically customize the data which is populated to the ProDataSet. Here is a short example of the data retrieval that is associated to the READ operation in the Business Entity (similar code is generated for other operations):
In addition, existing code can also be annotated to identify internal procedure or methods which may be required as part of the service interface (OERA). When you’re good with your BE’s, you can integrate them with the Mobile Service developed in an earlier step:
I hope this short post whets your appetite for OpenEdge Mobile. Stay tuned for a closer look at the wonderful world of JSDO’s and “the catalog” in a future post!
Gary is responsible for developing go-to-market strategies, providing technical marketing support and developing best practice materials for the Rollbase aPaaS platform.
Copyright © 2016, Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks or appropriate markings.