Port backends to Q/KProcess
Open, Needs TriagePublic

Description

@rishabhg was accepted as GSoC'2017 student. His work is described below:

The main aim of this project is to port all the backends to make use of standard streams for communication. At the moment, Cantor use different methods to communicate with the backends. Some of them use C Api, some use D-Bus protocol and some have already been making use of Q/K process.

This project is important since this way Cantor will make use of a standard technology to implement backend and it will enable the use of Cantor in different operational systems.

This task will help to track the subtasks related to the project.

Good luck @rishabhg. :)

@rishabhg you must to develop your project in a different branch of Cantor. Only after finish it we will merge in master.

@rishabhg you must to develop your project in a different branch of Cantor. Only after finish it we will merge in master.

@filipesaraiva Thank you creating these tasks and yes I will most probably carry out the work of every back end in a separate branch

Hum I was thinking here @rishabhg, Julia backend uses DBus too. Maybe you need to port that to Q/KProcess as well. Let's see how you work with those listed backends.

According to T6111 and T6211, we choose port the backends to QProcess.

sirgienko added a subscriber: sirgienko.EditedSep 4 2018, 8:58 PM

@filipesaraiva, GSoC'2017 ended, but this task is still important, so maybe better remove info about GSoC and use the describtion from GSoC task (The main aim of this project...)?

filipesaraiva renamed this task from Port backends to Q/KProcess - Google Summer of Code 2017 to Port backends to Q/KProcess.Oct 11 2018, 10:17 PM
filipesaraiva removed rishabhg as the assignee of this task.