I was pulled off a hot! project to work on another hot! project after being pulled off a previous hot! project, and now, after two hours of searching I am still unable to find the relevant files and pick the first hot! project back up.
And my partners wonder why so many projects take so long...
Deliverables, boyos, deliverables. As in, allowing your programmer to meet one once in a friggin' while.
Late edit: found the files. In any case, it turns out the "Prototype" javascript library is incompatible with my existing javascript work* and so can't be used**. That's okay though...there's only a couple things I would need it for anyway, and I can write my own wrappers for that. There's also an "X" library that provides many similar functions, and doesn't conflict.
P.S. There will be a post about the weekend - which was awesome - but it will come later after I put some miles between me and the current crises.
* I thought for...in with associative arrays was okay...apparently it's not. ***
** Meaning I have to more or less start over on the original hot! project anyway.
*** For the two of you that might be interested, the Prototype library adds a bunch of methods and properties to array handling that, when for...in is used, are iterated as if they were elements of the array. I have no idea why someone thought that was useful when the use of the for loop is ubiquitous, but there it is.
And my partners wonder why so many projects take so long...
Deliverables, boyos, deliverables. As in, allowing your programmer to meet one once in a friggin' while.
Late edit: found the files. In any case, it turns out the "Prototype" javascript library is incompatible with my existing javascript work* and so can't be used**. That's okay though...there's only a couple things I would need it for anyway, and I can write my own wrappers for that. There's also an "X" library that provides many similar functions, and doesn't conflict.
P.S. There will be a post about the weekend - which was awesome - but it will come later after I put some miles between me and the current crises.
* I thought for...in with associative arrays was okay...apparently it's not. ***
** Meaning I have to more or less start over on the original hot! project anyway.
*** For the two of you that might be interested, the Prototype library adds a bunch of methods and properties to array handling that, when for...in is used, are iterated as if they were elements of the array. I have no idea why someone thought that was useful when the use of the for loop is ubiquitous, but there it is.