LiveArt HTML5 Product Designer v1.0.0 Migration Guide
LiveArt HTML5 v1.0.0 supports the same configuration files as LiveArt v0.10.* branch, published and available on liveart.github.io/slate/
Please note the following differences between the versions.
General:
- The designs, saved under 0.10.* version of the designer, are no longer compatible with 1.0.0. Any templates and designs have to be recreated respectively.
- 1.0.0 version uses Cufon fonts only, thus requiring Cufon font preparation.
- The colorizable producs and gallery artwork, prepared for 0.10.* version may not be compatible with 1.0.0 (see migration guide below).
- By default, we deprecated adding a stroke to one-color images.
- Canvas size changed from
587×543px
to590×530px
. - By default, the canvas is responsive.
Deprecated, removed, and unsupported configuration properties:
Main configuration file:
config.options.includeProductInDesign
- deprecated;- This feature was moved to production output microservice;
- Update production output config file
services/config/output.json
with theincludeProduct
property.
options.includePrintingAreaInDesign
- deprecated.options.includeMaskInDesign
- deprecated;- Mask now acts as part of the product - see
config.options.includeProductInDesign
;
- Mask now acts as part of the product - see
options.deleteOnDoubleClick
- deprecated.options.checkTextFXThrottle
- deprecated.options.fitProductImage
&options.fitEditableArea
- deprecated;- v1.0.0 works like these properties are set to true.
options.hideDesignIdeas
- deprecated;- Pass an empty value in
getTemplatesUrl
instead.
- Pass an empty value in
options.showSuitableProductColorize
- deprecated.options.mergeDesignIdeas
- not supported yet.options.enableSnapGuides
- replaced withoptions.snapConfigs.enableSnapGuides
.options.defaultUnit
&options.secondaryUnit
- replaced withoptions.unit
,options.unit2
,options.unitConversionMult
(more info here).options.zoomEnabled
,options.minZoom
,options.maxZoom
,options.zoomStep
- replaced withoptions.zoomConfigs.enabled
,options.zoomConfigs.min
,options.zoomConfigs.max
,options.zoomConfigs.step
.
Product configuration file:
products.restrictions
- should be removed (not supported).products.colorizableElements.hidePantones
- should be removed (not supported).categories.thumbUrl
- replaced withcategories.thumb
.products.colorizableElements[].id
- replaced withproducts.colorizableElements[].query
with valid element id (e.g."#body"
) to apply the fill.
Graphics configuration file:
graphics.multicolor
- property changes are ignored usegraphicsList.colorize
instead.graphics.colorize
- indicates the ability to change graphics image(area) fill (both single and multicolor). By default - true, previous default value - false.graphics.colorizableElements.hidePantones
- deprecated.graphics.colors
accepts an array of hex values only the previous version also accepted strings and numbers, which caused major issues for the integrators.categories.thumbUrl
- replaced withcategories.thumb
.graphics.colorizableElements[].id
- replaced withgraphics.colorizableElements[].query
with valid element id (e.g."#body"
) to apply the fill.
Services changed:
- Request/Response changes:
application/x-www-form-urlencoded
Content-Type in all services - replaced withapplication/json
.{ "data": { ...request content } }
property insaveDesign
request - replaced with{ ...request content }
.name
property insaveTemplate
- replaced withtitle
.
- Data payload of the POST requests - sent in body (refer to point 1), not as query params.
- Services should pass version (
X-LA-Service-Version
) in header. Configs.php
changes:$LAJS_FOLDER_PATH = "../"
- replaced with$LAJS_FOLDER_PATH = "../../"
$DESIGN_RELATIVE_LAJS_FOLDER_PATH = "../"
- replaced with$DESIGN_RELATIVE_LAJS_FOLDER_PATH = "../../"
Premade Templates and Design Idea migration:
Multicolor graphics/products migration:
- Simple (Using Ilustrator):
- Pros: requires minimal steps, graphics may be processed as a batch;
- Cons: layer names will be replaced with "Color 1", "Color 2", etc.
- Open image in Illustrator and re-save with the next options: sample;
- Set
"parseColorAreas": true
in the configuration for this image; - Remove
colorizableElements
in the configuration for this image.
- Advanced (sample for steps below):
- Pros: keep the same layer names;
- Cons: requires processing of each file separately (may be automated).
- Reconfigure colorizable layers inside SVG:
- Replace
class
withid
. - Add
fill
attribute with default color instead of<style>
- Replace
- Config changes:
- Replace
"multicolor": true
with"colorize": true
in the configuration for this image; - Replace
colorizableElements.id
withcolorizableElements.query
- Set
id
configured fromclass
inside SVG as a value forcolorizableelements.query
.
- Replace