You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by ac...@apache.org on 2021/11/26 10:03:29 UTC

[camel-website] branch main updated: [Blog]VS Code AtlasMap 0.1.0

This is an automated email from the ASF dual-hosted git repository.

acosentino pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-website.git


The following commit(s) were added to refs/heads/main by this push:
     new 5720856  [Blog]VS Code AtlasMap 0.1.0
5720856 is described below

commit 57208565155de08a06555be9ad3049edaf2c20c3
Author: Aurélien Pupier <ap...@redhat.com>
AuthorDate: Thu Nov 25 16:59:53 2021 +0100

    [Blog]VS Code AtlasMap 0.1.0
    
    Signed-off-by: Aurélien Pupier <ap...@redhat.com>
---
 .../NewDataTransformationCommand.gif               | Bin 0 -> 195863 bytes
 .../codelens-open-atlasmap.gif                     | Bin 0 -> 447151 bytes
 .../dirtySave-AtlasMap.gif                         | Bin 0 -> 415872 bytes
 .../double-clickToOpen.gif                         | Bin 0 -> 127617 bytes
 .../2021/11/vscode-atlasmap-release-0.1.0/index.md |  69 +++++++++++++++++++++
 .../severalAtlasMapEditor.gif                      | Bin 0 -> 436900 bytes
 6 files changed, 69 insertions(+)

diff --git a/content/blog/2021/11/vscode-atlasmap-release-0.1.0/NewDataTransformationCommand.gif b/content/blog/2021/11/vscode-atlasmap-release-0.1.0/NewDataTransformationCommand.gif
new file mode 100644
index 0000000..272d92c
Binary files /dev/null and b/content/blog/2021/11/vscode-atlasmap-release-0.1.0/NewDataTransformationCommand.gif differ
diff --git a/content/blog/2021/11/vscode-atlasmap-release-0.1.0/codelens-open-atlasmap.gif b/content/blog/2021/11/vscode-atlasmap-release-0.1.0/codelens-open-atlasmap.gif
new file mode 100644
index 0000000..118618a
Binary files /dev/null and b/content/blog/2021/11/vscode-atlasmap-release-0.1.0/codelens-open-atlasmap.gif differ
diff --git a/content/blog/2021/11/vscode-atlasmap-release-0.1.0/dirtySave-AtlasMap.gif b/content/blog/2021/11/vscode-atlasmap-release-0.1.0/dirtySave-AtlasMap.gif
new file mode 100644
index 0000000..3e427c2
Binary files /dev/null and b/content/blog/2021/11/vscode-atlasmap-release-0.1.0/dirtySave-AtlasMap.gif differ
diff --git a/content/blog/2021/11/vscode-atlasmap-release-0.1.0/double-clickToOpen.gif b/content/blog/2021/11/vscode-atlasmap-release-0.1.0/double-clickToOpen.gif
new file mode 100644
index 0000000..e733b0f
Binary files /dev/null and b/content/blog/2021/11/vscode-atlasmap-release-0.1.0/double-clickToOpen.gif differ
diff --git a/content/blog/2021/11/vscode-atlasmap-release-0.1.0/index.md b/content/blog/2021/11/vscode-atlasmap-release-0.1.0/index.md
new file mode 100644
index 0000000..f055e32
--- /dev/null
+++ b/content/blog/2021/11/vscode-atlasmap-release-0.1.0/index.md
@@ -0,0 +1,69 @@
+---
+title: "New release of VS Code AtlasMap 0.1.0"
+date: 2021-11-26
+authors: [apupier]
+categories: ["Releases","Tooling"]
+preview: "New release of VS Code AtlasMap 0.1.0: new development flow."
+---
+
+A new release of [VS Code AtlasMap](https://marketplace.visualstudio.com/items?itemName=redhat.atlasmap-viewer) 0.1.0 is available. It includes a new development flow closer to a classical VS Code development flow.
+
+# New features
+
+## Create a new AtlasMap Data Transformation
+
+A new command is available in the command palette to create a new AtlasMap Data Transformation.
+
+![Command palette provide a command to create a new AtlasMap Data Transformation file. It asks for workspace folder and a name then open the editor](./NewDataTransformationCommand.gif)
+
+## Open AtlasMap UI for AtlasMap Data Transformation from workspace
+
+It is now possible to click on an *.adm file from the VS Code explorer. It will load the file in the AtlasMap UI.
+
+![Double-click on file in VS Code explorer is opening the adm file in AtlasMap UI](./double-clickToOpen.gif) 
+
+Previously a right-click was necessary.
+
+## Open AtlasMap UI from Camel URI in Text editor
+
+In textual editor, above Camel URI using an AtlasMap component, a codelens is provided to open the AtlasMap Data transformation file when it is found.
+
+![From a textual editor, click on codelens to open AtlasMap UI](codelens-open-atlasmap.gif)
+
+## Save AtlasMap Data Transformation with VS Code Save command
+
+The AtlasMap UI is now embedded inside a VS Code editor. When a modification is done, the editor is marked as dirty. When calling save (Ctrl+S), the modifications are directly written to the corresponding *.adm file.
+
+![Modification in AtlasMap UI is marking editor as dirty. Save action is available and saving in adm file](./dirtySave-AtlasMap.gif)
+
+## Open several AtlasMap Data Transformation at the same time
+
+It is now possible to open several AtlasMap Data Transformation editor at the same time.
+
+![Demonstrating several AtlasMap editor opened at the same time and side by side](./severalAtlasMapEditor.gif)
+
+Be careful to not open too many of them as available memory can become a problem.
+
+## Compatibility version table
+
+VS Code AtlasMap is using a single AtlasMap UI version in each release. Defined Data Transformation are ensured to be compatible only with the same version of AtlasMap runtime. To help users to know which combination of version has the best chance to work, please see the new tables in the [readme](https://github.com/jboss-fuse/vscode-atlasmap#relation-between-vs-code-atlasmap-and-atlasmap-runtime-version).
+
+# Video demonstrating combination of the new features
+
+If you want to see all features combined, here is a [video](https://youtu.be/7bdih_yG7BE).
+
+# Under the hood
+
+Previously, a VS Code webview as used. it implied that there was no tracking of dirtyness and ability to save from VS Code normal flow. Users required to use specific AtlasMap UI to export the Data transformation
+Also, on click from the VS Code file explorer an empty editor was displayed. It was required to pen through a contextual menu.
+
+With new release, the VS Code webview is used inside a VS Code Custom editor. It allows to open file on direct click from VS Code file explorer and having the dirty/save lifecycle completely integrated with normal VS code development flow.
+
+Please note that it is using AtlasMap UI 2.4.0-M1 which is ensured to be compatible only with AtlasMap runtime 2.4.0-M1. For deployment to other versions, please double-check that features used are available.
+
+# What's next?
+
+Provide your feedback and ideas!
+You can start discussions on [Zulip camel-tooling channel](https://camel.zulipchat.com/#narrow/stream/258729-camel-tooling).
+You can create and vote for issues on github [issue](https://github.com/jboss-fuse/vscode-atlasmap).
+You can create and vote for issues on the [jira](https://issues.redhat.com/browse/FUSETOOLS2) used by the Red Hat Integration tooling team.
diff --git a/content/blog/2021/11/vscode-atlasmap-release-0.1.0/severalAtlasMapEditor.gif b/content/blog/2021/11/vscode-atlasmap-release-0.1.0/severalAtlasMapEditor.gif
new file mode 100644
index 0000000..d0dd2a8
Binary files /dev/null and b/content/blog/2021/11/vscode-atlasmap-release-0.1.0/severalAtlasMapEditor.gif differ