KDB Studio 2 Prototype

[ColinEberhardt]

Hi All,

The KDB Studio re-implementation prototype is at a point where we are happy to share progress:

https://github.com/ScottLogic/kdb-studio-2

This project uses:

• The monaco editor, and adds q syntax support
• Electron to allow the application to run on the desktop
• Vue and Element for the UI layer
• node-q for the communication layer

The current functionality is as follows:

• Add / edit / delete servers
• Query editing (with syntax highlighting)
• Query execution, with results displayed as a simple HTML table

Considering that this prototype doesn't actually involve that much code, this is a decent amount of functionality.

I think this is looking like a viable route forwards. I'd be interested in opinions of others from @finos/dt-kdb - perhaps something to discuss in the project call in a couple of weeks?

[mcleo-d]

Hi @ColinEberhardt

Well done on this awesome update! 🌟 Please see the following comment where I have asked how much time you need to present the POC to the KDB team ... https://github.com/finos/kdb/issues/50#issuecomment-872377679

Also, I'd to tie the conversation thread on comment where https://github.com/jshinonome/vscode-q is introduced to @alvin-c-shih, @gyorokpeter and @psmulovics ... https://github.com/finos/kdb/issues/46#issuecomment-832779043

Do you think there's value inviting the vscode-q maintainer to this conversation if there's potential for a joint initiative?

James.

cc @dzmipt (Dmitry Zakharov)

[psmulovics]

Our discussion was more aligned whether it should be a new standalone app (using electron, etc), or should it be 'just' a well defined VSCode plugin (where most of the features for editing, displaying, windowing, etc would be provided by VSCode). Doing VSCode gives the ability to have the Q code coexist with the rest of your source code editing experience, git experience, etc., and can even work with being invoked when Q code is met within another language's source code.