a looking-glass book

dilemma

(yes, im working on thanksgiving.)

is it better to store all info in the format of seconds? this means that the backend will all be in the same format, but will require some math every time i want to spit it out. (or just once and stored in a variable.)

or...i store in a more human readable format for things (which is the way i have been doing it) but it means that i have to do do conversions the other way to be able to compare timecode.

i guess in the end it doesnt really matter - i have to convert one way to the other regardless. and i suppose since i already have most of the timecode stuff in a human readable format, there isnt any reason to shift it from that. (although, in the db, times would be stored then as largeints, as opposed to 'time'. but i dont think that truly matters either.)

i suppose i could dig around to see if i could find an argument, but im just not caring right now.

i just wanted to reason through it.

also, the page i am writing is getting annoying. i (fear i) am going to have to split it up, though im not sure how yet.

the architecture depends greatly on the functionality. and since that isnt completely defined yet, i imagine itll mean one of two things: 1. lots o rewrites or 2. lots of little pieces that i can plug and replug. (which i think comes down to lots o iframes. oi.)

happy thanksgiving.