RGB Rangefinder Notes
RGB Rangefinder Versions
RGB Rangefinder is a program I've been working on solo. These versions are known to work with IE8
RGB Rangefinder v10 March 8, 2014
New Capability: Click R%G%B% as static row button, and you are returned in a table a list of the named colors closest to the color you input; the list tells you how close each color is to the color you input. Problem is that it is still buggy-- when you first click on the 'R%G%B% as static row button' nothing happens and you have to click on it a second time to get the program going. And, after refresh of the page you have to reset the inputs to 100, 100, 100, and run the program with the inputs at 100, 100, 100, or otherwise the program will not work. When you first load the page to get the program going you have to click twice on the 'R%G%B% as static row button' and run it once at the default 100 100 100 setting to get it working. 100 100 100 is the default input.
Tech Notes: Suffice it to say that the javascript engine sometimes behaves erratically while a program is being built, and that such can drive even a sane genius nuts. Too tired to expound at length re all I suffered through now.
RGB Rangefinder v9 March 7, 2014
Added Capability: Using the percentage rgb button, one can now make a static row that is part of the background/foreground table, represent whatever color you want it to. Unlike the other rows in the background/foreground table, this added row is not changed when a ranging-process is done on a color and returned to the background/foreground table. Sitting at my desk doing deep thinking re the capabilities of the program, I decided that this static row was the top priority.
Tech Notes: Attempted to set up a form in an unfamiliar environment (form encapsulated triple-nested table). Micromanaging CSS via inline CSS became necessary as normal CSS failed due to nesting of table. This created clutter of code. In clutter of code, I failed to realize that I had placed a 'name-blah' tag not in the input tag where I wanted to place it, but rather, in the td tag holding the input. The form being built in an unfamiliar environment, the triple-nested table, with new unfamiliar content (multiple action-buttons in one form) led me to suspect all kinds of problems aside from the reality of the name-identifier having been placed in the wrong tag. I removed the form from encapsulating a triple-nested table, changed that to encapsulating a nested table, and it worked, but I am not sure if it would have worked encapsulating a triple-nested table. Have to be aware of how dull sweatshopish work emplacing inline-styles, and the code-clutter such creates, can lead to fatigue/boredom as a result of which one misses basic facts such as the name-identifier being placed in the wrong tag. I suspect that as opposed to tiring myself out working on this program, as a result of which I fail to exercise, I now need to forget programming prioritize exercise and program when resting from exercise, which I have not done for a few days.
RGB Rangefinder v8 March 6, 2014
Added capability: RGB Rangefinder v8, keeps track of all the color choices you have made in a table which: lists the time at which you took your action; what action you took; the color you applied with your action; the proportional range you applied if you were applying a range; and, the absolute range you applied if you were applying a range.
Tech Notes: according to alert-box, the code of a programmatically-assembled link, was a properly written link, with all the quotation marks in the correct places; but, when this link, was placed in a row, which was then inserted in the history table, the code of the link became distorted and the link became dysfunctional, as a check re the innerHTML of the table verified. The Problem was that upon integrating the row into the table, the js engine helpfully added quotation marks around the javascript:blah() which was inside the inserted table-row, according to the report of the inner-html of the table in question, received from the alert box. This resulted in duplication of quotation marks whenI tried to write out the quotation marks perfectly, result being some of the quotation marks being replaced with question-marks, and the link being dysfunctional. Writing out the function-triggering javascript links without the quotation marks worked fine. And I'm a Sherlock Holmes to figure that out.
RGB Rangefinder v7 March 4, 2014
Added background-changing links to middle columns of bacgkround/foreground table, and added box showing color link will turn background to in outside columns of background/foreground table.
Tech Notes: Suffered from absent-minded mistakes (not that I am especially absent-minded, but in building these things there is so much on the mind that it is easy to miss something). Got distracted by turmoil and confusion amongst programmers who teach and learn via the internet, due to a desire to learn a couple more ways of doing something that I already know how to do.
RGB Rangefinder v6 March 2, 2014
Added capability: the color loaded as background in the background/foreground table, can now be sent to the rangefinder for processing to show specified ranges for it. I was plagued by absent-minded mistakes while adding this capability.
Tech Notes: While adding this capability, made absent-minded mistakes (need some time off from programming?). The program has become more and more complicated. I find myself drowning in a sea of multiple copies of stylesheets, of external javascripts, and of the HTML page itself; more than once I caught myself, editing the wrong copy of a stylesheet, javascript, or html page.
RGB Rangefinder v5 March 1, 2014
Added interaction with my own original color-picker, which is mathematically based to produce a perfectly balanced sample of colors.
Tech Notes: production of this version required huge sacrifice in terms of mental stress. The javascript demon was out to make me insane again. There were two comment lines above a call to a function in the opener window (//opener.document.getElementById('hometrigger').click();
//window.opener.alurt();). The function was not working. When I removed the comments, the line below the comments, (window.opener.cponepreranger();) worked. When I put the comments back in, it then continued to work! And the damned javascript is complex enough without such insane things happening. The entire program was held up for at least an hour because of such insane machine-flakiness that was not my fault, that made good code look bad, and that sent me looking for unnecessary solutions (result-me being tortured by false-gurus, verbosities, and obfuscators) and double-testing everything (such machine-flakiness has happened more than once).
Also, time/energy was eaten up due to another machine-error: an external type .js javascript file I created for the program did not work. When I clicked on the file in its folder, I received a '800A03EA', microsoft jscript compilation error' notice, which I had never received before; restart of PC did not fix things. I did not get this notice with any of my other .js files. On the internet I encountered much turmoil confusion and bad advice re the '800A03EA' error, and no good advice. My original hackish but effective solution to the problem (born of a kind of thinking produced by never having anyone to help me with programming problems): copy an existing .js file that is working; empty it out; rename it; and then use it. It will work even though for some reason every new .js file you create does not work and gives you an error notice.
RGB Rangefinder v4 February 28, 2014
Added ability to range colors based on name input of color such as 'red', 'green', 'blue'. This is a trick that has completely stumped the programming world till now. The code I used to do the trick is original, not learned from others.
RGB Rangefinder v3 February 27, 2014
RGB Rangefinder v2 February 2, 2014
RGB Rangefinder v1 January 31, 2014
RGB Rangefinder is a program I've been working on solo. These versions are known to work with IE8
RGB Rangefinder v10 March 8, 2014
New Capability: Click R%G%B% as static row button, and you are returned in a table a list of the named colors closest to the color you input; the list tells you how close each color is to the color you input. Problem is that it is still buggy-- when you first click on the 'R%G%B% as static row button' nothing happens and you have to click on it a second time to get the program going. And, after refresh of the page you have to reset the inputs to 100, 100, 100, and run the program with the inputs at 100, 100, 100, or otherwise the program will not work. When you first load the page to get the program going you have to click twice on the 'R%G%B% as static row button' and run it once at the default 100 100 100 setting to get it working. 100 100 100 is the default input.
Tech Notes: Suffice it to say that the javascript engine sometimes behaves erratically while a program is being built, and that such can drive even a sane genius nuts. Too tired to expound at length re all I suffered through now.
RGB Rangefinder v9 March 7, 2014
Added Capability: Using the percentage rgb button, one can now make a static row that is part of the background/foreground table, represent whatever color you want it to. Unlike the other rows in the background/foreground table, this added row is not changed when a ranging-process is done on a color and returned to the background/foreground table. Sitting at my desk doing deep thinking re the capabilities of the program, I decided that this static row was the top priority.
Tech Notes: Attempted to set up a form in an unfamiliar environment (form encapsulated triple-nested table). Micromanaging CSS via inline CSS became necessary as normal CSS failed due to nesting of table. This created clutter of code. In clutter of code, I failed to realize that I had placed a 'name-blah' tag not in the input tag where I wanted to place it, but rather, in the td tag holding the input. The form being built in an unfamiliar environment, the triple-nested table, with new unfamiliar content (multiple action-buttons in one form) led me to suspect all kinds of problems aside from the reality of the name-identifier having been placed in the wrong tag. I removed the form from encapsulating a triple-nested table, changed that to encapsulating a nested table, and it worked, but I am not sure if it would have worked encapsulating a triple-nested table. Have to be aware of how dull sweatshopish work emplacing inline-styles, and the code-clutter such creates, can lead to fatigue/boredom as a result of which one misses basic facts such as the name-identifier being placed in the wrong tag. I suspect that as opposed to tiring myself out working on this program, as a result of which I fail to exercise, I now need to forget programming prioritize exercise and program when resting from exercise, which I have not done for a few days.
RGB Rangefinder v8 March 6, 2014
Added capability: RGB Rangefinder v8, keeps track of all the color choices you have made in a table which: lists the time at which you took your action; what action you took; the color you applied with your action; the proportional range you applied if you were applying a range; and, the absolute range you applied if you were applying a range.
Tech Notes: according to alert-box, the code of a programmatically-assembled link, was a properly written link, with all the quotation marks in the correct places; but, when this link, was placed in a row, which was then inserted in the history table, the code of the link became distorted and the link became dysfunctional, as a check re the innerHTML of the table verified. The Problem was that upon integrating the row into the table, the js engine helpfully added quotation marks around the javascript:blah() which was inside the inserted table-row, according to the report of the inner-html of the table in question, received from the alert box. This resulted in duplication of quotation marks whenI tried to write out the quotation marks perfectly, result being some of the quotation marks being replaced with question-marks, and the link being dysfunctional. Writing out the function-triggering javascript links without the quotation marks worked fine. And I'm a Sherlock Holmes to figure that out.
RGB Rangefinder v7 March 4, 2014
Added background-changing links to middle columns of bacgkround/foreground table, and added box showing color link will turn background to in outside columns of background/foreground table.
Tech Notes: Suffered from absent-minded mistakes (not that I am especially absent-minded, but in building these things there is so much on the mind that it is easy to miss something). Got distracted by turmoil and confusion amongst programmers who teach and learn via the internet, due to a desire to learn a couple more ways of doing something that I already know how to do.
Added capability: the color loaded as background in the background/foreground table, can now be sent to the rangefinder for processing to show specified ranges for it. I was plagued by absent-minded mistakes while adding this capability.
Tech Notes: While adding this capability, made absent-minded mistakes (need some time off from programming?). The program has become more and more complicated. I find myself drowning in a sea of multiple copies of stylesheets, of external javascripts, and of the HTML page itself; more than once I caught myself, editing the wrong copy of a stylesheet, javascript, or html page.
Added interaction with my own original color-picker, which is mathematically based to produce a perfectly balanced sample of colors.
Tech Notes: production of this version required huge sacrifice in terms of mental stress. The javascript demon was out to make me insane again. There were two comment lines above a call to a function in the opener window (//opener.document.getElementById('hometrigger').click();
//window.opener.alurt();). The function was not working. When I removed the comments, the line below the comments, (window.opener.cponepreranger();) worked. When I put the comments back in, it then continued to work! And the damned javascript is complex enough without such insane things happening. The entire program was held up for at least an hour because of such insane machine-flakiness that was not my fault, that made good code look bad, and that sent me looking for unnecessary solutions (result-me being tortured by false-gurus, verbosities, and obfuscators) and double-testing everything (such machine-flakiness has happened more than once).
Also, time/energy was eaten up due to another machine-error: an external type .js javascript file I created for the program did not work. When I clicked on the file in its folder, I received a '800A03EA', microsoft jscript compilation error' notice, which I had never received before; restart of PC did not fix things. I did not get this notice with any of my other .js files. On the internet I encountered much turmoil confusion and bad advice re the '800A03EA' error, and no good advice. My original hackish but effective solution to the problem (born of a kind of thinking produced by never having anyone to help me with programming problems): copy an existing .js file that is working; empty it out; rename it; and then use it. It will work even though for some reason every new .js file you create does not work and gives you an error notice.
RGB Rangefinder v4 February 28, 2014
Added ability to range colors based on name input of color such as 'red', 'green', 'blue'. This is a trick that has completely stumped the programming world till now. The code I used to do the trick is original, not learned from others.
RGB Rangefinder v3 February 27, 2014
RGB Rangefinder v2 February 2, 2014
RGB Rangefinder v1 January 31, 2014
posted by David Virgil at 2:29 AM
0 Comments:
Post a Comment
<< Home