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: 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...@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: 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: 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 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: 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: 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-12 19:07:30
|
Am Sat, 10 May 2008 23:07:51 -0700 schrieb "Eric Van Dewoestine" <erv...@gm...>: > Please give the latest version a shot and report any issues to me. I checked out eclim and formic, but there is still so much missing. Do I really have to install all php, pydev, wst plugins for eclipse? What additional settings do I need? BTW: Is the project meant to be built from eclipse? Or do you use eclim yourself ? I'm not really interested in building eclim as is, I just want to try it out, perhaps make some modifications to make it "headful" for example, or reduce it to a minimal feature-set to test out interaction with vimplugin... Isn't there any developer documentation? Perhaps you could give a very short outline of the internal architecture. Here is what I have figured out from the sources: 1.) eclimd is a headless eclipse that manages a minimal set of (eclipse)-plugins residing in src/eclipse/plugins. The plugins have no plugin.xml and seem to have no classes. 2.) I can talk to eclimd with vim or "eclim". ":PingEclim" is the same as "eclim -command ping" "eclim" is just the class org.eclim.command.Main which calls implementations of the java interface org.eclim.command.Command. 3.) These commands (magically) can perform eclipse actions like CodeCompletion. Is this because both applications (eclimd and eclim) live in the same JVM? Best regards, Sebastian. |
From: Nageshwar <nag...@st...> - 2008-05-12 19:20:20
|
Hi, I think making vimplugin to use eclim is not that good idea, or atleast following the way eclim implemented the things. Their case is different, they have to implement each and every eclipse functionality inside vim. Eclim people implemented the code for code completion [abstractcompletioncommand.java i guess] and some other commands. they also have vim scripts for displaying the data. We can just simply use the code of the commands those we want implement. I'm trying to implement code completion part by taking the code from the above mentioned file. Correct me, if I'm wrong or if you people have some other ideas. On Mon, May 12, 2008 at 8:08 PM, Sebastian Menge <seb...@un...> wrote: > Am Sat, 10 May 2008 23:07:51 -0700 > schrieb "Eric Van Dewoestine" <erv...@gm...>: > > > > Please give the latest version a shot and report any issues to me. > > I checked out eclim and formic, but there is still so much missing. > Do I really have to install all php, pydev, wst plugins for eclipse? > What additional settings do I need? > > BTW: Is the project meant to be built from eclipse? Or do you use eclim > yourself ? > > I'm not really interested in building eclim as is, I just want to try it > out, perhaps make some modifications to make it "headful" for example, > or reduce it to a minimal feature-set to test out interaction with > vimplugin... > > Isn't there any developer documentation? > > Perhaps you could give a very short outline of the internal > architecture. Here is what I have figured out from the sources: > > 1.) eclimd is a headless eclipse that manages a minimal set of > (eclipse)-plugins residing in src/eclipse/plugins. The plugins have no > plugin.xml and seem to have no classes. > > 2.) I can talk to eclimd with vim or "eclim". > ":PingEclim" is the same as "eclim -command ping" > "eclim" is just the class org.eclim.command.Main which calls > implementations of the java interface org.eclim.command.Command. > > 3.) These commands (magically) can perform eclipse actions like > CodeCompletion. Is this because both applications (eclimd and eclim) > live in the same JVM? > > Best regards, Sebastian. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > > _______________________________________________ > vimplugin-devel mailing list > vim...@li... > https://lists.sourceforge.net/lists/listinfo/vimplugin-devel > -- Best Regards, Nageshwar M. |
From: Eric V. D. <erv...@gm...> - 2008-05-12 20:24:20
|
> > Please give the latest version a shot and report any issues to me. > > I checked out eclim and formic, but there is still so much missing. You don't need formic. That is only used to create an installer, which is for your purposes is unnecessary. > Do I really have to install all php, pydev, wst plugins for eclipse? No, as my first message in this thread noted, you can simply run: $ ant -Dplugins=ant,jdt to only build the specified plugins (ant and jdt in this case). > What additional settings do I need? The only setting you need is one which specifies where your eclipse install is located so that the build can deploy the plugins. If you try running ant and that setting is not found, then you will get an informative message indicating how to set it... like so: $ ant Buildfile: build.xml [echo] [echo] ${eclipse.home} not set. [echo] Please set via system arg (ant -Declipse.home=...) or [echo] via environment variable (export ECLIM_ECLIPSE_HOME="..."). [echo] BUILD FAILED eclim/build.xml:43: missing required property (see above) Total time: 0 seconds So, if my eclipse home is at /opt/eclipse then I would run: ant -Declipse.home=/opt/eclipse or for a windows example ant -Declipse.home="C:/Program Files/eclipse" > BTW: Is the project meant to be built from eclipse? Or do you use eclim > yourself ? I never use eclispe directly. Eclim was meant to be built via its ant build file. > Isn't there any developer documentation? Aside from the javadocs, not yet. > Perhaps you could give a very short outline of the internal > architecture. Here is what I have figured out from the sources: > > 1.) eclimd is a headless eclipse that manages a minimal set of > (eclipse)-plugins residing in src/eclipse/plugins. More or less, yes. > The plugins have no plugin.xml and seem to have no classes. The only true eclipse plugin is org.eclim, and as such, it is the only one that has a plugin.xml. The others are essentially just osgi bundles loaded by org.eclim. The actual java source files are located under src/java. > 2.) I can talk to eclimd with vim or "eclim". > ":PingEclim" is the same as "eclim -command ping" > "eclim" is just the class org.eclim.command.Main which calls > implementations of the java interface org.eclim.command.Command. Correct > 3.) These commands (magically) can perform eclipse actions like > CodeCompletion. Is this because both applications (eclimd and eclim) > live in the same JVM? I suppose the "magic" you are missing is performed by nailgun (http://www.martiansoftware.com/nailgun/), which allows you to invoke a main class running in another jvm using their command line client (written in c). I'll try to find some time to put together a more comprehensive document outlining eclim's design. Up until now it just hasn't been a high priority. -- eric |