Anonymous user
Talk:Bitmap/Histogram: Difference between revisions
→Task description: i am not the creator of that task
(It is not about the number of colors) |
(→Task description: i am not the creator of that task) |
||
Line 22:
::: It already is [[grayscale image|see here]]. "Bitmap storage" is a task, which was intended, as I understand it, to define types and/or other language objects necessary to deal with images. Histogram type/class, call it is as you wish, logically belongs there. It extends that package. If you want to restructure it, I think you should discuss it there, or ask [[User:ShinTakezou]], who created it. --[[User:Dmitry-kazakov|Dmitry-kazakov]] 16:55, 16 January 2009 (UTC)
::::: I've not created the [[grayscale image]] task, nor the [[basic bitmap storage]] task; I've created the [[read image file through a pipe]], which is "complementar" to [[PPM conversion through a pipe]]. I suppose there's nothing odd asking a "pragmatic" usage of a task, that also works like an example of usage of a function that complete the task. There are many other tasks having usage example. The B/W (even though using the grayscale output, using just two levels, Black and White) through histogram "analysis" is so easy ans simple that likely it does not throw shadows over the real task. --[[User:ShinTakezou|ShinTakezou]] 22:47, 18 January 2009 (UTC)
:::: No, no, no and no. The link you gave is '''not''' B/W image, it is grayscale image. I am talking about the B/W conversion that is specified in '''this''' task. And it should '''not''' be in this task. It is an entirely separate function from histogram calculation. The idea of Rosetta Code is to have separate simple programming tasks impemented in different languages. There is no point putting multiple unrelated tasks into a single task definition.
| |||