* [Wish List entry 614] Enhanced plugin editor

[Mark1834]

An enhanced plugin editor that provides basic tools such as auto-complete (to remind users of exact FH function names and expected arguments) and context-sensitive formatting (to readily distinguish between FH functions, Lua code, variables and string literals) would be of great benefit to both existing authors and users who wish to explore writing plugins.

I know that there are workarounds, but they are not suitable for anyone other than an experienced coder. It’s a niche requirement, so won’t get many votes, but having it on the wish list at least brings it to CP’s attention, and might just break the existing vicious circle of nothing being done as it’s always well down the priority list due to the scarcity of authors.

[ColeValleyGirl]

I agree with it going on the wish list but wouldn't use it as I am very happy with Visual Studio Code including integration with Github. I must update the FH function definition file I use for V7 though...

[tatewise]

Could the method of using the Visual Studio Extension for Lua with Plugin scripts be added to the Knowledge Base similar to the way PSPad is explained in Use PSPad to Format Functions.

[ColeValleyGirl]

It's on my to-do list, Mike, but not high up as it's a niche interest.

[Valkrider]

Several IDE's do have support for LUA and not all are paid. Such as https://studio.zerobrane.com/ however not being a LUA coder I don't know how good they are. My son who is a coder for a living rates IntelliJ from JetBrains which has a LUA plugin. I use PhpStorm from JetBrains and whilst it is normally a pay for application if you develop public domain/open source apps then they waive the fee. May be worth a look.

[ColeValleyGirl]

Colin, the issue with IDEs is hooking into the FH runtime environment. Using Visual Studio Code (free) I have to copy the code file into the FH plugins directory to debug it... not something everyone would be willing to do.

[Mark1834]

Let's not lose sight of the objective here - improved out of the box tools for new and casual users, not more workarounds for experts.

[ColeValleyGirl]

As I said, I agree it ought to go on the Wish List. But I'm not hopeful...

Also, I wouldn't call a fully functional IDE with GitHub integration a 'workaround'. It's not something an infrequent plugin developer would want, It's a solution for plugin authors who already use it for other purposes/languages and/or want features which it's unreasonable to expect CP to deliver.

[tatewise]

... remind users of exact FH function names and expected arguments ...

I know it's slightly off topic but a starting point for that would be a similar feature for Expressions with better syntax analysis of errors instead of simply saying the Expression is invalid.

[Vyger]

Wish List entry 614 has been created

[David2416]

Voted for

[shoshk]

Hi Helen,

I’m back after a long absence (I think over two years!).

Anyway, I was using Zerobrane, but see that you have moved to Visual Studio Code. Other than the extensions you mentioned in your earlier post from 2021, are you using any others?

Thanks,
Shoshanna

[ColeValleyGirl]

Other than the extensions you mentioned in your earlier post from 2021, are you using any others?

Thanks,
Shoshanna

Full list I've currently got installed (with author for disambiguation):

• Lua (sumneko) - Lua language support
• StyLua (JohnnyMorganz) - Formatting
• Todo Tree (GruntFuggly) - Show TODO, FIXME, etc. comment tags in a tree view
• Easy HighLight (Brandon Blaschke) - Easily highlight lines of text
• GitLens (GitKraken) - Better Github integration than the standard
• Draw.io Integration (Henning Dietrichs) -- allows diagrams drawn ith draw.io to be accessed within VS Code

Some of these are must haves (Lua, StyLua or an alternative formatter, and arguably Todo Tree). Others are to do with the way I work.

[shoshk]

Thank you