-
Notifications
You must be signed in to change notification settings - Fork 758
added basic documentation for using extensions #7395
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
added basic documentation for using extensions #7395
Conversation
Creating initial extension documentation so that we can clairfy what it is and how to install extensions in the documentation.
Added images and information
created folder
Removed dummy file that was created when creating extensions folder through github
added info for version
|
Hi @mauritselzinga-mx , thanks for submitting the PR! A few questions about extensions:
|
|
Hi Maria,
Extensions can be packaged in Add-on modules, but contain functionality that extend studio pro, much like a plugin. We also have a dedicated extensions category in the marketplace.
Since this adds functionality to SP, it’s diferent than most other modules, which extend the model or modelling language with widgets or java actions.
The term extension does currently not occur yet in Studio Pro, but soon it will in an extensions overview.
Extensions that are provided by mendix will be marked as platform-supported. Currently though, we only have the industrial edge plugin which is made by Siemens.
Maurits Elzinga
Sr. Product Manager | Mendix | Studio Pro
From: Maria Shaposhnikova ***@***.***>
Date: Monday, 11 March 2024 at 16:24
To: mendix/docs ***@***.***>
Cc: Maurits Elzinga ***@***.***>, Mention ***@***.***>
Subject: Re: [mendix/docs] added basic documentation for using extensions (PR #7395)
You don't often get email from ***@***.*** Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
Hi @mauritselzinga-mx<https://github.com/mauritselzinga-mx> , thanks for submitting the PR! A few questions about extensions:
1. We currently have documentation on add-on modules and solutions for SP, how is extension different from them? In the Marketplace guide, we have categories for Modules, Services, Widgets, Partner Solutions, are extensions part of any of those?
2. Does the term "extension" appear anywhere in the UI in SP?
3. Are extensions marked as Platform-Supported in the Marketplace?
—
Reply to this email directly, view it on GitHub<#7395 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A5C5FCBQRCON75I4IIIQGQTYXXEBPAVCNFSM6AAAAABEITXUP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBYG4YDINRYGY>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
Hi @mauritselzinga-mx , I've reviewed the PR. Based on your answers on extensions and after a discussion with other tech writers, I suggest the following:
|
|
|
||
| #### 3.3.1 Studio Pro Extensions API | ||
|
|
||
| The Studio Pro Extensions API allows you to customize different parts of Mendix Studio Pro by adding a new functionality to them, as well as interact with the open app model. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mauritselzinga-mx , can we add a link to this API here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The API is currently not yet public and only available to partners and ISVs. Once this becomes public we can definitely add the link here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MarkvanMents @MariaShaposhnikova As Maurits said, the API is not public yet. Then should we offer this information about the API in our public facing documentation at this point?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that the API isn't public, but extension usage by all users is. So might be relevant for users to know what they are actually retrieving
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that we should say somewhere that when you download an extension it is adding functionality to Studio Pro and it isn't just a module in your app.
I think we should also say that all these are platform supported, otherwise customers will be uncomfortable that they are running additional code which can affect the functioning of Studio Pro.
However, I don't think we should technically say that this is done via an API as the mechanism is irrelevant to the user.
|
@Luyao-Zhang-1 , as agreed before, I've moved extention info to the Marketplace guide, could you take a look at the changes when you have time? |
|
|
||
| It is possible to add new functionality to these elements and add custom interfaces that interact with the current open app model. | ||
|
|
||
| #### 3.3.2 Installing Extensions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it be better to put this section under 3.2 Importing Content from Studio Pro's App Explorer instead, as this section seems to be about installing Marketplace content?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Luyao-Zhang-1, I think extensions appear as modules in the end, that is why I've put it after modules (Using a Module). I agree that the instructions seem to focus mainly on installion, but also mention Extension API, for example,
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
they indeed appear as modules, however you do get some different behavior when importing an extension rather than a regular module.
@mauritselzinga-mx Currently in the Marketplace, if I select Extensions as the category, confusingly, I get Advanced Audit Trail and Windows Service Console (please see the screenshot below). Do these two modules fit the definition of an extension as described here? |
| * [Database Connector](/appstore/modules/database-connector/) | ||
| * [Mendix Feedback](/appstore/modules/mendix-feedback/) | ||
| * [Mendix Mini Surveys](/appstore/modules/mendix-mini-surveys/) | ||
| <a id="extensions"></a>{{% alert color="info" %}}Extensions are a special type of modules that allows you to add new functionality to your development environment in Studio Pro. Extensions are part of your application, and therefore will become available to all members of your app who are developing it. Extensions come as part of [add-on modules](/refguide/consume-add-on-modules-and-solutions/). This means you can download them directly from the Marketplace.</br>Currently, extensions can only be created by Mendix Partners and are available from Studio Pro versions [10.6.3](/releasenotes/studio-pro/10.6/#1063) and above. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we really need an anchor here. It is only two lines below the Introduction and I don't think we really need to scroll to it.
I would just link the the document or, if necessary, add an anchor for the introduction.
| * [Extensions](#extensions) | ||
| * [Apps](#apps) | ||
|
|
||
| ##### 2.1.1.1 Widgets {#widgets} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we could get rid of one level of heading by having
2.1 Finding and Download Content in Studio Pro 9.19 and above
2.2 Finding and Downloading Content in Studio Pro 9.18 and below
Not worth doing now, but perhaps we can look at the structure as this seems to be a very long section number for something which is actually quite simple!
Or perhaps we can do something without section numbers?
Not sure exactly - but something to look at later?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good. We can take a look at this later.
Update use-content.md
Co-authored-by: Mark van Ments <35492184+MarkvanMents@users.noreply.github.com>

Added documentation for how to use extensions in Studio Pro, and how to install an extension.