From 162e2241863a42c21068652e899fd0810b1c54c8 Mon Sep 17 00:00:00 2001 From: John Cupitt Date: Sun, 5 Mar 2017 22:24:52 +0000 Subject: [PATCH] notes --- ChangeLog | 1 + TODO | 29 ++++++++++++----------------- 2 files changed, 13 insertions(+), 17 deletions(-) diff --git a/ChangeLog b/ChangeLog index 44719245..c50ba239 100644 --- a/ChangeLog +++ b/ChangeLog @@ -34,6 +34,7 @@ - vips_region_shrink() knows about alpha, helps dzsave and tiffsave - use expat, not libxml, for XML load ... removes a required dependency, since we get expat as part of glib +- new sequential mode infrastructure is faster and more flexible 8/12/16 started 8.4.5 - allow libgsf-1.14.26 to help centos, thanks tdiprima diff --git a/TODO b/TODO index 74f14f08..721da8bb 100644 --- a/TODO +++ b/TODO @@ -1,4 +1,16 @@ + + +- VIPS_META_SEQUENTIAL will be saved to vips files, then loaded back again argh + + we need to set a value that can't be saved + + do we need a seq cache for reducev as well? we could have up to a 3x + reduction there + + + + - vips_object_class_install_argument() should check for duplicate priorities, it's been behind a few nasty bugs @@ -9,23 +21,6 @@ vips_rot( smartcrop->sobel, &smartcrop->sobel90, VIPS_ANGLE_D90, NULL ) -- vips linecache has access there twice! - -- VIPS_META_SEQUENTIAL will be saved to vips files, then loaded back again argh - - we need to set a value that can't be saved - - do we need a seq cache for reducev as well? we could have up to a 3x - reduction there - - -- VIPS_META_SEQUENTIAL will be saved to vips files, then loaded back again argh - - we need to set a value that can't be saved - - do we need a seq cache for reducev as well? we could have up to a 3x - reduction there - -vips linecache has access there twice!