1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
|
/****************************************************************************
**
** Copyright (C) 2015 The Qt Company Ltd.
** Copyright (C) 2014 basysKom GmbH, author Bernd Lamecker <bernd.lamecker@basyskom.com>
** Contact: http://www.qt.io/licensing/
**
** This file is part of the QtWebChannel module of the Qt Toolkit.
**
** $QT_BEGIN_LICENSE:LGPL21$
** Commercial License Usage
** Licensees holding valid commercial Qt licenses may use this file in
** accordance with the commercial license agreement provided with the
** Software or, alternatively, in accordance with the terms contained in
** a written agreement between you and The Qt Company. For licensing terms
** and conditions see http://www.qt.io/terms-conditions. For further
** information use the contact form at http://www.qt.io/contact-us.
**
** GNU Lesser General Public License Usage
** Alternatively, this file may be used under the terms of the GNU Lesser
** General Public License version 2.1 or version 3 as published by the Free
** Software Foundation and appearing in the file LICENSE.LGPLv21 and
** LICENSE.LGPLv3 included in the packaging of this file. Please review the
** following information to ensure the GNU Lesser General Public License
** requirements will be met: https://www.gnu.org/licenses/lgpl.html and
** http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html.
**
** As a special exception, The Qt Company gives you certain additional
** rights. These rights are described in The Qt Company LGPL Exception
** version 1.1, included in the file LGPL_EXCEPTION.txt in this package.
**
** $QT_END_LICENSE$
**
****************************************************************************/
'use strict';
var readline = require('readline');
var QWebChannel = require('./qwebchannel.js').QWebChannel;
var websocket = require('faye-websocket');
var address = 'ws://127.0.0.1:12345';
var socket = new websocket.Client(address);
console.log('Chat client connecting to ' + address + ' (Ctrl-D to quit)');
var createReadlineInterface = function() {
var bye = function() {
console.log('Bye...');
process.exit(0);
}
var rlif = readline.createInterface({
input: process.stdin,
output: process.stdout
});
rlif.setPrompt('chat: ');
// Handle Ctrl-D and Ctrl-C
rlif.on('close', bye);
rlif.on('SIGINT', bye);
return rlif;
}
var createWebChannel = function(transport, rlif) {
return new QWebChannel(transport, function(channel) {
// We connect to the 'sendText' signal of the remote QObject
// Be aware, that the signal is named for the remote side,
// i.e. the server wants to 'send text'.
// This can be confusing, as we connect to the signal
// to receive incoming messages on our side
channel.objects.dialog.sendText.connect(function(message) {
process.stdout.cursorTo(0);
process.stdout.clearLine(0);
console.log(' << ' + message);
rlif.prompt();
// Go to end of existing input if any
rlif.write(null, {ctrl: true, name: 'e'})
});
rlif.on('line', function(line) {
var l = line.trim();
if (l !== '') {
process.stdout.moveCursor(0, -1);
process.stdout.cursorTo(0);
process.stdout.clearLine(0);
// The 'receiveText' slot of the remote QObject
// is called with our message.
// Again the naming is for the server side,
// i.e. the slot is used _by the server_ to receive text.
channel.objects.dialog.receiveText(l);
console.log(' >> ' + l);
}
rlif.prompt();
});
rlif.prompt();
});
}
socket.on('open', function(event) {
console.log("info: Client connected");
var transport = {
// We cant't do 'send: socket.send' here
// because 'send' wouldn't be bound to 'socket'
send: function(data) {socket.send(data)}
};
createWebChannel(transport, createReadlineInterface());
// QWebChannel has set up its onmessage handler
// on the transport in the constructor.
// Now we connect it to the websocket event.
socket.on('message', function(event) {
transport.onmessage(event);
});
});
socket.on('error', function (error) {
console.log('Connection error: ' + error.message);
process.exit(1);
});
socket.on('close', function () {
console.log('Connection closed.');
process.exit(1);
});
|
