• Drafts

• Rename zpm name package.

Make it published from GitHub via ZPM

Initial Release

ZPM updated

added module.xml for ZPM

Initial Release

UploadAssets change

• Assume UTF8 as a a default

Update module.xml

• added support for serial fields
• added support for recursively nested fields
• added support for BigInt, SmallInt, TinyInt, Decimal, Double, Float, Currency, Char, boolean, VarString field types
• added "navigate to object" button
• added mock data service for devs
• extended error showing method to show error details
• fixed issue with record count during loading
• fixed issue with saving objects

Added DC link

Initial Release

Initial Release

changed title

• fixed fonts issue
• added missing fonts

Initial Release

fixed font issue

Version update

Version update

Initial Release

Initial Release

Initial Release

• Support debugging when connected to a Deltanji service. Requires VCM-D-0731 update to Deltanji.
• Embedded Deltanji Solo changes:
  • Add favicon.
  • Fix layout issues affecting Firefox on Linux.

bugfix, ZPM module update, docker environment update

Initial Release

Initial Release

1. Official test server

To check if your package is published in the registry and then installed from it, use the test registry: https://test.pm.community.intersystems.com/registry/
login: test
password: test

To switch to the test registry use the command
repo -r -n registry -url https://test.pm.community.intersystems.com/registry/ -user test -pass test

Once a day, the test registry is updated and all data in it is reset

2. New commands for the most frequent actions with the module

Previously, to publish a module in the current registry, you had to use the module-action command, for example module-action mymodule publish, and it could be written shorter mymodule publish.

Now you can use the publish command: publish mymodule - use the organic word order

New commands:

• reload
• compile
• test
• package
• verify
• publish

3. Generate command

Using the generate command, you can create a module.xml file template in a second.

Usage:

• generate -template /my/project
  Creates a module.xml file with fictional data in /my/project
  
  After that you must open and edit this file to change module meta information and specify module resources (classes, csp pages, globals, test)

• generate /my/project
  Without -template (or -t) flag this command creates a module.xml file in an interactive mode. Just answer several questions. Use -author (-a) flag to add information about module author

zpm: USER>generate /temp/zzzz

Enter module name: zzzz
Enter module version: 1.0.0 => 1.0.1
Enter module description: module description
Enter module keywords: module keywords
Enter module source folder: src => 

Existing Web Applications:
    /csp/user
    Enter a comma separated list of web applications or * for all: /csp/user
    Enter path to csp files for /csp/user:  src/web
Dependencies:
    Enter module:version or empty string to continue: sslclient:1.0.1
    Enter module:version or empty string to continue: 
zpm: USER>

4. Globals location

Now Globals are expected in /src/gbl (but not in /gbl )

5. Version command

Version command displays currently installed zpm version number; shows locally installed zpm registry and connected remote repository and their version.

zpm: USER>version

 zpm 0.2.2
 Locally installed zpm-registry not found
https://pm.community.intersystems.com - 0.0.2

6. Reset Username and password while switching to another remote repository

If you do not specify the username and password modifiers in the repo command for the remote registry, the previously set values for username and password will be reset.

zpm: USER>repo -r -n registry -url https://pm.community.intersystems.com/

Initial Release

Initial Release