[interfacekit] Re: Hook functions + work done

Fun flies when you're doin' time (a favorite of my father that I will 
probably repeat eternally now that I am a father myself ;).  Seriously 
though, sorry about the drop out, guys.  Between work and my ISP 
folding, staying on top of stuff has been a nightmare.

There is reasonably good news, however.  Work has mellowed considerably 
over the beginning of this week; we may actually ship not only on time, 
but also without any (known) issues and a with a few extra features that 
were originally scheduled for the next point release.  Yay for us!  
Additionally, my DSL is scheduled to get re-connected (via a new ISP) on 
the 12th.  Now if I can just get NetworkSolutions to let me move my 
domain hosting ... =[

I've also managed to find a little time to ponder the nature of 
app_server/interface kit communication (look for something written about 
this in the near future) as well as doing some more serious work on the 
true nature of BArchivable, along with instantiate_object & co.  It's 
still in progress, but I may actually check some stuff in under testing: 
 once I'm finished with it (another night or two of work, I figure), it 
will likely be an excellent unit test for our replacement code.  So I'm 
happy about that anyway.  Now onto some overdue replies.

>    OK, so when I said I'd be able to bang out the hook functions, I 
had no 
>idea that it would be as big a task as it has been. I know Yuri and 
Erik have 

Heh.  I had a feeling it would end up being hairy.  Haven't done a lot 
of what you'd call straight to the metal graphics programming though, so 
I thought I'd keep quiet. ;)

>able to. I *think* I've gotten the basic setup stuff done. Don't quote 
me on 
>that, though. ;)

What does this consist of, exactly?

>    Next on the list I'd say would be fleshing out the non-accelerated 
hook 
>functions and begin the *real* work - layers, windows, and so forth. 
It's 
>probably a wise idea for us to get something to see before we 
experiment with 
>doing the code to allow us to drop our test server in for a "let's plug 
it in 
>and see what happens just for the heck of it." If you guys want the 
code (I 
>fixed the crash-and-burn bug BTW), I'll send it to you or post it to my 
WWW 
>site, but I still don't think it's quite worth it to upload it to the 
server 
>yet. It's at the point where it's fun to toy with, though. :)

Yes, please do post it (don't send -- I'm still hating life on a 28K 
connection), I'm extremely interested to see what you've got happening.

e

Data is not information, and information is not knowledge: knowledge is 
not understanding, and understanding is not wisdom.
        - Philip Adams

Other related posts: