Am 23.02.2011 19:08, schrieb Joachim Ott:
Hello Christian,
can you split your program into 2 parts:
- a daemon, that does the real work, with dbus interface, maybe
written in vala instead of python to have a smaller daemon
- a gui, that just shows scan results, active connections, buttons to
start/stop connections, set parameters and such
The advantages would be:
- you can start the daemon at system startup and have your favorite
connections established automatically in background
- start the gui only to search/connect new networks, change settings
and unload it again, thus saving RAM
- the connections don't go down if X is restarted, like it happens
with iliwi and such
This was my plan from the beginning, but since this is my first attempt
of writing an application with dbus, bluetooth and elf and I first tried
to get a concept and overview of what I'm doing in one application
before I try to split it up.
From the early beginning I had an eye on the interfaces between "the
daemon parts" and the gui to keep the communication between easy and in
a few places.
After I solve the problem with the blocking dbus calls I will attend to
the next step.
Chris
_______________________________________________
Shr-User mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-user
