Interested in contribution to : Finalize ODMA Content Provider into production quality

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Interested in contribution to : Finalize ODMA Content Provider into production quality

sireesha sarma
This post was updated on .
CONTENTS DELETED
The author has deleted this message.
Reply | Threaded
Open this post in threaded view
|

RE: Interested in contribution to : Finalize ODMA Content Provider into production quality

Dennis E. Hamilton
 Hello Sireesha,

I have not reviewed the ODMA Content Provider recently but some related work
(on a Java client library for ODMA access) has confirmed problems with
attempting to integrate ODMA via a UCB content provider:

 * ODMA does not offer a container model, so it is difficult to provide ODMA
access as if there is a directory or folder with managed documents in it.

 * ODMA works (the sweet spot, we say) by allowing the DMS integration to
provide modal dialogs against the application's GUI window, providing
operational integration into the dialog usage of the application.  The UCB
Provider has a difficult time of this, needing to pass the correct windows
handle to the ODMA Connection Manager at the beginning of a session with
ODMA.  I'm not sure it can ever work via UCB and the Content Provider model.

This leaves me mystified that the ODMA Content Provider works at all (and I
have not been able to operate it successfully, but that was some time ago).

Meanwhile, I have discovered that the OO.o 2.3 Novell Edition does attempt
conventional ODMA integration, the kind that is typical of other desktop
applications, is expected by users of ODMA-aware applications, and is not
via the UCB content-provider mechanism.  There are some glitches in the
Novell implementation and my attention is providing test cases and bug
reports for that support of ODMA back to the developer.

Unfortunately, I have not found any place where there is visibility on the
development tree for the Novell editions, but reports, CVS/SVN, etc.  I am
still looking.  All of the links and information in those builds points to
OO.o. but of course the Novell editions are not exclusively based on the
current OO.o 2.3 code base, so there is no help there for problems with the
Novell additions.  I'm not in a position to sort that out.  I am still
searching.

 - Dennis

Dennis E. Hamilton
------------------
AIIM DMware Technical Coordinator
mailto:[hidden email] | gsm:+1-206.779.9430
http://DMware.info http://ODMA.info/ http://TROSTing.org 


-----Original Message-----
From: Sireesha Sarma [mailto:[hidden email]]
Sent: Tuesday, January 22, 2008 11:28
To: [hidden email]; [hidden email]
Subject: [ucb-dev] Interested in contribution to : Finalize ODMA Content
Provider into production quality

Hello,

I am sireesha, with 7 years of experience in C++ programming. I am
interested in contributing to the above mentioned module. Please let me know
how to proceed further.

thanks and regards,

--
- Sireesha Sarma.
http://treasureofthoughts.googlepages.com
****************************************************************************
******************
I would very much love to change the world but I don't have the source code.
:)
****************************************************************************
******************


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Interested in contribution to : Finalize ODMA Content Provider into production quality

Kai Sommerfeld
In reply to this post by sireesha sarma
Hi all,

  AFAIK Novell uses a modified/enhanced version of the original ODMA
Content Provider for OpenOffice.org Novell Edition.

=> http://www.openoffice.org/issues/show_bug.cgi?id=32741

  As you can read there, we're very interested in getting Novell's
patches into OOo main trunk.

- Kai.

On 01/23/2008 07:59 PM, Dennis E. Hamilton wrote:

>  Hello Sireesha,
>
> I have not reviewed the ODMA Content Provider recently but some related work
> (on a Java client library for ODMA access) has confirmed problems with
> attempting to integrate ODMA via a UCB content provider:
>
>  * ODMA does not offer a container model, so it is difficult to provide ODMA
> access as if there is a directory or folder with managed documents in it.
>
>  * ODMA works (the sweet spot, we say) by allowing the DMS integration to
> provide modal dialogs against the application's GUI window, providing
> operational integration into the dialog usage of the application.  The UCB
> Provider has a difficult time of this, needing to pass the correct windows
> handle to the ODMA Connection Manager at the beginning of a session with
> ODMA.  I'm not sure it can ever work via UCB and the Content Provider model.
>
> This leaves me mystified that the ODMA Content Provider works at all (and I
> have not been able to operate it successfully, but that was some time ago).
>
> Meanwhile, I have discovered that the OO.o 2.3 Novell Edition does attempt
> conventional ODMA integration, the kind that is typical of other desktop
> applications, is expected by users of ODMA-aware applications, and is not
> via the UCB content-provider mechanism.  There are some glitches in the
> Novell implementation and my attention is providing test cases and bug
> reports for that support of ODMA back to the developer.
>
> Unfortunately, I have not found any place where there is visibility on the
> development tree for the Novell editions, but reports, CVS/SVN, etc.  I am
> still looking.  All of the links and information in those builds points to
> OO.o. but of course the Novell editions are not exclusively based on the
> current OO.o 2.3 code base, so there is no help there for problems with the
> Novell additions.  I'm not in a position to sort that out.  I am still
> searching.
>
>  - Dennis
>
> Dennis E. Hamilton
> ------------------
> AIIM DMware Technical Coordinator
> mailto:[hidden email] | gsm:+1-206.779.9430
> http://DMware.info http://ODMA.info/ http://TROSTing.org 
>
>
> -----Original Message-----
> From: Sireesha Sarma [mailto:[hidden email]]
> Sent: Tuesday, January 22, 2008 11:28
> To: [hidden email]; [hidden email]
> Subject: [ucb-dev] Interested in contribution to : Finalize ODMA Content
> Provider into production quality
>
> Hello,
>
> I am sireesha, with 7 years of experience in C++ programming. I am
> interested in contributing to the above mentioned module. Please let me know
> how to proceed further.
>
> thanks and regards,
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: Interested in contribution to : Finalize ODMA Content Provider into production quality

Dennis E. Hamilton
The way that the OO.o 2.3 Novell edition behaves, I am not so sure they are
still following that approach, posted in 2004.  I will do some tests to see
if I can confirm that.

I agree that getting the ODMA support into the OO.o code base would be a
good thing, whichever way it is done.  I'll follow up here when I have more
definitive information.

 - Dennis

PS: I have also discovered that, assuming that the dialog box case can be
dealt with on those platforms, there may be a tidy way to move the ODMA
integration model to Unix (Linux, Solaris, etc.), thanks to a nice binary
COM-porting device that I found in the Java JNI libraries!  Wouldn't that be
a hoot.

Dennis E. Hamilton
------------------
AIIM DMware Technical Coordinator
mailto:[hidden email] | gsm:+1-206.779.9430
http://DMware.info http://ODMA.info/ http://TROSTing.org 
 

-----Original Message-----
From: [hidden email] [mailto:[hidden email]]
Sent: Thursday, January 24, 2008 06:29
To: [hidden email]
Subject: Re: [ucb-dev] Interested in contribution to : Finalize ODMA Content
Provider into production quality

Hi all,

  AFAIK Novell uses a modified/enhanced version of the original ODMA
Content Provider for OpenOffice.org Novell Edition.

=> http://www.openoffice.org/issues/show_bug.cgi?id=32741

  As you can read there, we're very interested in getting Novell's
patches into OOo main trunk.

- Kai.

On 01/23/2008 07:59 PM, Dennis E. Hamilton wrote:
>  Hello Sireesha,
>
> I have not reviewed the ODMA Content Provider recently but some related
work
> (on a Java client library for ODMA access) has confirmed problems with
> attempting to integrate ODMA via a UCB content provider:
>
>  * ODMA does not offer a container model, so it is difficult to provide
ODMA
> access as if there is a directory or folder with managed documents in it.
>
>  * ODMA works (the sweet spot, we say) by allowing the DMS integration to
> provide modal dialogs against the application's GUI window, providing
> operational integration into the dialog usage of the application.  The UCB
> Provider has a difficult time of this, needing to pass the correct windows
> handle to the ODMA Connection Manager at the beginning of a session with
> ODMA.  I'm not sure it can ever work via UCB and the Content Provider
model.
>
> This leaves me mystified that the ODMA Content Provider works at all (and
I
> have not been able to operate it successfully, but that was some time
ago).

>
> Meanwhile, I have discovered that the OO.o 2.3 Novell Edition does attempt
> conventional ODMA integration, the kind that is typical of other desktop
> applications, is expected by users of ODMA-aware applications, and is not
> via the UCB content-provider mechanism.  There are some glitches in the
> Novell implementation and my attention is providing test cases and bug
> reports for that support of ODMA back to the developer.
>
> Unfortunately, I have not found any place where there is visibility on the
> development tree for the Novell editions, but reports, CVS/SVN, etc.  I am
> still looking.  All of the links and information in those builds points to
> OO.o. but of course the Novell editions are not exclusively based on the
> current OO.o 2.3 code base, so there is no help there for problems with
the

> Novell additions.  I'm not in a position to sort that out.  I am still
> searching.
>
>  - Dennis
>
> Dennis E. Hamilton
> ------------------
> AIIM DMware Technical Coordinator
> mailto:[hidden email] | gsm:+1-206.779.9430
> http://DMware.info http://ODMA.info/ http://TROSTing.org 
>
>
> -----Original Message-----
> From: Sireesha Sarma [mailto:[hidden email]]
> Sent: Tuesday, January 22, 2008 11:28
> To: [hidden email]; [hidden email]
> Subject: [ucb-dev] Interested in contribution to : Finalize ODMA Content
> Provider into production quality
>
> Hello,
>
> I am sireesha, with 7 years of experience in C++ programming. I am
> interested in contributing to the above mentioned module. Please let me
know
> how to proceed further.
>
> thanks and regards,
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Interested in contribution to : Finalize ODMA Content Provider into production quality

Kai Sommerfeld
In reply to this post by sireesha sarma
Dennis,

On 01/24/2008 06:22 PM, Dennis E. Hamilton wrote:
> The way that the OO.o 2.3 Novell edition behaves, I am not so sure they are
> still following that approach, posted in 2004.  I will do some tests to see
> if I can confirm that.

  2004? Look at the date of the latest comment from tml:

<quote>
  ------ Additional comments from tml Sun Apr 15 15:10:45 +0000 2007 -------

We (Novell) use a fairly extensive patch to the ODMA UCP and also add an
ODMA
file picker. Feel free to have a view at
http://svn.gnome.org/viewcvs/ooo-build/trunk/patches/src680/novell-win32-odma.diff?view=log

There are still some rough edges and known buggy corner case behaviour.
Maybe we
should defer upstreaming this until the known problems have been fixed.
There
are also some gratuitous spacing/formatting changes that I probably
should revert...
</quote>

- Kai.

>
> I agree that getting the ODMA support into the OO.o code base would be a
> good thing, whichever way it is done.  I'll follow up here when I have more
> definitive information.
>
>  - Dennis
>
> PS: I have also discovered that, assuming that the dialog box case can be
> dealt with on those platforms, there may be a tidy way to move the ODMA
> integration model to Unix (Linux, Solaris, etc.), thanks to a nice binary
> COM-porting device that I found in the Java JNI libraries!  Wouldn't that be
> a hoot.
>
> Dennis E. Hamilton
> ------------------
> AIIM DMware Technical Coordinator
> mailto:[hidden email] | gsm:+1-206.779.9430
> http://DMware.info http://ODMA.info/ http://TROSTing.org 
>  
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]]
> Sent: Thursday, January 24, 2008 06:29
> To: [hidden email]
> Subject: Re: [ucb-dev] Interested in contribution to : Finalize ODMA Content
> Provider into production quality
>
> Hi all,
>
>   AFAIK Novell uses a modified/enhanced version of the original ODMA
> Content Provider for OpenOffice.org Novell Edition.
>
> => http://www.openoffice.org/issues/show_bug.cgi?id=32741
>
>   As you can read there, we're very interested in getting Novell's
> patches into OOo main trunk.
>
> - Kai.
>
> On 01/23/2008 07:59 PM, Dennis E. Hamilton wrote:
>>  Hello Sireesha,
>>
>> I have not reviewed the ODMA Content Provider recently but some related
> work
>> (on a Java client library for ODMA access) has confirmed problems with
>> attempting to integrate ODMA via a UCB content provider:
>>
>>  * ODMA does not offer a container model, so it is difficult to provide
> ODMA
>> access as if there is a directory or folder with managed documents in it.
>>
>>  * ODMA works (the sweet spot, we say) by allowing the DMS integration to
>> provide modal dialogs against the application's GUI window, providing
>> operational integration into the dialog usage of the application.  The UCB
>> Provider has a difficult time of this, needing to pass the correct windows
>> handle to the ODMA Connection Manager at the beginning of a session with
>> ODMA.  I'm not sure it can ever work via UCB and the Content Provider
> model.
>> This leaves me mystified that the ODMA Content Provider works at all (and
> I
>> have not been able to operate it successfully, but that was some time
> ago).
>> Meanwhile, I have discovered that the OO.o 2.3 Novell Edition does attempt
>> conventional ODMA integration, the kind that is typical of other desktop
>> applications, is expected by users of ODMA-aware applications, and is not
>> via the UCB content-provider mechanism.  There are some glitches in the
>> Novell implementation and my attention is providing test cases and bug
>> reports for that support of ODMA back to the developer.
>>
>> Unfortunately, I have not found any place where there is visibility on the
>> development tree for the Novell editions, but reports, CVS/SVN, etc.  I am
>> still looking.  All of the links and information in those builds points to
>> OO.o. but of course the Novell editions are not exclusively based on the
>> current OO.o 2.3 code base, so there is no help there for problems with
> the
>> Novell additions.  I'm not in a position to sort that out.  I am still
>> searching.
>>
>>  - Dennis
>>
>> Dennis E. Hamilton
>> ------------------
>> AIIM DMware Technical Coordinator
>> mailto:[hidden email] | gsm:+1-206.779.9430
>> http://DMware.info http://ODMA.info/ http://TROSTing.org 
>>
>>
>> -----Original Message-----
>> From: Sireesha Sarma [mailto:[hidden email]]
>> Sent: Tuesday, January 22, 2008 11:28
>> To: [hidden email]; [hidden email]
>> Subject: [ucb-dev] Interested in contribution to : Finalize ODMA Content
>> Provider into production quality
>>
>> Hello,
>>
>> I am sireesha, with 7 years of experience in C++ programming. I am
>> interested in contributing to the above mentioned module. Please let me
> know
>> how to proceed further.
>>
>> thanks and regards,
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: Interested in contribution to : Finalize ODMA Content Provider into production quality

Dennis E. Hamilton
You're absolutely right!  I missed that.  Very important and useful.

That now explains something I noticed in running ODMA logs with OO.o
2.3Novell.  I will see that Tor gets my test results.

It looks like Shireesha should communicate with Tor, now that we know where
he keeps his development tree [;<).

 - Dennis

Dennis E. Hamilton
------------------
AIIM DMware Technical Coordinator
mailto:[hidden email] | gsm:+1-206.779.9430
http://DMware.info http://ODMA.info/ http://TROSTing.org 


-----Original Message-----
From: [hidden email] [mailto:[hidden email]]
Sent: Friday, January 25, 2008 00:29
To: [hidden email]
Subject: Re: [ucb-dev] Interested in contribution to : Finalize ODMA Content
Provider into production quality

Dennis,

On 01/24/2008 06:22 PM, Dennis E. Hamilton wrote:
> The way that the OO.o 2.3 Novell edition behaves, I am not so sure they
are
> still following that approach, posted in 2004.  I will do some tests to
see
> if I can confirm that.

  2004? Look at the date of the latest comment from tml:

<quote>
  ------ Additional comments from tml Sun Apr 15 15:10:45 +0000 2007 -------

We (Novell) use a fairly extensive patch to the ODMA UCP and also add an
ODMA
file picker. Feel free to have a view at
http://svn.gnome.org/viewcvs/ooo-build/trunk/patches/src680/novell-win32-odm
a.diff?view=log

There are still some rough edges and known buggy corner case behaviour.
Maybe we
should defer upstreaming this until the known problems have been fixed.
There
are also some gratuitous spacing/formatting changes that I probably
should revert...
</quote>

- Kai.
>
> I agree that getting the ODMA support into the OO.o code base would be a
> good thing, whichever way it is done.  I'll follow up here when I have
more
> definitive information.
>
>  - Dennis
>
> PS: I have also discovered that, assuming that the dialog box case can be
> dealt with on those platforms, there may be a tidy way to move the ODMA
> integration model to Unix (Linux, Solaris, etc.), thanks to a nice binary
> COM-porting device that I found in the Java JNI libraries!  Wouldn't that
be

> a hoot.
>
> Dennis E. Hamilton
> ------------------
> AIIM DMware Technical Coordinator
> mailto:[hidden email] | gsm:+1-206.779.9430
> http://DMware.info http://ODMA.info/ http://TROSTing.org 
>  
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]]
> Sent: Thursday, January 24, 2008 06:29
> To: [hidden email]
> Subject: Re: [ucb-dev] Interested in contribution to : Finalize ODMA
Content

> Provider into production quality
>
> Hi all,
>
>   AFAIK Novell uses a modified/enhanced version of the original ODMA
> Content Provider for OpenOffice.org Novell Edition.
>
> => http://www.openoffice.org/issues/show_bug.cgi?id=32741
>
>   As you can read there, we're very interested in getting Novell's
> patches into OOo main trunk.
>
> - Kai.
>
> On 01/23/2008 07:59 PM, Dennis E. Hamilton wrote:
>>  Hello Sireesha,
>>
>> I have not reviewed the ODMA Content Provider recently but some related
> work
>> (on a Java client library for ODMA access) has confirmed problems with
>> attempting to integrate ODMA via a UCB content provider:
>>
>>  * ODMA does not offer a container model, so it is difficult to provide
> ODMA
>> access as if there is a directory or folder with managed documents in it.
>>
>>  * ODMA works (the sweet spot, we say) by allowing the DMS integration to
>> provide modal dialogs against the application's GUI window, providing
>> operational integration into the dialog usage of the application.  The
UCB
>> Provider has a difficult time of this, needing to pass the correct
windows
>> handle to the ODMA Connection Manager at the beginning of a session with
>> ODMA.  I'm not sure it can ever work via UCB and the Content Provider
> model.
>> This leaves me mystified that the ODMA Content Provider works at all (and
> I
>> have not been able to operate it successfully, but that was some time
> ago).
>> Meanwhile, I have discovered that the OO.o 2.3 Novell Edition does
attempt
>> conventional ODMA integration, the kind that is typical of other desktop
>> applications, is expected by users of ODMA-aware applications, and is not
>> via the UCB content-provider mechanism.  There are some glitches in the
>> Novell implementation and my attention is providing test cases and bug
>> reports for that support of ODMA back to the developer.
>>
>> Unfortunately, I have not found any place where there is visibility on
the
>> development tree for the Novell editions, but reports, CVS/SVN, etc.  I
am
>> still looking.  All of the links and information in those builds points
to

>> OO.o. but of course the Novell editions are not exclusively based on the
>> current OO.o 2.3 code base, so there is no help there for problems with
> the
>> Novell additions.  I'm not in a position to sort that out.  I am still
>> searching.
>>
>>  - Dennis
>>
>> Dennis E. Hamilton
>> ------------------
>> AIIM DMware Technical Coordinator
>> mailto:[hidden email] | gsm:+1-206.779.9430
>> http://DMware.info http://ODMA.info/ http://TROSTing.org 
>>
>>
>> -----Original Message-----
>> From: Sireesha Sarma [mailto:[hidden email]]
>> Sent: Tuesday, January 22, 2008 11:28
>> To: [hidden email]; [hidden email]
>> Subject: [ucb-dev] Interested in contribution to : Finalize ODMA Content
>> Provider into production quality
>>
>> Hello,
>>
>> I am sireesha, with 7 years of experience in C++ programming. I am
>> interested in contributing to the above mentioned module. Please let me
> know
>> how to proceed further.
>>
>> thanks and regards,
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]