Hi everyone,
 
I am operating in Windows2000 environment and I am using Microsoft Visual C++ to implement my application. At the moment I am trying to create an MFC GUI on top of the ARToolkit 2.52 (windows + Vision SDK version). I am trying to eliminate the use of GLUT so that the ARToolkit window will run inside the MFC application. Has anybody done somethething similar or knows where I can find some resources? Thank you.
 
Best Regards,
 
Fotis Liarokapis
__________________________________
Fotis Liarokapis - Research Officer
Centre for VLSI and Computer Graphics,
School of Engineering and Information Technology, 
University of Sussex, Stage II, Room 4B4.
Brighton, Falmer, BN1 9QT.
Work Site : http://www.arco-web.org/
Research Site : http://www.sussex.ac.uk/Users/tapi8/index
e-mail: F.Liarokapis@s ...........
tel:  +44 (0)1273 606755 ext 2556
fax: +44 (0)1273 690816

Hi Fotis,
 
I am very interested into doing something similar, i.e. reduce dependencies of the different parts of the code in order to increase flexibility. This could be achieved by isolating the different functions of the ARToolKit (camera calibraiton, frame grabber, image processing, tracking results, 3D drawing etc.). It seems that newer verisons of the toolkit are starting to get cleaner, but unfortunately, the whole library is still just raw uncommented C code.
 
I would definitely like join forces with anyone else trying to modularize the ARToolKit. I am particularly interested in removing the Glut layer (but plan to use wxWindows instead of MFC, for portability reasons). I have had a look at the JARToolKit as an example of OO approach but unfortunately, the sources are not available yet (and they DO use Glut if I remeber well).
 
For now, I'm just waiting for the new ARToolKit site and forum to come up, as Mark sugested earlier. Do not hesitate to drop me a line if you wish to discuss this topic more thoroughly. 
 
Regards,
 
 
Fivos Doganis
 
 

-----Message d'origine-----
De : owner-artoolkit@h .................. [mailto:owner-artoolkit@h ..................]De la part de Fotis Liarokapis
Envoyé : mardi 11 février 2003 15:33
À : artoolkit@h ..................
Objet : MFC + ARToolkit


Hi everyone,
 
I am operating in Windows2000 environment and I am using Microsoft Visual C++ to implement my application. At the moment I am trying to create an MFC GUI on top of the ARToolkit 2.52 (windows + Vision SDK version). I am trying to eliminate the use of GLUT so that the ARToolkit window will run inside the MFC application. Has anybody done somethething similar or knows where I can find some resources? Thank you.
 
Best Regards,
 
Fotis Liarokapis
__________________________________
Fotis Liarokapis - Research Officer
Centre for VLSI and Computer Graphics,
School of Engineering and Information Technology, 
University of Sussex, Stage II, Room 4B4.
Brighton, Falmer, BN1 9QT.
Work Site : http://www.arco-web.org/
Research Site : http://www.sussex.ac.uk/Users/tapi8/index
e-mail: F.Liarokapis@s ...........
tel:  +44 (0)1273 606755 ext 2556
fax: +44 (0)1273 690816

Fivos DOGANIS wrote:

> Hi Fotis,
>  
> I am very interested into doing something similar, i.e. reduce 
> dependencies of the different parts of the code in order to increase 
> flexibility. This could be achieved by isolating the different 
> functions of the ARToolKit (camera calibraiton, frame grabber, image 
> processing, tracking results, 3D drawing etc.). It seems that newer 
> verisons of the toolkit are starting to get cleaner, but 
> unfortunately, the whole library is still just raw uncommented C code.
>  
> I would definitely like join forces with anyone else trying to 
> modularize the ARToolKit. I am particularly interested in removing the 
> Glut layer (but plan to use wxWindows instead of MFC, for portability 
> reasons). I have had a look at the JARToolKit as an example of OO 
> approach but unfortunately, the sources are not available yet (and 
> they DO use Glut if I remeber well).

The ARToolkit is already pretty well modularised, all you really need 
are the 'core' functionalities of the toolkit, that is, tracking.

If you only use ar32.lib, which is where the tracking functionality 
lies, you can implement all the generic peripheral code (image grabbing, 
3d modelling etc.) according to your taste in environment. As far as I 
know ar32 has no dependencies that would limit its use.

-- 
______________________________________________________________________
Dr.Jeremy Goslin
Geneva Interaction Lab, Université de Genève.
http://www.jeremygoslin.com

Fivos DOGANIS wrote:

> Hi Fotis,
>  
> I am very interested into doing something similar, i.e. reduce 
> dependencies of the different parts of the code in order to increase 
> flexibility. This could be achieved by isolating the different 
> functions of the ARToolKit (camera calibraiton, frame grabber, image 
> processing, tracking results, 3D drawing etc.). It seems that newer 
> verisons of the toolkit are starting to get cleaner, but 
> unfortunately, the whole library is still just raw uncommented C code.
>  
> I would definitely like join forces with anyone else trying to 
> modularize the ARToolKit. I am particularly interested in removing the 
> Glut layer (but plan to use wxWindows instead of MFC, for portability 
> reasons). I have had a look at the JARToolKit as an example of OO 
> approach but unfortunately, the sources are not available yet (and 
> they DO use Glut if I remeber well).

The ARToolkit is already pretty well modularised, all you really need 
are the 'core' functionalities of the toolkit, that is, tracking.

If you only use ar32.lib, which is where the tracking functionality 
lies, you can implement all the generic peripheral code (image grabbing, 
3d modelling etc.) according to your taste in environment. As far as I 
know ar32 has no dependencies that would limit its use.

-- 
______________________________________________________________________
Dr.Jeremy Goslin
Geneva Interaction Lab, Université de Genève.
http://www.jeremygoslin.com

Hi Jeremy,

Thank you for your tip. I'll have a look at ar32.lib and wil try to add my
code around it. Tracking is indeed the only part that I want to keep.

Regards,

Fivos


-----Message d'origine-----
De : owner-artoolkit@h ..................
[mailto:owner-artoolkit@h ..................]De la part de Jeremy Goslin
Envoyé : vendredi 14 février 2003 12:46
À : Fivos DOGANIS; artoolkit@h ..................
Objet : Re: MFC + ARToolkit


Fivos DOGANIS wrote:

> Hi Fotis,
>
> I am very interested into doing something similar, i.e. reduce
> dependencies of the different parts of the code in order to increase
> flexibility. This could be achieved by isolating the different
> functions of the ARToolKit (camera calibraiton, frame grabber, image
> processing, tracking results, 3D drawing etc.). It seems that newer
> verisons of the toolkit are starting to get cleaner, but
> unfortunately, the whole library is still just raw uncommented C code.
>
> I would definitely like join forces with anyone else trying to
> modularize the ARToolKit. I am particularly interested in removing the
> Glut layer (but plan to use wxWindows instead of MFC, for portability
> reasons). I have had a look at the JARToolKit as an example of OO
> approach but unfortunately, the sources are not available yet (and
> they DO use Glut if I remeber well).

The ARToolkit is already pretty well modularised, all you really need
are the 'core' functionalities of the toolkit, that is, tracking.

If you only use ar32.lib, which is where the tracking functionality
lies, you can implement all the generic peripheral code (image grabbing,
3d modelling etc.) according to your taste in environment. As far as I
know ar32 has no dependencies that would limit its use.

--
______________________________________________________________________
Dr.Jeremy Goslin
Geneva Interaction Lab, Université de Genève.
http://www.jeremygoslin.com

Hi Jeremy,

Thank you for your tip. I'll have a look at ar32.lib and wil try to add my
code around it. Tracking is indeed the only part that I want to keep.

Regards,

Fivos


-----Message d'origine-----
De : owner-artoolkit@h ..................
[mailto:owner-artoolkit@h ..................]De la part de Jeremy Goslin
Envoyé : vendredi 14 février 2003 12:46
À : Fivos DOGANIS; artoolkit@h ..................
Objet : Re: MFC + ARToolkit


Fivos DOGANIS wrote:

> Hi Fotis,
>
> I am very interested into doing something similar, i.e. reduce
> dependencies of the different parts of the code in order to increase
> flexibility. This could be achieved by isolating the different
> functions of the ARToolKit (camera calibraiton, frame grabber, image
> processing, tracking results, 3D drawing etc.). It seems that newer
> verisons of the toolkit are starting to get cleaner, but
> unfortunately, the whole library is still just raw uncommented C code.
>
> I would definitely like join forces with anyone else trying to
> modularize the ARToolKit. I am particularly interested in removing the
> Glut layer (but plan to use wxWindows instead of MFC, for portability
> reasons). I have had a look at the JARToolKit as an example of OO
> approach but unfortunately, the sources are not available yet (and
> they DO use Glut if I remeber well).

The ARToolkit is already pretty well modularised, all you really need
are the 'core' functionalities of the toolkit, that is, tracking.

If you only use ar32.lib, which is where the tracking functionality
lies, you can implement all the generic peripheral code (image grabbing,
3d modelling etc.) according to your taste in environment. As far as I
know ar32 has no dependencies that would limit its use.

--
______________________________________________________________________
Dr.Jeremy Goslin
Geneva Interaction Lab, Université de Genève.
http://www.jeremygoslin.com

Dear Anders,

Sorry for the delayed repply. There are two ways which I can think can be
done to use MFC and ARToolkit. The first one involves the recompilation of
GLUT in a way so that only the arguments are used and the child window is
created using win32. Remember that GLUT is based on win32 functionality. The
second way is to eliminate ARToolKit gsub function which uses GLUT functions
and replace them with win32 code or pure MFC if you prefer. You need to know
some basic MFC/win32 programming in order to do this but it is not very
difficult because I have managed to create a sample MFC win32 application.
Concering the stability issues I have resolved them, and they had to do with
the drawing of the scene in a child window. I faced these problems because I
used MFC for the first time in my life and I had to learn things from
scratch. I hope that this helps.

Best Regards,

 Fotis Liarokapis

----- Original Message -----
From: <anderaus@s ...........>
To: "Fotis Liarokapis" <F.Liarokapis@s ...........>
Sent: Monday, March 24, 2003 9:25 PM
Subject: Re: MFC + ARToolkit


> Dear Fotis
>
> Sorry for bothering you, but I'm starting on implementing a MFC
> application using ARToolKit today. It seems that having an OpenGL scene
> rendered in a child window is trivial. The image aquisition and pattern
> recognition from ARToolKit will run in the background, and since the
> viewing of captured data (as a texture) and rendered objects is done
> using OpenGL I think the elimination of GLUT should be possible to
> achieve. Have You been forced to do changes in the ARToolKit source code
> (like splitting GLUT-dependent functions etc), or is the kit so modul-
> based that this isn't necessary?
>
> You mentioned problems with stability? Could you explain more precise
> what problems you have encountered?
>
> Thanks!
>
> Regards,
> Anders Austad

Dear Anders,

Sorry for the delayed repply. There are two ways which I can think can be
done to use MFC and ARToolkit. The first one involves the recompilation of
GLUT in a way so that only the arguments are used and the child window is
created using win32. Remember that GLUT is based on win32 functionality. The
second way is to eliminate ARToolKit gsub function which uses GLUT functions
and replace them with win32 code or pure MFC if you prefer. You need to know
some basic MFC/win32 programming in order to do this but it is not very
difficult because I have managed to create a sample MFC win32 application.
Concering the stability issues I have resolved them, and they had to do with
the drawing of the scene in a child window. I faced these problems because I
used MFC for the first time in my life and I had to learn things from
scratch. I hope that this helps.

Best Regards,

 Fotis Liarokapis

----- Original Message -----
From: <anderaus@s ...........>
To: "Fotis Liarokapis" <F.Liarokapis@s ...........>
Sent: Monday, March 24, 2003 9:25 PM
Subject: Re: MFC + ARToolkit


> Dear Fotis
>
> Sorry for bothering you, but I'm starting on implementing a MFC
> application using ARToolKit today. It seems that having an OpenGL scene
> rendered in a child window is trivial. The image aquisition and pattern
> recognition from ARToolKit will run in the background, and since the
> viewing of captured data (as a texture) and rendered objects is done
> using OpenGL I think the elimination of GLUT should be possible to
> achieve. Have You been forced to do changes in the ARToolKit source code
> (like splitting GLUT-dependent functions etc), or is the kit so modul-
> based that this isn't necessary?
>
> You mentioned problems with stability? Could you explain more precise
> what problems you have encountered?
>
> Thanks!
>
> Regards,
> Anders Austad