Return-Path: <tiff-bounces@remotesensing.org>
Received: from inmx012.isp.belgacom.be (inmx012.isp.belgacom.be [195.238.3.90])
        by mailst034.isp.belgacom.be (8.12.11/8.12.11/Skynet-MAILSTORE-2.14) with ESMTP id i8GIOwg6027173
        for <joris.at.lebbeke@skynet.be>; Thu, 16 Sep 2004 20:25:02 +0200
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from xserve.flids.com (adsl-065-083-169-202.sip.mco.bellsouth.net [65.83.169.202])
        by inmx012.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-2.32) with ESMTP id i8GIOh0V029980
        for <joris.at.lebbeke@skynet.be>; Thu, 16 Sep 2004 20:24:46 +0200
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from adsl-065-083-169-202.sip.mco.bellsouth.net (localhost [127.0.0.1])
	by xserve.flids.com (Postfix) with ESMTP
	id 2EDC02F046E; Thu, 16 Sep 2004 14:24:26 -0400 (EDT)
X-Original-To: tiff@remotesensing.org
Delivered-To: tiff@remotesensing.org
Received: from scooby.simplesystems.org (scooby.simplesystems.org
	[65.66.246.67])
	by xserve.flids.com (Postfix) with ESMTP id BB83D2F044A
	for <tiff@remotesensing.org>; Thu, 16 Sep 2004 14:24:23 -0400 (EDT)
Received: from blade.simplesystems.org (blade.simplesystems.org [65.66.246.74])
	by scooby.simplesystems.org (8.12.10+Sun/8.12.10) with ESMTP id
	i8GIGq9p014933; Thu, 16 Sep 2004 13:16:52 -0500 (CDT)
Date: Thu, 16 Sep 2004 13:16:52 -0500 (CDT)
From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
X-X-Sender: bfriesen@blade.simplesystems.org
To: "Kabongo, Kalonji (DET)" <KKabongo@detma.org>
Subject: RE: [Tiff] libtiff and .net
In-Reply-To: <C929616FF578D21197B000A0C9D1BF74050967E9@det-exch-01.det.root.detma.org>
Message-ID: <Pine.SOC.4.60.0409161310170.15634@blade.simplesystems.org>
References: <C929616FF578D21197B000A0C9D1BF74050967E9@det-exch-01.det.root.detma.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: "'tiff@remotesensing.org'" <tiff@remotesensing.org>
X-BeenThere: tiff@remotesensing.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: TIFF and libtiff discussion  <tiff.remotesensing.org>
List-Unsubscribe: <http://xserve.flids.com/mailman/listinfo/tiff>,
	<mailto:tiff-request@remotesensing.org?subject=unsubscribe>
List-Archive: <http://xserve.flids.com/pipermail/tiff>
List-Post: <mailto:tiff@remotesensing.org>
List-Help: <mailto:tiff-request@remotesensing.org?subject=help>
List-Subscribe: <http://xserve.flids.com/mailman/listinfo/tiff>,
	<mailto:tiff-request@remotesensing.org?subject=subscribe>
Sender: tiff-bounces@remotesensing.org
Errors-To: tiff-bounces@remotesensing.org
X-UIDL: b0e61ac6c5a52d1e9a32f855c23607bc

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: RE: [Tiff] libtiff and .net
>
> 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
>> ======================================
>> Bob Friesenhahn
>> bfriesen@simple.dallas.tx.us
>> http://www.simplesystems.org/users/bfriesen
>>
>
> ======================================
> Bob Friesenhahn
> bfriesen@simple.dallas.tx.us
> http://www.simplesystems.org/users/bfriesen
> _______________________________________________
> Tiff mailing list
> Tiff@remotesensing.org
> http://xserve.flids.com/mailman/listinfo/tiff
>
>
>

======================================
Bob Friesenhahn
bfriesen@simple.dallas.tx.us
http://www.simplesystems.org/users/bfriesen
_______________________________________________
Tiff mailing list
Tiff@remotesensing.org
http://xserve.flids.com/mailman/listinfo/tiff
