You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/apidocs-mxsdk/apidocs/extensibility-api/extensibility-api-howtos/add-menu.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ weight: 15
8
8
9
9
This how-to describes how you can add a menu that contains submenus, some of which also contain submenus of their own. Before you start this how-to, it is recommended to [create a menu extension](/apidocs-mxsdk/apidocs/extensibility-api/create-menu-extension/) first.
10
10
11
-
You can download the example in this how-to in [this Github repository](https://github.com/mendix/ExtensionAPI-Samples).
11
+
You can download the example in this how-to in [this GitHub repository](https://github.com/mendix/ExtensionAPI-Samples).
Copy file name to clipboardExpand all lines: content/en/docs/apidocs-mxsdk/apidocs/extensibility-api/extensibility-api-howtos/build-todo-example-extension.md
+31-30Lines changed: 31 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -198,8 +198,8 @@ In this section, you will add a view model to store our view data:
yieldreturnnewMenuViewModel("To Do List", () =>_dockingWindowService.OpenPane(ToDoListDockablePaneExtension.PaneId));
581
+
}
582
+
}
582
583
```
583
584
584
585
## 9 Adding a Web-based User Interface
@@ -591,7 +592,7 @@ Up to now you have been adding all the logic that will allow your extension to r
591
592
2. Inthefolder, addtwofiles:
592
593
593
594
*AHTMLpagethatcontainsthelayoutoftheuser interface. Call it `index.html`
594
-
* A Javascript file that contains the client side logic for the user interface. Call it `main.js`
595
+
* A JavaScript file that contains the client side logic for the user interface. Call it `main.js`
595
596
596
597
3. Open `index.html`.
597
598
4. Replace its contents with the following:
@@ -640,7 +641,7 @@ Up to now you have been adding all the logic that will allow your extension to r
640
641
</html>
641
642
```
642
643
643
-
5. Open `main.js` and add the Javascript logic by replacing the contents of the file with the following:
644
+
5. Open `main.js` and add the JavaScript logic by replacing the contents of the file with the following:
644
645
645
646
```js
646
647
function postMessage(message, data) {
@@ -716,7 +717,7 @@ Up to now you have been adding all the logic that will allow your extension to r
716
717
717
718
ThisHTMLpageisself-explanatory, asyouareprovidingaverysimpleinterfacewith some added css styling provided by Tailwind CSS.
718
719
719
-
Within the Javascript file, you need to add some logic so that the web view can communicate with your extension logic correctly.
720
+
Within the JavaScript file, you need to add some logic so that the web view can communicate with your extension logic correctly.
720
721
721
722
You add a small helper function to simplify the call to the browser API:
722
723
@@ -726,7 +727,7 @@ function postMessage(message, data) {
726
727
}
727
728
```
728
729
729
-
You also need to perform some initialization to ensure that you can respond to messages send to javascript and
730
+
You also need to perform some initialization to ensure that you can respond to messages send to JavaScript and
730
731
731
732
```javascript
732
733
// Register message handler.
@@ -746,7 +747,7 @@ It is important to set these two `index.html` and `main.js` files to *Copy alway
746
747
747
748
## 10 Setting up Communication Between the User Interface and Extension {#set-up-communication}
748
749
749
-
So far you have configured the extension to be usable in Studio Pro. You added support for storing the to do items. You also added a user interface that users can interact with. The last step in this process is to link the extension c# logic with the webbased javascript logic.
750
+
So far you have configured the extension to be usable in Studio Pro. You added support for storing the to do items. You also added a user interface that users can interact with. The last step in this process is to link the extension c# logic with the web-based JavaScript logic.
750
751
751
752
1. Start with adding a utility class to help simplify the way you interact with web responses. Call the file `HttpListenerResponseUtils.cs`.
752
753
2. Replace the contents of the file with the following:
Copy file name to clipboardExpand all lines: content/en/docs/apidocs-mxsdk/apidocs/extensibility-api/extensibility-api-howtos/create-context-menu.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ It is possible to add a context menu to an `IEntity` in Studio Pro or to a `IDoc
10
10
11
11
This how-to describes how you can add a context menu to an entity. Before you start this how-to, it is recommended to [create a menu extension](/apidocs-mxsdk/apidocs/extensibility-api/create-menu-extension/) first.
12
12
13
-
You can download the example in this how-to in [this Github repository](https://github.com/mendix/ExtensionAPI-Samples).
13
+
You can download the example in this how-to in [this GitHub repository](https://github.com/mendix/ExtensionAPI-Samples).
14
14
15
15
## 2 Creating an Entity Context Menu Extension Class
Copy file name to clipboardExpand all lines: content/en/docs/apidocs-mxsdk/apidocs/extensibility-api/extensibility-api-howtos/create-dockable-pane.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ weight: 5
8
8
9
9
This how-to describes how you can add a custom dockable web pane window to Studio Pro. Before you start this how-to, it is recommended to [create a menu extension](/apidocs-mxsdk/apidocs/extensibility-api/create-menu-extension/) first.
10
10
11
-
You can download the example in this how-to in [this Github repository](https://github.com/mendix/ExtensionAPI-Samples).
11
+
You can download the example in this how-to in [this GitHub repository](https://github.com/mendix/ExtensionAPI-Samples).
Copy file name to clipboardExpand all lines: content/en/docs/apidocs-mxsdk/apidocs/extensibility-api/extensibility-api-howtos/create-menu-extension.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ You can download the example in this how-to in [this GitHub repository](https://
14
14
15
15
1. Create a new project in Visual Studio based on `C# Class Library` template.
16
16
2. Choose a name for the project. Use a format similar to `MyCompany.MyProject.MendixExtension`, but it is not a hard requirement.
17
-
3. Choose `.NET 6.0` Framework.
17
+
3. Choose `.NET 8.0` Framework.
18
18
4. Add `Mendix.StudioPro.ExtensionsAPI` NuGet package to the project references. Pick the version that does not exceed the Studio Pro version you installed. To do so, perform the following steps:
19
19
1. Include a reference to the Extensions API [NuGet package](https://www.nuget.org/packages/Mendix.StudioPro.ExtensionsAPI):
20
20
2. Add new file named `manifest.json` to your project. Put the following content into it:
0 commit comments