Comment 2 for bug 793955

Hi Isak,

That's great news. Thanks for your initialive.

1) Core
I have an additional thought on this and I believe it could help: as
you might know, the file manager extension requires two servers which
are listening for clients (that Dropbox's design...). Maybe instead of
creating yet another server, we could re-use this one for the purpose
of communicating with potential GUI clients.

The protocol is not really nice, but it allows passing commands and
arguments. Check this post for more details on the protocol. Also look
at the attached PHP script which communicates with the client:
https://lists.launchpad.net/syncany-team/msg00010.html

What do you think?

2) ConfigPanel
What do you have in mind? Could you elaborate on that?

Cheers,
Philipp

On Tue, Jun 7, 2011 at 4:25 PM, isakkarlsson <email address hidden> wrote:
> I think this is a great idea and I've started working on an "api"
> service that will use json to communicate with clients. The ConfigPanel
> needs to be rethinked though (as some way of defining maybe the possible
> config values and then build the gui from that or whatever).
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/793955
>
> Title:
>  Daemonize Syncany Core & Externalize GUI
>
> Status in Syncany:
>  New
>
> Bug description:
>  The Syncany GUI is currently a core part of Syncany. Launching and
>  controlling Syncany without a GUI is not possible. In order to
>  interact with Syncany by other programs, it might be useful to
>  externalize the GUI in a separate application.
>
>  This bug is meant to discuss details for this blueprint:
>  https://blueprints.launchpad.net/syncany/+spec/daemonize-core
>
>  What do you guys think of that? How could this be realized? Any
>  volunteers?
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/syncany/+bug/793955/+subscribe
>