Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Reverted from v. 5

This section contains the reference links for FrameworX extension APIs

Those APIs allows the creation of additional components to integrated in the product, and also enable  external applications to interact with FrameworX system.

FramewoX has published APIs for the following extensions:

Extension APIs refer to the suite of tools designed to enhance and customize a software platform by allowing additional creation components and facilitating external application interactions. These APIs extend the platform's capabilities in areas such as communication drivers, graphical user interfaces, engineering automation, solutions management, and data access.

The DriverToolkit API enables the development of new drivers for device protocols, the Portable API supports the creation of
  • WPF, HTML5, or portable graphical

user controls for displays, the EngWrapper API automates the generation of solutions
  • User Controls to use on displays. 

  • Engineering Automation:  EngWrapper API enables the automated creation of Solutions from .NET programming languages

using various file formats, the RemoteManager API provides tools for connecting to and managing multiple installations and product releases, the Toolkit API facilitates third-party application integration, and the DataAccess API allows for HTTPS requests for data exchange with a remote solution server.
  • , consuming CSV, XML or JSON files.

  • Solutions Management: :  RemoteManager API allows to connect and manage multiple FrameworX installations, managing product and  solution releases.

  • External Applications: Toolkit API allows external programs and applications to interact with FrameworX solutions.

  • HTTPS Requests: DataAccess API enables WebPages and JavaScript code to exchange data with a remote FrameworX server

When planning to use external APIs, keep in mind FrameworX Script Module, has also support for C#, VB.NET, Python and JavaScript, as well the ability to easily access Web Services and REST APIs, and external DLLs. Therefore in some cases, it's not necessary to create a new external component, just to leverage the built-in classes and tools available natively in the platform. 


DriverToolkit API

Requirements: Net Standard 2.0, Licensed FrameworX system

 Contact us for more information

Portable API

Requirements: Net Standard 4,8 Licensed FrameworX system

Contact us for more information

EngWrapper API

Requirements: Net Standard 4,8 Licensed FrameworX system

Contact us for more information




RemoteManager API

Requirements: Net Standard 4,8 Licensed FrameworX system

Contact us for more information

Toolkit API

Requirements: Net Standard 4,8 Licensed FrameworX system

Contact us for more information

DataAccess API

Requirements: Net Standard 4,2 Licensed FrameworX system

Contact us for more information

Configuring these APIs involves technical settings and processes that tailor the software platform to specific requirements, ensuring seamless integration and functionality. Users employ these APIs through direct coding practices, leveraging .NET language features and web technologies to interact with and extend the software platform.

On this page:

Table of Contents
maxLevel3
stylenone

Application Programming Interfaces

Children Displaystyleh3excerptTyperich content


In this section:

Page Tree
root@self
spacesV10