You can subscribe to this list here.
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(4) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
2007 |
Jan
|
Feb
|
Mar
(12) |
Apr
(19) |
May
(16) |
Jun
(5) |
Jul
|
Aug
(4) |
Sep
(25) |
Oct
(49) |
Nov
(9) |
Dec
(2) |
2008 |
Jan
(2) |
Feb
(13) |
Mar
(4) |
Apr
(11) |
May
(35) |
Jun
(4) |
Jul
(10) |
Aug
(5) |
Sep
(24) |
Oct
(8) |
Nov
(25) |
Dec
(35) |
2009 |
Jan
(10) |
Feb
(12) |
Mar
(20) |
Apr
(30) |
May
(35) |
Jun
(27) |
Jul
(42) |
Aug
(8) |
Sep
(2) |
Oct
|
Nov
(4) |
Dec
(8) |
2010 |
Jan
(7) |
Feb
(9) |
Mar
(2) |
Apr
(2) |
May
(1) |
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(1) |
2013 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
(2) |
Jul
(2) |
Aug
(5) |
Sep
(2) |
Oct
|
Nov
|
Dec
(1) |
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
From: Eric V. D. <erv...@gm...> - 2008-05-11 06:07:44
|
FYI: I just made some modifications to the eclim build file to rely less on environment variables. I also added validation of the only required user specific property (eclipse.home) which, if not set correctly, will cause the build to abort with an informative message rather than attempt to build and fail along the way. > I'll try to find some time to test the build scripts on windows again. I also tested everything out again on windows and the build ran smoothly. Please give the latest version a shot and report any issues to me. -- eric |
From: Sebastian M. <seb...@un...> - 2008-05-10 21:37:16
|
Am Sat, 10 May 2008 14:27:46 -0700 schrieb mooseydoom <moo...@gm...>: > Apologies, that was my patch that was returning the > parent.embeddedHandle. I was having problems getting the wid using > c.getField(linuxWID).getInt(parent) method on Fedora (core 8) / fedora > eclipse (based on eclipse 3.3.0). fixed already. > I am having more problems under Ubuntu (8.4 > "Hardy"). works for me .. Seb. |
From: mooseydoom <moo...@gm...> - 2008-05-10 21:27:40
|
Nageshwar - Apologies, that was my patch that was returning the parent.embeddedHandle. I was having problems getting the wid using c.getField(linuxWID).getInt(parent) method on Fedora (core 8) / fedora eclipse (based on eclipse 3.3.0). I am having more problems under Ubuntu (8.4 "Hardy"). The c.getField(linuxWID).getInt(parent) method works, but when vim is started using the ProcessBuilder, it doesn't connect to the VimServer. I can see the process running, but vim complains "Vim: Warning: Output is not to a terminal Vim: Warning: Input is not from a terminal", and eclipse hangs. Vim plugin works properly if vim is started using p = Runtime.getRuntime().exec(args); [in the org.vimplugin.VimServer start(args) function]. Might be some environment variable settings, or maybe just some weird java thing. On 5/10/08, vim...@li... < vim...@li...> wrote: > > > Message: 7 > Date: Sat, 10 May 2008 10:03:26 +0530 > From: Nageshwar <nag...@st...> > Subject: [vimplugin-devel] Problem on windows > To: "vimplugin mailing list" <vim...@li...> > Message-ID: > <1cd...@ma...> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi, > > In the file widhandler.java, parent.embeddedHandle was used to get the > window Id. This field is not supported > on eclipse sdk 3.3.2 on windows. I got some errors when I tried to run > the project reporting that the field doesn't exist. > > I replaced the line > return parent.embeddedHandle; > with the following. > return c.getField("embeddedHandle").getInt(parent); > > I don't know whether the above code works or not. someone, please > check this on linux machine and commit the changes. > > -- > Best Regards, > Nageshwar M. > > |
From: Sebastian M. <seb...@un...> - 2008-05-10 21:22:33
|
BTW on this topic: I have started a compatibility matrix at http://vimplugin.org/compatibility Please add your configuration and comments there ... Am Sat, 10 May 2008 10:03:26 +0530 schrieb Nageshwar <nag...@st...>: > I don't know whether the above code works or not. someone, please > check this on linux machine and commit the changes. I tried your code, but it uses again an int instead of long which reintroduces the bug with 64bit systems fixed by "moosydoom" (do we have a policy on realnames !?). Nageshwar, could you try this please? if (Platform.getOS().equals(Platform.OS_LINUX)) { f = c.getField(linuxWID); } else if (Platform.getOS().equals(Platform.OS_WIN32)) { f = c.getField(win32WID); } else { f = c.getField(win32WID); } return f.getLong(parent); ^^^^^^^ This should suffice on 64bit systems. Hmm, the getWid() method doesnt do anything more beside the if statement above. The WidHandler class has only that (static) method. The method is called only at one place. The error handling (return WID_ERROR) is not java-like (thats what exceptions are for..). Would anyone mind if I move the statement to its call at AbstractVimEditor ? Seb. |
From: Eric V. D. <erv...@gm...> - 2008-05-10 19:31:28
|
>> And on Linux it is a pain too. I have given up ... > > And I thought it is just me who can't get the build process of eclim to work. Could you guys elaborate on the issues you are encountering. As the author of eclim, I continuously build it without issues, so with some additional feedback perhaps I can make things easier for you guys. > I did the needed changes to my best knowledge but since the eclim build > process is so broken I was never able to test the code. Again, please provide specifics so I can remedy the situation. Although I did make some changes to the build scripts to support windows, I don't build on that platform with any regularity so please report any issues and I'll try to resolve them in a timely manner. I'm a bit busy this weekend (mother's day and all), but I'll try to find some time to test the build scripts on windows again. Also, one other thing worth noting: I made some recent (1 or 2 weeks ago) changes to the build script to allow you to specify only the eclim plugins you would like to build. This would allow you to only build those portions you are working on and alleviate the need to have all the third party plugins (wst and pdt specifically) installed just to build eclim. Example which should only build and deploy the ant and jdt eclim plugins: $ ant -Dplugins=ant,jdt Note: by default the build script will attempt to build all available plugins. -- eric |
From: Martin K. <kri...@us...> - 2008-05-10 19:02:53
|
Am Samstag 10 Mai 2008 schrieb Sebastian Menge: > Am 10.05.2008 um 09:58 schrieb Martin Krischik > <kri...@us... > > > Compiling and Testing turned out to be a pain as the eclim build > > process is > > designed for Linux only. > > And on Linux it is a pain too. I have given up ... And I thought it is just me who can't get the build process of eclim to work. > Would it be possible for anyone to implement something like a minimal > eclim? Just to say "hello world" from vim(plugin) to eclipse ... > > I tend to start the whole thing from bottom up, since eclim is too > complicated , at least for me ... Maybe creating a new build and deployment process for eclim would be enough. Only my eclipse plugin skill are not up to it. Eclim itself is ok - it's just the build which is pain. > > But this has been fixed so I might restart - but before that can be > > done > > currend eclim and vimplugin code need to be merged in > > What do you mean by "merge in"? For the eclimplugin I made a copy of eclim and the vimplugin and checked both into a new directory tree inside our subversion archive: https://vimplugin.svn.sourceforge.net/svnroot/vimplugin/branches/eclimplugin And I worked from there. From time to time I merge the code changes from the main eclim and vimplugin into the code base. Note that the use of svn:externals makes this not as painfull as it sounds. And to turn eclim into eclimplugin one need to change only a hand full of files (just the startup code). I did the needed changes to my best knowledge but since the eclim build process is so broken I was never able to test the code. Martin -- Martin Krischik mailto://kri...@us... |
From: Sebastian M. <seb...@ud...> - 2008-05-10 17:21:39
|
Am 10.05.2008 um 09:58 schrieb Martin Krischik <kri...@us... >: > Compiling and Testing turned out to be a pain as the eclim build > process is > designed for Linux only. And on Linux it is a pain too. I have given up ... Would it be possible for anyone to implement something like a minimal eclim? Just to say "hello world" from vim(plugin) to eclipse ... I tend to start the whole thing from bottom up, since eclim is too complicated , at least for me ... > But this has been fixed so I might restart - but before that can be > done > currend eclim and vimplugin code need to be merged in What do you mean by "merge in"? Seb. |
From: Martin K. <kri...@us...> - 2008-05-10 08:03:07
|
Am Samstag 10 Mai 2008 schrieb Sebastian Menge: > Concerning eclim: There were some ideas, and I think Martin is > working at that front from time to time... What is the status there, > Martin? Compiling and Testing turned out to be a pain as the eclim build process is designed for Linux only. But this has been fixed so I might restart - but before that can be done currend eclim and vimplugin code need to be merged in. Martin -- Martin Krischik mailto://kri...@us... |
From: Nageshwar <nag...@st...> - 2008-05-10 04:33:19
|
Hi, In the file widhandler.java, parent.embeddedHandle was used to get the window Id. This field is not supported on eclipse sdk 3.3.2 on windows. I got some errors when I tried to run the project reporting that the field doesn't exist. I replaced the line return parent.embeddedHandle; with the following. return c.getField("embeddedHandle").getInt(parent); I don't know whether the above code works or not. someone, please check this on linux machine and commit the changes. -- Best Regards, Nageshwar M. |
From: Sebastian M. <seb...@ud...> - 2008-05-09 22:37:30
|
Concerning eclim: There were some ideas, and I think Martin is working at that front from time to time... What is the status there, Martin? We also had eclims lead developer on this list. The main idea was to make the eclim plugin work "headful" (as opposed to headless) and in parallel to vimplugin. But perhaps it'll be easier to copy their ideas and implement the right (whatever that may mean) eclipse extension points ... I would propose to start a wiki page on that topic: gather usecases, share ideas, discuss other designs (eg eclim) Greetings, Sebastian. Am 09.05.2008 um 21:03 schrieb Nageshwar <nag...@st...>: > Hi, > I just visited vimplugin.org. It looks very nice and has plenty of > information for starters. great contribution by sebastian. guys, if > you have any hacks on vimplugin or have something to share with the > users please edit the wiki and make your contribution. > > @developers: I read something on wiki related to combining vimplugin > and eclim. does anyone started steps towards bringing the eclipse > functionality to vim (like eclim)? I think the next major goal should > be to bring the eclipse editor functionality like code suggestions, > refactoring etc., to vim. If you accept that, then start exploring > eclim, eclipse api and the other possibilities. comments are most > welcome!! > > -- > Thanks, > Nageshwar M. > > --- > ---------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save > $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > vimplugin-devel mailing list > vim...@li... > https://lists.sourceforge.net/lists/listinfo/vimplugin-devel |
From: Nageshwar <nag...@st...> - 2008-05-09 19:02:53
|
Hi, I just visited vimplugin.org. It looks very nice and has plenty of information for starters. great contribution by sebastian. guys, if you have any hacks on vimplugin or have something to share with the users please edit the wiki and make your contribution. @developers: I read something on wiki related to combining vimplugin and eclim. does anyone started steps towards bringing the eclipse functionality to vim (like eclim)? I think the next major goal should be to bring the eclipse editor functionality like code suggestions, refactoring etc., to vim. If you accept that, then start exploring eclim, eclipse api and the other possibilities. comments are most welcome!! -- Thanks, Nageshwar M. |
From: Sebastian M. <seb...@un...> - 2008-05-09 16:46:37
|
Hi all Just did some things on general infrastructure : * Updated the wiki-engine, (most notably better rss feeds and email subscriptions) * More content and structure on the wiki * refactored the anonymous listeners out of the lengthy method. * prepared http://vimplugin.org/api (not up to date by now...) ( so write javadocs! ) Regards, Seb. |
From: Sebastian M. <seb...@un...> - 2008-05-08 07:15:50
|
Am Tue, 6 May 2008 11:09:32 -0700 schrieb "Aaron H." <aa...@ho...>: > I'm looking forward to the future of vimplugin, and would like to help > if my time permits, (we'll see) Cool. Glad to have you on board. > Is there any protocol for editing the wiki? I'd like to update the > installation docs specifically with regard to the windows setup. It > took me several tries and numerous hours to get up and running > properly under windows, and it's simple if you know what to do. No protocol. Just use your common sense. Technical writing is complicated. Take care that you make the right assumptions, write them down (versions), write simple, structure well. But first rule in wikis: Be Bold. We can refine at any later point. Thanks for contributing, Sebastian. |
From: David F. <Dav...@ia...> - 2008-05-07 21:19:13
|
Aaron, When you have made your changes please post. I would like to try this out. TIA, Dave > -----Original Message----- > From: vim...@li... > [mailto:vim...@li...] On > Behalf Of David Terei > Sent: Tuesday, May 06, 2008 5:00 PM > To: vimplugin mailing list > Subject: [vimplugin_eclipse] Re: [vimplugin-devel] Introduction > > Hi Aaron, > > Great to hear from you, we would appreciate any help, there > are quite a few of us now (4) but none of us have much time > at all so progress is quite slow. > > Talking to us first before changing the Wiki is great, we > haven't discussed a policy for editing but given the low rate > of change I think we would all be happy to allow you and > others to edit away in good faith and any issues that arise > we will contact you or revert the changes. > > Regards, > David > > On 5/6/08, Aaron H. <aa...@ho...> wrote: > > Hello, > > > > My name is Aaron Hachez. I'm an avid Vim user, and a > production Eclipse user. > > > > I'm looking forward to the future of vimplugin, and would like to > > help if my time permits, (we'll see) > > > > Is there any protocol for editing the wiki? I'd like to > update the > > installation docs specifically with regard to the windows > setup. It > > took me several tries and numerous hours to get up and running > > properly under windows, and it's simple if you know what to do. > > > > Cheers, > > Aaron > > > > > > > ---------------------------------------------------------------------- > > --- This SF.net email is sponsored by the 2008 JavaOne(SM) > Conference > > Don't miss this year's exciting event. There's still time > to save $100. > > Use priority code J8TL2D2. > > > > > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com > > /javaone _______________________________________________ > > vimplugin-devel mailing list > > vim...@li... > > https://lists.sourceforge.net/lists/listinfo/vimplugin-devel > > > > > -- > Best regards, > > David Terei > > -------------------------------------------------------------- > ----------- > This SF.net email is sponsored by the 2008 JavaOne(SM) > Conference Don't miss this year's exciting event. There's > still time to save $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java > .sun.com/javaone > _______________________________________________ > vimplugin-devel mailing list > vim...@li... > https://lists.sourceforge.net/lists/listinfo/vimplugin-devel > |
From: David T. <dav...@gm...> - 2008-05-07 19:30:04
|
Hi all, On 5/7/08, Nageshwar <nag...@st...> wrote: > Hi guys, > > > > Nageshwar submitted a patch which has > > been added to Vim a while ago (although not yet in a released version) > > I think it is in the latest release 7.1 No its patch patch 7.1.091 (extra) so wont be released till 7.2 > > > > > > 1) Vim when started isn't 100% maximised and can be resized. Ideally > > it should fill the whole window and can't be resized, the GTK version > > functions this way. > > > > Didn't we write code for resizing the gvim window to the size of the > editor window ? Not sure, I think so but that its off by 1 pixel or so. > > > > > 2) It steals the focus from Eclipse. Even though its 'inside' and > > 'part of' Eclipse, when you select the Vim instance, Eclipse > > completely looses the focus, e.g The title bar becomes the deactivate > > title bar. > > > > > oh, I never observed this. what method the mplayer guys are using for > embedding ? Ok, I'll have to install Eclipse and the plugin when I have time since I have a new laptop, MPlayer guys are using the method that I mentiioned before, I'm not very clear on the method as I was still studying it to potentially implement a patch for vim but it was not needed since you solved the problem. > > > -- > Best Regards, > Nageshwar M. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > vimplugin-devel mailing list > vim...@li... > https://lists.sourceforge.net/lists/listinfo/vimplugin-devel > -- Best regards, David Terei |
From: Nageshwar <nag...@st...> - 2008-05-07 06:59:31
|
Hi guys, > Nageshwar submitted a patch which has > been added to Vim a while ago (although not yet in a released version) I think it is in the latest release 7.1 > > 1) Vim when started isn't 100% maximised and can be resized. Ideally > it should fill the whole window and can't be resized, the GTK version > functions this way. > Didn't we write code for resizing the gvim window to the size of the editor window ? > 2) It steals the focus from Eclipse. Even though its 'inside' and > 'part of' Eclipse, when you select the Vim instance, Eclipse > completely looses the focus, e.g The title bar becomes the deactivate > title bar. > oh, I never observed this. what method the mplayer guys are using for embedding ? -- Best Regards, Nageshwar M. |
From: David T. <dav...@gm...> - 2008-05-06 20:59:49
|
Hi Aaron, Great to hear from you, we would appreciate any help, there are quite a few of us now (4) but none of us have much time at all so progress is quite slow. Talking to us first before changing the Wiki is great, we haven't discussed a policy for editing but given the low rate of change I think we would all be happy to allow you and others to edit away in good faith and any issues that arise we will contact you or revert the changes. Regards, David On 5/6/08, Aaron H. <aa...@ho...> wrote: > Hello, > > My name is Aaron Hachez. I'm an avid Vim user, and a production Eclipse user. > > I'm looking forward to the future of vimplugin, and would like to help > if my time permits, (we'll see) > > Is there any protocol for editing the wiki? I'd like to update the > installation docs specifically with regard to the windows setup. It > took me several tries and numerous hours to get up and running > properly under windows, and it's simple if you know what to do. > > Cheers, > Aaron > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > vimplugin-devel mailing list > vim...@li... > https://lists.sourceforge.net/lists/listinfo/vimplugin-devel > -- Best regards, David Terei |
From: David T. <dav...@gm...> - 2008-05-06 20:56:39
|
Hey Sebastian, > I plan to make a change in the design: > > In VimConnection there is this one: > > //TODO simplify this long method? > private void addListeners() { ... > > I propose to make a named class for each listener. This will be easier > to read and extend. > > Any objections? > No, I think this is a great decision in fact it was something I had in my todolist as well :). Best regards, David Terei |
From: David T. <dav...@gm...> - 2008-05-06 20:53:46
|
I think that should cover it. The other large problem at the moment is windows support for embedding. Nageshwar submitted a patch which has been added to Vim a while ago (although not yet in a released version) but it has some problems compared to the GTK version. 1) Vim when started isn't 100% maximised and can be resized. Ideally it should fill the whole window and can't be resized, the GTK version functions this way. 2) It steals the focus from Eclipse. Even though its 'inside' and 'part of' Eclipse, when you select the Vim instance, Eclipse completely looses the focus, e.g The title bar becomes the deactivate title bar. I think the problem is we are using the SetParent win32 function which is meant more for MDI apps which isn't exactly what we want. When I was looking at some code of how other applications do this (mplayer is a good example) they seemed to retrieve the window they wanted to embed in and use that as the root window to paint to... not sure if that makes sense, if not ill try to explain it better. Anyway, I think that's a big issue which we need to solve since WIN32 support at the moment with embedding is pretty horrible, no offence to Nageshwar intended. We might also be able to fix up the current method through just changing some window properties (e.g disable resizing) but I'm worried about the focus issue, perhaps we can fix that in the current method but I suspect it perhaps requires a different method of embedding or changes elsewhere in the Win32 GUI code for Vim. Also, I have been since the start of this year (and will be until mid July ) travelling so I don't have any time to work on the project but hope to be able to once I'm back home. Oh and yes for a current release it sounds great, there are probably some more stability issues which need to be solved but the current code is a definite improvement so might as well get it out. Best regards, David On 5/6/08, Sebastian Menge <seb...@un...> wrote: > Hi vimpluginners > > Am Wed, 30 Apr 2008 19:41:33 +0200 > schrieb Martin Krischik <kri...@us...>: > > > > I made a few Windows related fixes and they tested ok. Only I can't > > manage to create a new deployment :-(. Could any of you pick up where > > I left? > > > I made 0.3.3 from the current trunk and pushed it to the update-site. > > Please try it on your platforms (64bit-systems, Windows, Linuxes, > different eclipse-versions etc.) and report here. > > Martin, it seems you are the only one working regularly on vimplugin. > Great :-) But I found some files in the trunk that contain your local > stuff: > http://vimplugin.svn.sourceforge.net/viewvc/vimplugin?view=rev&revision=203 > E.g. paths like C:\Work\... or programs like "ncftpput" and "7za" wont > be available on any other system than yours. > > In general I would appreciate to discuss things before committing. Or, > at least, report afterwards (like im doing now ...). > > 4,6 or 8 eyes will see more flaws than 2 :-) That way we can keep > better quality. Please be careful to commit only really good stuff. > > Nageshwar asked to collect current issues. As far as I can see it's only > the "howto get it under windows" (bugid: 1938885) and "64bit"-issue > (which i had myself ...) > > Both seem to be fixed now. Also the bug "blank tabs" by edyfox could be > closed if the embedding under Windows works. > > What other issues are there currently ? Any showstoppers? > > best wishes, Sebastian. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > vimplugin-devel mailing list > vim...@li... > https://lists.sourceforge.net/lists/listinfo/vimplugin-devel > |
From: Aaron H. <aa...@ho...> - 2008-05-06 18:09:36
|
Hello, My name is Aaron Hachez. I'm an avid Vim user, and a production Eclipse user. I'm looking forward to the future of vimplugin, and would like to help if my time permits, (we'll see) Is there any protocol for editing the wiki? I'd like to update the installation docs specifically with regard to the windows setup. It took me several tries and numerous hours to get up and running properly under windows, and it's simple if you know what to do. Cheers, Aaron |
From: Nageshwar <nag...@st...> - 2008-05-06 16:49:13
|
Hi, On Tue, May 6, 2008 at 4:36 PM, Sebastian Menge <seb...@un...> wrote: > Hi > > I plan to make a change in the design: > > In VimConnection there is this one: > > //TODO simplify this long method? > private void addListeners() { ... > > I propose to make a named class for each listener. This will be easier > to read and extend. > Good idea.. and please take care about the names of the listener classes. It is also good if we have a abstract base listener class. All the implemented listener class should implement compulsory methods for example run() which takes the mesgs and processes. > Any objections? > No I have an issue with the current vimplugin. What I observed is, our plugin response is very low. we should improve it at this point. Otherwise, users will shift back to the eclipse editor. For now, I dont have eclipse installed on my system.. I'll start my contribution in a week :) -- Thanks, Nageshwar M. |
From: Sebastian M. <seb...@un...> - 2008-05-06 15:35:53
|
Hi I plan to make a change in the design: In VimConnection there is this one: //TODO simplify this long method? private void addListeners() { ... I propose to make a named class for each listener. This will be easier to read and extend. Any objections? Seb. |
From: Sebastian M. <seb...@un...> - 2008-05-06 15:10:41
|
Hi vimpluginners Am Wed, 30 Apr 2008 19:41:33 +0200 schrieb Martin Krischik <kri...@us...>: > I made a few Windows related fixes and they tested ok. Only I can't > manage to create a new deployment :-(. Could any of you pick up where > I left? I made 0.3.3 from the current trunk and pushed it to the update-site. Please try it on your platforms (64bit-systems, Windows, Linuxes, different eclipse-versions etc.) and report here. Martin, it seems you are the only one working regularly on vimplugin. Great :-) But I found some files in the trunk that contain your local stuff: http://vimplugin.svn.sourceforge.net/viewvc/vimplugin?view=rev&revision=203 E.g. paths like C:\Work\... or programs like "ncftpput" and "7za" wont be available on any other system than yours. In general I would appreciate to discuss things before committing. Or, at least, report afterwards (like im doing now ...). 4,6 or 8 eyes will see more flaws than 2 :-) That way we can keep better quality. Please be careful to commit only really good stuff. Nageshwar asked to collect current issues. As far as I can see it's only the "howto get it under windows" (bugid: 1938885) and "64bit"-issue (which i had myself ...) Both seem to be fixed now. Also the bug "blank tabs" by edyfox could be closed if the embedding under Windows works. What other issues are there currently ? Any showstoppers? best wishes, Sebastian. |
From: Nageshwar <nag...@st...> - 2008-05-06 10:01:17
|
Hi guys, First lets dig out all the problems with the current vimplugin.. Previously we got some mails reporting some errors and bugs. Lets find out solutions for them. On Tue, May 6, 2008 at 10:52 AM, Sebastian Menge <seb...@un...> wrote: > Am Mon, 5 May 2008 14:42:45 -0700 > schrieb mooseydoom <moo...@gm...>: > > > > > I patched vimplugin so it works on my fedora core 8 (64 bit) system. > > The WidHandler wasn't returning the right window id. Also set the > > window id to be a long instead of an int and added a sleep while the > > editor is waiting to connect to the vim server. See my forum post > > for more info: http://sourceforge.net/forum/message.php?msg_id=4941569 > > Patch works fine, fixes same problems under my Ubuntu 64bit .. > > Ill commit it ASAP, and make a "release" next weekend. > > Are there other things to be done for a new version? > > Regards, Sebastian. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > vimplugin-devel mailing list > vim...@li... > https://lists.sourceforge.net/lists/listinfo/vimplugin-devel > -- Thanks, Nageshwar M. |
From: Sebastian M. <seb...@un...> - 2008-05-06 09:51:59
|
Am Mon, 5 May 2008 14:42:45 -0700 schrieb mooseydoom <moo...@gm...>: > I patched vimplugin so it works on my fedora core 8 (64 bit) system. > The WidHandler wasn't returning the right window id. Also set the > window id to be a long instead of an int and added a sleep while the > editor is waiting to connect to the vim server. See my forum post > for more info: http://sourceforge.net/forum/message.php?msg_id=4941569 Patch works fine, fixes same problems under my Ubuntu 64bit .. Ill commit it ASAP, and make a "release" next weekend. Are there other things to be done for a new version? Regards, Sebastian. |