mirror of
https://github.com/socketio/socket.io-client-cpp.git
synced 2026-06-09 19:54:46 +00:00
add QT demo project tutorials
This commit is contained in:
parent
8dcaf8ff3e
commit
0c5b723cb2
282
Tutorial.md
Normal file
282
Tutorial.md
Normal file
@ -0,0 +1,282 @@
|
||||
In this tutorial we’ll learn how to create a QT chat application that communicates with a [Socket.IO Node.JS chat server](https://github.com/Automattic/socket.io/tree/master/examples/chat).
|
||||
###Introduction
|
||||
To follow along, start by cloning the repository: [socket.io-client-cpp](https://github.com/socketio/socket.io-client-cpp).
|
||||
Using:
|
||||
|
||||
```bash
|
||||
git clone --recurse-submodules https://github.com/socketio/socket.io-client-cpp.git
|
||||
```
|
||||
|
||||
The app has the following features:
|
||||
|
||||
*Sending a message to all users joining to the room.
|
||||
*Notifies when each user joins or leaves.
|
||||
*Notifies when an user start typing a message.
|
||||
|
||||
###Install QT community
|
||||
Visit [QT community download link](http://www.qt.io/download-open-source/#section-2) to get the install package.
|
||||
Just install it with default installation option.
|
||||
|
||||
###Create a QT GUI application.
|
||||
Launch QT Creator.
|
||||
In welcome page, select `New Project`, There you can create a `QT Widget Application`, We named it `SioChatDemo`
|
||||
You'll see the project structure is like:
|
||||
|
||||
```
|
||||
SioChatDemo
|
||||
|__ SioChatDemo.pro
|
||||
|__Headers
|
||||
| |__mainwindow.h
|
||||
|__Sources
|
||||
| |__main.cpp
|
||||
| |__mainwindow.cpp
|
||||
|__Forms
|
||||
|__mainwindow.ui
|
||||
```
|
||||
|
||||
###Import SioClient and config compile options.
|
||||
You can copy the SioClient into the QT project as a subfolder `sioclient`.
|
||||
|
||||
Edit `SioChatDemo.pro` to config paths and compile options, simply add:
|
||||
|
||||
```bash
|
||||
SOURCES += ./sioclient/src/sio_client.cpp \
|
||||
./sioclient/src/sio_packet.cpp
|
||||
|
||||
HEADERS += ./sioclient/src/sio_client.h \
|
||||
./sioclient/src/sio_message.h
|
||||
|
||||
INCLUDEPATH += $$PWD/sioclient/lib/rapidjson/include
|
||||
INCLUDEPATH += $$PWD/sioclient/lib/websocketpp
|
||||
```
|
||||
|
||||
We need also add two additional compile option
|
||||
|
||||
```bash
|
||||
CONFIG+=no_keywords
|
||||
CONFIG+=c++11
|
||||
```
|
||||
|
||||
`no_keywords` is for preventing qmake treat some function's name `emit` as the keyword of signal-slot mechanism.
|
||||
`c++11` ask for C++11 support.
|
||||
|
||||
##Import boost
|
||||
Suppose you now have your boost `headers` and a fat boost `static lib` named `libboost.a`(non-win32) or `boost.lib`(win32) ready.
|
||||
|
||||
To import them you need to Edit `SioChatDemo.pro` again,add header include:
|
||||
|
||||
```bash
|
||||
INCLUDEPATH += `your boost headers folder`
|
||||
```
|
||||
|
||||
also linker option:
|
||||
|
||||
```bash
|
||||
win32:CONFIG(release, debug|release): LIBS += -L`your Win32 boost static lib folder` -lboost
|
||||
else:win32:CONFIG(debug, debug|release): LIBS += -L`your Win32 boost static lib folder` -lboost
|
||||
else:unix: LIBS += -L`your osx boost static lib folder` -lboost
|
||||
```
|
||||
|
||||
###Make up mainwindow ui.
|
||||
We can make up a simple ui by drag and drop widget from `Widget box` in left side.
|
||||
|
||||
We finally end up with this:
|
||||

|
||||
it contains:
|
||||
|
||||
*a `QLineEdit` at the top for nickname inputing, named `nickNameEdit`
|
||||
*a `QPushButton` at the topright for login, named `loginBtn`
|
||||
*a `QListWidget` at the center for showing messages, named `listView`
|
||||
*a `QLineEdit` at the bottom for typing message, named `messageEdit`
|
||||
*a `QPushButton` at the bottomright for sending message, named `sendBtn`
|
||||
|
||||
###Add Slots in mainwindow
|
||||
We need add slots in `mainwindow` class to handle UI events
|
||||
They are
|
||||
* click login
|
||||
* click send message
|
||||
* message text change (for typing status)
|
||||
* message edit returned (for sending message by return)
|
||||
Insert following code into `MainWindow` class in `mainwindow.h`
|
||||
|
||||
```C++
|
||||
public Q_SLOTS:
|
||||
void SendBtnClicked();
|
||||
void TypingChanged();
|
||||
void LoginClicked();
|
||||
void OnMessageReturn();
|
||||
```
|
||||
|
||||
###Connect UI event signal and slots together
|
||||
Open `mainwindow.ui` in Design mode. switch to `signals/slots` mode by check `Menu->Edit->Edit Signals/Slots`
|
||||
|
||||
By press left mouse on widget and drag on to the window (cursor will become a sign of electrical ground), to open the connection editor.
|
||||
|
||||
In the connection editor, edit the slots of MainWindow at the right side, add Those slots function name added in `mainwindow.h` before.
|
||||
|
||||
Then you'll be able to connect the event signal from widget with your own slots.
|
||||
|
||||
We finally end up with this:
|
||||

|
||||
|
||||
###Adding UI refresh Signals/Slots
|
||||
We may need request UI refresh in `sio::client` callbacks which may not be in UI thread, So we need `Signal` for non-UI thread to request `Slots` functions been executed in UI thread. Say we have to signal `QListWidgetItem` being added, we need to add:
|
||||
|
||||
```C++
|
||||
//In mainwindow.h
|
||||
Q_SIGNALS:
|
||||
void RequestAddListItem(QListWidgetItem *item);
|
||||
private Q_SLOTS:
|
||||
void AddListItem(QListWidgetItem *item);
|
||||
```
|
||||
|
||||
```C++
|
||||
//In mainwindow.cpp
|
||||
void MainWindow::AddListItem(QListWidgetItem* item)
|
||||
{
|
||||
this->findChild<QListWidget*>("listView")->addItem(item);
|
||||
}
|
||||
```
|
||||
|
||||
We also need to connect them in `MainWindow` constructor.
|
||||
|
||||
```C++
|
||||
connect(this,SIGNAL(RequestAddListItem(QListWidgetItem*)),this,SLOT(AddListItem(QListWidgetItem*)));
|
||||
```
|
||||
|
||||
###Init sio::client in MainWindow
|
||||
Since we are making a single window application, we let `MainWindow` class holding the `sio::client`.
|
||||
declare a `unique_ptr` member of `sio::client` and Several event handling functions in `mainwindow.h`
|
||||
|
||||
```C++
|
||||
private:
|
||||
void OnNewMessage(std::string const& name,message::ptr const& data,bool hasAck,message::ptr &ack_resp);
|
||||
void OnUserJoined(std::string const& name,message::ptr const& data,bool hasAck,message::ptr &ack_resp);
|
||||
void OnUserLeft(std::string const& name,message::ptr const& data,bool hasAck,message::ptr &ack_resp);
|
||||
void OnTyping(std::string const& name,message::ptr const& data,bool hasAck,message::ptr &ack_resp);
|
||||
void OnStopTyping(std::string const& name,message::ptr const& data,bool hasAck,message::ptr &ack_resp);
|
||||
void OnLogin(std::string const& name,message::ptr const& data,bool hasAck,message::ptr &ack_resp);
|
||||
void OnConnected();
|
||||
void OnClosed(client::close_reason const& reason);
|
||||
void OnFailed();
|
||||
|
||||
std::unique_ptr<client> _io;
|
||||
```
|
||||
|
||||
Init `sio::client` and setup event bindings in `MainWindow` constructor.
|
||||
|
||||
Now the `MainWindow` constructor:
|
||||
|
||||
```C++
|
||||
MainWindow::MainWindow(QWidget *parent) :
|
||||
QMainWindow(parent),
|
||||
ui(new Ui::MainWindow),
|
||||
_io(new client())
|
||||
{
|
||||
ui->setupUi(this);
|
||||
using std::placeholders::_1;
|
||||
using std::placeholders::_2;
|
||||
using std::placeholders::_3;
|
||||
using std::placeholders::_4;
|
||||
_io->bind_event("new message",std::bind(&MainWindow::OnNewMessage,this,_1,_2,_3,_4));
|
||||
_io->bind_event("user joined",std::bind(&MainWindow::OnUserJoined,this,_1,_2,_3,_4));
|
||||
_io->bind_event("user left",std::bind(&MainWindow::OnUserLeft,this,_1,_2,_3,_4));
|
||||
_io->bind_event("typing",std::bind(&MainWindow::OnTyping,this,_1,_2,_3,_4));
|
||||
_io->bind_event("stop typing",std::bind(&MainWindow::OnStopTyping,this,_1,_2,_3,_4));
|
||||
_io->bind_event("login",std::bind(&MainWindow::OnLogin,this,_1,_2,_3,_4));
|
||||
_io->set_connect_listener(std::bind(&MainWindow::OnConnected,this));
|
||||
_io->set_fail_listener(std::bind(&MainWindow::OnFailed,this));
|
||||
_io->set_close_listener(std::bind(&MainWindow::OnClosed,this,_1));
|
||||
connect(this,SIGNAL(RequestAddListItem(QListWidgetItem*)),this,SLOT(AddListItem(QListWidgetItem*)));
|
||||
}
|
||||
```
|
||||
|
||||
###Managing connection state
|
||||
We have several connection listeners for connection events.
|
||||
First we want to send login message once we're connected.
|
||||
|
||||
```C++
|
||||
void MainWindow::OnConnected()
|
||||
{
|
||||
QByteArray bytes = m_name.toUtf8();
|
||||
std::string nickName(bytes.data(),bytes.length());
|
||||
_io->emit("add user", nickName);
|
||||
}
|
||||
```
|
||||
|
||||
Then if connection is closed or failed, we need to restore to the UI before connect.
|
||||
|
||||
```C++
|
||||
void MainWindow::OnClosed(client::close_reason const& reason)
|
||||
{
|
||||
//restore UI to pre-login state
|
||||
}
|
||||
|
||||
void MainWindow::OnFailed()
|
||||
{
|
||||
//restore UI to pre-login state
|
||||
}
|
||||
|
||||
```
|
||||
|
||||
If `MainWindow` is exit, we need to clear event bindings and listeners.
|
||||
|
||||
the `sio::client` object will be destruct by `unique_ptr`
|
||||
|
||||
```C++
|
||||
MainWindow::~MainWindow()
|
||||
{
|
||||
_io->clear_event_bindings();
|
||||
_io->clear_con_listeners();
|
||||
delete ui;
|
||||
}
|
||||
```
|
||||
|
||||
###Handle socket.io events
|
||||
You'll need to handle socket.io events in your functions bind to socket.io events.
|
||||
For example, we need to show received messages to the `listView`
|
||||
|
||||
```C++
|
||||
void MainWindow::OnNewMessage(std::string const& name,message::ptr const& data,bool hasAck,message::ptr &ack_resp)
|
||||
{
|
||||
if(data->get_flag() == message::flag_object)
|
||||
{
|
||||
std::string msg = data->get_map()["message"]->get_string();
|
||||
std::string name = data->get_map()["username"]->get_string();
|
||||
QString label = QString::fromUtf8(name.data(),name.length());
|
||||
label.append(':');
|
||||
label.append(QString::fromUtf8(msg.data(),msg.length()));
|
||||
QListWidgetItem *item= new QListWidgetItem(label);
|
||||
//emit RequestAddListItem signal
|
||||
//so that 'AddListItem' will be executed in UI thread.
|
||||
Q_EMIT RequestAddListItem(item);
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
###Sending chat message
|
||||
When `sendBtn` is clicked, we need to send the text in `messageEdit` to chatroom.
|
||||
Add code to `SendBtnClicked()`:
|
||||
|
||||
```C++
|
||||
void MainWindow::SendBtnClicked()
|
||||
{
|
||||
QLineEdit* messageEdit = this->findChild<QLineEdit*>("messageEdit");
|
||||
QString text = messageEdit->text();
|
||||
if(text.length()>0)
|
||||
{
|
||||
QByteArray bytes = text.toUtf8();
|
||||
std::string msg(bytes.data(),bytes.length());
|
||||
_io->emit("new message",msg);//emit new message
|
||||
text.append(":You");
|
||||
QListWidgetItem *item = new QListWidgetItem(text);
|
||||
item->setTextAlignment(Qt::AlignRight);
|
||||
Q_EMIT RequestAddListItem(item);
|
||||
messageEdit->clear();
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
###Further reading
|
||||
If you want to learn more, I recommanded you to look into the [Demo project](https://github.com/socketio/socket.io-client-cpp/tree/master/examples/QT/SioChatDemo) for other features.
|
||||
|
||||
BIN
screenshots/Qmainwindow.jpg
Normal file
BIN
screenshots/Qmainwindow.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 44 KiB |
BIN
screenshots/SignalsSlots.jpg
Normal file
BIN
screenshots/SignalsSlots.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 33 KiB |
Loading…
x
Reference in New Issue
Block a user