Re: VimWiki - again - but with a brand new option
Am Mittwoch, den 09.05.2007, 10:33 -0500 schrieb Tom Purl: I wasn't aware of this, and it's definitely a problem. Here's what I propose we do: First, im not sure about what you mean by a) formatting standard and b) a script that supports the standard is a) something like a template in mediawiki-speak? see: http://home.comcast.net/~gerisch/MediaWikiTemplates.html http://www.mediawiki.org/wiki/Help:Templates is b) something that reads the tips-db on vim.org and posts it to the wiki? Everything else is agreed and appreciated :-) Seb. PS: When writing this mail I got my hands dirty on the scratchpad of wikia.com: http://scratchpad.wikia.com/wiki/VimTest http://scratchpad.wikia.com/wiki/Template:Tip PPS: There are extensions for mediawiki that could be useful: To supply a HTML-Form to submit a tip: http://meta.wikimedia.org/wiki/Help:Inputbox To order a list of pages by popularity http://semeb.com/dpldemo/index.php/Manual Both are installed on wikia.org
Re: VimWiki - again - but with a brand new option
Am Mittwoch, den 09.05.2007, 13:06 -0500 schrieb Tom Purl: We do have a Wikia site available if we want it (http://vim.wikia.com/wiki/Main_Page). I agree with you; it has a lot of nice features, and may give us a bit more flexibility than the wikibooks option. I think we should revisit this topic once we're ready The features are mostly the same. In fact all major extensions are installed on wikibooks too. On any mediawiki try out the page Special:Version to see all installed extensions: http://wikibooks.org/wiki/Special:Version Note the modules SpamBlacklist, UsernameBlacklist and ConfirmEdit (Captcha) Wikia.com is clearly aimed at making money with ads. Therefore I now vote for wikibooks.org. :-) Sebastian.
Re: VimWiki - again - but with a brand new option
Am Montag, den 07.05.2007, 16:07 -0700 schrieb Ian Tegebo: The Wiki would ideally understand how to link to vim-scripts and vim-tips like vimonline currently does. As a bonus, mailing-list posts would also linkable Easy:http://en.wikipedia.org/wiki/Interwiki#Shorthand_for_non-wiki_sites For Wikia: http://www.wikia.com/wiki/Interwiki_map But this touches the critical point: The real question is, howto organize/access existing contributions (and contribution channels) from a wiki. Wikipages are generic, while tips, scripts, plugins, helpfiles etc. have more structure and - perhaps because of that - an established infrastructure. There is nothing against writing new things freely in the wiki and then, afterwards, copy them to svn or make a script/plugin/syntax-file/tutor or whatever ... Probably one could also easily write some html-form that submits a tip/script to the database on vim.org I would like to see the VimWiki as a kind of portal to the plethora of vim-related material. (Recall the slogan: Avoid redundancy!) In such a community-driven portal, each contributor has an interest to get her contribution found. Thus there is no need for a centralized management as on vim.org. A question to the experienced users/developers: How is that plethora organized internally? What are the main (most important, most popular) sections? Sebastian.
Re: VimWiki - again - but with a brand new option
Hi all Independent of the implementation used, I suggest to develop good guidelines. The Wiki should be really valuable and not redundant to vim-tips or mailing-lists. I think it's also important to have some people feeling responsible for it so if someone doesn't follow the rules, they will tidy it up quickly. my 2 cents, Sebastian. PS: I would clearly prefer wikia.org over sf.net (I would not build up upon any beta ...)
Re: Vim's ole functionality
Am Donnerstag, den 26.04.2007, 14:08 +0200 schrieb Sebastian Menge: Perhaps this Mail from eclipse helps: [ ... ] quote from that mail: SWT supports the embedding of OleDocuments and Active X Controls only. In order to be an ActiveX control, the control must support a minimum set of interfaces. The error you are getting is Interface not supported. [...] but my guess is it does not have the minimum set of API required to be an ActiveX Control. Some of the required interfaces are: IOleObject IOleInPlaceObject IOleInPlaceActiveObject IOleControl Are the if_ole developers around? Does gvim implement these interfaces !? I don't see them in the OLEViewer from M$ ... Sebastian.
Re: Vim's ole functionality
Am Dienstag, den 24.04.2007, 16:46 +0530 schrieb Nageshwar M: I tried all the options I checked :version and there is this line with OLE support. I tried to run the application from python as said in documentation and its working fine there. But from java with swt library I'm getting the same error. Please give more information: Perhaps it's a java problem? Can you post (some of) your code? Then we could try to reproduce it. Sebastian.
Re: Reannouncing vimplugin: A vim plugin for Eclipse
Am Sonntag, den 01.04.2007, 13:33 -0400 schrieb Silent1: Just a quick question about the overal goal of the project. Would vim just become an editor inside eclipse? Or would we be able to still use vim inside eclipse but still use code completion say from plugins like zends php project for eclipse or phpeclipse or any of the languagle specific plugins? Thanks --Brendon [replying to vim-dev only] [crossposting to vimplugin-devel] The overall goal of the project is to tightly integrate vim into eclipse. That means that the developer should choose what features of what program to use. On a higher level the idea is to treat vim as real editor component but to let other things like compiling, cvs/svn, integration of api-documentation, large scale refactorings, perhaps gui-building to the IDE. So the spirit is Vim is not an IDE. The eclipse core plugin architecture uses so called extension points to define its interfaces. The idea of vimplugin is to map those extension points to vim features where possible/adequate. That means that if phpeclipse and the like work as intended with such interfaces, the integration with vim could work out. Problems will come when there are redundant features: Which one is the better? (e.g. QuickFix, Buffers) But that's still a long way to go. At the moment we are struggling to build a text(terminal)-based vim with netbeans support. From :help netbeans-configure Currently, only gvim is supported in this integration as NetBeans does not have means to supply a terminal emulator for the vim command. Furthermore, there is only GUI support for GTK, GNOME, and Motif. Any idea why it is like that or how one could change it !? Help or suggestions are appreciated. Sebastian.
Reannouncing vimplugin: A vim plugin for Eclipse
Hi all After a long time of no activity we restarted the work on a small plugin to embed vim into the Eclipse IDE. See http://vimplugin.sf.net and http://sf.net/vimplugin for details. If you are familiar with eclipse, there is an update site http://vimplugin.sf.net/update with the latest build. Microsoft users have to use the cygwin version of vim. We also have a prototype of an eclipse-plugin that talks to a gvim that acts as netbeans server (:help netbeans). More detailed info on that can be found here: http://vimplugin.svn.sourceforge.net/svnroot/vimplugin/branches/vimclient/doc/README Both projects are standard eclipse projects that can be checked out anonymously via subversion (you need subclipse then): http://vimplugin.svn.sourceforge.net/svnroot/vimplugin/trunk/vimplugin http://vimplugin.svn.sourceforge.net/svnroot/vimplugin/branches/vimclient This time we'll keep an better eye on community building: So please try it out and give some feedback. On http://sf.net/projects/vimplugin you can find forums and of course mailinglists. Best regards, Sebastian.
Re: Netbeans Interface
Am Donnerstag, den 01.06.2006, 16:08 +0200 schrieb Sebastian Menge:
Or does it mean that i have to compile my own vim with disabled
gui-support and enabled netbeans?
I forgot to mention what I want to do ...
I want to communicate via the netbenas-protocol with a vim in a
terminal. That vim should not have any X or GUI features.
Is that possible?
If yes, how would I have to ./configure vim? I tried
./configure --enable-gui=no --enable-netbeans
But it doesnt seem to work.
On my ubuntu box 'vim --version' has +netbeans_intg and +X11, is linked
against gnome-libs. If I start my homebrewn netbeans-server, and then
'vim -nb', nothing happens. If I type :gui in the same vim-instance, it
immediatly connects to the server and executes the test command.
Thanks to anyone helping me with this.
regards, Sebastian.
PS: my test server:
start it first, then 'gvim -nb'
---
import java.io.BufferedReader;
import java.io.IOException;
import java.io.InputStreamReader;
import java.io.PrintWriter;
import java.net.ServerSocket;
import java.net.Socket;
public class VimNBApp {
private static ServerSocket socket;
private static Socket vimSocket;
public static void main(String[] args) {
try {
socket = new ServerSocket(3219);
System.out.print(Server waiting for connection ...);
vimSocket = socket.accept();
System.out.println( connected.);
PrintWriter out =
new PrintWriter(vimSocket.getOutputStream(), true);
BufferedReader in =
new BufferedReader(
new InputStreamReader(vimSocket.getInputStream()
));
//handshake
System.out.println(in.readLine());
System.out.println(in.readLine());
System.out.println(in.readLine());
String cmd = 1:editFile!123 \/tmp/test.txt\;
out.println(cmd);
System.out.println(sent: +cmd);
} catch (IOException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
}
}
-
Re: Netbeans Interface
Am Donnerstag, den 01.06.2006, 12:49 -0700 schrieb Xavier de Gaye: Netbeans can only be used with gvim compiled either with GTK, Motif, or with the Windows version of gvim. It cannot be used with plain vim running in a terminal. No workaround? The communication itself does not need the gui. Im no c-programmer, but that sounds, as if one would have to change little in netbeans.c .. !? Seb.
