lcgamboa

I made all the modifications you requested. Sorry for the lack of comments in the source code, it really is my fault for not being used to working in a...

Yes I have learned a lot working on Ripes. As for the rebase, as my branch is based on your `external_io` branch, I believe you have to rebase it first...

I usually prefer to work with binary protocols because of the ease of decoding a datagram using only structs and using less processing (in C or C++). On the other...

I know but have never used protobuf's. I usually use more bare-metal solutions because I'm used to developing for embedded systems. I would use something like: ``` typedef struct{ uint32_t...

I have implemented a protocol for testing using QTcpSocket (because Ripes already uses it). The problem is that QTcpSocket is asynchronous, I haven't found a way to make it work...

I've come across some solutions like yours using QFuture, but I found it too cumbersome to use thread synchronization just to replace what a simple blocking call to the standard...

I created an XTcpSocket class (using normal sockets with blocking) to replace the QTcpSocket class, in the first tests it is working without problems on Linux. After testing it on...

The first integration tests of Ripes with PICSimLab were very satisfactory. I have implemented two 16-bit GPIO ports, so it is possible to access almost all PICSimLab devices. But going...

I asked initially because all peripherals already implemented in Ripes have addresses incremented from 4 to 4. As in the case of the D-Pad which has 1 bit and each...

Despite the problem with the size of the reading generated by Ripes (explained in the previous message), it is possible to test with PICSimLab. I published the changes for integration...