Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

Full support for workspaces was added in Profound.js 5.0.0.


Note

The ability to create a workspace is only available in the Profound.js IDE. This functionality is not available in the Profound UI Visual Designer. You can access the Profound.js IDE using the following URL: http://systemName:port/ide (where 'systemName' is the name of your system and 'port' is the port number that your Profound.js instance is installed on). 

What is a Workspace?

A workspace is a convenient way of organizing your projects. A workspace is a directory on the file system that includes all of the source code and configuration files needed to make an application work, along with a Git repository for source control. Workspace directories are stored within the 'modules' sub-directory of the Profound.js installation directory. Workspaces from Profound.js can easily be deployed in the cloud on Profound.js Spaces and vice versa.

Use of workspaces in Profound.js is optional, but strongly recommended. On Profound.js Spaces, all applications are organized into workspaces.

...

To run an application, you must first create one or more callable Profound.js modules. See here for instructions on creating a callable module. Then, you must configure a route (a URL path) that will be used to call the module. To configure routes, right-click on your Profound.js module file or Rich Display File JSON file in the files Files Tree and select Properties:

 

On the File Properties dialog, you can configure 2 two different types of routes: 

  • An App Start Route. There can be only 1 one App Start Route in each workspace. This route runs a module when the URL specifies just the workspace name. The route can be either a stateful Rich Display File program, or a stateless Express program. For a stateful Rich Display File program, just click the App Start box:

...

For a stateless Express program, also check the Express Route Box box and optionally select the desired HTTP method to respond to:

...

  • A Named Route. A workspace can contain any number of Named Routes. These routes run when the URL includes a route path name, in addition to the workspace name. Named Routes can also be either stateful Rich Display File programs, or stateless Express programs. To set up a named route, check the Express Route box, uncheck the App Start Route box, select the desired HTTP method, and fill in the desired route namepath. Route names paths must be unique within the workspace. For a stateful Rich Display File program, set the HTTP Method to 'get' and check the Rich Display App box.

The Files Tree will display an icon next to any files associated with a Named Route:

Anchor
run
run
Running Routes

Workspace routes are run using URLs like this:

  • http://yourServer:port/run/workspace_name/  (App Start Route)
  • http://yourServer:port/run/workspace_name/route_name path (Named Route)

If an App Start Route is configured, it can be launched in a browser tab by using the option Launch→Launch App in Browser Tab from Home section of the ribbon:

...

And then selecting the workspace from the Workspace tab on the Open Dialog:

Spaces Workspaces can also be opened using the Spaces List in the bottom bar:

...

To rename a workspace, use the right-click option in the Files Tree to rename the workspace directory:

...

Or use the right-click option in the Files Tree to delete the workspace directory:

Customizing HTML Page and Built-in Screens for Rich Display File Apps

Profound.js applications use the Profound UI Rich Display File framework. The following files can be customized in each workspace:

  • To customize the Profound UI 'start.html' file, place a copy in the Workspace Directory and name it 'puistart.html'.
  • To customize the built-in sign on, error, session timeout, session end, and message box screens, place a copy of the 'puiscreens.json' file in the Workspace Directory.