bugs/issue-0f058c9b238cbc19fa0c88834b1f997e97631aa0.yaml

   1 --- !ditz.rubyforge.org,2008-03-06/issue
   2 title: Consider whether transformation constructor should include height and width parameters.
   3 desc: ""
   4 type: :task
   5 component: libale
   6 release:
   7 reporter: David Hilvert <dhilvert@auricle.dyndns.org>
   8 status: :unstarted
   9 disposition:
  10 creation_time: 2009-02-16 18:48:18.619226 Z
  11 references: []
  12
  13 id: 0f058c9b238cbc19fa0c88834b1f997e97631aa0
  14 log_events:
  15 - - 2009-02-16 18:48:19.547700 Z
  16   - David Hilvert <dhilvert@auricle.dyndns.org>
  17   - created
  18   - ""
  19 - - 2009-02-19 14:04:47.366718 Z
  20   - David Hilvert <dhilvert@auricle.dyndns.org>
  21   - commented
  22   - |-
  23     Given the role of the ALE resize code in adapting a transformation to a new image,
  24     old image size would probably have to be embedded within either the transformation
  25     or within some other maintained structure, between the two of which transformation
  26     seems a reasonable resolution.  Hence, keeping height and width parameters within
  27     the constructor also seems reasonable.
  28 - - 2009-03-07 19:31:53.425420 Z
  29   - David Hilvert <dhilvert@auricle.dyndns.org>
  30   - commented
  31   - |-
  32     As an alternative to taking height and width parameters, the constructor could
  33     instead take an image instance.
  34 git_branch: