[prev in list] [next in list] [prev in thread] [next in thread] 

List:       vim-dev
Subject:    Re: using vim with gtk2, gnome2, bonobo
From:       Mickael Marchand <lists () freenux ! org>
Date:       2002-11-21 11:28:32
[Download RAW message or body]

Le Jeudi 21 Novembre 2002 11:08, vous avez écrit :
> Around about 20/11/2002 17:14, Mickael Marchand typed ...
>
> > If we could fix the event loop stuff in Vim GUI then we could make a
> > common
> > XPart that we could use in gnome and in kde and other toolkits and we
> > could
> > do everything we wants with Vim, controlling directly Vim without the
> > need of
> > a communication system.
>
>    You got any links to xpart docs.?

have a look there : 
http://webcvs.kde.org/cgi-bin/cvsweb.cgi/kdebindings/xparts/doc/

> > Vim is far from usable as a component even if you can graphically show
> > it as
> > an embedded component. The worst problem will be the control of Vim.
> > Quick example : the component asks Vim to open a file, the user works
> > on it,
> > then opens another file with :e myfile.txt, hey :) the component can't
> > know
> > it and still believe you are on the first file ;). I let you imagine
> > what can
> > happen after that when the component sends other commands :).
>
>    Sounds like we need an extended stdin/stderr I/F to a 'remote' vim;
> taking ex commands (with which we can do anything we want in vim) [these
> would have to be 'run' by the remote vim uponreceipt of the <cr>, with
> maybe a fake preceeeding <c-o> [would have to be raw, in case user has
> mapped that!] if user's in INSERT mode, and other caveats],  and sending
> some standardised feedback via stdout (opened file blah, saved file
> blah, etc.).
>
>    The app. would have to cope with vim doing the splits (as it were :)
> ), though - it's not as simple as 'not edit the original file anymore'.
would be much better to be able to look in Vim internals directly so that we 
knows what happens ...
to get information about Vim's state, using ex commands will be much slower, I 
don't want to sent a "remote/ex" 'echo &vim_var' to see if vim_var is set, 
it's faster to look directly at the variable inside Vim if we can do it ;)

Cheers,
Mik

-- 
Mickael Marchand, marchand@kde.org, marchand@freenux.org
KVim maintainer, http://freehackers.org/kvim
"Leading Vim to the K Desktop Environment !"

[prev in list] [next in list] [prev in thread] [next in thread]