Jump to content

Talk:Color of a screen pixel: Difference between revisions

Multiple examples OK!
(is this task about the language, or its environment?)
(Multiple examples OK!)
Line 7:
:just like any other task, this is based on the typical running environment for your program. However, I have added the line: "The mouse cursor may or may not have to be active in a gui created by your program." —[[User:tinku99|tinku99]]
:: So what happens when the typical running environment for a program is an emacs comint buffer? Or a web browser session? (I am thinking that this, like some other tasks here, has very heavy dependencies on the hosting environment. Perhaps such tasks should get a special category, and perhaps such tasks warrant multiple implementations based on different host environments for languages which do not abstract this kind of issue.) --[[User:Rdm|Rdm]] 18:38, 10 June 2010 (UTC)
::: If code has dependencies beyond what's guaranteed by the core language, [[Template:works with]] and [[Template:library]] are used to identify them. As far as it helps illuminate comparative relevant use of platform, implementations, libraries, etc., I very much ''like'' to see multiple code examples per language/task pair. The site software isn't very well constructed to make, e.g. comparison-by-library easy, but that is one of my ultimate aims. --[[User:Short Circuit|Michael Mol]] 22:52, 10 June 2010 (UTC)
 
Getting pixel information is a basic task related to "accessibility", "testing", and just "getting things done". Thats what programming is for in the first place. Its not a security problem if your are the owner of the computer, and that is what you want to do. If a particular language can not do the task, it should be put in its ignore list. The task should not be modified to fit that language. —[[User:tinku99|tinku99]]
Cookies help us deliver our services. By using our services, you agree to our use of cookies.