VS Code plugin #15

New Issue

NQN · 2018-12-27T00:11:42Z

NQNStudios commented

2018-12-27 00:11:42 +00:00

(Migrated from github.com)

Although I kind of want to learn to write VS Code plugins, I'm inclined to declare this out of scope for my personal work on Hank. Anyone is welcome to share ideas and prototypes, though.

zicklag commented

2018-12-28 23:58:07 +00:00

(Migrated from github.com)

I just realized that because Hank is written in Haxe, if you wrote a VSCode plugin, you could get an incredibly integrated editor because the VSCode plugin could run the Javascript compiled version of the Hank interpreter right inside of the VSCode plugin ( or just write the plugin in Haxe and include the Hank library ).

You would get full access to the parser and even be able to evaluate the HScript expressions all inside of the plugin without having to host an external debugging server or anything like that. You could get a full IDE that is easily better than Inky.

I just realized that because Hank is written in Haxe, if you wrote a VSCode plugin, you could get an incredibly integrated editor because the VSCode plugin could run the Javascript compiled version of the Hank interpreter right inside of the VSCode plugin ( or just write the plugin in Haxe and include the Hank library ). You would get full access to the parser and even be able to evaluate the HScript expressions all inside of the plugin without having to host an external debugging server or anything like that. You could get a full IDE that is easily better than Inky.

NQN closed this issue

2025-10-30 19:33:36 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: NQN/hank#15