Developer notes

Documentation viewer (doc.p):

  1. I am using MS Frontpage to edit the documentation pages.
  2. By using the doc.p program to display the docs there is no need for any static pages for the Pluspack.
  3. The doc.p viewer program will substitute for the location of the Webspeed static files if other than "Webspeed31A".
  4. It also substitutes links in the Frontpage docs to make it remain dynamic through the browser.
  5. I wish to keep the documentation dynamic so I can later substitute other stuff.

RCS:

  1. Unfortunately it's barely tested and I have little experience in using it trough the Pluspack.
  2. It might need a total redesign as for how I've designed the task-system. It's based on the Roundtable method.
  3. There's currently no Deployment Manager, making it unusable as Roundtable replacement.
  4. I wish to create a RCS database in the plus directory for xref's etc for Roundtable functionality.

Compatibility:

  1. This version is not compatible with Webspeed 2.1, because of extensive use of dynamic queries.
  2. It should work on all platforms, but unfortunately the testing has been limited to NT/W2K due to availability of hardware.
  3.  

PLUS Database: (my wish for future expansion)

  1. I'd like to have a database (automatically configured) for Pluspack data in the PLUS directory.
  2. It should automatically synchronize with ubroker.properties and conmgr.properties using file-date-timestamp.
  3. It should keep program data for include/xref data for Roundtable functionality
  4. It can be used to configure the FFW toolpack and other stuff in ubroker.properties.
  5. It can be used for deployment help for saving and automatically configuring ubroker.properties and conmgr.properties.
  6.  

Broker-less operation mode: (my wish for future expansion)

  1. "/scripts/pluspack.exe/"
  2. I wish to create a messenger that automatically starts one Progress process and communicates with it using Sockets.
  3. It would enable an Explorer like functionality using HTML and Webspeed code.
  4. This can be used for stopping starting the admin-service remotely, and killing processes left behind.
  5. This could eventually be an HTML alternative for the adminservice.
  6. This could enable us to use the web for Data-dictionary functionality.
  7.