TermKit.app shows me a black window with no interaction opportunities

[maghoff]

On OS X 10.6.8.

I seem to be able to run the back-end well enough:

mag@lebigmac:~/prog/TermKit/Node$ node nodekit.js 
   info  - socket.io started

I then start the front-end:

mag@lebigmac:~/prog/TermKit/Build$ ./TermKit.app/Contents/MacOS/TermKit 
2012-01-21 12:45:52.356 TermKit[12355:903] loadView loading URL: file://localhost/Users/mag/prog/TermKit/Build/TermKit.app/Contents/Resources/HTML/index.html
2012-01-21 12:45:52.358 TermKit[12355:903] info plist: 0.3.4-alpha

If I check back on the server side, the following has been output:

   debug - client authorized
   info  - handshake authorized
   info  - handshaken 352cfae1a7389dffa40143803fd76167
   debug - setting request GET /socket.io/1/websocket/352cfae1a7389dffa40143803fd76167
   debug - publishing that 352cfae1a7389dffa40143803fd76167 connected
   debug - initializing client store for 352cfae1a7389dffa40143803fd76167
   debug - set heartbeat interval for client 352cfae1a7389dffa40143803fd76167
   debug - subscribing 352cfae1a7389dffa40143803fd76167
   debug - websocket writing 1::
   debug - websocket writing 4:::{"termkit":"1","timestamp":1327146353055}
   debug - websocket received data packet 3:::[object Object]
   debug - got packet
   debug - websocket received data packet 3:::[object Object]
   debug - got packet
   debug - emitting heartbeat for client 352cfae1a7389dffa40143803fd76167
   debug - websocket writing 2::
   debug - set heartbeat timeout for client 352cfae1a7389dffa40143803fd76167
   debug - websocket received data packet 2::
   debug - got heartbeat packet
   debug - cleared heartbeat timeout for client 352cfae1a7389dffa40143803fd76167
   debug - set heartbeat interval for client 352cfae1a7389dffa40143803fd76167

And so on, with the heartbeats.

In short: There does not seem to be anything wrong.

Yet, all I can see in the TermKit.app window is a black void. Apart from the window chrome there is only uniform black color. Typing on the keyboard does not effect any change.

I have tried opening the web inspector, and it seems to have loaded a DOM document and lots of scripts. There are no error messages waiting for me.

---

I guess the conclusion is: TermKit doesn't complain about anything, yet it does not work. I would be happy to fix any problems it reported, but it reports no problems.

[derDoc]

You on OSX 10.7?
You need to recompile TermKit.app from source, or use one of the ones provided around here.
(I have added an x64 build to my forked TermKit, in case you're interested...)

[maghoff]

I'm on 10.6.

Compiling from source solved the problem for me.

However, I will let the issue stay open, because failure to work with no error message might be worth looking into anyway.

(Incidentally, I tried compiling from source before I created this issue, but I couldn't get it to work because I was writing xbuild [mono-tool] instead of xcodebuild. Silly me)

[fxthomas]

I'm on 10.7 with the same issue (with both unzipped TermKit.app and manually built app).
Shame, TermKit looked really cool and I looking forward to it...

[karlbohlmark]

I had the same issue, but it worked when I manually compiled Termkit.app (It didn't compile right away though)
I'm on 10.7

[fxthomas]

Now, I got it to work a little by removing the "require()" lines in the source, but every command I type fails... I don't have time to check this out right now, but that was just to let you guys know!