Table of Contents
- Auto-Sensing Environment
- Suggested Modifications to PFC
- Unsupported user objects
- Unsupported standard class objects
- Unsupported object properties
- Unsupported object functions
- Unsupported object events
- Unsupported system functions
- Unsupported Shared variables
- Unsupported Function not found
- Unsupported calls
- Differently behaved features
Appeon supports most PFC features. As such, under most situations the existing PFC code can also work under the Appeon environment without any modifications. However, there are a few features that are not supported. For that handful of unsupported features, Appeon would devise a workaround or alternate implementation of those features. Then, the PFC framework would be enhanced with any auto-sensing feature that would detect whether the PFC framework is being run as Client/Server or as Appeon Web. If Client/Server, then for those features that Appeon does not support it will execute the original Client/Server implementation. If Web, then only for those features that Appeon does not support it will execute the modified implementation.
After modifying these unsupported features, you can deploy the PFC application just as how you deploy a normal PowerBuilder application.
