On Tue, Feb 23, 2010 at 8:20 PM, Marc Weber <[email protected]> wrote:
> Excerpts from Kana Natsuno's message of Tue Feb 23 12:59:38 +0100 2010: > > On Tue, 23 Feb 2010 07:12:15 +0900, Marc Weber <[email protected]> > wrote: > > > for vim-addon-manager I added missing metadata myself. > > > Eg for the perl browser plugin I added meta data in > > > vim-addon-known-repsoitories this way: > > > > > > " this is mainly used to add missing dependencies > > > let s:missing_addon_infos["browser_4025"] = '{ "dependencies" : > {"synmark":{}}, "runtimepath": "vim" }' > > > > How about using Vim Wiki to put such data? > By suggesting this you've missed the whole point about vim-addon-manager > and vimana. > > Those tools assist you installing plugins. This means they do this > automatically. > Using a wiki is a bad format to store this kind of meta data. > To use wiki page to store this kind of data is not a good idea, these thing should just query from database. I think it's easy to write some php code to output these meta data in json format, but why nobody does it? To the question , script type "class". because autoload script doesnt provide the feature of calling other autoload function from an autoload function, so Objects is hard to declare in an autoload script to reuse. these things could put into ~/.vim/plugin/ , but which is not very appropriate. So I think if Vim could load these class at first, then run plugin scripts, Or let autoload function support calling other autoload functions. -- Best Regards. Cornelius ( Yo-An Lin ) E-mail: [email protected] -- You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php
