Re: [orion-dev] beginner questions about plugins

[Susan Franklin McCourt <susan_franklin@xxxxxxxxxx>]

Hi, Philippe.
As Mark mentioned, you have to craft your own URL using coding.html for now.
If you want to play with writing a simple plug-in to do this, you can register a "fileCommands" extension that will concatenate coding.html + the selected navigator file. That will give you the orion editor on any file types you want.

The URL would appear in the menu in the actions column rather than work directly from the file link, but it will get you going.
For an example of this, see /static/plugins/sampleFileCommands.html.

Look at the command called "Open HTML Raw".
You could instead define the run method to do something like

return "coding.html#" + item.Location;

And you could change the file types to work with whatever files you want.

susan



Mark MacDonald ---05/10/2011 10:21:58 AM---Hi Philippe, At the moment, the Orion navigator only knows how to open a limited,

From: Mark MacDonald <Mark_MacDonald@xxxxxxxxxx>
To: Orion developer discussions <orion-dev@xxxxxxxxxxx>
Date: 05/10/2011 10:21 AM
Subject: Re: [orion-dev] beginner questions about plugins
Sent by: orion-dev-bounces@xxxxxxxxxxx

---

Hi Philippe,

At the moment, the Orion navigator only knows how to open a limited, hard-coded set of file types. We need to add support for registering additional file types (see [1] ).
As a temporary workaround, you can craft a URL that takes you to an editor for a file. In your case it might look something like:

http://localhost:8080/coding.html#http://localhost:8080/A/mysource/somefile.cst

(You can get the part after the # by finding the .cst file you want to edit in the navigator, and copying its URL.)

Re: having to reinstall the plugin -- the list of plugins you've installed is kept in your browser's localStorage, which shouldn't be affected by a server restart.
Here are a few things I can think of that *would* require you to reinstall your plugin:

- Your cookies were cleared at some point (doing this can also wipe your localStorage)
- You're accessing your server via a different port, hostname, or scheme (causing the browser to treat it as a different site for localStorage purposes)

Regards,
Mark

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=345291

Philippe Marschall ---05/06/2011 03:18:16 PM---2011/5/6 Richard Backhouse <backhous@xxxxxxxxxx> >

From: Philippe Marschall <philippe.marschall@xxxxxxxxx>
To: Orion developer discussions <orion-dev@xxxxxxxxxxx>
Date: 05/06/2011 03:18 PM
Subject: Re: [orion-dev] beginner questions about plugins
Sent by: orion-dev-bounces@xxxxxxxxxxx

---

2011/5/6 Richard Backhouse <backhous@xxxxxxxxxx>
>
> tunnel.html is part of the OpenAjax packaging and is also required along with OpenAjaxManagedHub-all.js.

Ah, the problem was that I was on OpenAjax 2.0.7 with doesn't have the
file, in this version it's called rpc_relay.html. Reverting back to
2.0.2 fixed the problem.

Now I have a new problem however. When I try to edit a file instead of
the editor I get a download window or a plain file. Do I additionally
need to register the editor besides the styler or do I have to add a
mime mapping or something similar? You can see the source code at [1]
and the plugin is deployed at [2].

Another problem I have is that whenever I restart the Orion server I
have to reinstall the plugin. Is this known or did I something wrong?

[1] http://svn.codespot.com/a/eclipselabs.org/coral-syntax/trunk/orion-coral/src/main/webapp/
[2] http://orion-coral.appspot.com/

Cheers
Philippe
_______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orion-dev
_______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orion-dev