tests/subversion/edm.diff

0001 Index: NEWS
0002 ===================================================================
0003 1c
0004 just a fake modif for kompare tests
0005 .
0006 Index: README
0007 ===================================================================
0008 116a
0009 Hope you'll enjoy Vim inside KDE :)
0010 Mickael "Mikmak" Marchand (marchand@kde.org)
0011 .
0012 115a
0013 So, it's designed for KDE 3.x (if someone wants to port it to KDE 2 that
0014 should be easy), it uses GVim or KVim (even Motif Vim works) 6.x.
0015 It can be used in different apps :
0016         - KDevelop (version 3)
0017         - Konqueror (as a file viewer)
0018         - KWrite
0019         - KMail (coming in KDE 3.2)
0020         - Kompare, KBabel ........ ;)
0021
0022 CONFIGURATION
0023 =============
0024 once you compiled and installed it as any other app,
0025 start your KDE Control Center, go to the file manager section
0026 and open the Vim Component configuration module.
0027 Here, you have to select a Vim executable which may be found on
0028 your computer (generally /usr/bin/vim) will do it fine for most
0029 linux distributions. All you need is that it's a GUI-enabled Vim 6.0 or
0030 better.
0031 Push the test button, if that's okay then that's should be enough to start
0032 using it :)
0033
0034 FUNCTIONMENT
0035 ============
0036 Philippe Fremy (pfremy@kde.com) wrote the initial version of this kpart.
0037 The concept is to start a normal GUI Vim (like gvim), then "embeds" the Vim
0038 window into a KDE Widget.
0039 It used to be based on the ClientServer feature of Vim (type :help
0040 clientserver in Vim for more info) using external processus to control the
0041 embedded Vim. That was running quite fine, but was slow :/
0042 We changed that :)
0043 Now we communicate directly from the kpart to the embedded Vim thanks to X11
0044 without using externals processus. That's much faster and reliable ;)
0045 KVim has also another remote control system using KDE's DCOP communication
0046 backend.
0047 Currently I would advice people to use DCOP when running KVim and using X11
0048 communication with GVim (DCOP won't work with GVim anyway).
0049 There may be some differences in speed, though I have not noticed it here.
0050 The most important difference is that DCOP provides a signal system and that can
0051 make a difference to improve the interaction between KVim and the hosting
0052 application (KDevelop for example). But it's not yet used.
0053 .
0054 1,114c
0055 Yes, that's really a Vim Komponent :)
0056 Yes, you can have Vim inside KDE apps, you guessed it :)
0057 .