UI extension work (tracking issue)

Tracking/discussion issue for planned UI enhancements. NB: being mentioned on the list below is not a guarantee for being done at any specific time scale, nor is the order necessarily indicative of readiness/priority (except perhaps for the smaller follow-up items for multigrid, which I hope to get done pretty soon). Feel free to add stuff. - [x] multigrid (#8455 **merged**) - [x] improve size handling: non-screen functions should use requested size, not grid allocated size. - [x] `:term` sizing issues (fix `terminal_resize`) - [x] mouse support (#9429) - [ ] messages on dedicated grid (when not `ext_messages`) - [x] floating windows (#6619) - [x] for `!ext_popupmenu`: pum as float (#9530) - [x] for `ext_popupmenu`: add tests for grid anchoring - [x] `nvim_win_close` to close window by id. - [x] Ex-commands for floats (#9663) - [x] #9920 - [x] `pumblend` but for floats (because why not) - [x] `ext_messages` (#7466) - [ ] `ext_windows`: UI control of layout and wincmds (#8707) - [x] use `ext_popupmenu` events for wildmenu to support info and pum (#9607) - [ ] `ext_statusline` (I have some ideas/pre-WIP code...) - [ ] external columns (number, signs) by transmitting `wline_T` info (no work done) - [ ] "tabgrid" (#7541 but with multigrid) - [x] transmit UI highlight definitions for `ext_popupmenu` using `hl-Pmenu`, etc. (#10504) - [x] ensure that we always use concrete rgb colors for `default_colors_set` - [ ] allow subscribing non-default gro

Posted by bfredl on Dec 31, 2018, 5:45 PM

Tags

• ux (E-commerce)

Related issues

• It’s such an annoying problem to solve.
• > My point is, the impression many people will unavoidably take away from "many recalls" is that the vehicle must me in the shop all the ...
• [Feature]: Ability to merge old runs with a new run
• Add `findManyAndCount()` to return count of queried items
• One of the best, and first, things we did when starting our machine learning platform was to design it using a plugin architecture.
• gh pr push