Qt contributors summit 2017 Program: Difference between revisions
Fmeerkoetter (talk | contribs) (Add a BOF session for Qt OpcUa) |
|||
| Line 83: | Line 83: | ||
|- | |- | ||
! 11:00 - 11:50 | ! 11:00 - 11:50 | ||
| | | Qt CoAP protocol | ||
| | | | ||
|- | |- | ||
| Line 125: | Line 125: | ||
Frank Meerkötter | Frank Meerkötter | ||
A quick get together for people interested in OPC UA. I'd like to hear about your use-cases for Qt OPC UA. I'd also like to discuss the pros/cons of having a Qt-based implementation at all. Is there mostly interest in a C++ API? What about a QML API? What parts of OPC UA are used in the field? How to get the existing Qt OpcUa based code base off the ground? Is the approach of wrapping an existing implementation sane? Do we wrap the right implementation? Would it be a way forward to build on top of open62541? | A quick get together for people interested in OPC UA. I'd like to hear about your use-cases for Qt OPC UA. I'd also like to discuss the pros/cons of having a Qt-based implementation at all. Is there mostly interest in a C++ API? What about a QML API? What parts of OPC UA are used in the field? How to get the existing Qt OpcUa based code base off the ground? Is the approach of wrapping an existing implementation sane? Do we wrap the right implementation? Would it be a way forward to build on top of open62541? | ||
=== Qt CoAP protocol === | |||
Adrien Leravat | |||
We are contributing a CoAP protocol module for Qt, and would like to hear your inputs regarding current implementation and API. CoAP is a protocol similar to HTTP used in IoT contexts. I will explain a few use case, current status of contribution, and what's to be expected next. We can then have a look at the API and how it is designed to discuss openly these aspects. | |||
=== Next topic === | === Next topic === | ||
Revision as of 09:25, 16 June 2017
Back to Qt contributors summit 2017
This page is a placeholder, the event is in 2017
Monday 9.10.2017
| Time | bcc A level lobby |
|---|---|
| 9.00 - 9.30 | Registration |
| 9.30 - 10.15 | Welcome session and planning |
| Time | Room A3 | Room A4 | Room A5 | Room A6 |
|---|---|---|---|---|
| 10:30 - 11:20 | ||||
| 11:30 - 12:20 | ||||
| 12:20 - 13:20 | Lunch! | Lunch! | Lunch! | Lunch! |
| 13:20 - 14:10 | ||||
| 14:20 - 15:10 | ||||
| 15:20 - 16:10 | ||||
| 16:20 - 17:10 |
Tuesday 10.10.2017
On Tuesday we will have limited rooms. Enough space, but not so many rooms.
| Time | Room 1 | Room 2 |
|---|---|---|
| 9:00 - 9:50 | ||
| 10:00 - 10:50 | ||
| 11:00 - 11:50 | Qt CoAP protocol | |
| 12:00 - 12:50 | ||
| 13:00 - 13:50 | Lunch! | Lunch! |
| 14:00 - 14:50 | ||
| 15:00 - 15:50 | BOF Qt OpcUa | |
| 16:00 - 16:50 | ||
| 17:00 - 17:15 | Thank you! |
Session descriptions for Monday
Topic
Name of owner
Short description. Two or three sentences that get the point across to the reader. Move this text forward, so there is an example for the next person editing.
Session descriptions for Tuesday
BOF Qt OpcUa
Frank Meerkötter
A quick get together for people interested in OPC UA. I'd like to hear about your use-cases for Qt OPC UA. I'd also like to discuss the pros/cons of having a Qt-based implementation at all. Is there mostly interest in a C++ API? What about a QML API? What parts of OPC UA are used in the field? How to get the existing Qt OpcUa based code base off the ground? Is the approach of wrapping an existing implementation sane? Do we wrap the right implementation? Would it be a way forward to build on top of open62541?
Qt CoAP protocol
Adrien Leravat
We are contributing a CoAP protocol module for Qt, and would like to hear your inputs regarding current implementation and API. CoAP is a protocol similar to HTTP used in IoT contexts. I will explain a few use case, current status of contribution, and what's to be expected next. We can then have a look at the API and how it is designed to discuss openly these aspects.
Next topic
Name of owner
Short description. Two or three sentences that get the point across to the reader. Move this text forward, so there is an example for the next person editing.