No comprehensive list of plugins with explanations of what they do about npppluginlist HOT 16 CLOSED

@helpdata This repo contains the input for the pluginAdmin window visible in N++ in json format containing a description for each plugin. The input therefore is:
https://github.com/notepad-plus-plus/nppPluginList/blob/master/src/pl.x64.json
and
https://github.com/notepad-plus-plus/nppPluginList/blob/master/src/pl.x86.json
where the raw data is available in text form.
Do you have other needs?

from npppluginlist.

If you mean a plugin list in plain English like is normal for any software project available for a general public: the answer is NO.

from npppluginlist.

I agree with akoppa. Digging into a json file is not an adequate answer.

from npppluginlist.

So your expectation is something like https://marketplace.visualstudio.com/vscode or https://github.com/emacs-tw/awesome-emacs#awesome-emacs?

There are currently no plans for that, but I think it should be possible to transform the json input to a markdown file with the plugin name + description + homepage to have at least the basic informations.

from npppluginlist.

What about a generator to build it from those files?
Any language preference?

from npppluginlist.

@mattesh Currently python is used to parse the json input against a schema and check that the downloads are usable. So python probably would be a good choice to create some markdown file from the x32 and x64 input files.

from npppluginlist.

...
Python -> md sounds good, but.
Please, don't expect smthng tomorrow ;-D

from npppluginlist.

What about this:
get_pl.py takes one parameter x**.json and prints the ready made table w/o header and footer.
Description "\r\n" gets replaced by <br> and "|" by & vert;

Two tables of this format would be printed:

1. Plugin Name = ij.display-name
2. Author = ij.author
3. Homepage = ij.homepage
4. Version and link = "[" + ij.version + " - " + json_file.arch + " bit](" + ij.repository +")"
5. Description = " <details> <summary> " + first_two_lines(ij.description) + " </summary> " rest_of_text(ij.description) +"</details>"

List of Plugins 32 bit

|Plugin name | Author | Homepage | Version and link | Description |
|---|---|---|---|---|---|
| 3P - Progress Programmers Pal | Julien Caillon | [3P - 32 bit](https://jcaillon.github.io/3P/) | [1.8.6](https://github.com/jcaillon/3P/releases/download/v1.8.6/3P.zip) | <details> <summary> [Requires .NET framework v4.6.1]<br>Designed to help writing OpenEdge ABL (formerly known as Progress 4GL) code. It provides :</summary> <br>- a powerful auto-completion<br>- tool-tips on every words<br>- a code explorer to quickly navigate through your code<br>- a file explorer to easily access all your sources<br>- the ability to run/compile and even PROLINT your source file with an in-line visualization of errors<br>- more than 50 options to better suit your needs<br>- and so much more!<br>Visit https://jcaillon.github.io/3P/ for more details on the plugin </details> |

from npppluginlist.

Hi,
what do you think about this?
6f40c13...mattesh:e709d1935a
plugin_list_x64.zip

Only point to clarify would be how to copy it into stable place when commit was taken into the master.
Regards, Mattes

from npppluginlist.

Plugin List - 64 bit

(version 1.1.7)

from npppluginlist.

@mattesh Lokes usable to me. In your example there is an
|---|
to much. Only drawback seen here is the collapsed description data which makes it difficult to search.

from npppluginlist.

@chcg
the solution would be a small script snippet. But we seem to be not allowed to add this directly on github.
We may be able embed some html script on the server: from here. However, my limited tests did not show a solution to combine script with markdown code.

Do you have already an idea how we would make this lists visible in some place?
e.g. in plugin docs?
Regards, Mattes

from npppluginlist.

@mattesh My first thought was to add the md files to the artefacts of a release, but then they are not immediately visible from within the browser. Maybe just add it with the release the repo and link it from the readme.

from npppluginlist.

isn't it at the time when a new release is created, when the list need to be generated and pushed into https://github.com/notepad-plus-plus/npp-usermanual ?
See more in the other thread.

from npppluginlist.

First test versions from appveyor CI:
https://github.com/notepad-plus-plus/nppPluginList/blob/master/doc/plugin_list_x86.md
and
https://github.com/notepad-plus-plus/nppPluginList/blob/master/doc/plugin_list_x64.md
from current master.
Still needs some automatic checkin which might be easier done by github action.

from npppluginlist.

Updated manually with each tagging.

from npppluginlist.