Warning, /sdk/kompare/tests/subversion/contextm.diff is written in an unsupported language. File is not indexed.

0001 Index: NEWS
0002 ===================================================================
0003 *** NEWS
0004 --- NEWS        Sun Sep 22 14:34:37 2002
0005 ***************
0006 *** 1 ****
0007 ! 
0008 --- 1 ----
0009 ! just a fake modif for kompare tests
0010 Index: README
0011 ===================================================================
0012 *** README
0013 --- README      Fri Sep 13 23:05:48 2002
0014 ***************
0015 *** 1,117 ****
0016 !                                               Vim KPart
0017 ! 
0018 ! 
0019 !                                                                       by Philippe Fremy <pfremy@kde.com>
0020 ! 
0021 ! 
0022 ! Okay, I made it : a Vim KPart!
0023 ! 
0024 ! This means that you can have Vim embedded inside Konqueror, and everywhere a
0025 ! text ReadWrite or ReadOnly KPart is requested. Actually, there is almost no
0026 ! place right now where this is the case in KDE. KMail uses its own editor,
0027 ! KDEvelop uses its own editor, Kate uses some more powerful Kate component.
0028 ! 
0029 ! But this only the beginning. Enabling a part in those programs shouldn't be
0030 ! much hassle and you can probably help me do it. My hope is really to get
0031 ! KDevelop use Vim.
0032 ! 
0033 ! 
0034 ! ======= OBSOLETE ===========
0035 ! Requirements:
0036 ! -------------
0037 ! To make this KPart work, you need a graphicial Vim version 6 with the client-server stuff feature activated and with the vim60-vimpart-patch.diff applied. The patch is in this dir. I hope to get it into the main Vim tree.  KVim has already the patch but is slightly less stable that the original GVim.  A big advantage of KVim is that you get the native KDE dialogs when vim asks a question.
0038 ! 
0039 ! 
0040 ! ======= OBSOLETE ===========
0041 ! Installation:
0042 ! -------------
0043 ! To make your vimpart work, you'll have to go into the vimpart directory and run "testVim your_patched_vim". If the test does work, a file goodVim will be created. You will be able to install and use the component. Else, the test will report why it fails (features missing in vim).
0044 ! 
0045 ! 
0046 ! 
0047 ! ======= OBSOLETE ===========
0048 ! Testing:
0049 ! --------
0050 ! If you want to see your component without installing it, you can do the
0051 ! following:
0052 ! 
0053 ! 1. configure, build. Then go into the Vimpart subdirectory.
0054 ! 
0055 ! 2. Include the current Vimpart directory in your KDEDIRS:
0056 ! export KDEDIRS=`pwd`:$KDEDIR
0057 ! 
0058 ! 3. Symlink .libs to lib
0059 ! ln -s .libs lib
0060 ! 
0061 ! 4. Create pseudo share/services dir:
0062 ! mkdir share; mkdir share/services;
0063 ! 
0064 ! 5. Symlink to Vimpart.desktop:
0065 ! ln -s Vimpart.desktop share/services/Vimpart.desktop
0066 ! 
0067 ! 6. Create a pseudo share/config dir
0068 ! mkdir share/config;
0069 ! 
0070 ! 7. Symlink to vimwidgetrc
0071 ! ln -s vimwidgetrc share/config/vimwidgetrc
0072 ! 
0073 ! 8. Update the desktop mimetype database:
0074 ! kbuildsycoca
0075 ! 
0076 ! To test it, run VimPartShell. Or run konqueror from this dir and click on a
0077 ! text file.
0078 ! 
0079 ! 
0080 ! ======= OBSOLETE ===========
0081 ! Remarks:
0082 ! --------
0083 ! The initial preference of the Vim KPart is 10. Kate uses 8, so if you install the part, it will override Kate for all the mimetypes. You can always change that by manually editing the initial preference in the desktop file or by simply selecting which editor you prefer for which mimetype in the control center.
0084 ! 
0085 ! If you find some mimetype not handled by the Vim KPart although they should be, send me a patch!
0086 ! 
0087 ! 
0088 ! 
0089 ! How it works:
0090 ! -------------
0091 ! At the beginning, we started to write KVim, a port of GVim to KDE to make
0092 ! it possible to embed Vim inside KDE. But with the latest version of Vim, it
0093 ! turns out that it is not necessary to have a native Vim.
0094 ! 
0095 ! 
0096 ! I use QXembed, a widget which can embed any X application if it knows its X Window Id, using some X feature.  The patch I provide will make vim displays its window id on stdout when the window is mapped. GVim 6.0 then provides a way to send commands to a Vim window from another process. If you look at the VimWidget source, you will see that 70% of the code is there to handle the communication process. The rest uses the communication channel to send the vim commands needed by kpart and ktexteditor.
0097 ! 
0098 ! As far as I can tell, the part is race-condition free. If you issue many sendNormalCmd and many evalExpr, they are guaranted to be executed sequentially. This has caused me enough problems when it wasn't the case!
0099 ! 
0100 ! 
0101 ! Qt, KDE2 and KDE3:
0102 ! ------------------
0103 ! The VimWidget itself depends very litle on KDE. It is quite easy to port remove the KDE specific stuff, to use it in a Qt only program. In fact, at the beginning, it was only Qt-based.
0104 ! 
0105 ! 
0106 ! 
0107 ! ======= OBSOLETE ===========
0108 ! Features & TODO:
0109 ! ----------------
0110 ! I think most basic features required by an editor widget or part are supported. There are some possible improvement but I would like more feedback to know what really needs to be done. So don't hesitate to write me about your feelings using this.
0111 ! 
0112 ! My TODO list is:
0113 ! - restore the editing mode after sendCmd
0114 ! - implement KTextEditor interface
0115 ! - add some useful actions to the part (like search, ...)
0116 ! 
0117 ! 
0118 ! 
0119 ! Feedback:
0120 ! ---------
0121 ! For the Vim KPart : pfremy@kde.com
0122 ! For KVim: pfremy@kde.org, mikmak@freenux.org, orzel@kde.org
0123 ! 
0124 ! 
0125 ! 
0126 ! 
0127 ! 
0128 ! 
0129 ! 
0130   
0131   
0132   
0133 --- 1,47 ----
0134 ! Yes, that's really a Vim Komponent :)
0135 ! Yes, you can have Vim inside KDE apps, you guessed it :)
0136   
0137 + So, it's designed for KDE 3.x (if someone wants to port it to KDE 2 that
0138 + should be easy), it uses GVim or KVim (even Motif Vim works) 6.x.
0139 + It can be used in different apps : 
0140 +       - KDevelop (version 3)
0141 +       - Konqueror (as a file viewer)
0142 +       - KWrite
0143 +       - KMail (coming in KDE 3.2)
0144 +       - Kompare, KBabel ........ ;)
0145 + 
0146 + CONFIGURATION
0147 + =============
0148 + once you compiled and installed it as any other app, 
0149 + start your KDE Control Center, go to the file manager section
0150 + and open the Vim Component configuration module.
0151 + Here, you have to select a Vim executable which may be found on 
0152 + your computer (generally /usr/bin/vim) will do it fine for most
0153 + linux distributions. All you need is that it's a GUI-enabled Vim 6.0 or
0154 + better.
0155 + Push the test button, if that's okay then that's should be enough to start
0156 + using it :)
0157 + 
0158 + FUNCTIONMENT
0159 + ============
0160 + Philippe Fremy (pfremy@kde.com) wrote the initial version of this kpart.
0161 + The concept is to start a normal GUI Vim (like gvim), then "embeds" the Vim
0162 + window into a KDE Widget.
0163 + It used to be based on the ClientServer feature of Vim (type :help
0164 + clientserver in Vim for more info) using external processus to control the
0165 + embedded Vim. That was running quite fine, but was slow :/
0166 + We changed that :)
0167 + Now we communicate directly from the kpart to the embedded Vim thanks to X11
0168 + without using externals processus. That's much faster and reliable ;)
0169 + KVim has also another remote control system using KDE's DCOP communication
0170 + backend.
0171 + Currently I would advice people to use DCOP when running KVim and using X11
0172 + communication with GVim (DCOP won't work with GVim anyway).
0173 + There may be some differences in speed, though I have not noticed it here.
0174 + The most important difference is that DCOP provides a signal system and that can
0175 + make a difference to improve the interaction between KVim and the hosting
0176 + application (KDevelop for example). But it's not yet used.
0177   
0178 + Hope you'll enjoy Vim inside KDE :)
0179 + Mickael "Mikmak" Marchand (marchand@kde.org)
0180