Boost-Commit :

Date view	Thread view	Subject view	Author view

Subject: [Boost-commit] svn:boost r83328 - in trunk/libs: . gil/example gil/io/doc gil/io/doc/html gil/io/doc/html/gil gil/io/doc/html/gil/io
From: chhenning_at_[hidden]
Date: 2013-03-05 20:43:47

Next message: john_at_[hidden]: "[Boost-commit] svn:boost r83329 - trunk/libs/math/test"
Previous message: afojgo_at_[hidden]: "[Boost-commit] svn:boost r83327 - in sandbox/icl/libs/xplore/value_sem/TreeSync1/TreeSync1: . Syncable"

Author: chhenning
Date: 2013-03-05 20:43:46 EST (Tue, 05 Mar 2013)
New Revision: 83328
URL: http://svn.boost.org/trac/boost/changeset/83328

Log:
Added gil::io documentation and added it to libraries.htm.
Updated maintainer.txt to reflect new gil maintainer.
Added:
   trunk/libs/gil/io/doc/html/
   trunk/libs/gil/io/doc/html/gil/
   trunk/libs/gil/io/doc/html/gil/io/
   trunk/libs/gil/io/doc/html/gil/io/running_gil__io_tests.html (contents, props changed)
   trunk/libs/gil/io/doc/html/gil/io/tutorial.html (contents, props changed)
   trunk/libs/gil/io/doc/html/gil/io/using_io.html (contents, props changed)
   trunk/libs/gil/io/doc/html/index.html (contents, props changed)
Text files modified:
   trunk/libs/gil/example/interleaved_ptr.hpp | 2 +-
   trunk/libs/gil/example/mandelbrot.cpp | 2 +-
   trunk/libs/gil/io/doc/io.qbk | 2 +-
   trunk/libs/libraries.htm | 4 ++++
   trunk/libs/maintainers.txt | 2 +-
   5 files changed, 8 insertions(+), 4 deletions(-)

Modified: trunk/libs/gil/example/interleaved_ptr.hpp
==============================================================================
--- trunk/libs/gil/example/interleaved_ptr.hpp (original)
+++ trunk/libs/gil/example/interleaved_ptr.hpp 2013-03-05 20:43:46 EST (Tue, 05 Mar 2013)
@@ -195,4 +195,4 @@
};
} } // namespace boost::gil

-#endif
\ No newline at end of file
+#endif

Modified: trunk/libs/gil/example/mandelbrot.cpp
==============================================================================
--- trunk/libs/gil/example/mandelbrot.cpp (original)
+++ trunk/libs/gil/example/mandelbrot.cpp 2013-03-05 20:43:46 EST (Tue, 05 Mar 2013)
@@ -79,4 +79,4 @@
jpeg_write_view("out-mandelbrot.jpg",mandel);

return 0;
-}
\ No newline at end of file
+}

Added: trunk/libs/gil/io/doc/html/gil/io/running_gil__io_tests.html
==============================================================================
--- (empty file)
+++ trunk/libs/gil/io/doc/html/gil/io/running_gil__io_tests.html 2013-03-05 20:43:46 EST (Tue, 05 Mar 2013)
@@ -0,0 +1,82 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Running gil::io tests</title>
+<link rel="stylesheet" href="../../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.77.1">
+<link rel="home" href="../../index.html" title="Chapter 1. Boost.GIL.IO">
+<link rel="up" href="../../index.html" title="Chapter 1. Boost.GIL.IO">
+<link rel="prev" href="using_io.html" title="Using IO">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table cellpadding="2" width="100%"><tr>
+<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../../boost.png"></td>
+<td align="center">Home</td>
+<td align="center">Libraries</td>
+<td align="center">People</td>
+<td align="center">FAQ</td>
+<td align="center">More</td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="using_io.html"><img src="../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../../index.html"><img src="../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../../doc/src/images/home.png" alt="Home"></a>
+</div>
+<div class="section gil_io_running_gil__io_tests">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="gil.io.running_gil__io_tests"></a><a class="link" href="running_gil__io_tests.html" title="Running gil::io tests">Running gil::io tests</a>
+</h2></div></div></div>
+
+ gil::io comes with a large suite of test cases which reads and writes various
+ file formats. It uses some test image suites which can be found online or which
+ can be demanded from me by sending me an email ( <a href="../../chhenning" target="_top">**
+ @ ** gmail.com</a> ).
+ 
+
+ There are some test images created by me in the test folder. To enable unit
+ tests which make use of them set the following compiler options BOOST_GIL_IO_TEST_ALLOW_READING_IMAGES
+ and BOOST_GIL_IO_TEST_ALLOW_WRITING_IMAGES.
+ 
+
+ The following list provides all links to the image suites the compiler symbol
+ to enable the tests:
+ 
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem">
+ BMP: http://entropymine.com/jason/bmpsuite/
+ -- BOOST_GIL_IO_USE_BMP_TEST_SUITE_IMAGES
+ </li>
+<li class="listitem">
+ PNG: http://www.schaik.com/pngsuite/pngsuite.html
+ -- BOOST_GIL_IO_USE_PNG_TEST_SUITE_IMAGES
+ </li>
+<li class="listitem">
+ PNM: ** @ ** gmail.com -- BOOST_GIL_IO_USE_PNM_TEST_SUITE_IMAGES
+ </li>
+<li class="listitem">
+ TARGA: http://www.fileformat.info/format/tga/sample/index.htm
+ -- BOOST_GIL_IO_USE_TARGA_FILEFORMAT_TEST_SUITE_IMAGES
+ </li>
+<li class="listitem">
+ TIFF: http://www.remotesensing.org/libtiff/images.html
+ -- BOOST_GIL_IO_USE_TIFF_LIBTIFF_TEST_SUITE_IMAGES
+ </li>
+<li class="listitem">
+ TIFF ftp://ftp.graphicsmagick.org/pub/tiff-samples/tiff-sample-images-be.tar.gz
+ -- BOOST_GIL_IO_USE_TIFF_GRAPHICSMAGICK_TEST_SUITE_IMAGES
+ </li>
+</ul></div>
+</div>
+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
+<td align="left"></td>
+<td align="right"><div class="copyright-footer">Copyright © 2012 Christian Henning
+ Distributed under the Boost Software License, Version 1.0. (See accompanying
+ file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ 
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="using_io.html"><img src="../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../../index.html"><img src="../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../../doc/src/images/home.png" alt="Home"></a>
+</div>
+</body>
+</html>

Added: trunk/libs/gil/io/doc/html/gil/io/tutorial.html
==============================================================================
--- (empty file)
+++ trunk/libs/gil/io/doc/html/gil/io/tutorial.html 2013-03-05 20:43:46 EST (Tue, 05 Mar 2013)
@@ -0,0 +1,191 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Tutorial</title>
+<link rel="stylesheet" href="../../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.77.1">
+<link rel="home" href="../../index.html" title="Chapter 1. Boost.GIL.IO">
+<link rel="up" href="../../index.html" title="Chapter 1. Boost.GIL.IO">
+<link rel="prev" href="../../index.html" title="Chapter 1. Boost.GIL.IO">
+<link rel="next" href="using_io.html" title="Using IO">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table cellpadding="2" width="100%"><tr>
+<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../../boost.png"></td>
+<td align="center">Home</td>
+<td align="center">Libraries</td>
+<td align="center">People</td>
+<td align="center">FAQ</td>
+<td align="center">More</td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="../../index.html"><img src="../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../../index.html"><img src="../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="using_io.html"><img src="../../../../../../../doc/src/images/next.png" alt="Next"></a>
+</div>
+<div class="section gil_io_tutorial">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="gil.io.tutorial"></a><a class="link" href="tutorial.html" title="Tutorial">Tutorial</a>
+</h2></div></div></div>
+
+ Thanks to modern C++ programming techniques the interface for this library
+ is rather small and easy to use. In this tutorial I'll give you a short walk-around
+ on how to use this boost::gil extension. For more details please refer to section
+ 3.
+ 
+
+ Since this is an extension to boost::gil I expect the user to have some very
+ basic understanding of the gil ( generic image library ). Please see here for
+ the help.
+ 
+<h3>
+<a name="gil.io.tutorial.h0"></a>
+ <a name="gil.io.tutorial.header_files"></a><a class="link" href="tutorial.html#gil.io.tutorial.header_files">Header
+ Files</a>
+ </h3>
+
+ The header files to be included all have the same format. For instance, tiff_all.hpp
+ will allow to read and write. Whereas, tiff_read.hpp only allows for reading.
+ If the user only wants to write jpeg's include jpeg_write.hpp. All formats
+ provide these three types of header files:
+ 
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem">
+ xxx_all.hpp
+ </li>
+<li class="listitem">
+ xxx_read.hpp
+ </li>
+<li class="listitem">
+ xxx_write.hpp
+ </li>
+</ul></div>
+
+ xxx stands for image format.
+ 
+<h3>
+<a name="gil.io.tutorial.h1"></a>
+ <a name="gil.io.tutorial.reading_an_image"></a><a class="link" href="tutorial.html#gil.io.tutorial.reading_an_image">Reading
+ An Image</a>
+ </h3>
+
+ Probably the most common case to read a tiff image can be done as follows:
+ 
+<pre class="programlisting">std::string filename( "image.tif" );
+rgb8_image_t img;
+read_image( filename, img, tiff_tag() );
+</pre>
+
+ The code would be same for all other image formats. The only thing that needs
+ to change is the tag type ( tiff_tag ) in the read_image call. The read_image()
+ expects the supplied image type to be compatible with the image stored in the
+ file. If the user doesn't know what format an image has he/she can use read_and_convert_image().
+ Another important fact is that read_image() will allocate the appropriate memory
+ needed for the read operation. There are read_view or read_and_convert_view
+ counterparts, if the memory is already allocated.
+ 
+
+ Sometimes the user only wants to read a sub-part of an image, then the above
+ call would look as follows:
+ 
+<pre class="programlisting">read_image( filename
+ , img
+ , image_read_settings< tiff_tag >( point_t( 0, 0 ), point_t( 50, 50 ) )
+ );
+</pre>
+
+ The image_read_settings class will provide the user with image format independent
+ reading setting but can also serves as a pointer for format dependent settings.
+ Please see the specific image format sections <a class="link" href="using_io.html#gil.io.using_io.supported_image_formats">Supported
+ Image Formats</a> for more details.
+ 
+<h3>
+<a name="gil.io.tutorial.h2"></a>
+ <a name="gil.io.tutorial.writing_an_image"></a><a class="link" href="tutorial.html#gil.io.tutorial.writing_an_image">Writing
+ An Image</a>
+ </h3>
+
+ Besides reading the information also writing is the second part of this boost::gil
+ extension. Writing is a lot simpler than reading since an existing image view
+ contains all the information. For instance writing an image can be done as
+ follows:
+ 
+<pre class="programlisting">std::string filename( "image.tif" );
+rgb8_image_t img( 640, 480 );
+
+// write data into image
+
+write_view( filename
+ , view( img )
+ , tiff_tag()
+ );
+</pre>
+
+ The interface is similar to reading an image. To add image format specific
+ parameter the user can use image_write_info class. For instance, a user can
+ specify the jpeg quality when writing like this:
+ 
+<pre class="programlisting">std::string filename( "image.jpg" );
+rgb8_image_t img( 640, 480 );
+
+// write data into image
+
+write_view( filename
+ , view( img )
+ , image_write_info< jpeg_tag >( 95 )
+ );
+</pre>
+
+ The above example will write an image where the jpeg quality is set to 95 percent.
+ 
+<h3>
+<a name="gil.io.tutorial.h3"></a>
+ <a name="gil.io.tutorial.reading_and_writing_in_memory_buffers"></a><a class="link" href="tutorial.html#gil.io.tutorial.reading_and_writing_in_memory_buffers">Reading
+ And Writing In-Memory Buffers</a>
+ </h3>
+
+ Reading and writing in-memory buffers are supported as well. See as follows:
+ 
+<pre class="programlisting">// 1. Read an image.
+ifstream in( "test.tif", ios::binary );
+
+rgb8_image_t img;
+read_image( in, img, tiff_tag() );
+
+// 2. Write image to in-memory buffer.
+stringstream out_buffer( ios_base::out | ios_base::binary );
+
+rgb8_image_t src;
+write_view( out_buffer, view( src ), tiff_tag() );
+
+// 3. Copy in-memory buffer to another.
+stringstream in_buffer( ios_base::in | ios_base::binary );
+in_buffer << out_buffer.rdbuf();
+
+// 4. Read in-memory buffer to gil image
+rgb8_image_t dst;
+read_image( in_buffer, dst, tag_t() );
+
+// 5. Write out image.
+string filename( "out.tif" );
+ofstream out( filename.c_str(), ios_base::binary );
+write_view( out, view( dst ), tiff_tag() );
+</pre>
+
+ In case the user is using his own stream classes he has to make sure it has
+ the common interface read, write, seek, close, etc. Interface.
+ 
+</div>
+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
+<td align="left"></td>
+<td align="right"><div class="copyright-footer">Copyright © 2012 Christian Henning
+ Distributed under the Boost Software License, Version 1.0. (See accompanying
+ file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ 
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="../../index.html"><img src="../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../../index.html"><img src="../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="using_io.html"><img src="../../../../../../../doc/src/images/next.png" alt="Next"></a>
+</div>
+</body>
+</html>

Added: trunk/libs/gil/io/doc/html/gil/io/using_io.html
==============================================================================
--- (empty file)
+++ trunk/libs/gil/io/doc/html/gil/io/using_io.html 2013-03-05 20:43:46 EST (Tue, 05 Mar 2013)
@@ -0,0 +1,772 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Using IO</title>
+<link rel="stylesheet" href="../../../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.77.1">
+<link rel="home" href="../../index.html" title="Chapter 1. Boost.GIL.IO">
+<link rel="up" href="../../index.html" title="Chapter 1. Boost.GIL.IO">
+<link rel="prev" href="tutorial.html" title="Tutorial">
+<link rel="next" href="running_gil__io_tests.html" title="Running gil::io tests">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table cellpadding="2" width="100%"><tr>
+<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../../../boost.png"></td>
+<td align="center">Home</td>
+<td align="center">Libraries</td>
+<td align="center">People</td>
+<td align="center">FAQ</td>
+<td align="center">More</td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="tutorial.html"><img src="../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../../index.html"><img src="../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="running_gil__io_tests.html"><img src="../../../../../../../doc/src/images/next.png" alt="Next"></a>
+</div>
+<div class="section gil_io_using_io">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="gil.io.using_io"></a><a class="link" href="using_io.html" title="Using IO">Using IO</a>
+</h2></div></div></div>
+<h3>
+<a name="gil.io.using_io.h0"></a>
+ <a name="gil.io.using_io.general_overview"></a><a class="link" href="using_io.html#gil.io.using_io.general_overview">General
+ Overview</a>
+ </h3>
+
+ The tutorial pointed out some use cases for reading and writing images in various
+ image formats. This section will provide a more thorough overview.
+ 
+
+ The next sections will introduce the Read and Write interface. But it might
+ be worth poiting out that by using some advanced metaprogramming techniques
+ the interface is rather small and hopefully easy to understand.
+ 
+
+ Besides the general interface the user also has the ability to interface directly
+ with the underlying image format. For that each reader or writer provides access
+ to the so-called backend. For instance:
+ 
+<pre class="programlisting">typedef get_reader_backend< const std::string
+ , tag_t
+ >::type backend_t;
+
+backend_t backend = read_image_info( bmp_filename
+ , tag_t()
+ );
+
+BOOST_CHECK_EQUAL( backend._info._width , 127 );
+BOOST_CHECK_EQUAL( backend._info._height, 64 );
+</pre>
+
+ Of course, the typedef can be removed when using c++11's auto feature.
+ 
+<h3>
+<a name="gil.io.using_io.h1"></a>
+ <a name="gil.io.using_io.read_interface"></a><a class="link" href="using_io.html#gil.io.using_io.read_interface">Read
+ Interface</a>
+ </h3>
+
+ As the Tutorial demonstrated there are a few ways to read images. Here is an
+ enumeration of all read functions with a short description:
+ 
+<pre class="programlisting">* read_image - read into a gil image with no conversion. Memory is allocated.
+* read_view - read into a gil view with no conversion.
+* read_and_convert_image - read and convert into a gil image. Memory is allocated.
+* read_and_convert_view - read and convert into a gil view.
+* read_image_info - read the image header.
+</pre>
+
+ Conversion in this context is necessary if the source ( file ) has an incompatible
+ color space with the destination ( gil image type ). If that's the case the
+ user has to use the xxx_and_convert_xxx variants.
+ 
+
+ All functions take the filename or a device as the first parameter. The filename
+ can be anything from a c string, std::string, std::wstring, and a boost::filesystem
+ path. When using the path object the user needs to define the ADD_FS_PATH_SUPPORT
+ compiler symbol to include the boost::filesystem dependency. Devices could
+ be a FILE*, std::ifstream, and a TIFF* for TIFF images.
+ 
+
+ The second parameter is either an image or view type depending on the read_xxx
+ function. The third and last parameter is either an instance of the image_read_settings<FormatTag>
+ or just the FormatTag. The settings can be various depending on the format
+ which is being read. But the all share settings for reading a partial image
+ area. The first point describes the top left image coordinate whereas the second
+ are the dimensions in x and y directions. Here an example of setting up partial
+ read.
+ 
+<pre class="programlisting">read_image( filename
+ , img
+ , image_read_settings< tiff_tag >( point_t( 0, 0 ), point_t( 50, 50 ) )
+ );
+</pre>
+
+ Each format supports reading just the header information, using read_image_info().
+ Please refer to the format specific sections under 3.3. A basic example follows:
+ 
+<pre class="programlisting">image_read_info< tiff_t > info = read_image_info( filename
+ , tiff_t()
+ );
+</pre>
+
+ GIL also comes with a dynamic image extension. In the context of GIL.IO a user
+ can define an any_image type based on several image types. The IO extension
+ would then pick the matching image type to the current image file. The following
+ example shows this feature:
+ 
+<pre class="programlisting">typedef mpl::vector< gray8_image_t
+ , gray16_image_t
+ , rgb8_image_t
+ , rgba_image_t
+ > my_img_types;
+
+any_image< my_img_types > runtime_image;
+
+read_image( filename
+ , runtime_image
+ , tiff_tag()
+ );
+</pre>
+
+ During the review it became clear that there is a need to read big images scanline
+ by scanline. To support such use case a scanline_reader is implemented for
+ all supported image formats. The scanline_read_iterators will then allow to
+ traverse through the image. The following code sample shows the usage:
+ 
+<pre class="programlisting">typedef tiff_tag tag_t;
+
+typedef scanline_reader< typename get_read_device< const char*
+ , tag_t
+ >::type
+ , tag_t
+ > reader_t;
+
+reader_t reader = make_scanline_reader( "C:/boost/libs/gil/io/test_images/tiff/test.tif", tag_t() );
+
+typedef rgba8_image_t image_t;
+
+image_t dst( reader._info._width, reader._info._height );
+fill_pixels( view(dst), image_t::value_type() );
+
+typedef reader_t::iterator_t iterator_t;
+
+iterator_t it = reader.begin();
+iterator_t end = reader.end();
+
+for( int row = 0; it != end; ++it, ++row )
+{
+ copy_pixels( interleaved_view( reader._info._width
+ , 1
+ , ( image_t::view_t::x_iterator ) *it
+ , reader._scanline_length
+ )
+ , subimage_view( view( dst )
+ , 0
+ , row
+ , reader._info._width
+ , 1
+ )
+ );
+}
+</pre>
+
+ There are many ways to travese an image but for as of now only by scanline
+ is supported.
+ 
+<h3>
+<a name="gil.io.using_io.h2"></a>
+ <a name="gil.io.using_io.write_interface"></a><a class="link" href="using_io.html#gil.io.using_io.write_interface">Write
+ Interface</a>
+ </h3>
+
+ There is only one function for writing out images, write_view. Similar to reading
+ the first parameter is either a filename or a device. The filename can be anything
+ from a c string, std::string, std::wstring, and a boost::filesystem path. When
+ using the path object the user needs to define the ADD_FS_PATH_SUPPORT compiler
+ symbol to include the boost::filesystem dependency. Devices could be a FILE*,
+ std::ifstream, and a TIFF* for TIFF images.
+ 
+
+ The second parameter is an view object to image being written. The third and
+ last parameter is either a tag or an image_write_info< FormatTag > object
+ containing more settings. One example for instance is the jpeg quality. Refer
+ to the format specific sections under 3.3. to have a list of all the possible
+ settings.
+ 
+
+ Writing an any_image<...> is supported. See the following example:
+ 
+<pre class="programlisting">typedef mpl::vector< gray8_image_t
+ , gray16_image_t
+ , rgb8_image_t
+ , rgba_image_t
+ > my_img_types;
+
+
+any_image< my_img_types > runtime_image;
+
+// fill any_image 
+
+write_view( filename
+ , view( runtime_image )
+ , tiff_tag()
+ );
+</pre>
+<h3>
+<a name="gil.io.using_io.h3"></a>
+ <a name="gil.io.using_io.compiler_symbols"></a><a class="link" href="using_io.html#gil.io.using_io.compiler_symbols">Compiler
+ Symbols</a>
+ </h3>
+
+ The following table gives an overview of all supported compiler symbols that
+ can be set by the user:
+ 
+<div class="table">
+<a name="gil.io.using_io.t0"></a>Table 1.1. Compiler Symbols
+<div class="table-contents"><table class="table" summary="Compiler Symbols">
+<colgroup>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>
+ 
+ Symbol
+ 
+ </th>
+<th>
+ 
+ Description
+ 
+ </th>
+</tr></thead>
+<tbody>
+<tr>
+<td>
+ 
+ BOOST_GIL_IO_ENABLE_GRAY_ALPHA
+ 
+ </td>
+<td>
+ 
+ Enable the color space "gray_alpha".
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ BOOST_GIL_IO_ADD_FS_PATH_SUPPORT
+ 
+ </td>
+<td>
+ 
+ Enable boost::filesystem 3.0 library.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ BOOST_GIL_IO_PNG_FLOATING_POINT_SUPPORTED
+ 
+ </td>
+<td>
+ 
+ Use libpng in floating point mode. This symbol is incompatible with
+ BOOST_GIL_IO_PNG_FIXED_POINT_SUPPORTED.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ BOOST_GIL_IO_PNG_FIXED_POINT_SUPPORTED
+ 
+ </td>
+<td>
+ 
+ Use libpng in integer mode. This symbol is incompatible with BOOST_GIL_IO_PNG_FLOATING_POINT_SUPPORTED.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ BOOST_GIL_EXTENSION_IO_JPEG_C_LIB_COMPILED_AS_CPLUSPLUS
+ 
+ </td>
+<td>
+ 
+ libjpeg is compiled as c++ lib.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ BOOST_GIL_EXTENSION_IO_PNG_C_LIB_COMPILED_AS_CPLUSPLUS
+ 
+ </td>
+<td>
+ 
+ libpng is compiled as c++ lib.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ BOOST_GIL_EXTENSION_IO_RAW_C_LIB_COMPILED_AS_CPLUSPLUS
+ 
+ </td>
+<td>
+ 
+ libraw is compiled as c++ lib.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ BOOST_GIL_EXTENSION_IO_TIFF_C_LIB_COMPILED_AS_CPLUSPLUS
+ 
+ </td>
+<td>
+ 
+ libtiff is compiled as c++ lib.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ BOOST_GIL_IO_TEST_ALLOW_READING_IMAGES
+ 
+ </td>
+<td>
+ 
+ Allow basic test images to be read from local hard drive. The paths
+ can be set in paths.hpp
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ BOOST_GIL_IO_TEST_ALLOW_WRITING_IMAGES
+ 
+ </td>
+<td>
+ 
+ Allow images to be written to the local hard drive. The paths can
+ be set in paths.hpp
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ BOOST_GIL_IO_USE_BMP_TEST_SUITE_IMAGES
+ 
+ </td>
+<td>
+ 
+ Run tests using the bmp test images suite. See http://entropymine.com/jason/bmpsuite/
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ BOOST_GIL_IO_USE_PNG_TEST_SUITE_IMAGES
+ 
+ </td>
+<td>
+ 
+ Run tests using the png test images suite. See http://www.schaik.com/pngsuite/pngsuite.html
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ BOOST_GIL_IO_USE_PNM_TEST_SUITE_IMAGES
+ 
+ </td>
+<td>
+ 
+ Run tests using the pnm test images suite. Send me an email for accessing
+ the files.
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ BOOST_GIL_IO_USE_TARGA_FILEFORMAT_TEST_SUITE_IMAGES
+ 
+ </td>
+<td>
+ 
+ Run tests using the targa file format test images suite. See http://www.fileformat.info/format/tga/sample/index.htm
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ BOOST_GIL_IO_USE_TIFF_LIBTIFF_TEST_SUITE_IMAGES
+ 
+ </td>
+<td>
+ 
+ Run tests using the targa file format test images suite. See http://www.remotesensing.org/libtiff/images.html
+ 
+ </td>
+</tr>
+<tr>
+<td>
+ 
+ BOOST_GIL_IO_USE_TIFF_GRAPHICSMAGICK_TEST_SUITE_IMAGES
+ 
+ </td>
+<td>
+ 
+ Run tests using the targa file format test images suite. See ftp://ftp.graphicsmagick.org/pub/tiff-samples/tiff-sample-images-be.tar.gz
+ 
+ </td>
+</tr>
+</tbody>
+</table></div>
+</div>
+ <h3>
+<a name="gil.io.using_io.h4"></a>
+ <a name="gil.io.using_io.supported_image_formats"></a><a class="link" href="using_io.html#gil.io.using_io.supported_image_formats">Supported
+ Image Formats</a>
+ </h3>
+<h4>
+<a name="gil.io.using_io.h5"></a>
+ <a name="gil.io.using_io.bmp"></a><a class="link" href="using_io.html#gil.io.using_io.bmp">BMP</a>
+ </h4>
+
+ For a general overview of the BMP image file format go to the following http://en.wikipedia.org/wiki/BMP_file_format.
+ 
+
+ Please note, the code has not been tested on X Windows System variations of
+ the BMP format which are usually referred to XBM and XPM formats.
+ 
+
+ Here, only the MS Windows and OS/2 format is relevant.
+ 
+
+ Currently the code is able to read and write the following image types:
+ 
+
+ Read: gray1_image_t, gray4_image_t, gray8_image_t, rgb8_image_t and, rgba8_image_t
+ Write: rgb8_image_t and, rgba8_image_t
+ 
+
+ The lack of having an indexed image type in gil restricts the current interface
+ to only write out non-indexed images. This is subject to change soon.
+ 
+<h4>
+<a name="gil.io.using_io.h6"></a>
+ <a name="gil.io.using_io.jpeg"></a><a class="link" href="using_io.html#gil.io.using_io.jpeg">JPEG</a>
+ </h4>
+
+ For a general overview of the JPEG image file format go to the following http://en.wikipedia.org/wiki/JPEG.
+ 
+
+ This jpeg extension is based on the libjpeg library which can be found here,
+ JPEG_Lib.
+ 
+
+ The user has to make sure this library is properly installed. I strongly recommend
+ the user to build the library yourself. It could potentially save you a lot
+ of trouble.
+ 
+
+ Currently the code is able to read and write the following image types:
+ 
+
+ Read: gray8_image_t, rgb8_image_t, cmyk8_image_t Write: gray8_image_t, rgb8_image_t,
+ cmyk8_image_t
+ 
+
+ Reading YCbCr or YCCK images is possible but might result in inaccuracies since
+ both color spaces aren't available yet for gil. For now these color space are
+ read as rgb images. This is subject to change soon.
+ 
+<h4>
+<a name="gil.io.using_io.h7"></a>
+ <a name="gil.io.using_io.png"></a><a class="link" href="using_io.html#gil.io.using_io.png">PNG</a>
+ </h4>
+
+ For a general overview of the PNG image file format go to the following http://en.wikipedia.org/wiki/Portable_Network_Graphics.
+ 
+
+ This png extension is based on the libpng, which can be found here, _PNG_Lib.
+ 
+
+ The user has to make sure this library is properly installed. I strongly recommend
+ the user to build the library yourself. It could potentially save you a lot
+ of trouble.
+ 
+
+ Currently the code is able to read and write the following image types:
+ 
+
+ Read: gray1, gray2, gray4, gray8, gray16, gray_alpha_8, gray_alpha_16, rgb8,
+ rgb16, rgba8, rgba16 Write: gray1, gray2, gray4, gray8, gray16, gray_alpha_8,
+ gray_alpha_16, rgb8, rgb16, rgba8, rgba16
+ 
+
+ For reading gray_alpha images the user has to enable the ENABLE_GRAY_ALPHA
+ compiler switch. This color space is defined in the toolbox by using gray_alpha.hpp.
+ 
+<h4>
+<a name="gil.io.using_io.h8"></a>
+ <a name="gil.io.using_io.pnm"></a><a class="link" href="using_io.html#gil.io.using_io.pnm">PNM</a>
+ </h4>
+
+ For a general overview of the PNM image file format go to the following http://en.wikipedia.org/wiki/Portable_anymap.
+ 
+
+ No external library is needed for the pnm format. Both ascii and binary formats
+ are supported.
+ 
+
+ Currently the code is able to read and write the following image types:
+ 
+
+ Read: gray1, gray8, rgb8 Write: gray1, gray8, rgb8
+ 
+
+ When reading a mono text image the data is read as a gray8 image.
+ 
+<h4>
+<a name="gil.io.using_io.h9"></a>
+ <a name="gil.io.using_io.raw"></a><a class="link" href="using_io.html#gil.io.using_io.raw">RAW</a>
+ </h4>
+
+ For a general overview see _RAW_Wiki.
+ 
+
+ Currently the extension is only able to read rgb8 images.
+ 
+<h4>
+<a name="gil.io.using_io.h10"></a>
+ <a name="gil.io.using_io.targa"></a><a class="link" href="using_io.html#gil.io.using_io.targa">TARGA</a>
+ </h4>
+
+ For a general overview of the BMP image file format go to the following TARGA_Wiki.
+ 
+
+ Currently the code is able to read and write the following image types:
+ 
+
+ Read: rgb8_image_t and rgba8_image_t Write: rgb8_image_t and rgba8_image_t
+ 
+
+ The lack of having an indexed image type in gil restricts the current interface
+ to only write out non-indexed images. This is subject to change soon.
+ 
+<h4>
+<a name="gil.io.using_io.h11"></a>
+ <a name="gil.io.using_io.tiff"></a><a class="link" href="using_io.html#gil.io.using_io.tiff">TIFF</a>
+ </h4>
+
+ For a general overview of the TIFF image file format go to the following http://en.wikipedia.org/wiki/Tagged_Image_File_Format.
+ 
+
+ This tiff extension is based on the libtiff, which can be found, http://www.remotesensing.org/libtiff/.
+ 
+
+ The user has to make sure this library is properly installed. I strongly recommend
+ the user to build the library yourself. It could potentially save you a lot
+ of trouble.
+ 
+
+ TIFF images can virtually encode all kinds of channel sizes representing various
+ color spaces. Even planar images are possible. For instance, rbg323 or gray7.
+ The channels also can have specific formats, like integer values or floating
+ point values. For a complete set of options please consult the following websites:
+ 
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem">
+ http://www.awaresystems.be/imaging/tiff/tifftags/baseline.html
+ </li>
+<li class="listitem">
+ http://www.awaresystems.be/imaging/tiff/tifftags/extension.html
+ </li>
+</ul></div>
+
+ The author of this extension is not claiming all tiff formats are supported.
+ This extension is likely to be a moving target adding new features with each
+ new milestone. Here is an incomplete lists:
+ 
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem">
+ Multi-page tiffs - read only
+ </li>
+<li class="listitem">
+ Strip tiffs - read and write support
+ </li>
+<li class="listitem">
+ Tiled tiffs - read and write support with user defined tiled sizes
+ </li>
+<li class="listitem">
+ bit images tiffs - fully supported, like gray1_image_t ( minisblack )
+ </li>
+<li class="listitem">
+ planar tiffs - fully supported
+ </li>
+<li class="listitem">
+ floating point tiffs - fully supported
+ </li>
+<li class="listitem">
+ palette tiffs - supported but no indexed image type is available as of
+ now
+ </li>
+</ul></div>
+
+ This gil extension uses two different test image suites to test read and write
+ capabilities. See test_image folder. It's advisable to use ImageMagick's test
+ viewer to display images.
+ 
+<h3>
+<a name="gil.io.using_io.h12"></a>
+ <a name="gil.io.using_io.extending_gil__io_with_new_formats"></a><a class="link" href="using_io.html#gil.io.using_io.extending_gil__io_with_new_formats">Extending
+ GIL::IO with new Formats</a>
+ </h3>
+
+ Extending the gil::io with new formats is meant to be simple and straightforward.
+ Before adding I would recommend to have a look at existing implementations
+ and then trying to follow a couple of guidelines:
+ 
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem">
+ Create the following files for your new xxx format
+ <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle; ">
+<li class="listitem">
+ xxx_read.hpp // Only includes read code
+ </li>
+<li class="listitem">
+ xxx_write.hpp // Only includes write code
+ </li>
+<li class="listitem">
+ xxx_all.hpp // includes xxx_read.hpp and xxx_write.hpp
+ </li>
+</ul></div>
+ </li>
+<li class="listitem">
+ Add the code to the boost::gil::detail namespace
+ </li>
+<li class="listitem">
+ Create a tag type for the new format. Like this:
+<pre class="programlisting">struct xxx_tag : format_tag {};
+</pre>
+ </li>
+<li class="listitem">
+ Create the image_read_info for the new format. It contains all the information
+ that are necessary to read an image. It should be filled and returned by
+ the get_info() member of the reader class. See below.
+<pre class="programlisting">template<> struct image_read_info< xxx_tag > {};
+</pre>
+ </li>
+<li class="listitem">
+ Create the image_write_info for the new format. It contains all the information
+ that are necessary to write an image.
+<pre class="programlisting">template<> struct image_write_info< xxx_tag > {};
+</pre>
+ </li>
+<li class="listitem">
+ Use the following reader skeleton as a start:
+<pre class="programlisting">template< typename Device
+ , typename ConversionPolicy
+ >
+class reader< Device
+ , xxx_tag
+ , ConversionPolicy
+ >
+ : public reader_base< xxx_tag
+ , ConversionPolicy
+ >
+{
+private:
+
+ typedef typename ConversionPolicy::color_converter_type cc_t;
+
+public:
+
+ reader( Device& device )
+ : _io_dev( device )
+ {}
+
+ reader( Device& device
+ , const cc_t& cc
+ )
+ : _io_dev( device )
+ , reader_base< xxx_tag
+ , ConversionPolicy
+ >( cc )
+ {}
+
+ image_read_info< xxx_tag > get_info()
+ {
+ // your implementation here
+ }
+
+ template< typename View >
+ void apply( const View& dst_view )
+ {
+ // your implementation here
+ }
+};
+</pre>
+ </li>
+<li class="listitem">
+ The writer skeleton:
+<pre class="programlisting">template< typename Device >
+class writer< Device
+ , xxx_tag
+ >
+{
+public:
+
+ writer( Device & file )
+ : out(file)
+ {}
+
+ template<typename View>
+ void apply( const View& view )
+ {
+ // your implementation here
+ }
+
+ template<typename View>
+ void apply( const View& view
+ , const image_write_info< xxx_tag >& info )
+ {
+ // your implementation here
+ }
+};
+</pre>
+ </li>
+</ul></div>
+</div>
+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
+<td align="left"></td>
+<td align="right"><div class="copyright-footer">Copyright © 2012 Christian Henning
+ Distributed under the Boost Software License, Version 1.0. (See accompanying
+ file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ 
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="tutorial.html"><img src="../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../../index.html"><img src="../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="running_gil__io_tests.html"><img src="../../../../../../../doc/src/images/next.png" alt="Next"></a>
+</div>
+</body>
+</html>

Added: trunk/libs/gil/io/doc/html/index.html
==============================================================================
--- (empty file)
+++ trunk/libs/gil/io/doc/html/index.html 2013-03-05 20:43:46 EST (Tue, 05 Mar 2013)
@@ -0,0 +1,109 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Chapter 1. Boost.GIL.IO</title>
+<link rel="stylesheet" href="../../../../../doc/src/boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.77.1">
+<link rel="home" href="index.html" title="Chapter 1. Boost.GIL.IO">
+<link rel="next" href="gil/io/tutorial.html" title="Tutorial">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table cellpadding="2" width="100%"><tr>
+<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../boost.png"></td>
+<td align="center">Home</td>
+<td align="center">Libraries</td>
+<td align="center">People</td>
+<td align="center">FAQ</td>
+<td align="center">More</td>
+</tr></table>
+<hr>
+<div class="spirit-nav"><a accesskey="n" href="gil/io/tutorial.html"><img src="../../../../../doc/src/images/next.png" alt="Next"></a></div>
+<div class="chapter">
+<div class="titlepage"><div>
+<div><h2 class="title">
+<a name="gil.io"></a>Chapter 1. Boost.GIL.IO</h2></div>
+<div><div class="author"><h3 class="author">
+Christian Henning
+</h3></div></div>
+<div>Copyright © 2012 Christian Henning</div>
+<div><div class="legalnotice">
+<a name="gil.io.legal"></a>
+ Distributed under the Boost Software License, Version 1.0. (See accompanying
+ file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ 
+</div></div>
+</div></div>
+<div class="toc">
+Table of Contents
+<dl>
+<dt>Overview</dt>
+<dt>Tutorial</dt>
+<dt>Using IO</dt>
+<dt>Running gil::io tests</dt>
+</dl>
+</div>
+<div class="section gil_io_overview">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="gil.io.overview"></a><a class="link" href="index.html#gil.io.overview" title="Overview">Overview</a>
+</h2></div></div></div>
+
+ This extension to boost::gil provides an easy to use interface for reading
+ and writing various image formats. It also includes a framework for adding
+ new formats.
+ 
+
+ Please see section 3.3 for all supported image formats. A basic tutorial is
+ provided in section <a class="link" href="gil/io/tutorial.html" title="Tutorial">Tutorial</a>. Also,
+ this extension requires Boost version 1.42 and up. Furthermore the gil extension
+ Toolbox is used.
+ 
+
+ For adding new image formats please refer to section <a class="link" href="gil/io/using_io.html#gil.io.using_io.extending_gil__io_with_new_formats">Extending
+ GIL::IO with new Formats</a>.
+ 
+<h3>
+<a name="gil.io.overview.h0"></a>
+ <a name="gil.io.overview.supported_platforms"></a><a class="link" href="index.html#gil.io.overview.supported_platforms">Supported
+ Platforms</a>
+ </h3>
+
+ All platforms supported by boost which have a decent C++ compiler. Depending
+ on the image format one or more of the following image libraries might be needed:
+ 
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem">
+ libtiff
+ </li>
+<li class="listitem">
+ libjpeg
+ </li>
+<li class="listitem">
+ libpng
+ </li>
+<li class="listitem">
+ libraw
+ </li>
+<li class="listitem">
+ zlib
+ </li>
+</ul></div>
+
+ The library is designed to support as many formats as required by the user.
+ For instance, if the user only needs bmp support none of the above mentioned
+ dependencies are required.
+ 
+
+ There are more details available in this documentation on the image format
+ dependencies. Please see section <a class="link" href="gil/io/using_io.html#gil.io.using_io.supported_image_formats">Supported
+ Image Formats</a>.
+ 
+</div>
+</div>
+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
+<td align="left">Last revised: March 06, 2013 at 01:32:50 GMT</td>
+<td align="right"><div class="copyright-footer"></div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav"><a accesskey="n" href="gil/io/tutorial.html"><img src="../../../../../doc/src/images/next.png" alt="Next"></a></div>
+</body>
+</html>

Modified: trunk/libs/gil/io/doc/io.qbk
==============================================================================
--- trunk/libs/gil/io/doc/io.qbk (original)
+++ trunk/libs/gil/io/doc/io.qbk 2013-03-05 20:43:46 EST (Tue, 05 Mar 2013)
@@ -1,7 +1,7 @@
[library Boost.GIL.IO
         [quickbook 1.3]
     [authors [Henning, Christian] ]
- [copyright 2012 Christian Henning]
+ [copyright 2013 Christian Henning]
     [purpose
         An generic, user-friendly interface for reading and writing different image formats.
     ]

Modified: trunk/libs/libraries.htm
==============================================================================
--- trunk/libs/libraries.htm (original)
+++ trunk/libs/libraries.htm 2013-03-05 20:43:46 EST (Tue, 05 Mar 2013)
@@ -160,6 +160,8 @@
 From Joel de Guzman, Dan Marsden and Tobias Schwinger.</li>
 <li>gil - Generic Image Library, from
 Lubomir Bourdev and Hailin Jin.</li>
+ <li>gil::io - Generic Image Library IO extension, from
+ Christian Henning.</li>
 <li>geometry - Geometry Library, from
 Barend Gehrels, Bruno Lalande and Mateusz Loskot.</li>
 <li>graph -
@@ -593,6 +595,8 @@
<ul>
 <li>gil - Generic Image Library, from
 Lubomir Bourdev and Hailin Jin.</li>
+ <li>gil::io - Generic Image Library IO extension, from
+ Christian Henning.</li>
</ul>

<h3><a name="IO">Input/Output</a></h3>

Modified: trunk/libs/maintainers.txt
==============================================================================
--- trunk/libs/maintainers.txt (original)
+++ trunk/libs/maintainers.txt 2013-03-05 20:43:46 EST (Tue, 05 Mar 2013)
@@ -46,7 +46,7 @@
fusion Joel de Guzman <joel -at- boost-consulting.com>, Dan Marsden <danmarsden -at- yahoo.co.uk>, Tobias Schwinger <tschwinger -at- isonews2.com>
function_types Tobias Schwinger <tschwinger -at- isonews2.com>
geometry Barend Gehrels<barend -at- xs4all.nl>, Bruno Lalande <bruno.lalande -at- gmail.com>, Mateusz Loskot <mateusz -at- loskot.net>
-gil Lubomir Bourdev <lbourdev -at- adobe.com>, Hailin Jin <hljin -at- adobe.com>
+gil Christian Henning <chhenning -at- gmail.com>
graph Andrew Sutton <asutton -at- cs.kent.edu>
heap Tim Blechmann <tim -at- klingt.org>
icl Joachim Faulhaber <afojgo -at- gmail.com>

Next message: john_at_[hidden]: "[Boost-commit] svn:boost r83329 - trunk/libs/math/test"
Previous message: afojgo_at_[hidden]: "[Boost-commit] svn:boost r83327 - in sandbox/icl/libs/xplore/value_sem/TreeSync1/TreeSync1: . Syncable"

Date view	Thread view	Subject view	Author view

Boost-Commit list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk