Panagiotis Tourlas

I did this by adding a component to the file action handler that listens for a custom event, and displays a dialog. The component returns a promise and if resolved...

Please note that I added the comment `/* FAULTY IMPORTS */` to the imports that were available at the MolQL repo but not here. How should we handle these?

- [x] `../types.ts`, `../helper.ts`, `../transpiler.ts` you can add to `/mol-script/transpilers/` - [x] `Expression` you can import from `/mol-script/language/expression.ts` > > > Could you please also add the relevant (pymol, vmd)...

Additionally, @arose @dsehnal what is required to make a functional example of this feature? Even something very rough and unpolished (like providing a string to a function which is attached...

@arose @dsehnal Greetings! Is there any update on this PR?

> @ptourlas There are quite a few errors since the MonadicParser in molstar is not exactly the same as the one in molql. I can have a look but not...

> This is not a correct way. What you are looking for is `plug-in.state.data.selectQ(...)`. Where you find a sub tree with the current node and the filter it say based...