Skip to content

Commit

Permalink
reorder how to use section
Browse files Browse the repository at this point in the history
  • Loading branch information
@Floby
Floby committed May 19, 2011
1 parent 9bc2a18 commit 6057aca
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions Readme.md
View file
Expand Up @@ -37,8 +37,8 @@ Addresses following problems:
## How to use:

1. [Install node.js and npm](http://howtonode.org/how-to-install-nodejs).
3. Clone the TermKit repository
2. Run `npm install` in the root directory
2. Clone the TermKit repository
3. Run `npm install` in the root directory
4. Run the NodeKit daemon: `node Node/nodekit.js`
5. Unzip and run the Mac app in Build/TermKit.zip
5bis: Alternatively, navigate to http://localhost:2222/ with your webkit-based browser
Expand Down

7 comments on commit 6057aca

@hileon
Copy link

@hileon hileon commented on 6057aca May 20, 2011

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can I start termkit in a server, and use chrome browser to access it from another machine?

just tested install it in a debian(without X), and access it from chrome in a windows machine. but I can get only a black screen, no more content show up.

@Floby
Copy link
Owner Author

@Floby Floby commented on 6057aca May 20, 2011

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suppose you could. I will test in a bit.
In the meantime, you can check a few things:

  • the node daemon doesn't log any error
  • the chrome console (Ctrl+Maj+J) doesn't log any error
  • there is no 404 error in the network panel of the chrome developer tools

@hileon
Copy link

@hileon hileon commented on 6057aca May 20, 2011

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Floby
Copy link
Owner Author

@Floby Floby commented on 6057aca May 20, 2011

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep I found the cause. The address of the node daemon was hardcoded in the client code to localhost:2222. This is necessary when webkit is running in a native app because then it doesn't load its file through the webserver.
However, when loaded in a browser, socket.io default to the same host and address that the page is at.

A push is comming.

@Floby
Copy link
Owner Author

@Floby Floby commented on 6057aca May 20, 2011

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the jsonp error message is socket.io trying every transport method it knows from Websocket to jsonp polling (jsonp is the last) since it's not even the right host (localhost) none of them work.

@Floby
Copy link
Owner Author

@Floby Floby commented on 6057aca May 20, 2011

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fix is there

@hileon
Copy link

@hileon hileon commented on 6057aca May 20, 2011

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

works pretty fine now, thanks Floby.

Please sign in to comment.