aboutsummaryrefslogtreecommitdiff
path: root/gmail.lua
AgeCommit message (Collapse)AuthorFiles
2010-02-12gmail: reworked feed handling and changed username formatAdrian C. (anrxc)1
Nothing hard coded in the worker now. Feeds are together with user data, easily swaped. Feeds are not widget args because user needs to modify the file for login data anyway. No progress toward safer storage, Kwallet looks promising but dbus handling is hell - what of non KDE users? Every other script, including much praised checkgmail has plain text login. Nobody cares?
2010-01-02vicious: update copyrightAdrian C. (anrxc)1
2009-11-04De-obfuscate e-mail addressAdrian C. (anrxc)1
2009-11-03gmail: add scrolling support and truncate controlAdrian C. (anrxc)1
Same as the mpd widget. No argument, string is returned in full. Number enables truncate. Table enables scrolling.
2009-10-26Ensure returned numbers are of type numberAdrian C. (anrxc)1
Thanks to Felix for bringing this to my attention. Obviously there was already a safety net for feeding progressbars and graphs... and while this makes for a good coding practice it's not a big deal. We have widgets of type textbox for one, and a lot of string concatenation happens. Strings are formatted, markup is applied...
2009-10-05Lots of coding style changesAdrian C. (anrxc)1
2009-10-01gmail: count all unread messagesAdrian C. (anrxc)1
Widget now uses the Gmail unread tag to get a list of all unread messages, not only the Inbox. The auth argument was removed, and login information should now be placed directly in the widget (and file made read-only by user) until a safer storage is introduced.
2009-09-29Rewrote all headersAdrian C. (anrxc)1
2009-09-14General cleanupAdrian C. (anrxc)1
2009-09-10Curl connect timeout 1s, max time 3sAdrian C. (anrxc)1
2009-09-08Gmail widget includedAdrian C. (anrxc)1
Widget returns the count of new and subject of last e-mail in a Gmail inbox. Use ${count} and ${subject} in the format string to retrieve the values. Widget takes a table with login information as an argument. I don't like how gmail widgets handle sensitive data but I gave in seeing how popular they are. Better storing and handling of login information would be in order but this isn't Python and I'm out of ideas. For now use it on your own responsability, I would suggest to set login info directly in the widget and file as read-only by user.