Thomas Witt | 1 May 01:04
Picon
Favicon

[1.34.0] Deadline


Hi,

I will not accept any changes to 1.34.0 whatsoever starting Thursday May 3. 
Please make sure you report all problems/fixes/doc changes till then.

Only real show stoppers (i.e. build might start thermonuclear war) will be
considered after that date.  

That notwithstanding please DO NOT SUBMIT to RC_1_34_0 without prior approval.

Thanks

Thomas

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

Thomas Witt | 1 May 01:17
Picon
Favicon

Re: Boost 1.34.0 Beta released

In article <nemoMon043007034944 <at> alphaone.com> Thomas Witt
<witt <at> acm.org> wrote:

> <nothing/>

Did I mention my newsreader is in Beta?

The new getting started is in the release

more/getting_started/index.html

We can't update the website yet.

HTH

Thomas

> 
> _______________________________________________
> Unsubscribe & other changes:
> http://lists.boost.org/mailman/listinfo.cgi/boost
> 

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

Cromwell Enage | 1 May 01:18
Picon
Favicon
Gravatar

Re: [1.34.0] Deadline

--- Thomas Witt wrote:
> Hi,
> 
> I will not accept any changes to 1.34.0 whatsoever
> starting Thursday May 3. 
> Please make sure you report all problems/fixes/doc
> changes till then.

A few somewhat-recently accepted libraries (e.g. ASIO,
Fusion, Interprocess, MPI, PropertyTree) are available
in both the beta distribution and via CVS but are not
advertised in either libs/libraries.htm or
doc/html/index.html; will their presence at least be
announced in the news section of the home page during
the official release?

                              Cromwell D. Enage

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

Thomas Witt | 1 May 01:48
Picon
Favicon

Re: [1.34.0] Deadline

In article <624789.81580.qm <at> web53912.mail.re2.yahoo.com> Cromwell Enage
<sponage <at> yahoo.com> wrote:

> A few somewhat-recently accepted libraries (e.g. ASIO,
> Fusion, Interprocess, MPI, PropertyTree) are available
> in both the beta distribution and via CVS but are not
> advertised in either libs/libraries.htm or
> doc/html/index.html; will their presence at least be
> announced in the news section of the home page during
> the official release?

As of now there is no such plan. They are not part of the official release
and as such are not mentioned in the docs.

Thomas

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

Kim Barrett | 1 May 02:18

Re: [1.34.0] Deadline

At 4:18 PM -0700 4/30/07, Cromwell Enage wrote:
>A few somewhat-recently accepted libraries (e.g. ASIO,
>Fusion, Interprocess, MPI, PropertyTree) are available
>in both the beta distribution and via CVS

I don't see any of these in the beta distribution; specifically, they
aren't in the tar.bz2 package I downloaded last week.

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

Jeff Garland | 1 May 03:05

Re: 1.35 release approach (was [1.34.0] Deadline)

Thomas Witt wrote:
> In article <624789.81580.qm <at> web53912.mail.re2.yahoo.com> Cromwell Enage
> <sponage <at> yahoo.com> wrote:
> 
>> A few somewhat-recently accepted libraries (e.g. ASIO,
>> Fusion, Interprocess, MPI, PropertyTree) are available
>> in both the beta distribution and via CVS but are not
>> advertised in either libs/libraries.htm or
>> doc/html/index.html; will their presence at least be
>> announced in the news section of the home page during
>> the official release?
> 
> As of now there is no such plan. They are not part of the official release
> and as such are not mentioned in the docs.
> 

To clarify, none of the listed libraries are in the beta distribution I have. 
  And property tree isn't in CVS yet AFAICS.

Most of these libraries should be in 1.35, which will hopefully be released 
'quickly'.  By quickly, I mean ~1.5 months...which means a beta release 1 
month  after 1.34.  Yep, that's right, I think we need to set some very hard 
goals to re-energize the boost release process. After the '1.34 experience' 
I've become even more of an advocate a hard line release approach. That is, we 
should set the deadline and only accept code that can make it in the release 
timeframe -- if it's not ready then we take it out and let it slide to the 
next release.

To minimize risk of delay and release the pent-up backlog of new libraries I 
believe we should hold all existing 1.34 libs constant and only add in new 
(Continue reading)

Philippe Vaucher | 1 May 03:53
Picon

Re: boost::timers finalization

On 4/30/07, Sebastian Redl <sebastian.redl <at> getdesigned.at> wrote:
>
> It is implemented and works. I've got a 2.6.14 kernel 64-bit Gentoo with
> a 2.5 glibc.

I found why my device_doesn't work, it's because I time a usleep(), and for
some reasons I ignore it refuses to work.

Here's a code to illustrate it :

#include <iostream>
#include <cstdio>
#include <ctime>

#include <sys/time.h>

using namespace std;

inline void test_usleep(int milliseconds)
{
    usleep(milliseconds * 1000);
}

inline void do_something()
{

    for(int i = 0; i < 10000; ++i)
        cout << 1 << '\b' << flush;
}

(Continue reading)

Tom Brinkman | 1 May 04:16
Picon

[gil] added hsl color space to gil

The HSL color space is a needed addition.  I took a quick look and I'll try
it out soon, but it looks good.  It follows the lead of the adobe gil
developers and uses mpl::vector3, which I think is a pretty clever use of
mpl.  I'll give some more feedback within a week or so.
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

Lubomir Bourdev | 1 May 04:26
Picon
Favicon

Re: [gil] added hsl color space to gil

Christian,

I looked at your code and it looks great. Thanks! (though I haven't
verified the formulas).

One suggestion: It is trivial to make it work for any HSB channel (not
just bits32f).
Simply channel_convert from the source to your intermediate format
(bits32f) and then channel_convert the result back to the destination.
For improved performance, in the future we can add specializations for
concrete channel types that could use shortcut formulas, but for now
converting to/from float should be fine.

Lubomir

> -----Original Message-----
> From: boost-bounces <at> lists.boost.org [mailto:boost-
> bounces <at> lists.boost.org] On Behalf Of Christian Henning
> Sent: Monday, April 30, 2007 6:04 AM
> To: boost <at> lists.boost.org
> Subject: [boost] [gil] added hsl color space to gil
> 
> Hi guys, I have added the HSL color space as an extension to gil. The
> code is structured similar to other color spaces, like rgb. You can
> get the code at
> 
> http://gil-
>
contributions.googlecode.com/svn/trunk/gil_2/boost/gil/extension/toolbo
> x/hsl.hpp
(Continue reading)

Christian Henning | 1 May 04:45
Picon

Re: [gil] added hsl color space to gil

Hi Lubomir, just added hsv color space. If you want to check the
formulars just use the hsl.cpp test code. It generates some color
plates that show the formulars seems working.

> One suggestion: It is trivial to make it work for any HSB channel (not
> just bits32f).
> Simply channel_convert from the source to your intermediate format
> (bits32f) and then channel_convert the result back to the destination.
> For improved performance, in the future we can add specializations for
> concrete channel types that could use shortcut formulas, but for now
> converting to/from float should be fine.

I was sticking to bits32f for now since I don't know how to handle the
hue value correctly. I would like to add some algorithms where the hue
value is represented in degrees, you know like 60 ( can't find the
small circle on my keyboard ;-) ). So, such a value doesn't quite fit
in 0...255 but in 0...359. Any ideas are welcome.

I actually stumpled on an "interesting" problem with defining the
channel names. Both the hsl and the hsv spaces share the same hue_t
and saturation_t structs. Please review my solution and write me what
you think.

The more I work with the more I like it. I learn quite a bit I can tell you. ;-)

Christian
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

(Continue reading)


Gmane