Bug 170891

Summary:	Improve integration of evolution and gnome-panel
Product:	[Fedora] Fedora	Reporter:	Matthias Clasen <mclasen>
Component:	gnome-panel	Assignee:	Dave Malcolm <dmalcolm>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-01-27 20:45:16 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	172234
Bug Blocks:	170756

Description Matthias Clasen 2005-10-15 03:11:46 UTC

Double-clicking on the panel clock's calendar brings up the evolution calendar,
but it doesn't show the day that was selected in the clock's calendar. It should.

Also, it should close the clock's calendar and use startup notification, since
it takes some time for evolution to come up.

Comment 1 Dave Malcolm 2005-10-27 22:26:19 UTC

Yes, it seems to come up with a new window containing whatever view the last
calendar window had selected (e.g. week view, month view, etc).  I agree that it
should show the day view for the day you double-clicked on.

Comment 2 Dave Malcolm 2005-11-01 19:43:02 UTC

Looks like the necessary work has already been done and is sitting unapplied in
upstream bugzilla; gnome-panel clock needs patching, evolution doesn't:
http://bugzilla.gnome.org/show_bug.cgi?id=162305

Changing component to gnome-panel and reassigning.

Comment 3 Dave Malcolm 2005-11-01 19:44:58 UTC

Oops; didn't see the evolution patch as well...

So both evolution and gnome-panel will need patching...

Comment 4 Dave Malcolm 2005-11-01 19:50:18 UTC

(I created bug 172234 to track the necessary work to evolution that will need to
happen before the gnome-panel patch will work)

Comment 5 Dave Malcolm 2005-11-01 20:06:44 UTC

Reassigning back to me to keep it easier to work on.

Comment 6 Christopher Aillon 2006-01-27 20:45:16 UTC

We'll pull this in when it gets into upstream.  There are appropriate upstream
bugs which will handle it and there's no reason to diverge from them, which
could potentially introduce bugs.  Marking UPSTREAM.