On 11/5/06, Marc Weber <[EMAIL PROTECTED]> wrote:
I've posted some time ago about this ideas:

seperate user interface (mappings autocommands ..) from script code.
Unify efforts (thus make it easier to existing code) ..

I did call my attempt vimlib.
It can be used here:
http://mawercer.de/marcweber/vim/vimlib/

You can try out the installer files how it might look like to install different 
scripts.
If you want add another runtimepath to be sure to not modify your existing vim 
configuration (1)

goto docs -> index_file.html to get some overview of all files.
Especially I recommend reading:
        vl_create_docs.vim ( how the documentation has been created 
automatically from .vim source file comments)
        scriptsettings.vim ( how to save / load user settings )
        vimlib.vim ( more about this idea.)
        vim_vimlib.vim ( how a user interface can be distributed )
        taghelper.vim ( define tag profiles and add tag/ create tag files 
really easily )
        vimfile.vim ( vim autoload function prefix correction / function 
completion )
        scan_and_cache_file.vim ( calls a scanning func to extract some 
information which is cached in mem or additionally in a file. see vimfile.vim 
for examples)
        multifile_distribution.vim/ create_installer.vim / 
create_installer_examples ( creates the installer)

Its even posseble to browse documentation, copy some example code and run 
"DownloadEverythingNeededFor <file>"
to get all dependencies automatically after installing the base files using the 
installer.
Some things might be broken and much isn't implemented yet..

Currently darcs is used as version control system.
If you want to get everything use
darcs get http://mawercer.de/marcweber/vim/vimlib/repository/
Then its easy to create and send patches.

But last but not least I need your comments.
Do you think it would be useful to put more efforts into developing this?

        Greetings Marc

(1)
just enter eg /home/you/vimlib_test as runtimepath to save to
add
        set runtimepath+=~/vimlib_test
to your .vimrc
After finishing testing you can remove the directory and nothing will be left 
except of
~/.vim/permanent_memory ( used to cache file scan results) and
~/.vim/scriptsettings ( used to save script settings )


Where is user documentation ? Readme-shmeadme ?

Yakov

Reply via email to