> There are many different parts of SynCE, as we all know. All of these
> parts seem catered for on the command line (select_partnership.py, pls,
> pcp, msynctool --sync..) Availability on your desktop is a different
> story though. For example:
>
> File browsing:
>    GNOME: gnomevfs
>    KDE:   rapip (needs separating from synce-kde perhaps)

Again, I really think we should package this separately, because it will be 
benefecial for everybody, since I don't want to encourage people using wm5+ 
devices to install the whole current synce-kde stuff, just to get rapip 
working.


>
> Application management:
>    GNOME: --
>    KDE:   synce-kdm

Working on it :)


>
> Connection state (bit of a loose example here!):
>    GNOME: trayicon
>    KDE:   -- (perhaps synce-kdm in the future?)

That is basically already done within synce-kdm. The moment you plugin your 
phone, it detects this and acts upon this. Same holds for unplug. I have to 
look into some examples of QSystemTrayIcon, but then I could get synce-kdm to 
minimize to system tray also.


>
> Password entry if required:
>    GNOME: synce-gnome && traycon IIRC
>    KDE:   -- (but perhaps synce-kdm soon?)

I might copy the code of synce-gnome regarding the password stuff, but can't 
test at the moment. What exactly happens when you lock yourself out, and how 
bad is that? Does it need a hard reset?

>
> Registry editor (option, of course):
>    GNOME: registry-tool
>    KDE:   --

Since I updated the synce-registry tool I found that accessing the reg is 
quite slow if you want to download it as a whole. If you would like to only 
list the 'active open keys' it might be possible to do quite fast. Would be 
nice idea to implement this as a future version in synce-kdm (imho is part of 
device management ;) )


>
> kcemirror-esque application:
>    GNOME: -- (Mark, you said you'd created a clone?)
>    KDE:   kcemirror (obviously)

If kcemirror has some easy way of starting, I could start it from within 
synce-kdm.


>
> Partnership management:
>    GNOME: --
>    KDE:   --

I could look at the partnership code within the sync-engine, might be possible 
to use that as a base to do the partnership stuff from within synce-kdm also. 
Should be not too hard I guess.

But for all of the above, where gnome is missing, I would like to try and set 
up the code nicely, meaning that i would like to separate the data layer from 
the GUI layer. This means that somebody later on could write just a PyGTK GUI 
around this easily meaning we only have one codebase to maintain, plus two 
gui layers.

It would mean that we would create a synce-DM (SynCE Device Manager) with a 
KDE and GNOME frontend to it.

>
> Anyway, those are the basic tools for desktops (excluding syncing). This
> list points out two things: some desktops have missing applications; and
> there are an awful number of different applications for the same
> desktop.
> For example, with GNOME, it would be great if trayicon lived in your
> tray (obviously) and it: managed partnerships, notified  the user upon
> device connection/disconnection, displayed a password entry if needed,
> managed application installation/removal, and contained up a
> Gtk-kcemirror-esque app. (Perhaps even contain the registry editor?)
> SynCE is already in so many parts that having yet more desktop
> applications would be bad..
>
> I'd love for people to install everything needed for great usage of
> SynCE with: libsynce, librapi2, librra, odccm, sync-engine, synce-gnome
> (replace gnome with kde where appropriate).
>
> The desktop syncing question is a whole different thing. I personally
> would stick with a third-party syncing app like we're doing at the
> moment with opensync. Perhaps my ideal trayicon application (detailed
> above) could skip through setting up a SynCE group for OpenSync and call
> "sync"..? OpenSync has actually got a D-BUS interface.
> (Another option could be to use Conduit. This, however, is whole
> different I will not discuss here. I would hate a raki-esque tool for
> only syncing SynCE to be created. A waste of time in my opinion.)

In that way it would be an option to set it up: thus I use the GUI to start 
calling the needed other stuff for syncing.


>
> I hope some of this makes sense. I kind-of diverged from the subject of
> dccms onto desktop applications.
>
> Thoughts?

All in the above lines ;)

Guido Diepen



-- 
Aviation is proof that given the will, we have the 
capacity to achieve the impossible.
     --Eddie Rickenbacker

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
SynCE-Devel mailing list
SynCE-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synce-devel

Reply via email to