I don't know why people are giving you grief over whether or not your question is about development methodologies, or whether a perfect solution exists, as if either are reasons alone to close your question. While it's true there is a technical definition to "development methodology", using it in a colloquial sense to mean "a high-level method to handle a programming problem" is still on-topic and exactly what Programmers is for.

To me, it's pretty clear that's what your question is looking for—high-level design advice—and it's definitely a practical problem someone would actually face. So in that sense, What kind of questions should I not ask here? section of the FAQ doesn't apply.

However, your question is lacking one crucial thing, which thorsten müller tried to draw out:

Why exactly do you want to disregard those solutions? They work reasonably well for most needs. Most other solutions would need to directly access the pixel data (after putting the image in a canvas element), which would be slow and a lot of work to implement. (That at least if it needs to be done within a web site)

Or, to put it another way, your question doesn't address what you've tried. If you expand your question to explain why the solutions you've found so far are not sufficient, and—even better—go into what you've tried yourself (and where you came up short), your question would be perfectly fine and I'd vote to reopen it.

I don't know why people are giving you grief over whether or not your question is about development methodologies, or whether a perfect solution exists, as if either are reasons alone to close your question. While it's true there is a technical definition to "development methodology", using it in a colloquial sense to mean "a high-level method to handle a programming problem" is still on-topic and exactly what Programmers is for.

To me, it's pretty clear that's what your question is looking for—high-level design advice—and it's definitely a practical problem someone would actually face. So in that sense, What kind of questions should I not ask here? section of the FAQ doesn't apply.

However, your question is lacking one crucial thing, which thorsten müller tried to draw out:

Why exactly do you want to disregard those solutions? They work reasonably well for most needs. Most other solutions would need to directly access the pixel data (after putting the image in a canvas element), which would be slow and a lot of work to implement. (That at least if it needs to be done within a web site)

Or, to put it another way, your question doesn't address what you've tried. If you expand your question to explain why the solutions you've found so far are not sufficient, and—even better—go into what you've tried yourself (and where you came up short), your question would be perfectly fine and I'd vote to reopen it.

I don't know why people are giving you grief over whether or not your question is about development methodologies, or whether a perfect solution exists, as if either are reasons alone to close your question. While it's true there is a technical definition to "development methodology", using it in a colloquial sense to mean "a high-level method to handle a programming problem" is still on-topic. To me, it's pretty clear that's what your question is looking for: for high-level design advice which is exactly what Programmers is for.

However, your question is lacking one crucial thing, which thorsten müller tried to draw out:

Why exactly do you want to disregard those solutions? They work reasonably well for most needs. Most other solutions would need to directly access the pixel data (after putting the image in a canvas element), which would be slow and a lot of work to implement. (That at least if it needs to be done within a web site)

Or, to put it another way, your question doesn't address what you've tried. If you expand your question to explain why the solutions you've found so far are not sufficient, and—even better—go into what you've tried yourself (and where you came up short), your question would be perfectly fine and I'd vote to reopen it.

I don't know why people are giving you grief over whether or not your question is about development methodologies, or whether a perfect solution exists, as if either are reasons alone to close your question. While it's true there is a technical definition to "development methodology", using it in a colloquial sense to mean "a high-level method to handle a programming problem" is still on-topic and exactly what Programmers is for. 

To me, it's pretty clear that's what your question is looking for—high-level design advice—and it's definitely a practical problem someone would actually face. So in that sense, What kind of questions should I not ask here? section of the FAQ doesn't apply.

However, your question is lacking one crucial thing, which thorsten müller tried to draw out:

Why exactly do you want to disregard those solutions? They work reasonably well for most needs. Most other solutions would need to directly access the pixel data (after putting the image in a canvas element), which would be slow and a lot of work to implement. (That at least if it needs to be done within a web site)

Or, to put it another way, your question doesn't address what you've tried. If you expand your question to explain why the solutions you've found so far are not sufficient, and—even better—go into what you've tried yourself (and where you came up short), your question would be perfectly fine and I'd vote to reopen it.