Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Platform » [ANN] Fileopen plugin 0.0.1
[ANN] Fileopen plugin 0.0.1 [message #71173] Wed, 11 June 2003 16:52 Go to next message
Eclipse UserFriend
Originally posted by: ed.burnette.REMOVE.THIS.sas.com

Based on an idea by Matthew Conway, this plugin provides support for editing
files outside the Eclipse workspace. You can get it from:

http://www.eclipsepowered.org

Using the Fileopen plugin you can:

- Drag files from the windows explorer/desktop onto Eclipse to open them
- Use the File > Open menu to select any file to edit
- Cause Eclipse to open a file from outside the Workbench, for example
by double-clicking on a Java file from the Windows Explorer.

To open files from outside the Workbench run the eclipseclient program,
which
is a separate download from the plugin zip file. The syntax is:

java -jar eclipseclient.jar [-p port] [[+line] filename] ...

This works by sending a message to Eclipse causing it to open the file(s).
See the README file for details and limitations.

I've tested it under Eclipse 2.1 on Windows, but there is no host specific
code so it should work ok on other platforms.

Fileopen works without using links; it creates a new editor input and loads
the file much like editing source in jar files and CVS repositories work.

Covered by CPL; all source code provided.

--
Ed Burnette, co-author Eclipse in Action (www.manning.com/gallardo)
Re: [ANN] Fileopen plugin 0.0.1 [message #71855 is a reply to message #71173] Thu, 12 June 2003 00:42 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: muelleimer.usenet.katzien.de

* Ed Burnette <ed.burnette@REMOVE.THIS.sas.com> wrote:
> I've tested it under Eclipse 2.1 on Windows, but there is no host specific
> code so it should work ok on other platforms.

I've just tested it under debian KDE3.1 and it works fine. I've yet
to try the 'client'...

Only thing is, that it seems that you forgot to package the
properties file. So only the '%names' show...

Maybe you can do some internal stuff to provide the syntax
coloring for java files without disabling the editing capabilities?

Great Plugin!

Jan
Re: [ANN] Fileopen plugin 0.0.1/0.0.2 [message #73015 is a reply to message #71855] Fri, 13 June 2003 02:14 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: ed.burnette.REMOVE.THIS.sas.com

"Jan Schulz" <muelleimer@usenet.katzien.de> wrote in message
news:slrnbefj39.u5q.muelleimer@snoopy.katzien.de...
> Only thing is, that it seems that you forgot to package the
> properties file. So only the '%names' show...

Ooops, I've uploaded an update to correct that (0.0.2). I forgot to include
"plugin.properties" in my build.properties file. It worked ok in the
Run-Time Workbench but not in a real install.

> Maybe you can do some internal stuff to provide the syntax
> coloring for java files without disabling the editing capabilities?

I'm open to suggestions. It looks to me like the only real fix would be to
have IStorage have a setContents method and have StorageDocumentProvider use
it.

One thing I forgot in the readme - I set up keyboard shortcuts for opening a
file as follows:

Ctrl-O - open file (regular mode)
Ctrl-X Ctrl-F - open file (emacs mode)
Re: [ANN] Fileopen plugin 0.0.1 [message #73822 is a reply to message #71173] Fri, 13 June 2003 15:49 Go to previous messageGo to next message
Colin Sampaleanu is currently offline Colin SampaleanuFriend
Messages: 22
Registered: July 2009
Junior Member
I was only able to see the File|Open menu by closing the perspective
(Java or Resource) and reopening it. Just installing the plugin did not
make the menu item available, nor using a 'Reset Perspective' action. In
fact, one of my customized Java perspective, which I have even reset
back to default, I can not get the Open menu item to show in even after
closing it and reopening it. Can you think of any particular reason this
is going on?

Also, I see a
!MESSAGE Unable to find Action Set: filedrag.OpenActionSet
Unable to find Action Set: filedrag.OpenActionSet
error in the console when I try to open the perspective.

Note that I did have the previous 'filedrag' plugin in use before
fileopen, but took it out before adding in fileopen.

Regards,
Colin



Ed Burnette wrote:
> Based on an idea by Matthew Conway, this plugin provides support for editing
> files outside the Eclipse workspace. You can get it from:
>
> http://www.eclipsepowered.org
>
> Using the Fileopen plugin you can:
>
> - Drag files from the windows explorer/desktop onto Eclipse to open them
> - Use the File > Open menu to select any file to edit
> - Cause Eclipse to open a file from outside the Workbench, for example
> by double-clicking on a Java file from the Windows Explorer.
>
> To open files from outside the Workbench run the eclipseclient program,
> which
> is a separate download from the plugin zip file. The syntax is:
>
> java -jar eclipseclient.jar [-p port] [[+line] filename] ...
>
> This works by sending a message to Eclipse causing it to open the file(s).
> See the README file for details and limitations.
>
> I've tested it under Eclipse 2.1 on Windows, but there is no host specific
> code so it should work ok on other platforms.
>
> Fileopen works without using links; it creates a new editor input and loads
> the file much like editing source in jar files and CVS repositories work.
>
> Covered by CPL; all source code provided.
>
> --
> Ed Burnette, co-author Eclipse in Action (www.manning.com/gallardo)
>
>
>
Re: [ANN] Fileopen plugin 0.0.1/0.0.3 [message #74342 is a reply to message #73822] Sat, 14 June 2003 02:19 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: ed.burnette.REMOVE.THIS.sas.com

"Colin Sampaleanu" <colinml1@exis.com> wrote in message
news:bccrr4$igg$1@rogue.oti.com...
> I was only able to see the File|Open menu by closing the perspective
> (Java or Resource) and reopening it. Just installing the plugin did not
> make the menu item available, nor using a 'Reset Perspective' action.

That's a good idea. I've put out version 0.0.3 that should make this the
default for the most common perspectives (Resource, Java, etc.). A reset
should make it show up. Also I noticed that the Java editor was defining
Ctrl-O to mean Outline, so I defined Alt-O for File Open. You can customize
these of course.

Download at the same place: http://www.eclipsepowered.org

> In fact, one of my customized Java perspective, which I have even reset
> back to default, I can not get the Open menu item to show in even after
> closing it and reopening it.

For existing custom perspectives you'll have to add it yourself (Window >
Customize > Other > File Open Actions). For new custom perspectives they
should inherit the actions from the one you're customizing.

> Also, I see a
> !MESSAGE Unable to find Action Set: filedrag.OpenActionSet
> Unable to find Action Set: filedrag.OpenActionSet
> error in the console when I try to open the perspective.
>
> Note that I did have the previous 'filedrag' plugin in use before
> fileopen, but took it out before adding in fileopen.

References to the uninstalled action set must still be hanging around in
your metadata. When this has happened to me, the messages went away on their
own next time I started Eclipse. If they don't, it might be worth an Eclipse
bug report.

--Ed
Re: [ANN] Fileopen plugin 0.0.1/0.0.2 [message #74430 is a reply to message #73015] Sat, 14 June 2003 09:46 Go to previous message
Eclipse UserFriend
Originally posted by: muelleimer.usenet.katzien.de

* Ed Burnette <ed.burnette@REMOVE.THIS.sas.com> wrote:
>> Maybe you can do some internal stuff to provide the syntax
>> coloring for java files without disabling the editing capabilities?
> I'm open to suggestions. It looks to me like the only real fix would be to
> have IStorage have a setContents method and have StorageDocumentProvider use
> it.

Don'T know. I've once done some thingies with syntax highlighting and
IIRC, you had to add some scanners to the IDocument (or whatever...).
Maybe you can do the same (-> add the JDT Scaners to your document)...
For 2.1 crude hacks should be ok, as this should be adressed
properly in 3.0 :)

Jan
Previous Topic:Ant problem in M1
Next Topic:my own EditorInput
Goto Forum:
  


Current Time: Sat Oct 19 17:50:49 GMT 2024

Powered by FUDForum. Page generated in 0.03328 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top