AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2004.09.16 17:04 "[Tiff] libtiff and .net", by Kabongo, Kalonji
2004.09.16 17:09 "Re: [Tiff] libtiff and .net", by Bob Friesenhahn
2004.09.16 17:23 "RE: [Tiff] libtiff and .net", by Kabongo, Kalonji
2004.09.16 17:35 "RE: [Tiff] libtiff and .net", by Bob Friesenhahn
2004.09.16 17:44 "RE: [Tiff] libtiff and .net", by Kabongo, Kalonji
2004.09.16 18:16 "RE: [Tiff] libtiff and .net", by Bob Friesenhahn
2004.09.16 17:59 "RE: [Tiff] libtiff and .net", by Bill Bither
2004.09.20 19:48 "RE: [Tiff] libtiff and .net", by Bob Friesenhahn
2004.09.22 03:52 "RE: [Tiff] libtiff and .net", by Bill Bither
2004.09.22 04:13 "RE: [Tiff] libtiff and .net", by Bob Friesenhahn

2004.09.16 18:16 "RE: [Tiff] libtiff and .net", by Bob Friesenhahn

On Thu, 16 Sep 2004, Kabongo, Kalonji (DET) wrote:

I would not mind doing it to expand my knowledge of .net, libtiff and tiff. If there are other people willing to collaborate on this, we can form a team and plan for it. I realize doing it alone could take a longtime.

Do you have any king of diagram that shows the program flow?

Nope. I suggest that the first step is to become familiar with the limitations of Managed C++, study the libtiff APIs, develop your object model, and then write the wrapper classes to expose selected libtiff APIs to .net. Some libtiff APIs will not be suitable for .net at all. Others will require marshalling code since unsafe code is not allowed to directly access data in managed objects.

Bob

Kalonji Kabongo

-----Original Message-----

From: Bob Friesenhahn [mailto:bfriesen@simple.dallas.tx.us]

Sent: Thursday, September 16, 2004 1:36 PM

To: Kabongo, Kalonji (DET)

Cc: 'tiff@remotesensing.org'

Subject: libtiff and .net RE: [Tiff]

On Thu, 16 Sep 2004, Kabongo, Kalonji (DET) wrote:

I mean make it object oriented, run entirely within the managed space, etc...

I think it is safe to say that there are currently no plans to do this.

A diligent volunteer could write a wrapper in Managed C++ to export the object-oriented interface to .net. Libtiff could be built in a stripped down form in which it does all I/O via the wrapper (no more use of memory mapped files, read/write, or stdio). Even after all of this work, the resulting .net Assembly would be marked "unsafe" since the code uses heap memory and pointers and therefore could accidentally overwrite something else in the .net environment.

Bob

-----Original Message-----

From: Bob Friesenhahn [mailto:bfriesen@simple.dallas.tx.us] Sent: Thursday, September 16, 2004 1:10 PM

To: Kabongo, Kalonji (DET)
Cc: 'tiff@remotesensing.org'
Subject: Re: [Tiff] libtiff and .net

On Thu, 16 Sep 2004, Kabongo, Kalonji (DET) wrote:

Are there plans to port the libtiff library to the .net platform?

What do you mean by porting to the .net platform?

It should already be possible to compile libtiff as .net "managed" MSIL code using Visual Studio .net. That doesn't mean that it will become platform independent though since libtiff uses native APIs.

======================================
Bob Friesenhahn
bfriesen@simple.dallas.tx.us
http://www.simplesystems.org/users/bfriesen