← Back to team overview

genesis-devs team mailing list archive

Re: New notification/action system

 

Hi!

Am Sonntag, den 17.01.2010, 19:05 +0100 schrieb David Castellanos: 
> Sorry for not giving signs of life for so long. I'm not dead nor ill,
> only incredibly busy with the work, and with the PhD. Also, my brother
> brought a Wii this Christmas, so my productivity has decreased a lot
> :-S.

Ok, then at least I know what I can expect if I buy me one. ;-)

> I think until mid-February I'ill be very busy, and probably I won't
> have much free time. I have some outstanding things about Genesys, for
> example refine account management. Your new notification schema would
> be great, and I could integrate it in my account-management when I'll
> came back! I've seen there is a new bug about synchronization log;
> I've done a little snippet about that. It displays in a window the
> contents of the log file asynchronously. Frankly I do not know where
> it is, but I'll look for it.

Sounds cool! I also wanted to work on the log thing, it is heavily
broken. Maybe we can share thoughts and work.

Currently, Genesis only records the console output, it doesn’t really
touch the log file. This keeps the log displayed in an error case short
and readable, but isn’t very reliable.

You can find out about the last session directories with

        syncevolution --print-sessions <server>

(Which also prints the statistics. You can hide them with `--quiet`.)

That session directory contains the log file. Since SE is based on
Synthesis, it’s in HTML format and currently called sysynclib.html. I
think it’ll be called syncevolution-log.html in the future.

We should think about how to display it. Maybe just strip all HTML tags?
Or display it in an embedded web browser?

> Finally, I've refactored the sync_thread call and uploaded the code to
> lp:~davidcaste/genesis-sync/refact_sync_thread branch. I've done it
> some time ago when fixing a MS bug, and I think it could be useful for
> Genesys too. I don't remember exactly why I refactored it, but I think
> it was related to a problem with the tray icon spinning too fast,
> probably because after some condition it doesn't stop the tray
> animation when finishing the sync_thread call.

Is it ready to merge? I’ll look at it then, and merge if I don’t have
any questions.

> I'll read the emails from the list and taking a look at lp, and
> hopefully at mid-February I could be back in action :-)

As always, take your time. :-)

Cheers,
Frederik




References