Lets kill synce-gnome

[John Carr]

Doing IRC support for synce means you see some things a lot. This is
one of them. People see synce-kde and synce-gnome and think, as a
gnome, they should use synce-gnome. The thing is, they really
shouldn't.

Up until recently, the only real file in that part of the repository
was called test.py. At some point, we renamed it to synce-gnome, threw
a setup.py and released it. But if you examine it, within the first 10
lines you will still see "TestApp". It is about as old as odccm and
was created to test out some of the odccm dbus API. Currently its only
useful function it has is to deal with user passwords. It also has no
hal-dccm support. It is called synce-gnome, but the extent of its
gnome integration is that it has a GTK password entry box. It doesn't
even have an icon, install a menu item or start as part of the
session. For an end user, it kinda sucks.

synce-trayicon more than removes the need for synce-gnome. I think
even synce-sync-engine can handle passwords on its own (if it needs
to).

So does anyone have any objections to me moving synce-gnome to the
obsolete branch?

John

[Guido Diepen]

Post by John Carr
Doing IRC support for synce means you see some things a lot. This is
one of them. People see synce-kde and synce-gnome and think, as a
gnome, they should use synce-gnome. The thing is, they really
shouldn't.
Up until recently, the only real file in that part of the repository
was called test.py. At some point, we renamed it to synce-gnome, threw
a setup.py and released it. But if you examine it, within the first 10
lines you will still see "TestApp". It is about as old as odccm and
was created to test out some of the odccm dbus API. Currently its only
useful function it has is to deal with user passwords. It also has no
hal-dccm support. It is called synce-gnome, but the extent of its
gnome integration is that it has a GTK password entry box. It doesn't
even have an icon, install a menu item or start as part of the
session. For an end user, it kinda sucks.
synce-trayicon more than removes the need for synce-gnome. I think
even synce-sync-engine can handle passwords on its own (if it needs
to).
So does anyone have any objections to me moving synce-gnome to the
obsolete branch?

No objections here. I really don't think that synce-gnome is useful in any way
anymore.

+1 on the svn mv ;)

Guido

[David Eriksson]

Hi,

I won't mind!

Cheers,

David

Post by John Carr
Doing IRC support for synce means you see some things a lot. This is
one of them. People see synce-kde and synce-gnome and think, as a
gnome, they should use synce-gnome. The thing is, they really
shouldn't.
Up until recently, the only real file in that part of the repository
was called test.py. At some point, we renamed it to synce-gnome, threw
a setup.py and released it. But if you examine it, within the first 10
lines you will still see "TestApp". It is about as old as odccm and
was created to test out some of the odccm dbus API. Currently its only
useful function it has is to deal with user passwords. It also has no
hal-dccm support. It is called synce-gnome, but the extent of its
gnome integration is that it has a GTK password entry box. It doesn't
even have an icon, install a menu item or start as part of the
session. For an end user, it kinda sucks.
synce-trayicon more than removes the need for synce-gnome. I think
even synce-sync-engine can handle passwords on its own (if it needs
to).
So does anyone have any objections to me moving synce-gnome to the
obsolete branch?
John
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
SynCE-Devel mailing list
https://lists.sourceforge.net/lists/listinfo/synce-devel

--

[Jonny Lamb]

Post by John Carr
So does anyone have any objections to me moving synce-gnome to the
obsolete branch?

Not here.

[Mark Ellis]

Cool idea, done it.

Mark

Post by John Carr
Doing IRC support for synce means you see some things a lot. This is
one of them. People see synce-kde and synce-gnome and think, as a
gnome, they should use synce-gnome. The thing is, they really
shouldn't.
Up until recently, the only real file in that part of the repository
was called test.py. At some point, we renamed it to synce-gnome, threw
a setup.py and released it. But if you examine it, within the first 10
lines you will still see "TestApp". It is about as old as odccm and
was created to test out some of the odccm dbus API. Currently its only
useful function it has is to deal with user passwords. It also has no
hal-dccm support. It is called synce-gnome, but the extent of its
gnome integration is that it has a GTK password entry box. It doesn't
even have an icon, install a menu item or start as part of the
session. For an end user, it kinda sucks.
synce-trayicon more than removes the need for synce-gnome. I think
even synce-sync-engine can handle passwords on its own (if it needs
to).
So does anyone have any objections to me moving synce-gnome to the
obsolete branch?
John
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
SynCE-Devel mailing list
https://lists.sourceforge.net/lists/listinfo/synce-devel