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

List:       vim-dev
Subject:    Re: KVim 6.0 development
From:       Joseph Edward Miele <jemiele1 () tampabay ! rr ! com>
Date:       2001-11-04 15:46:32
[Download RAW message or body]

Mik -

I tried out the November 3 tarball. The "make install" works perfectly, 
no problems! :-)

Next, I tried out the toolbar. (First off, I noticed that you updated 
the README file in the November 3 source. Very cool.) I copied the 
menu.vim from the Kvim source to /usr/share/vim/current for SuSE Linux 
7.3 to replace my current menu.vim. Then I launched kvim from a konsole 
session. Upon startup, kvim started, but it also reported the following 
message on the konsole session:

Can't open file /usr/share/vim/syntax/nosyntax.vimgui_mch_show_toolbar: 
show: 0 : icons,tooltips 1

I did a find for this file, but it doesn't reside anywhere on my system. 
Is this something kvim specific?

Despite this message, I tried :set guioptions+=T, but all it did was 
overwrite some of the version information that normally displays when 
kvim starts up.

In summary, two issues remain before I can really start beating on kvim:
1. Toolbar/menu isn't running.
2. Font selection dialog. The hard coded font is very hard to read and I 
can't really test kvim with it.

Hope reporting all of these nitpicky little issues are helping you out. :-)

- Joe

Mickael Marchand wrote:

> Pleased to ear it works for you :)
> 
> so, the Makefile has been corrected from 03/11 concerning the make
> install problem
> the font problems is a big one with KDE, today i will try to add the
> font selection dialog, then i think we will see if that's enough or if
> we need more work on this point  (which i think will be),
> for KDE2 , i have disabled AntiAliased fonts in  kvim (looks really
> ugly) and i have 'hard' compiled a default font which looks fine on my
> computer, but maybe it's not a good choice for you.
> Concerning the toolbar, you're right the README.kvim is really out of
> date, to get  menus and toolbar you need to copy the 'menu.vim' file
> provided (top level directory) where are your vim files (something like
> /usr/share/vim/), this allow the KDE gui to get  menus and toolbars.
> For the toolbar, make sure your guioptions contains T (:set
> guioptions+=T)
> 
> thanks for your support,
> Mik
> 
> On Sun, Nov 04, 2001 at 01:33:27AM -0500, Joseph Edward Miele wrote:
> 
>>Mik -
>>
>>I had the libraries installed already, so it was just a matter of 
>>setting the variables in the Makefile. Compilation worked like a charm.
>>
>>The "make install" didn't fare quite as well. If /opt/kde2/bin/vim 
>>doesn't already exist, the "make install" dies. I created an empty kvim 
>>in /opt/kde2/bin and then make install did it's job.
>>
>>I have only run the program for a few minutes (it's really late right 
>>now and I need to get some sleep), but here are some observations.
>>
>>1. Kvim runs and edits files successfully. That's a good sign! :-)
>>2. No toolbar. The patch information in the README.kvim is out of date 
>>for Vim 6.0. There is going to have to be a different procedure/patch 
>>for getting that running. Too late for me to tinker with it.
>>3. The default font displayed in the Kvim window is seriously ugly. Does 
>>Kvim obey KDE font settings? I am going to have to play with that to 
>>find something that is easier on the eyes.
>>
>>For a first port to Vim 6.0, things aren't looking half bad. If you have 
>>some ideas on how to get that toolbar running, I will start trying to 
>>use Kvim has my main editor and see what kind of problems I can find for 
>>you.
>>
>>Looks like you are doing a fine job in adding KDE support to Vim!
>>
>>- Joe Miele
>>
>>Mickael Marchand wrote:
>>
>>
>>>hi,
>>>
>>>i've just checked the suse configuration on www.suse.com,
>>>so you need to have qt-devel and kdelibs-devel packages installed
>>>these will put KDE 's  headers in /opt/kde2/include (so KDEDIR=/opt/kde2)
>>>and  qt's headers will be installed in /usr/lib/qt2.3.1/include (so 
>>>QTDIR=/usr/lib/qt-2.3.1)
>>>i think you are missing these two packages since they are probably not 
>>>installed with the default configuration,
>>>
>>>cheers,
>>>Mik
>>>
>>
>>
>>
> 

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