On Sun, Jan 5, 2014 at 12:38 PM, Nimit Shah <[email protected]> wrote: > Hi Chenxiong, > There is a synchronization service rework in pipeline and this would be a > great addition to it! I like the idea of making the experience of Plugins > and Synchronization services being similar. The user interface part can be > discussed further. > > Just building upon your idea, we can have a box with 2 columns. There are > only 2 changes that I would like to make to your idea: > - Instead of keeping available status,we can use 3 ways to represent the > synchronization services. The synchronization service name can be showing in > bold text (available and enabled), black text (available but not enabled) > and grey text(not available).
Sounds good. > - Clicking on an available service, you get the description and > configuration options on the right hand side. The bottom right corner of the It would be great to allow backend author to provide custom configuration dialog, either shown by clicking a button like the Plugin or be embedded in the right hand side. > column will have enable/disable button. > - Clicking on the unavailable service will show you a description and which > modules are missing. There will not be any configuration options or > enable/disable button. > > We can keep a similar interface for plugins. The major change being that in > plugins, we can enable several plugins without any need for configuration > and hence the enable/disable button needs to be out of the right column and > in the main box itself. > > > Nimit Shah > > > On Sun, Jan 5, 2014 at 9:30 AM, tkdchen <[email protected]> wrote: >> >> Hi folks, >> >> In my machine, some GTG dependencies are missed, that results in three >> backends cannot be imported. I know this only when launch gtg from the >> command line. And as a non-technical user like others, when open the >> Synchronization Service, they are not listed in the cadidate list, no >> way to know what sync services provided by GTG and why some of them >> cannot be used. It's not a bit of reasonable. >> >> I prefer to allow user to see all backends. The solution is, >> >> - give another status to each backend, might be named `available`. >> That means whether a backend is available for using. >> - backend author is responsible for claiming the environment including >> all dependencies to run the backend very clearly. >> - change synchronization service to be similar with Plugins dialog. >> - in the left side of the dialog is a TreeView to show all backends, >> and use checkbox to indicate to enable or disable a backend >> - in the right side, the area shows information of each backend, >> even the custom configuration interaction >> >> Actually, based on current implementation of Synchronization Service, >> the first two items are enough. That's it. What do you say? >> >> Regards, >> Chenxiong Qi >> >> http://about.me/tkdchen >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~gtg-contributors >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~gtg-contributors >> More help : https://help.launchpad.net/ListHelp > > -- A Python developer living in Beijing http://about.me _______________________________________________ Mailing list: https://launchpad.net/~gtg-contributors Post to : [email protected] Unsubscribe : https://launchpad.net/~gtg-contributors More help : https://help.launchpad.net/ListHelp
