From: Ian Barton <lists@manor-farm.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Popup with Weekly Agenda?
Date: Mon, 08 Jun 2009 13:00:52 +0100 [thread overview]
Message-ID: <4A2CFD74.3030200@manor-farm.org> (raw)
In-Reply-To: <18988.2483.667852.67102@pinto.chemeng.ucl.ac.uk>
>> I am hacking together something which creates a gtk Tray Icon and uses a
>> standard gtk window for the notification. it's basically working, but I
>> need to make the gtk window look more like a Notify window and get a
>> grip on the rather complex way gtkTextBuffer marks up text.
>
> Another possibility would be to use conky which draws on the root
> window directly instead of on top of everything else. You could have
> the agenda constantly displayed then. Conky does support full
> colouring.
>
> Whether this is useful for anybody or not is another story, of
> course...
I use conky myself, but it's already a bit cluttered with lots of info,
including the status of my MythTV box:)
A pop up window would be useful to me and other family members, who
aren't emacs users.
I now have a working prototype which uses a Tray Icon to display a pop
up window. I abandoned trying to colour text in a gtk TextBuf myself and
went with pygtkcodebuffer, which is a syntax highlighting derivative of
gtkTextBuf. This has the advantage that you can easily define your own
syntax to produce whatever colouring effect takes your fancy.
I'll rewrite my prototype to get rid of all the cruft and put it on
github later this week.
Ian.
prev parent reply other threads:[~2009-06-08 12:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 21:07 Popup with Weekly Agenda? Karl Maihofer
2009-06-05 22:44 ` Eric S Fraga, Eric S Fraga
2009-06-06 6:56 ` Ian Barton
[not found] ` <18986.18993.624454.358724@pinto.chemeng.ucl.ac.uk>
2009-06-07 15:49 ` Ian Barton
2009-06-07 18:40 ` Eric S Fraga, Eric S Fraga
2009-06-08 12:00 ` Ian Barton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A2CFD74.3030200@manor-farm.org \
--to=lists@manor-farm.org \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).