{"id":338,"date":"2008-12-03T00:22:45","date_gmt":"2008-12-03T04:22:45","guid":{"rendered":"http:\/\/itp.indiamos.com\/blog\/?p=338"},"modified":"2009-04-14T01:12:29","modified_gmt":"2009-04-14T06:12:29","slug":"baby-steps","status":"publish","type":"post","link":"https:\/\/itp.indiamos.com\/blog\/2008\/12\/03\/baby-steps\/","title":{"rendered":"Baby steps"},"content":{"rendered":"

\"grid<\/a><\/p>\n

This is the second smidgen of the code for our final project. It<\/a> pulls RGB values and color names from a tab-delimited text file<\/a> (which is, itself, based on the actual Krylon color options<\/a>) and outputs this grid of swatches. The swatches don’t do<\/em> anything yet—just drawing them took me, like, two days, thank you very much, and that was with<\/em> some very helpful help from Shawn. Partly this is because I apparently can’t keep in my head for more than thirty seconds how arrays and objects work, and partly it’s because I just. can’t. focus. And partly it’s because I apparently have no idea what the fuck I’m doing.<\/p>\n

I’m beginning to really like Diego’s Plan B, as proposed over the weekend: <\/p>\n

\n\tFake our own deaths.\n<\/p><\/blockquote>\n


\nI keep telling myself I have to not panic and just write the code one piece at a time. Then, later, I can get somebody to help me put it all together, which is something I know<\/em> I have no clue how to do. But just accomplishing what seem like they should be simple things is stumping me. Most recently, I was trying to get the swatch name to be displayed when a square is rolled over. This is not by any means an important feature—in fact, it doesn’t really serve any purpose. But I should<\/em> be able to do it, and I can’t figure out why it doesn’t work. I keep getting errors like “The function showName() does not exist” or “Cannot find anything named ‘swatches.'” Both of these things do, of course, exist, and I can’t see any reason why they wouldn’t be found.<\/p>\n

I know it’s pretty rare for computers to just fuck up<\/em> and much more common for me<\/em> to do so, so I’m sure the answer is that I’ve done something really dumb and sloppy somewhere. But it could easily take me two hours to find that error, and every new goddamn line of code seems to cause some new mysterious issue. I can feel myself growing older just thinking about it. And there are a lot more lines of code to go. Here’s the stuff I was hoping to get done, oh, by, say, last Thursday: <\/p>\n

\n

Graffiti Glove Components<\/h3>\n

Brush selector<\/h4>\n