Allow customizing TextElement default vertical alignment

[simantics/platform.git] / releng / org.simantics.sdk.build.targetdefinition / README.md

diff --git a/releng/org.simantics.sdk.build.targetdefinition/README.md b/releng/org.simantics.sdk.build.targetdefinition/README.md
index 978bb419b3b073291e93885ef6840dd4857ab089..f5b19fd7381fe0d49640efdfebb3c535d38b70ff 100644 (file)
--- a/releng/org.simantics.sdk.build.targetdefinition/README.md
+++ b/releng/org.simantics.sdk.build.targetdefinition/README.md
@@ -1,8 +1,20 @@
 # Target platform definitions\r
 \r
-## org.simantics.sdk.build.targetdefinition.target\r
+Simantics 1.31.0 migrated to Eclipse 4.7 Oxygen platform.\r
 \r
-The platform definition that is used for building the Simantics SDK itself.\r
+At the same time [Obeo's Target Platform Definition DSL and Generator tool](https://github.com/mbarbero/fr.obeo.releng.targetplatform)\r
+was taken into use for target platform definition.\r
+\r
+Please read the detailed installation and basic use instructions from the tool's website.\r
+\r
+To summarize, the basic idea is that the `.tpd` files are the canonical source\r
+files for the actual target definition `.target` files. Always modify the `.tpd`\r
+files and use *ALT+R* in the `.tpd` file editor or *CTRL+R* to generate the new\r
+.target file and take it into use immediately.\r
+\r
+## org.simantics.sdk.build.targetdefinition.tpd\r
+\r
+This is the platform definition used for building the Simantics SDK itself.\r
 It does not include any of the parts of the org.simantics.sdk feature which\r
 defines the contents of the Simantics SDK.\r
 \r
@@ -12,10 +24,12 @@ external components required for building the Simantics SDK.
 See ../org.simantics.sdk.build.p2.site/ for how some of the external third-party\r
 libraries are bundled for use with the Simantics SDK.\r
 \r
-## simantics.target\r
+## simantics.tpd\r
 \r
-Includes all the same components as *org.simantics.sdk.build.targetdefinition.target*\r
-but also includes the Simantics SDK which is sourced from [http://www.simantics.org/download/<branch>/sdk/](http://www.simantics.org/download/<branch>/sdk/).\r
+Includes *org.simantics.sdk.build.targetdefinition.tpd*\r
+and the Simantics SDK (i.e. org.simantics.sdk.feature.group & org.simantics.sdk.source.feature.group)\r
+which is sourced from [http://www.simantics.org/download/<branch>/sdk/](http://www.simantics.org/download/<branch>/sdk/),\r
+where `<branch>` is `master`, `release/x.y.z`, etc.\r
 \r
 Each platform repository branch can have its own separate download location online, e.g:\r
 * [http://www.simantics.org/download/master/sdk/](http://www.simantics.org/download/master/sdk/)\r
@@ -24,3 +38,13 @@ Each platform repository branch can have its own separate download location onli
 * ...\r
 \r
 which the simantics.target definition then references to get the SDK bundles.\r
+\r
+Notice that the download site root location, e.g. [http://www.simantics.org/download/master/](http://www.simantics.org/download/master/) contains these same `.tpd` and `.target` files to\r
+enable sourcing both files directly from an HTTP URL.\r
+\r
+`.tpd` files can contain `include` statements that include other `.tpd` files from a URL.\r
+This greatly simplifies target definition by removing duplication from the their definitions. This is why \r
+publishing them online per platform branch is also highly useful.\r
+\r
+On the other hand legacy Buckminster builds can source `.target` files from a URL, which is why publishing them online\r
+per platform branch is useful.
\ No newline at end of file