Arch Linux

https://github.com/FireyFly/TermKit

last commit was on 9 days ago, probably the last remmanent living in this point

termkit

Error: require.paths is removed. Use node_modules folders, or the NODE_PATH environment variable instead.
at Function.Object.defineProperty.get (module.js:388:11)
at Object.<anonymous> (/usr/lib/node_modules/termkit/Node/nodekit.js:5:8)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Function.Module.runMain (module.js:497:10)
at startup (node.js:119:16)
at node.js:901:3
$

any idea??

this is easily fixed: just remove the braces around 'npm.install' (only one install file allowed, so a string instead of an array), and remove the nodejs-npm dependency.

Syntax of File is not up to date,
Node has npm in there by default...

I will temporarily disown this package and hope that someone smarter than me steps up to sort it out. I will still get notifications and will update the package if I get it solved. I wish there was a "broken" tag...

google-chrome fails to load protocol.js... I've being looking where it comes from but I'm no node.js expert, anyone knows why this happens??

Same result in Chromium (which is webkit based).

@DarwinSurvivor:
I am not sure you CAN use firefox since this is a webkit-based terminal and might thus only work with those browsers (chrom(e/ium), rekonq, surf, midori, eve, ...).
For the more general issue with a blank screen, I have tried to change git branch to:
git://github.com/lucassmagal/TermKitLinux.git
but that did not help and there I got installation issues related to the nodej.
If someone is more familiar with these things, I would be more than happy to disown these packages in favour of someone more competent as mantainer.

connecting to localhost:2222 (Firefox 5) just gives a black screen (like pg-termkit does). Anyone else have this?

@neokuno
No I did not know that. That sounds very interesting!

@WFCody:
Using browser as a client is not a 'real' solution.
Do you know there is a pygtk client in the latest TermKit repository?
It is reasonably good that using a dedicated program as client rather than using browser.

@WFCody:
Using browser as a client is not a 'real' solution.
Do you know there is a pygtk client in the latest TermKit repository?
It is reasonably good that using a dedicated program as client rather than using browser.

@WFCody:
Using browser as a client is not a 'real' solution.
Do you know there is a pygtk client in the latest TermKit repository?
It is reasonably good that using a dedicated program as client rather than using browser.

@neokuno: I agree that this will be cleaner and it also means that I only have 1 problem with this package: the npm installation and I can isolate the problem with the script starting the server + a browser acting as a client.

This really should separate into two packages, one server(daemon) and one client.
And the client should be free to implement, use whatever technology you like, chromium, pygtk, gnome seed ... so on.

Just a thought... perhaps I should keep the termkit itself and the browser launcher as sepparate packages? This way termkit is just a dependency for the browser launcher.

This really seems to be a tough one. But to make your current version work in the first place, you have to do a chmod +x ${pkgdir}/usr/bin/Termkit. I'd also recommend to put chromium into the depends line, because chromium is in the repos, google-chrome is not. In case other webkit browsers work as well, you might have to find another solution.

OK... A very ugly attempt. IF anyone is familiar with npm, I am interested in making npm install with a prefix pointing to $pkgdir rather than pulling all sources. Another issue is to make a startup script that starts the termkit server and launches a compatible (webkit) browser pointing to the correct port. In a single thread I either get a browser started prior to the server is active or the browser never starts because the script is stuck on starting the server.