cross-language-cpp / vscode-djinni Goto Github PK

The vscode plugin already has a mention on the documentation: https://djinni.xlcpp.dev/vscode-plugin/

As a maintainer I want this repository to have it's own mkdocs documentation that is integrated into the documentation website in the same way as the other components. This makes it easy for me to update the documentation of the plugin in it's code repository while having a single place where all djinni-related docs are displayed.

These things may be worth documenting in the first place:

• where to get the plugin (link to the vs marketplace)
• Developer Guide: how to publish a new version of the plugin (with the newly added github actions from #3)

In cross-language-cpp/djinni-generator#43 python support is proposed and will likely come into master as an experimental feature in the next months.

As a user I'd like the vscode extension to support interfaces that marked for implementation in python (+p)

As a maintainer I want to have an automated way to publish the plugin to the visual studio marketplace with a github action. That way any maintainer can easily publish a new version of the plugin by creating a new release on github without having to mess with the details.

The following things need to be done to achieve this:

• create a cross-language-cpp publisher in the vs marketplace
• add a github action that automatically builds the plugin on each PR into master, to ensure only buildable code goes into master.
• add a github action that automatically builds and releases the plugin when a release-tag is created in github

Hi,

When i use +w that is for WASM generator, everything is white:

If i remove, it show colored:

Can you add support for any +x?

Thanks.

As a user I want to see a special file icon for .djinni files in the file-explorer.

Currently .djinni files have a simle text-file icon:

I would like to have a special icon like in the intellij-plugin:

Example:

Team = record +c { id: i64; image: string; name: string; coach: string; }

The +c breaks syntax highlighting.

A quick fix is replacing line 125:

"begin": "(\\w+)\\s*(=)\\s*(record)\\s*({)",

with

"begin": "(\\w+)\\s*(=)\\s*(record)\\s+((\\+[cjo]\\s+)*)({)",

... in ~/.vscode/extensions/patrikminder.djinni-syntax-highlighting-1.0.1/syntaxes/djinni.tmLanguage.json

But an extension update would be better!

There are people that like VS Code but use a different version of it, like VSCodium, and there are quite some Cloud IDEs based on VS Code, and all those might (or have to) prefer Open VSX as their extension registry.

See https://open-vsx.org

Our extension should be there available.

For this to happen, we need to sign a publisher agreement, see
https://www.eclipse.org/legal/open-vsx-registry-faq/

Use an xlcpp.dev mail ? (which ?)

Hi Patrick
First if all, thank you for that plugin! I use and like it.

I wonder if you would be interested to move that repo to https://github.com/cross-language-cpp/ , where we continue to develop djinni and tools/technologies around it as a community project. (You might know that dropbox/djinni is an abandoned project). See also the new documentation pages at https://djinni.xlcpp.dev/

You can of course still be the maintainer of this plugin, if you want.
It would be nice to have that plugin alongside the Intelli J djinni plugin, so it is easier to find and it can be developed / adopted with possible upcoming future changes/extensions to the djinni IDL.

We would be very happy if you could consider that as an option for the future of this plugin.