Using external Text Editor

[clevername27]

@oskarsh Be aware that there are issues with using an external text editor—namely, that HISE will sometimes overwrite your original file. Usually, this happens when HISE opens the same file in HISE, like if you click on an error report in the Console. But sometimes it just happens. My workaround its to use an external editor that tells me when a file that it has open was overwritten by HISE, and gives me the option to reject HISE's changes, or keep my own. (Though HISE hasn't actually made any changes; it's simply overwritten my last changes in the external editor, though it's more nuanced than that, which is another of saying I'm too lazy to be more specific.) There was a bug about this which was fixed a while back, which improved the situation a lot. But problems remain, so be careful so you don't lose any code. I know @Christoph-Hart has put a lot of work into HISE's built-in editor, and after two years, I'm still finding about cool stuff in it that I wasn't aware of. If do decide to go with an external editor, I can send you my list of HISE Script keywords for your editor. (If you're using BBEdit, I went so far as creating a HISE Script language module.)

[oskarsh]

@clevername27 Yes I am aware that HISE will overwrite the changes. I am suggesting a button or just a function that we can bind to a shortcut "reload and compile" which basically uses the file on Disc and not from the memory.

I believe this should be easy to implement since we already have Load XML which basically does the same, reload all scripts, xml and compile them.
If we could only get a shortcut or button for this functionality...

I think the HISE editor is great for what it is but it will always lack against other editors which main job is to edit text. I am a big fan of removing dependencies and having a editor which I can style, use plugins (heck even VIM bindings) and have a very reliable and fast editing experience would be my biggest Christmas wish.

Many IDE's have moved away from this baked in editor style approach, just less dependencies and maintenance.

@Christoph-Hart can you play Santa and look into this? Mainly just a "reload and compile" function that we can bind to a shortcut?

[clevername27]

@oskarsh I love your idea.

[d.healey]

@oskarsh said in Using external Text Editor:

Mainly just a "reload and compile" function that we can bind to a shortcut?

I think a file watcher would be better, no need to hit a button manually. Just save the external file and the changes will be there in HISE.

[clevername27]

@d-healey I love that idea, too.

[clevername27]

@oskarsh @d-healey My keyword list only the HISE Script keywords—a list of API keywords would be fantastic. How are you handling that when using an external editor?

[oskarsh]

@d-healey you are right!

I am trying to get my Christmas Presents in time tho. Not sure Christoph has the prime delivery for a file watcher :D

So a button would do for the beginning. A file watcher would be the better solution but more work to get it right.

This one is the industry standard btw:
https://facebook.github.io/watchman/

[ustk]

For those who might have missed it, a code template has been introduced recently:

HISE | Glossary | Code snippet templates

Use code snippet templates in the script editor

(docs.hise.audio)

New feature: Code templates

What's the best way to return to coding after a vacation break? Yes, adding a fun feature that is easy on the brain cells. So here I present to you: Code sni...

Forum (forum.hise.audio)

[d.healey]

@ustk I completely forgot about that already!

[ulrik]

@ustk thanks for the reminder!