cancel
Showing results for 
Search instead for 
Did you mean: 

make an RCP Eclipse based smart/rich client interface?

fcorneli
Champ in-the-making
Champ in-the-making
Hi, we are currently developing an RCP based client interface tothe Alfresco repository.
I somone else also doing this or interested?
4 REPLIES 4

rdanner
Champ in-the-making
Champ in-the-making
Hi, we are currently developing an RCP based client interface tothe Alfresco repository.
I somone else also doing this or interested?

Tell us more! What kind of interaction are you looking to support?  Similar to the webclient or something different?  Maybe you would consider starting a wiki page (http://wiki.alfresco.com/) and a forge project (http://forge.alfresco.com/)?

fcorneli
Champ in-the-making
Champ in-the-making
Hi, we are in the process of creating an alternative interface for the ALfresco repository based on the Eclispe RCP plaforms. WE will make available for the community, baded on the JCR-RMI protocol interface:
-a "shell" where all other plugins (PI's) can be added to (completed)
-a login plugin (PI) (completed)
-a treeview on the repository (completed)
-showing  & editing details, versions & history viewer
-an image viewer plugin for jpg, jpeg 200 ,analyze7.5 and DICOM image foramts, incling viewing/editing the specific metadata for this types
-a DICOM structured report editor
-a PI for generating Alfresco ACP files
-a category management PI
-etc…
We would make a plea to the community to add other/extra plugins too.
The first source code will be available within 4 weeks from now.
best regards, frans Cornelissen, Technology Office, Pharma R& IT, J&J

cszamudio
Champ on-the-rise
Champ on-the-rise
Hi. I'm currently integrating the ability to search the Alfresco repository from an Eclipse RCP application and I'm curious why you chose JCR-RMI over the Web Services interface.  I'm guessing is a software architecture issue, but perhaps you've experienced problems with the WS approach.  Thanks.

btorfs
Champ in-the-making
Champ in-the-making
Hi;
We chose jcr-rmi because the WS approach is very chatty, meaning it communicates a lot. We did not test using the WS so we do not know wether there are problems or not.