Difference between revisions of "OpenIGTLink/Approaches"
From NAMIC Wiki
| Line 21: | Line 21: | ||
{|border="1" cellpadding="2" | {|border="1" cellpadding="2" | ||
| − | | style="width:25%; background:# | + | | style="width:25%; background:#7ECEA5"|Features |
| − | | style="width:25%; background:# | + | | style="width:25%; background:#7ECEA5"|From scratch |
| − | | style="width:25%; background:# | + | | style="width:25%; background:#7ECEA5"|igtlutil |
| − | | style="width:25%; background:# | + | | style="width:25%; background:#7ECEA5"|Open IGT Link Library |
|- | |- | ||
|style="width:25%; background:#8EDEB5"| Language | |style="width:25%; background:#8EDEB5"| Language | ||
Revision as of 15:01, 25 June 2008
Home < OpenIGTLink < ApproachesThree Approaches
Implement by yourself
- Writing applications in non-C/C++ languages
- The protocol is defined in the protocol description page.
Use simple C code (igtlutil)
- The code provides C structures for the generic header, image header and transform header, and supporting functions to create a message packet.
- Suitable for applications written in C and C++
- You can just copy the files into your source directory. You never have library link issue.
Use the Open IGT Link Library
- The library supports
- Classes to create Open IGT Link message
- TCP/IP Socket
- Thread and Mutex useful to make server program
- The library instruction is available in the Open IGT Link Library page.
| Features | From scratch | igtlutil | Open IGT Link Library |
| Language | Any | C/C++ | C++ |
| Platform | Any | ANSI C | Windows, Linux/UNIX, Mac OS X |
| Generic Header | - | Yes | Yes |
| Transform | - | Yes | Yes |
| Image | - | Yes | Yes |
| Endian Conversion | - | Yes | Yes |
| CRC Calculation | - | Yes | Yes |
| Socket | - | - | Yes |
| Thread & Mutex | - | - | Yes |
