Hi,
I wanted to let you know about an ongoing project of mine: a ncurses
interface
with json for connman written in C. This client interfaces will implement
basic
connection actions (e.g. no vpn nor fancy session management for the first
batch) and is meant to be more accessible than connmanctl and ligther than
python. All communications are done using json-c/libjson (because it's
handy and
can be used by other UI).
Here is the project diagram:
+--------------------------+
| Connman DBus's interface |
+------------^-------------+
|
| <----------------------+ DBus messages
|
+-----------v------------+
| Connman-json interface |
+-----------^------------+
|
| <----------------------+ Json-c structures
| |
+-------v--------+ |
| Json front-end | |
+--^----------^--+ |
| | |
| | <----------------+
| |
| +v-----------+
| | Ncurses UI |
| +------------+
|
| <---------------------------+ Json
|
+v---------+
| Other UI |
+----------+
"Json front-end" will be in charge of all data aggregation and operations
routing (close to Model-Controller in a Model View Controller pattern). Thus
ncurses will fill the View tasks.
I am currently finalizing the test of "Connman-json interface". This piece
is
basically a strip down of connmanctl with json-c integration.
If you have any thoughts/remarks don't hesitate, I know the code may not be
as
clean as possible but it's a start:
https://github.com/alan-mushi/connman/tree/ncurses/jsonclient
In the long term (when the development will be over), if you are interested
by
those functionalities, would you consider to merge it into the official
repository ?
Regards,
Thibault
_______________________________________________
connman mailing list
[email protected]
https://lists.connman.net/mailman/listinfo/connman
