On 15-Jul-09 12:42, mobi phil wrote:
> Hello,
>
> I hope you do not feel unconfortable with my intensive activity here on
> the mailing list.
> I was thinking how would it be possible to "prototype" new features
> smoothly and came
> to the conclusion that a plugin mechanism would do that. For instance
> the smartsearch
> I was talking in my previus email could be defined as a new command,
> let's say "//",
> the implementation would not interfer with the existing code at the
> begginning, but would,
> be implemented into a copy of those files that implement the original
> "/" built into a pluggin.
> There would be issues with existing symbols, but one could rename those
> symbols in the
> pluggin with sthg. like origFunction_smartsearch() etc. When the feature
> would be enough
> mature, or at major release the changes in the pluggin version +
> additional files from the
> plugging could flow into the main executables base.
>
> The pluggins would be loaded dynamiccaly, would have an init function,
> and would attach
> information to the global command map. The pluggins could use the
> exported functions from
> the exe to do their job.
>
> Even more existing features like python, perl etc interfaces could be
> optionally defined as
> pluggins and loaded if necessary. In embedded devices python might be
> used on demand for
> example.
>
> Such pluggin mechanism would allow to build connectors to other IDE's,
> something I see it is
> requested on the "wishlist" on vim.org <http://vim.org>
There is a "Vim patches" page on this group's Google page:
http://groups.google.com/group/vim_dev/web/vim-patches
You can post a proposed new feature as a patch to this list, and ask for
inclusion on the Vim patches page. Interested Vim users will try it out and
provide feedback, and hopefully the patch will eventually be incorporated into
the mainline.
If you use the Git version control system, you can easily download patches and
build a custom Vim version thanks to Markus Heidelberg's vim_extended Git
repository.
IMHO this process is simple and effective. Your plugin proposal would make
adopting experimental features even more easy, but in my opinion it also
introduces a lot of extra complexity and potential for problems. (Just consider
the many platforms that Vim supports!)
-- regards, ingo
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
