> > 4. Tiny scopes. I would recommend implementing each GUI feature > independently of the others. A special library for everything is > too hard to write, control and patch. Use conventions like > +gui_statusbar, +gui_dialog_-widgets, and +font_prop. By > implementing features in small steps, they can be developed and > tested more quickly. >
About two years ago I started to develop a popup list for Vim (script 2606). The first version was developed in Python. This year I ported it to (object-oriented) C. Unfortunately after 3 months of porting and about 7k lines of ooc I ran out of time, so the project is on hold. The code is here: http://code.google.com/r/markomahnic-vim-popuplist/ branch vim-popuplist, popuplst.c and included files. Currently it uses the Vim internal drawing functions (vim screen). The idea was to create interfaces for other GUI systems by reimplementing the "virtual functions" of the PopupList "class". I think that with some more work and some Vim Script it could also be turned into a dialog system for text mode with the basic widgets displayed as list items: label, button, radio button, line edit, check box, drop-down list. This way one could write scripts that use GUI dialogs that would be usable in GVim and in console Vim. Marko -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
