I tried copying all files in the quark/bin/cal/debug folder from the
old version to the new, but all my gems that previously appeared in
the GemCutterSaveModule no longer appear.
Thanks -- this is a bug.
The Gem Cutter has some logic to avoid creating folders unnecessarily.
Unfortunately in this case it looks like it has resulted in it putting
the designs under Quark/samples/simple/Designs.
We'll try to fix this for next time.
If all of your saved designs are in the GemCutterSaveModule, these are
what you should copy:
- Quark\bin\cal\debug\CAL\GemCutterSaveModule.cal (CAL source)
- Quark\bin\cal\debug\Metadata\-Gem-Cutter-Save-Module (CAL metadata)
- Quark\samples\simple\Designs\-Gem-Cutter-Save-Module (GemCutter
designs)
- It will work if you copy this to Quark\bin\cal\debug\Designs
Thanks,
- Edward
A couple of points to add to my last message:
1) You probably don't want to copy all of Quark/bin/cal/debug -- this
will result in copying *all* CAL modules.
There are changes to the core modules in this release that won't be
picked up if this is done.
2) To make upgrading easier in the future, one option is to work with
new modules in a folder outside of the Quark Platform install.
The platform uses Java classpath-relative locations to finds modules
and associated resources, so one way to do this might be:
- Create a CAL folder, with subfolders called "Metadata" and
"Designs".
- Create a new module in the CAL folder.
- Start the GemCutter with the environment property "QUARK_CP" set to
the parent of the CAL folder. The value of this property is prepended
to the Java classpath by the run scripts.
When you start Gem Cutter, the module can be added to your workspace
by selecting Workspace -> Add Module -> From Standard Vault... Any
edits to your module should now show up in your new folder.
If you want Gem Cutter to start up with the new module, you have to
add it to a workspace file.
A couple of ways to do this are:
a) Add to the default workspace file (/Quark/bin/cal/debug/Workspace
Declarations/gemcutter.(default/test).cws), or
b) Create a new workspace file importing gemcutter.(default/test).cws
and get Gem Cutter to use this workspace.
- copy and edit GemCutter.(bat/sh/command), and substitute in your
workspace name.
Cheers,
- Edward
If you like this can also contain a "Workspace Declarations" folder.
- Edward