opensync-users

[Opensync-users] Kitchensync doesn't work (update from 0.20 to 0

[Nicoco <tru...@gm...>]

Hi,

I've been using opensync 0.20 with kdepim and syncml plugin for some time
now.
Since the recent 0.34 update, nothing works.
kitchensync now complains :

Error initializing Synchronization Engine for group "Nokia"
No synchronizable objtype

Clicking OK results in a "This engine was not in state initialized: 0" in
the terminal

Has anyone a clue about what's going on ?

Thanks a lot.
-- 
View this message in context: http://www.nabble.com/Kitchensync-doesn%27t-work-%28update-from-0.20-to-0-tp14577217p14577217.html
Sent from the Opensync - User mailing list archive at Nabble.com.

Re: [Opensync-users] Kitchensync doesn't work (update from 0.20 to 0.34)

[Daniel G. <dg...@su...>]

On Wednesday 02 January 2008 13:02:15 Nicoco wrote:
> I've been using opensync 0.20 with kdepim and syncml plugin for some time
> now.
> Since the recent 0.34 update, nothing works.
> kitchensync now complains :

Which version of Kitchensync do you use?!

OpenSync 0.34 is experimental development and changed all over the place. The 
API changed al lot since 0.2x ... you need a ported Kitchensync version for 
the OpenSync 0.3x API. This is only the case for KDE4 and a special 
work-branch of KDE makes this possible... the default KDE3 is still intended 
for 0.2x..

>
> Error initializing Synchronization Engine for group "Nokia"
> No synchronizable objtype
>
> Clicking OK results in a "This engine was not in state initialized: 0" in
> the terminal

The group got never "discovered", this prodcure got introduced with the 
OpenSync 0.3x API. This got only slightly integrated so far in the 
Kitchensync compatible 0.3x versions... this is NOT (yet) integrated in the 
default KDE3 Kitchensync.... and those implementation are quite experimental 
as well since the discovery process is blocking and makes the UI not usable. 
There are some issues inside OpenSync 0.3x API to make "sane" use of a 
non-blocking osync_engine_discover call (on my todo list).

>
> Has anyone a clue about what's going on ?

Make sure you're using a ported version of Kitchensync for the OpenSync 0.3x 
API ... which tries to run the discovery after configurating the group. 
Currently we don't have any update process from 0.2x to 0.3x ... as i already 
mentioned 0.3x is experimental and intended to be a development branch. There 
are still the plans to change several configuration stored in ~/.opensync. If 
the latest changes about configuration are fixed, then we might provide 
update functionality. This isn't fixed yet, since OpenSync is still in a very 
early stage of development and we might just provide some "update scripts" 
instead of doing a proper update implementation from 0.2x to 0.3x. Since 0.2x 
didn't have any version information about the configuration, which makes 
out-of-the-box updating quite tricky. So for now the best way to got is just 
to drop/move your 0.2x ~/.opensync configuration... and experiment with a 
configuration from scratch.

Btw. did you build this from scratch? Or got this shipped by your distro?

best regards,
Daniel

[Opensync-users] We're fooling users currently

[Juha T. <Juh...@ik...>]

On Wednesday 02 January 2008 15:09:05 Daniel Gollub wrote:
> OpenSync 0.34 is experimental development and changed all over the place.

> Make sure you're using a ported version of Kitchensync for the OpenSync 0.3x 
> API ... which tries to run the discovery after configurating the group. 
> Currently we don't have any update process from 0.2x to 0.3x ... as i already 
> mentioned 0.3x is experimental and intended to be a development branch. There 

This is something that most users stumble nowdays. opensync.org
front page highlights list of versions - which gives an wrong impression 
that things are being polished, instead of being heavily broken and
under construction.

At the moment, there isn't really a working solution for nobody 
as 0.2x works only in some use cases and config combinations 
(yes, you can get quite a long list those in opensync).

So, there should be a big red warning box at the top of the page
stating the facts and telling end users to go away, come back
later. If you're a developer/willing to help in testing, here
are checkout + compilation instructions.

It's better to drive them away directly compared to having 
a lot of people to waste time over and over again to find 
out the current state in hard way. That pisses people off 
which nobody wants.

I'm not saying that we should loose testers actively but we should
put it out clearly and frankly, which isn't the case now.

Daniel, I'd like to hear your comments on this, do you agree?


Br,

Tuju


PS: I've saw a message that fedora maintainer is updating their pkgs.
-- 
Älä luota hattupäiseen autoilijaan.

Re: [Opensync-users] We're fooling users currently

[Daniel G. <dg...@su...>]

On Wednesday 02 January 2008 15:49:34 Juha Tuomala wrote:
> So, there should be a big red warning box at the top of the page
> stating the facts and telling end users to go away, come back
> later. If you're a developer/willing to help in testing, here
> are checkout + compilation instructions.
>
> It's better to drive them away directly compared to having
> a lot of people to waste time over and over again to find
> out the current state in hard way. That pisses people off
> which nobody wants.
>
> I'm not saying that we should loose testers actively but we should
> put it out clearly and frankly, which isn't the case now.
>
> Daniel, I'd like to hear your comments on this, do you agree?

I can agree in certain points...

AFAIK, everywhere beside the titlepage we placed information about 0.3x ...
Download page, Release Notes .. but not on the title page.

Not quite sure if we really should welcome users with a red warning box that 
everything is broken. But i can agree slightly that the amount of frustrating 
user is increase and the number of active developers stays low ...

Could you add such a hint on the title page? (maybe just in bold text .. not a 
red fat box ;)) So i can in meantime waste mine time with OpenSync 
development ;)

Thanks!

Daniel

Re: [Opensync-users] We're fooling users currently

[Juha T. <Juh...@ik...>]

On Wednesday 02 January 2008 20:58:04 Daniel Gollub wrote:
> AFAIK, everywhere beside the titlepage we placed information about 0.3x ...
> Download page, Release Notes .. but not on the title page.

Yep, but there is lot of stuff and also some of it is outdated.
I myself never read site through when studying new piece of 
software. Only then when I really *need* information, before
asking from others. Good software doesn't need much docs :)

> Not quite sure if we really should welcome users with a red warning box that 
> everything is broken. But i can agree slightly that the amount of frustrating 
> user is increase and the number of active developers stays low ...

Yep, that's sad and hopefully gets better later. Perhaps modification
steps should be smaller in future if possible.

> Could you add such a hint on the title page? (maybe just in bold text .. not a 
> red fat box ;)) So i can in meantime waste mine time with OpenSync 
> development ;)

Sure, I'm sick atm and trying to work also, but I'll do it asap.

Br,

Tuju

-- 
Älä luota hattupäiseen autoilijaan.