Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Eclipse Communications Framework (ECF) » File Types Natively Supported for Shared Editing
File Types Natively Supported for Shared Editing [message #624717] Wed, 08 April 2009 02:13 Go to next message
Rick Faircloth is currently offline Rick FairclothFriend
Messages: 8
Registered: July 2009
Junior Member
Hi, all...

I've been trying to get shared-editing working for ColdFusion files (.cfm
and .cfc), but have been confronted with only being able to open shared
files in "read-only" mode.

I've successfully shared .java and .txt files, but nothing else.

I've read about modifying the docshare plugin.xml file to enable other
editors, in my case I'm interested in CFEclipse, but was recently told by
a user that he was able to share .cfm and .cfc files with a friend without
modification of any plugin files.

Can I get an update on this and perhaps some guidance?

Thanks!

Rick
Re: File Types Natively Supported for Shared Editing [message #624718 is a reply to message #624717] Wed, 08 April 2009 04:44 Go to previous messageGo to next message
Chris Aniszczyk is currently offline Chris AniszczykFriend
Messages: 674
Registered: July 2009
Senior Member
Rick Faircloth wrote:
> Hi, all...
>
> I've been trying to get shared-editing working for ColdFusion files
> (.cfm and .cfc), but have been confronted with only being able to open
> shared files in "read-only" mode.
>
> I've successfully shared .java and .txt files, but nothing else.
>
> I've read about modifying the docshare plugin.xml file to enable other
> editors, in my case I'm interested in CFEclipse, but was recently told
> by a user that he was able to share .cfm and .cfc files with a friend
> without modification of any plugin files.
>
> Can I get an update on this and perhaps some guidance?

http://wiki.eclipse.org/Extending_Real-Time_Shared_Editing_f or_Use_with_Other_Editors

Does that help a bit?

Cheers,

Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk
Re: File Types Natively Supported for Shared Editing [message #624719 is a reply to message #624718] Wed, 08 April 2009 12:39 Go to previous messageGo to next message
Rick Faircloth is currently offline Rick FairclothFriend
Messages: 8
Registered: July 2009
Junior Member
Chris Aniszczyk wrote:

> Rick Faircloth wrote:
>> Hi, all...
>>
>> I've been trying to get shared-editing working for ColdFusion files
>> (.cfm and .cfc), but have been confronted with only being able to open
>> shared files in "read-only" mode.
>>
>> I've successfully shared .java and .txt files, but nothing else.
>>
>> I've read about modifying the docshare plugin.xml file to enable other
>> editors, in my case I'm interested in CFEclipse, but was recently told
>> by a user that he was able to share .cfm and .cfc files with a friend
>> without modification of any plugin files.
>>
>> Can I get an update on this and perhaps some guidance?

>
http://wiki.eclipse.org/Extending_Real-Time_Shared_Editing_f or_Use_with_Other_Editors

> Does that help a bit?

> Cheers,

> Chris Aniszczyk

Hi, Chris and thanks for the reply..

Yes, that does help, but I had read that previously and started down that
path of modifying the appropriate files (until I couldn't find all the
info I needed) when I talked with another user of Eclipse and CFEclipse
and he stated that with more recent version of Eclipse and CFEclipse that
he didn't have to do any file modifications...that CFEclipse was able to
perform shared-editing when installed.

So this has led to some confusion. I updated my CFEclipse plug-in to the
same version he has and we tried shared-editing last night, but we
couldn't get it to work with .cfm or .cfc files between our systems. It
would only work with .java and .txt files, which is consistent with the
info found at the site your referenced in your reply.

Just a little confused and trying to sort things out. Didn't know if that
info on the wiki was the latest and greatest or not.

So, as far as you know, the docshare plugin.xml file does have to be
edited to accommodate file types other than .java and .cfm at this point?

Thanks, again...

Rick
Re: File Types Natively Supported for Shared Editing [message #624720 is a reply to message #624719] Wed, 08 April 2009 17:44 Go to previous messageGo to next message
Scott Lewis is currently offline Scott LewisFriend
Messages: 1038
Registered: July 2009
Senior Member
Hi Rick,

Rick Faircloth wrote:
<stuff deleted>
>> Chris Aniszczyk
>
> Hi, Chris and thanks for the reply..
>
> Yes, that does help, but I had read that previously and started down
> that path of modifying the appropriate files (until I couldn't find all
> the info I needed) when I talked with another user of Eclipse and
> CFEclipse and he stated that with more recent version of Eclipse and
> CFEclipse that he didn't have to do any file modifications...that
> CFEclipse was able to perform shared-editing when installed.
>
> So this has led to some confusion. I updated my CFEclipse plug-in to
> the same version he has and we tried shared-editing last night, but we
> couldn't get it to work with .cfm or .cfc files between our systems. It
> would only work with .java and .txt files, which is consistent with the
> info found at the site your referenced in your reply.
>
> Just a little confused and trying to sort things out. Didn't know if
> that info on the wiki was the latest and greatest or not.
>
> So, as far as you know, the docshare plugin.xml file does have to be
> edited to accommodate file types other than .java and .cfm at this point?


No, it's only necessary to introduce *some" plugin.xml that uses/refers
to the appropriate context ids (as described in

http://wiki.eclipse.org/Extending_Real-Time_Shared_Editing_f or_Use_with_Other_Editors

So you can/could introduce your own plugin (with potentially no code,
but with plugin.xml markup) that would introduce markup something like this:

<extension point="org.eclipse.ui.menus">
<menuContribution
locationURI="popup:org.eclipse.php.core.phpsource.source.EditorContext ">
<dynamic
class=" org.eclipse.ecf.internal.provisional.docshare.menu.DocShareR osterMenuContributionItem "
id="com.foo.MyEditorContextID.dynamic1">
</dynamic>
</menuContribution>
</extension>

(this is for the php editor...so your locationURI will be different).

Note also that your plugin will need to have a dependency on the ECF
org.eclipse.ecf.docshare plugin, in order to be able to find the class
referenced in the markup (i.e.
class=org.eclipse.ecf.internal.provisional.docshare.menu.Doc ShareRosterMenuContributionItem).

Finally, note that with the ECF 3.0 stream (to be released with Galileo)
this package/class name has changed to

org.eclipse.ecf.docshare.menu.DocShareRosterMenuContribution Item

We haven't yet updated the wiki page with this package name
change...basically because ECF 3.0 hasn't been released yet.

Please let us know how we can help further. I would be very interested
in seeing the cold fusion editors supported.

Thanks,

Scott
Re: File Types Natively Supported for Shared Editing [message #624721 is a reply to message #624720] Wed, 08 April 2009 19:32 Go to previous messageGo to next message
Rick Faircloth is currently offline Rick FairclothFriend
Messages: 8
Registered: July 2009
Junior Member
Scott Lewis wrote:

> Hi Rick,

> No, it's only necessary to introduce *some" plugin.xml that uses/refers
> to the appropriate context ids (as described in
> http://wiki.eclipse.org/Extending_Real-
> Time_Shared_Editing_for_Use_with_Other_Editors

Yes, I saw the instructions about creating my own plugin, and did tinker
around with that, but I wasn't clear on what the purpose of creating my
own would be. But I see below that there just has to be a plugin
*somewhere* (how about in the CFEclipse plugin.xml?) with the correct
markup to enable CFEclipse to perform shared-editing.

> (this is for the php editor...so your locationURI will be different).

One of my main questions is what would be the "locationURI" for CFEclipse?
I don't know where to get that info or how it's derived. Clues? Is this
a reference to a path in the program folders in the installation location?

> Note also that your plugin will need to have a dependency on the ECF
> org.eclipse.ecf.docshare plugin, in order to be able to find the class
> referenced in the markup (i.e.
>
class=org.eclipse.ecf.internal.provisional.docshare.menu.Doc ShareRosterMenuContributionItem).

Ok...and since I'm still using ECF 2.1, then I need to use the above class
above, right?

Here's something I just found while looking through the code of the
plug-in, org.cfeclipse.cfml > plugin.xml, near the bottom of the xml ode
on the page:

<extension point="org.eclipse.ui.menus">
<menuContribution locationURI="popup:#CFMLEditorContext">
<dynamic class="org.eclipse.ecf.internal.provisional.docshare.menu.
DocShareRosterMenuContributionItem"
id="org.cfeclipse.cfml.cfmleditorcontext.DocShare1">
</dynamic>
</menuContribution>
</extension>

That would seem to me to be exactly what is needed to make shared-editing
work with Eclipse...is that right? Does there need to be something else
in another place to make sharing .cfm and .cfc, etc., work with
shared-editing?

Now, when attempting shared-editing with the CFEclipse view and editing a
cfm file, the menu item "Share Editor with" is already in the menu. It's
just that any file with a CF extension (.cfm, .cfc) when shared, results
in "You are about to open a read-only file. Do you want to continue?" or
something similar. If I continue, I get the file with content, but it's
not editable. If I click the button "Make writable", I get a blank
document.

It seems I'm soooo close to making this happen, but I just can't quite
figure out what's missing.

Suggestions? Clues?

Thanks for all your help!

Rick
Re: File Types Natively Supported for Shared Editing [message #624768 is a reply to message #624721] Mon, 13 April 2009 16:31 Go to previous messageGo to next message
Rick Faircloth is currently offline Rick FairclothFriend
Messages: 8
Registered: July 2009
Junior Member
Rick Faircloth wrote:

Hi, Scott, et al...

Just wondering if you had any perspective on my comments below...

Thanks,

Rick

> Scott Lewis wrote:

>> Hi Rick,

>> No, it's only necessary to introduce *some" plugin.xml that uses/refers
>> to the appropriate context ids (as described in
>> http://wiki.eclipse.org/Extending_Real-
>> Time_Shared_Editing_for_Use_with_Other_Editors

Yes, I saw the instructions about creating my own plugin, and did tinker
around with that, but I wasn't clear on what the purpose of creating my
own would be. But I see below that there just has to be a plugin
*somewhere* (how about in the CFEclipse plugin.xml?) with the correct
markup to enable CFEclipse to perform shared-editing.

>> (this is for the php editor...so your locationURI will be different).

One of my main questions is what would be the "locationURI" for CFEclipse?
I don't know where to get that info or how it's derived. Clues? Is this
a reference to a path in the program folders in the installation location?

>> Note also that your plugin will need to have a dependency on the ECF
>> org.eclipse.ecf.docshare plugin, in order to be able to find the class
>> referenced in the markup (i.e.
>> Class=org.eclipse.ecf.internal.provisional.docshare.menu.Doc ShareRosterMenuContributionItem).

Ok...and since I'm still using ECF 2.1, then I need to use the above class
above, right?

Here's something I just found while looking through the code of the
plug-in, org.cfeclipse.cfml > plugin.xml, near the bottom of the xml ode
on the page:

<extension point="org.eclipse.ui.menus">
<menuContribution locationURI="popup:#CFMLEditorContext">
<dynamic class="org.eclipse.ecf.internal.provisional.docshare.menu.
DocShareRosterMenuContributionItem"
id="org.cfeclipse.cfml.cfmleditorcontext.DocShare1">
</dynamic>
</menuContribution>
</extension>

That would seem to me to be exactly what is needed to make shared-editing
work with Eclipse...is that right? Does there need to be something else
in another place to make sharing .cfm and .cfc, etc., work with
shared-editing?

Now, when attempting shared-editing with the CFEclipse view and editing a
cfm file, the menu item "Share Editor with" is already in the menu. It's
just that any file with a CF extension (.cfm, .cfc) when shared, results
in "You are about to open a read-only file. Do you want to continue?" or
something similar. If I continue, I get the file with content, but it's
not editable. If I click the button "Make writable", I get a blank
document.

It seems I'm soooo close to making this happen, but I just can't quite
figure out what's missing.

Suggestions? Clues?

Thanks for all your help!

Rick
Re: File Types Natively Supported for Shared Editing [message #624771 is a reply to message #624768] Tue, 14 April 2009 21:16 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: marc.esher.comcast.net

I wanted to bump this up and more fully describe what's happening:

The "Share Editor With..." context menu does indeed appear in the CFEclipse
editor, using the menucontribution Rick described.

Two different "bad" things then occur:

1) immediately after sharing the editor with another user, a popup appears
saying "User has stopped sharing".

or

2) the file opens, gives the Read-only prompt that Rick mentioned, and then
even when selecting "OK" to make not read only, the file appears but is
empty.

I did get ColdFusion files sharing successfully with another person, but the
problem Rick and I had when sharing were consistently duplicatable. My
problem is that I don't know how to debug these things. Is there a way to
dig into this to find out why files would show up as read-only and empty? or
to find out why connections magically get dropped?

This was over XMPP with gtalk, for what it's worth.

Thanks for taking the time to help us out, Scott and Chris.

Marc



"Rick Faircloth" <Rick@WhiteStoneMedia.com> wrote in message
news:19ba5616471c35f099fa350d080577d8$1@www.eclipse.org...
> Rick Faircloth wrote:
>
> Hi, Scott, et al...
>
> Just wondering if you had any perspective on my comments below...
>
> Thanks,
>
> Rick
>
>> Scott Lewis wrote:
>
>>> Hi Rick,
>
>>> No, it's only necessary to introduce *some" plugin.xml that uses/refers
>>> to the appropriate context ids (as described in
>>> http://wiki.eclipse.org/Extending_Real-
>>> Time_Shared_Editing_for_Use_with_Other_Editors
>
> Yes, I saw the instructions about creating my own plugin, and did tinker
> around with that, but I wasn't clear on what the purpose of creating my
> own would be. But I see below that there just has to be a plugin
> *somewhere* (how about in the CFEclipse plugin.xml?) with the correct
> markup to enable CFEclipse to perform shared-editing.
>
>>> (this is for the php editor...so your locationURI will be different).
>
> One of my main questions is what would be the "locationURI" for CFEclipse?
> I don't know where to get that info or how it's derived. Clues? Is this
> a reference to a path in the program folders in the installation location?
>
>>> Note also that your plugin will need to have a dependency on the ECF
>>> org.eclipse.ecf.docshare plugin, in order to be able to find the class
>>> referenced in the markup (i.e.
>>> Class=org.eclipse.ecf.internal.provisional.docshare.menu.Doc ShareRosterMenuContributionItem).
>
> Ok...and since I'm still using ECF 2.1, then I need to use the above class
> above, right?
>
> Here's something I just found while looking through the code of the
> plug-in, org.cfeclipse.cfml > plugin.xml, near the bottom of the xml ode
> on the page:
>
> <extension point="org.eclipse.ui.menus">
> <menuContribution locationURI="popup:#CFMLEditorContext">
> <dynamic class="org.eclipse.ecf.internal.provisional.docshare.menu.
> DocShareRosterMenuContributionItem"
> id="org.cfeclipse.cfml.cfmleditorcontext.DocShare1">
> </dynamic>
> </menuContribution>
> </extension>
>
> That would seem to me to be exactly what is needed to make shared-editing
> work with Eclipse...is that right? Does there need to be something else
> in another place to make sharing .cfm and .cfc, etc., work with
> shared-editing?
>
> Now, when attempting shared-editing with the CFEclipse view and editing a
> cfm file, the menu item "Share Editor with" is already in the menu. It's
> just that any file with a CF extension (.cfm, .cfc) when shared, results
> in "You are about to open a read-only file. Do you want to continue?" or
> something similar. If I continue, I get the file with content, but it's
> not editable. If I click the button "Make writable", I get a blank
> document.
>
> It seems I'm soooo close to making this happen, but I just can't quite
> figure out what's missing.
>
> Suggestions? Clues?
>
> Thanks for all your help!
>
> Rick
>
>
Re: File Types Natively Supported for Shared Editing [message #624775 is a reply to message #624768] Thu, 16 April 2009 03:08 Go to previous messageGo to next message
Scott Lewis is currently offline Scott LewisFriend
Messages: 1038
Registered: July 2009
Senior Member
Hi Rick,

Rick Faircloth wrote:
> Rick Faircloth wrote:
>
> Hi, Scott, et al...
>
> Just wondering if you had any perspective on my comments below...
>
> Thanks,
>
> Rick
>
>> Scott Lewis wrote:
>
>>> Hi Rick,
>
>>> No, it's only necessary to introduce *some" plugin.xml that
>>> uses/refers to the appropriate context ids (as described in
>>> http://wiki.eclipse.org/Extending_Real-
>>> Time_Shared_Editing_for_Use_with_Other_Editors
>
> Yes, I saw the instructions about creating my own plugin, and did tinker
> around with that, but I wasn't clear on what the purpose of creating my
> own would be. But I see below that there just has to be a plugin
> *somewhere* (how about in the CFEclipse plugin.xml?) with the correct
> markup to enable CFEclipse to perform shared-editing.

Right.

>
>>> (this is for the php editor...so your locationURI will be different).
>
> One of my main questions is what would be the "locationURI" for CFEclipse?
> I don't know where to get that info or how it's derived. Clues? Is
> this a reference to a path in the program folders in the installation
> location?

Here's the java one for example:

locationURI="popup:#CompilationUnitEditorContext"

The relevant/important part of this is the
#CompilationUnitEditorContext. This is the editor's menu contribution
identifier. The easiest way to get this identifier is to use the
Plugin-Spy...by selecting the given editor and choosing Alt-Shift-F1.
The context menu identifier is under the heading:

The active menu contribution identifiers:

>
>>> Note also that your plugin will need to have a dependency on the ECF
>>> org.eclipse.ecf.docshare plugin, in order to be able to find the
>>> class referenced in the markup (i.e.
>>> Class=org.eclipse.ecf.internal.provisional.docshare.menu.Doc ShareRosterMenuContributionItem).
>>>
>
> Ok...and since I'm still using ECF 2.1, then I need to use the above
> class above, right?
>
> Here's something I just found while looking through the code of the
> plug-in, org.cfeclipse.cfml > plugin.xml, near the bottom of the xml ode
> on the page:
>
> <extension point="org.eclipse.ui.menus">
> <menuContribution locationURI="popup:#CFMLEditorContext">
> <dynamic class="org.eclipse.ecf.internal.provisional.docshare.menu.
> DocShareRosterMenuContributionItem"
> id="org.cfeclipse.cfml.cfmleditorcontext.DocShare1">
> </dynamic>
> </menuContribution>
> </extension>
>
> That would seem to me to be exactly what is needed to make
> shared-editing work with Eclipse...is that right? Does there need to be
> something else in another place to make sharing .cfm and .cfc, etc.,
> work with shared-editing?

This looks right...i.e. the #CFMSEditorContext looks right.

I think you are close...do let us know if there are further things we
can do. And once you get it going, I would appreciate it if you would
consider contributing the plugin.xml that you create...or making it
available on a wiki page...would that be ok?

Thanks,

Scott


>
> Now, when attempting shared-editing with the CFEclipse view and editing
> a cfm file, the menu item "Share Editor with" is already in the menu.
> It's just that any file with a CF extension (.cfm, .cfc) when shared,
> results in "You are about to open a read-only file. Do you want to
> continue?" or something similar. If I continue, I get the file with
> content, but it's not editable. If I click the button "Make writable",
> I get a blank document.
>
> It seems I'm soooo close to making this happen, but I just can't quite
> figure out what's missing.
>
> Suggestions? Clues?
>
> Thanks for all your help!
>
> Rick
>
>
Re: File Types Natively Supported for Shared Editing [message #624776 is a reply to message #624771] Thu, 16 April 2009 03:13 Go to previous messageGo to next message
Scott Lewis is currently offline Scott LewisFriend
Messages: 1038
Registered: July 2009
Senior Member
Hi Marc,

Marc E wrote:
> I wanted to bump this up and more fully describe what's happening:
>
> The "Share Editor With..." context menu does indeed appear in the
> CFEclipse editor, using the menucontribution Rick described.
>
> Two different "bad" things then occur:
>
> 1) immediately after sharing the editor with another user, a popup
> appears saying "User has stopped sharing".

This is unexpected (of course)...and I've not seen this in any tests.
Is it possible that you may be using both ECF 2.1 and 3.0 on one side or
the other? The reason I ask is that we've had to update the protocol
for 3.0, and they are not compatible with each other...which could
result in an immediate disconnect like you are seeing.

So first thing to check: what versions of Eclipse and ECF are you using
on both ends (i.e. the two clients).

>
> or
>
> 2) the file opens, gives the Read-only prompt that Rick mentioned, and
> then even when selecting "OK" to make not read only, the file appears
> but is empty.
>
> I did get ColdFusion files sharing successfully with another person, but
> the problem Rick and I had when sharing were consistently duplicatable.

This makes me think even more that it may be a client incompatibility
problem. Please do make sure that you and Rick have the same version of
ECF on both sides.


> My problem is that I don't know how to debug these things. Is there a
> way to dig into this to find out why files would show up as read-only
> and empty? or to find out why connections magically get dropped?

I don't think we had much tracing in 2.1, but we've since added a fair
amount of tracing to the 3.0 stream. So if you can it might be
worthwhile to move to the 3.0 stream. Then you could run in the Eclipse
debugger and turn tracing on (or set breakpoints, etc).

If you want help with this please let use know.

Scott
Re: File Types Natively Supported for Shared Editing [message #624779 is a reply to message #624776] Thu, 16 April 2009 09:54 Go to previous message
Eclipse UserFriend
Originally posted by: marc.esher.comcast.net

>
> This is unexpected (of course)...and I've not seen this in any tests. Is
> it possible that you may be using both ECF 2.1 and 3.0 on one side or the
> other? The reason I ask is that we've had to update the protocol for 3.0,
> and they are not compatible with each other...which could result in an
> immediate disconnect like you are seeing.
>
> So first thing to check: what versions of Eclipse and ECF are you using
> on both ends (i.e. the two clients).

I'm on ganymede 3.4.1, and the plugin registry's telling me I have
org.eclipse.ecf (2.0.0.v20080611-1715) (though I have the 2.1 sources).

I'll work more with rick and see if we can get our versions in sync and then
try it again.




>>
>> 2) the file opens, gives the Read-only prompt that Rick mentioned, and
>> then even when selecting "OK" to make not read only, the file appears but
>> is empty.
>>
>> I did get ColdFusion files sharing successfully with another person, but
>> the problem Rick and I had when sharing were consistently duplicatable.
>
> This makes me think even more that it may be a client incompatibility
> problem. Please do make sure that you and Rick have the same version of
> ECF on both sides.
>
>
>> My problem is that I don't know how to debug these things. Is there a way
>> to dig into this to find out why files would show up as read-only and
>> empty? or to find out why connections magically get dropped?
>
> I don't think we had much tracing in 2.1, but we've since added a fair
> amount of tracing to the 3.0 stream. So if you can it might be worthwhile
> to move to the 3.0 stream. Then you could run in the Eclipse debugger and
> turn tracing on (or set breakpoints, etc).
>
> If you want help with this please let use know.

Yup, that makes sense. I can try that and see if I make headway

thanks a lot, Scott. Marc

>
> Scott
Previous Topic:how to ask ECF is scheme is supported for file transfer
Next Topic:contributing ecf docshare from fragment
Goto Forum:
  


Current Time: Thu Mar 28 17:22:16 GMT 2024

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

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

Back to the top