Home » Modeling » EMF » [CDO] CDO Explorer.
| [CDO] CDO Explorer. [message #493730] |
Tue, 27 October 2009 17:33  |
 Juan Pedro Silva
Messages: 258
Registered: July 2009 |
Senior Member |
|
|
Hi everybody.
I'm trying CDOExplorer to see which functionality it already provides.
I've checked it out of the CVS and using it in a runtime workbench. I'm
also using the
https://build.eclipse.org/hudson/view/Modeling/job/cbi-emf-n et4j-cdo-3.0/109/artifact/build/N200910161608/
build Eike recommended, and a MySQL DB.
The CDOExplorer appears among the plugins in the runtime. However, no
new views are added to the already available ones.
So, I would like to know, are there some hints on how to use CDO
Explorer?, or, if not, could someone provide some, please?.
Also, could someone make a quick comment on the current state of the CDO
Explorer and its short-term plan?.
Thanks again.
Regards,
Juan Pedro
|
|
|
| Re: [CDO] CDO Explorer. [message #493882 is a reply to message #493730] |
Wed, 28 October 2009 10:47  |
Victor Roldan Betancort
Messages: 524
Registered: July 2009 |
Senior Member |
|
|
Hi Juan,
it's been a while since Eike gathered some requirements for the CDO
Explorer effort. AFAIK, the aim was trying to build a CDO client Eclipse
RCP with a set of nice reusable assets as views, editors, etc, so users
could download it and start playing around with a great deal of CDO
features.
You can see some of our ideas at:
http://wiki.eclipse.org/CDO_Explorer_%28work_in_progress%29
So, from what I know, I only played once with that RCP, and it was just
prototype more focused how will it look like, I mean, a stub. Anyway,
Eike will probably know better about the state of the CDO Explorer effort.
Regarding the short term, we are more focused now on core runtime
polishing and some new features rather than UI features. You might some
of the requirements in the WIKI page for the CDO Explorer effort. Don't
hesitate proposing new features!
There are a few interesting features that we implemented and should have
been shipped in the 2.0 release, and that we developed as part of the
CDO Explorer effort. This first step was integrating CDO with the Common
Navigator Framework. The plugins involved in this feature are:
org.eclipse.emf.cdo.team
org.eclipse.emf.cdo.ui.ide
To use it, first check that you have the plugins I listed previously and
then:
1. Create an empty project
2. Right click -> Team -> Share -> CDO
3. Introduce the server description (for instance, "tcp://localhost")
and the repository name (for instance, "repo1"). You should have a CDO
Server turned on and ready before sharing anything.
Remember to use Project Explorer View, not Package Explorer View!
From here, you'll be able to explore the registered packages and
folders and resources in the server. You can create new resources,
delete them, expand their contents in the project explorer view itself.
If you have CDO example models, you could even create GMF diagram for a
model stored in a CDO repository!
Now the bad part: we haven't tested these features since 2.0 and it
seems something is not working properly. Apparently, it is related with
the FailOverStrategyInjector extension, I'll try to fix it ASAP.
HTH,
Víctor.
Juan Pedro Silva escribió:
> Hi everybody.
> I'm trying CDOExplorer to see which functionality it already provides.
> I've checked it out of the CVS and using it in a runtime workbench. I'm
> also using the
> https://build.eclipse.org/hudson/view/Modeling/job/cbi-emf-n et4j-cdo-3.0/109/artifact/build/N200910161608/
> build Eike recommended, and a MySQL DB.
> The CDOExplorer appears among the plugins in the runtime. However, no
> new views are added to the already available ones.
>
> So, I would like to know, are there some hints on how to use CDO
> Explorer?, or, if not, could someone provide some, please?.
> Also, could someone make a quick comment on the current state of the CDO
> Explorer and its short-term plan?.
> Thanks again.
> Regards,
> Juan Pedro
|
|
| | |
| Re: [CDO] CDO Explorer. [message #493952 is a reply to message #493923] |
Wed, 28 October 2009 15:21 |
Victor Roldan Betancort
Messages: 524
Registered: July 2009 |
Senior Member |
|
|
Juan Pedro,
>> I was particularly interested in the decorators for locked elements. Was
>> something done on that particular subject for the curent version?.
No, I believe there isn't anything related with decorators for locking.
There are some decorators, for instance, the color of the font changes
when a CDOObject transits to "CONFLICT" state. You idea seems
interesting, feel free to raise an enhancement request :)
>> Being able to see elements currently in use by other modelers is
>> interesting to us. Getting a warning when trying to edit a model element
>> currently locked by other would also be a great alternative.
If you take a look at the CDOLock API, there are some methods that seems
related with your needs:
/**
* Returns <code>true</code> if this lock is currently held by the
requesting {@link CDOView view}, <code>false</code>
* otherwise.
*/
public boolean isLocked();
/**
* Returns <code>true</code> if this lock is currently held by
another {@link CDOView view} (i.e. any view different
* from the requesting one), <code>false</code> otherwise.
*/
public boolean isLockedByOthers();
You might get a lock by using methods on CDOObject:
/**
* Returns the read lock associated with this object.
*
* @return Never <code>null</code>.
* @since 2.0
*/
public CDOLock cdoReadLock();
/**
* Returns the write lock associated with this object.
*
* @return Never <code>null</code>.
* @since 2.0
*/
public CDOLock cdoWriteLock();
However, I'm not sure if this is the best way to know whether an object
is locked or not. Simon knows more about the lock topic. I'll CC him.
HTH,
Víctor.
|
|
|
| Re: [CDO] CDO Explorer. [message #493962 is a reply to message #493952] |
Wed, 28 October 2009 15:29 |
Juan Pedro Silva
Messages: 258
Registered: July 2009 |
Senior Member |
|
|
Thanks Victor.
After my last post I found this bug on the subject:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=283274
It's recent (three months ago). I've just added myself to the cc, and I
see simon is on it to, perhaps he could comment on the current state.
I see they are looking for help, but right know I can't tell if I can
commit to it.
I'll take a look (any pointers/docs would be appreciatted).
Best regards,
Juan Pedro
Víctor Roldán Betancort escribió:
> Juan Pedro,
>
>>> I was particularly interested in the decorators for locked elements.
>>> Was something done on that particular subject for the curent version?.
>
> No, I believe there isn't anything related with decorators for
> locking. There are some decorators, for instance, the color of the
> font changes when a CDOObject transits to "CONFLICT" state. You idea
> seems interesting, feel free to raise an enhancement request :)
>
>>> Being able to see elements currently in use by other modelers is
>>> interesting to us. Getting a warning when trying to edit a model
>>> element currently locked by other would also be a great alternative.
>
> If you take a look at the CDOLock API, there are some methods that
> seems related with your needs:
>
> /**
> * Returns <code>true</code> if this lock is currently held by the
> requesting {@link CDOView view}, <code>false</code>
> * otherwise.
> */
> public boolean isLocked();
>
> /**
> * Returns <code>true</code> if this lock is currently held by
> another {@link CDOView view} (i.e. any view different
> * from the requesting one), <code>false</code> otherwise.
> */
> public boolean isLockedByOthers();
>
>
> You might get a lock by using methods on CDOObject:
>
> /**
> * Returns the read lock associated with this object.
> *
> * @return Never <code>null</code>.
> * @since 2.0
> */
> public CDOLock cdoReadLock();
>
> /**
> * Returns the write lock associated with this object.
> *
> * @return Never <code>null</code>.
> * @since 2.0
> */
> public CDOLock cdoWriteLock();
>
>
> However, I'm not sure if this is the best way to know whether an
> object is locked or not. Simon knows more about the lock topic. I'll
> CC him.
>
> HTH,
> Víctor.
|
|
|
| Re: [CDO] CDO Explorer. [message #494537 is a reply to message #493962] |
Sat, 31 October 2009 09:08 |
|
Hi Juan Pedro,
Thanks for your offer to help. I think it's not one of the most trivial
tasks to add new notifications to the core as they use to impact large
parts of the technology stack. But it can also be fun and therefore I'll
add some hints to https://bugs.eclipse.org/283274
Cheers
/Eike
----
http://thegordian.blogspot.com
http://twitter.com/eikestepper
Juan Pedro Silva schrieb:
> Thanks Victor.
> After my last post I found this bug on the subject:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=283274
>
> It's recent (three months ago). I've just added myself to the cc, and
> I see simon is on it to, perhaps he could comment on the current state.
> I see they are looking for help, but right know I can't tell if I can
> commit to it.
> I'll take a look (any pointers/docs would be appreciatted).
> Best regards,
> Juan Pedro
>
> Víctor Roldán Betancort escribió:
>> Juan Pedro,
>>
>>>> I was particularly interested in the decorators for locked
>>>> elements. Was something done on that particular subject for the
>>>> curent version?.
>>
>> No, I believe there isn't anything related with decorators for
>> locking. There are some decorators, for instance, the color of the
>> font changes when a CDOObject transits to "CONFLICT" state. You idea
>> seems interesting, feel free to raise an enhancement request :)
>>
>>>> Being able to see elements currently in use by other modelers is
>>>> interesting to us. Getting a warning when trying to edit a model
>>>> element currently locked by other would also be a great alternative.
>>
>> If you take a look at the CDOLock API, there are some methods that
>> seems related with your needs:
>>
>> /**
>> * Returns <code>true</code> if this lock is currently held by the
>> requesting {@link CDOView view}, <code>false</code>
>> * otherwise.
>> */
>> public boolean isLocked();
>>
>> /**
>> * Returns <code>true</code> if this lock is currently held by
>> another {@link CDOView view} (i.e. any view different
>> * from the requesting one), <code>false</code> otherwise.
>> */
>> public boolean isLockedByOthers();
>>
>>
>> You might get a lock by using methods on CDOObject:
>>
>> /**
>> * Returns the read lock associated with this object.
>> *
>> * @return Never <code>null</code>.
>> * @since 2.0
>> */
>> public CDOLock cdoReadLock();
>>
>> /**
>> * Returns the write lock associated with this object.
>> *
>> * @return Never <code>null</code>.
>> * @since 2.0
>> */
>> public CDOLock cdoWriteLock();
>>
>>
>> However, I'm not sure if this is the best way to know whether an
>> object is locked or not. Simon knows more about the lock topic. I'll
>> CC him.
>>
>> HTH,
>> Víctor.
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
Goto Forum:
Current Time: Thu Sep 26 12:27:34 GMT 2024
Powered by FUDForum. Page generated in 0.05547 seconds |
] 
Search
Help
Register
Login
Home
