Re: Starting Some Documentation Tonight

["John Stowers" <john stowers gmail com>]

Hi Brent,

Great to hear you are working on this. I have replied with comments in line.

On Feb 14, 2008 5:03 AM, Brent Gueth <creeva gmail com> wrote:
> While going through last night and playing with settings I have
> managed to figure some things out - also discovering issues that
> should be documented for users (picasa only allows 500 pictures per
> album so if your remote sync has more your SOL it will just hang).

Awesome, I did not know that.

> The thing that I sat round and round trying to figure out - what do
> you do with the Gmail sync point - I attempted to backup all my emails
> to a folder - I get gmail not configured correctly - I kept getting
> this no matter what situation I tried to use it.  What is the function
> and how is the gmail sync point meant to be used.

I just tested this to sync all my emails to a folder. It worked fine.
I presume all the bugs you describe were fixed in SVN ages ago (when
we updated libgmail version)

>
> Next question - resizing.   If you are doing a two way sync and have
> resizing enabled - are all pictures going to be resized regardless of
> direction?  If not is this resizing for sending or receiving data?  If
> so can we get it so it only resizes one way?

It currently considers resizing in both directions, even though all
current DPs only really use it as the input type. I will think about
this more.

> Youtube  Syncing - I'm at a loss it doesn't seem to want to download
> my youtube video  - the only logical solution I can come up with that
> a third party dependent transcoder is not available.

Thomas was right. Fixed in SVN

> Logging - Well can I say someone at some point needs to put in an
> event log into the preferences of the GUI to give someone a shot at
> figuring out why something failed?  Something like an "event log" that
> can track every file read/write/transform/transcode/sync point open
> close/etc?

Filed as http://bugzilla.gnome.org/show_bug.cgi?id=516293

Most developers run Conduit from a terminal to look at the log output.

> Finally since I don't have conduit in front me - the last pain of the
> preferences windows that shows objects and their mappings between
> services - if you clear this does it reset the sync to start over (I
> didn't get that feeling from my testing just for clarification in the
> documentation).

Yes, but this button is only going to be shown in development releases
(its only a debugging tool). Im not sure about documenting its
function. Ideally Conduit should 'just work'

>
>
> I know this is a lot and you can keep the answers as short as
> possible- I'm intelligent and suitably geeky enough - just not a
> programmer so throwing code at me won't likely help.   Once I
> understand more of these things I can write something coherent that a
> normal user can understand.
>
>
> A couple bugs I found
>
> 1. It would seem that if you setup a group to sync one direction and
> then setup another group with the same sync points in the opposite
> direction it doesn't map the sync objects properly and resends the
> data that's already there.  Ironically if you delete a sync point and
> recreate it though it "remembers" - not sure why it treats it
> differently.

http://bugzilla.gnome.org/show_bug.cgi?id=516294

> 2.  I mentioned in a previous email that there should be a validation
> when a sync point doesn't work together (rss and calender in my case)
> there should be a way that either disallows setting this up or informs
> you other then a sync error.  I don't remember what group I set up - I
> think it was backpack and evolution notes or memos - but it showed up
> with a red arrow instead of the yellow arrow.   This informed me that
> it wasn't going to work from the get go.  What vaildation is behind
> this and can we get it uniformly - somewhere in the plugin that states
> that It supports type A, B, C outbound and A,B,D inbound.  If it
> doesn't fall within these parameters a red arrow will be displayed.

As mentioned in previous email this is not an easy one to solve in the
RSS case. A temporary fix would be to change the rss prefs to indicate
what type of feed it is.

John