Are you open to configurable ui options? about nvim-dap

[mfussenegger]

Would you be open to having the user be able to pass in win options to change the blend or to add a border or something?

Short answer is yes.

The longer answer is that I would like to have a pluggable widget system where users can combine windows, buffers and contents as they please.

There's an early prototype up at #165 but I'm still refining the API, filling up some gaps and iron out some bugs.

But the main idea should already be visible. There are going to be a couple of primitives and users can combine them together.

Some examples:

local widgets = require('dap.ui.widgets')

widgets.hover(widgets.scopes) -- opens scopes in a floating window
widgets.hover(widgets.frames) -- opens stack frames in a floating window

widgets.sidebar(widgets.scopes) -- opens scopes in a sidebar

This would be the high-level entry points.
There will be a different filetype per scope so that users can use ftplugin, but you can also use a lower level API to customize the window creation.

local widgets = require('dap.ui.widgets')

widgets.builder(widgets.scopes)
  .new_win(your_function_that_creates_a_window)
  .build()
  .open()

There might be some default new_win / new_buf functions and maybe even some combinators that could be re-usable. Not sure yet how far that will go.

Part of the credit goes to @rcarriga, the element system in nvim-dap-ui inspired some parts of the widget design.

Would be cool if some of the building blocks could even be re-used in nvim-dap-ui. (E.g the lower level layer that can be used to render lua objects to a buffer and have extmarks places that allows to access the lua object later on per line)

[theHamsta]

The file type to customize the highlight is dap-variables but the background should be the standard float background.

An option to choose the function that creates the window could be a solution just as for #161

make_floating_popup_options has a border option

[mfussenegger]

Made another iteration on the widget api stuff. #171 should now be ready for some testing and I'd appreciate some feedback on the API and customization options.

If you've use-cases that aren't covered yet, please let me know.

[mfussenegger]

Merged #171 and also added #172