Hi all, I have successfully replaced the old gil::io extension with the new gil::io. The new io has been developed on and off over the last few years and I believe it's a great improvement over the old one. Before going into details I like thank everyone that has been helping me out along the way. I have learned a lot of things and I'm very grateful for the experience! There are numerous improvements and perhaps it's best to study the documentation before using it. Here are some noteworthy points that come to my mind: * updating code that uses the old version only requires to change the header from "boost/extension/io/jpeg_io.hpp" to "boost/extension/io/jpeg/jpeg_io_old.hpp" * new formats: bmp, pnm, raw, targa * read numerous meta information from images. See boost/gil/extension/io/png_tags.hpp for example. * use all sorts of file metaphers or file names, like FILE*, ifstream, stringstream, wstring, filesystem::path, etc * in-memory images are supported * read large images with a scanline_read_iterator * have access to the file format backend * etc. There are some items left for which I need help from the boost maintainers. * How do I hook up the gil::io documentation so it's build when all boost documentation is build? * Same for the test suite. * Should I update boost_release? Or should the new extension "simmer" for a while? Again thanks for everything, Christian
On 18 February 2013 23:13, Christian Henning <chhenning@gmail.com> wrote:
Hi all,
I have successfully replaced the old gil::io extension with the new gil::io. The new io has been developed on and off over the last few years and I believe it's a great improvement over the old one.
Before going into details I like thank everyone that has been helping me out along the way. I have learned a lot of things and I'm very grateful for the experience!
There are numerous improvements and perhaps it's best to study the documentation before using it. Here are some noteworthy points that come to my mind:
* updating code that uses the old version only requires to change the header from "boost/extension/io/jpeg_io.hpp" to "boost/extension/io/jpeg/jpeg_io_old.hpp" * new formats: bmp, pnm, raw, targa * read numerous meta information from images. See boost/gil/extension/io/png_tags.hpp for example. * use all sorts of file metaphers or file names, like FILE*, ifstream, stringstream, wstring, filesystem::path, etc * in-memory images are supported * read large images with a scanline_read_iterator * have access to the file format backend * etc.
Christian, Congratulations and thank you very much for your efforts! BTW, as the GIL.IO review manager, is it me who is supposed to notify the review Wizards to add "added in " for GIL.IO in the schedule? If yes, shall it be "in 1.54.0"? Best regards, -- Mateusz Loskot, http://mateusz.loskot.net
Hi Mateusz,
BTW, as the GIL.IO review manager, is it me who is supposed to notify the review Wizards to add "added in " for GIL.IO in the schedule?
I'm not sure.
If yes, shall it be "in 1.54.0"?
I think we are safe to go for 1.54. Do you know when the deadline is? Christian
On 22 February 2013 16:05, Christian Henning <chhenning@gmail.com> wrote:
BTW, as the GIL.IO review manager, is it me who is supposed to notify the review Wizards to add "added in " for GIL.IO in the schedule?
I'm not sure.
Christian, I'll take care of it.
If yes, shall it be "in 1.54.0"?
I think we are safe to go for 1.54.
OK
Do you know when the deadline is?
It looks like it's due in two months: https://svn.boost.org/trac/boost/roadmap Best regards, -- Mateusz Loskot, http://mateusz.loskot.net
On Feb 22, 2013, at 8:15 AM, Mateusz Loskot <mateusz@loskot.net> wrote:
On 22 February 2013 16:05, Christian Henning <chhenning@gmail.com> wrote:
BTW, as the GIL.IO review manager, is it me who is supposed to notify the review Wizards to add "added in " for GIL.IO in the schedule?
I'm not sure.
Christian, I'll take care of it.
If yes, shall it be "in 1.54.0"?
I think we are safe to go for 1.54.
OK
Do you know when the deadline is?
It looks like it's due in two months:
I see that no one has updated the calendar at http://www.boost.org/development with milestones for 1.54. I'll see what I can do about that. That being said, the deadline for new libraries is usually about six weeks before the release date, so I would not dawdle if I were you. -- Marshall Marshall Clow Idio Software <mailto:mclow.lists@gmail.com> A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait). -- Yu Suzuki
On 22 February 2013 21:05, Marshall Clow <mclow.lists@gmail.com> wrote:
On Feb 22, 2013, at 8:15 AM, Mateusz Loskot <mateusz@loskot.net> wrote:
On 22 February 2013 16:05, Christian Henning <chhenning@gmail.com> wrote:
BTW, as the GIL.IO review manager, is it me who is supposed to notify the review Wizards to add "added in " for GIL.IO in the schedule?
I'm not sure.
Christian, I'll take care of it.
If yes, shall it be "in 1.54.0"?
I think we are safe to go for 1.54.
OK
Do you know when the deadline is?
It looks like it's due in two months:
I see that no one has updated the calendar at http://www.boost.org/development with milestones for 1.54. I'll see what I can do about that.
That being said, the deadline for new libraries is usually about six weeks before the release date, so I would not dawdle if I were you.
Marshall, thanks for the update. I'll leave the matter of submission for release to Christian. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net
I see that no one has updated the calendar at http://www.boost.org/development with milestones for 1.54. I'll see what I can do about that.
That being said, the deadline for new libraries is usually about six weeks before the release date, so I would not dawdle if I were you.
Not dawdling means I should push the new lib to release branch within the next two weeks? Regards, Christian
On Feb 22, 2013, at 1:39 PM, Christian Henning <chhenning@gmail.com> wrote:
I see that no one has updated the calendar at http://www.boost.org/development with milestones for 1.54. I'll see what I can do about that.
That being said, the deadline for new libraries is usually about six weeks before the release date, so I would not dawdle if I were you.
Not dawdling means I should push the new lib to release branch within the next two weeks?
Something like that. Since there hasn't been a deadline set, there isn't a deadline ;-), but yes, I would shoot for the next few weeks. Make sure that you've fulfilled all the pieces here <https://svn.boost.org/trac/boost/wiki/ReleasePractices/ManagerCheckList#NewLibraryChecklist> and then ask the release managers for permission to merge to release. [ Note: The first thing the release managers will ask is have you fulfilled all the things on the checklist above ] -- Marshall Marshall Clow Idio Software <mailto:mclow.lists@gmail.com> A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait). -- Yu Suzuki
participants (3)
-
Christian Henning -
Marshall Clow -
Mateusz Loskot