Just what it says: a big collection of templates to get you started.
Your options for calendaring in the Enterprise just ballooned.
After many months of testing, Google Calendar finally adds CalDAV support. “CalDAV is an open protocol that allows calendar access via WebDAV. CalDAV models calendar events as HTTP resources in iCalendar format, and models calendars containing events as WebDAV collections. This allows you to publish and subscribe to calendars, share them collaboratively, sync between multiple users and sync between multiple devices.”
For now, the only application supported by Google Calendar is Apple’s iCal. “With CalDAV support in Google Calendar, you’ll be able to view and edit your Google Calendar events directly in iCal. Any changes you make in iCal will automatically appear in Google Calendar the next time you sign in (and vice versa). If you use iCal while offline, changes you make will be saved and updated in Google Calendar when you get back online.”
In fact, this was so long in coming I switched to Thunderbird and Lightning on the Mac, instead of using iCal. But for those still using iCal … give it a try.
Mac users haven’t had a free solution for Gcal-to-iCal sync, which makes the free offering from Calgoo a godsend. All Calgoo products are now freeware, Windows and Mac OS X only.
They haven’t started to be mass produced yet (can’t imagine why and it currently has a limited list of motherboards supported, but I already want one. The current version lists at $125.
We proudly introduce to the world what probably is the most senseful hardware solution
for a Mac™ on a PC experience.
It allows the user to install Mac OS X™ straight from the original DVD
without having to worry about patches, replacing files and anything like that.
Here are some of the hacks I’ve found for Google Notifier for Mac to make it usable with multiple accounts.
One problem, however, is that alerts from simultaneous arrival of messages from multiple accounts overlay each other on the screen. Although this is not generally a problem, it is irritating at login. Feel free to leave comments suggesting how to move the alert window for each instance to a different location!
First, duplicate it:
- Duplicate the Google Notifier application.
- Select the duplicate, control-click on its icon, and choose Show Package Contents from the pop-up menu.
- Navigate into Contents, and then open Info.plist in an editor.
- There is a property in that file called CFBundleIdentifier, with the value com.google.GmailNotifier. Change the property’s value to com.google.GmailNotifierWhateverYouWant instead.
- Save your change and quit the editor.
Second, identify it:
To solve that, you’ll need the Developer Tools installed. If you havethem, inside the Gmail Notifier app (the copy you made), open Contents-> Resources -> English.lproj -> MainMenu.nib with InterfaceBuilder. Double-click on the BothMenu item and add an Itemmyname@mysociety.com. Save your work, and you’re done.
In addition, I change the color of a couple key Gmail icons for each additional account found in the same Resources folder as above: unread.png and GmailIcon.png (the icons are red, but changed them to blue in the duplicate copy. Pick your favorite color. I used SeaShore, but pick your favorite app to edit the png files).
Third, secure it
Start each version of the Notifier, then for each one pull down the Notifier menu (either Calendar or Gmail), hold down Command and Option, and click Preferences on the menu. You’ll see a hidden settings editor. Enter SecureAlways in the Key field (upper and lower case must be entered as shown) and 1 in the Value field, then click Set. Quit Notifier and start it up again. From now on, all connections with both Gmail & Gcal will be https. Thanks to this comment on the O’Reilly blogs for this trick!
There are a couple other tweaks:
You can use your multiple notifiers to access the same account, but have each one return a different label.
If you only want the notifier to fetch mail with a certain label, you can create a filter. To do this, enter “Label” in the key field and enter the name of the label you want to receive in the value field (that appears in the box brought up by command+option+Preferenes – as above). To receive all mail, leave this field blank.
You can change the number of messages listed in the main menu by setting MaxMessagesOnMainMenu
By default, the menu shows the last four unread messages received (or the last three received and an additional “View More” submenu). To change this, enter “MaxMessagesOnMainMenu” in the key field and enter the number of messages you want on the main menu in the value field (that appears in the box brought up by command+option+Preferenes – as above).
You can add applescript plugins to Notifier:
AppleScript plugins are written by simply implementing a handler like:
on NewMessagesReceived(messages, fullCount)
– Your code goes here…
To install, simply copy the script (plugin) to Library/Application Support/Gmail Notifier (create the directory if it doesn’t exist), and restart the Gmail Notifier. An example of a great plugin for the Gmail Notifier for MacOS X is the Gmail+Growl plugin, which sends Growl notifications when new mail arrives.
Slashdot has picked up on the news that Google isn’t just abandoning Browser Sync, but making it open source. So it may be that some kind soul will bring it along for Firefox 3.
But why wait? In a flurry of activity no doubt generated by the news of the impending Google release, the folks over at Mozilla labs released Weave 0.2. (Its not yet available for PPC Mac, but some folks have been working to compile it on that platform and it may be available soon.)
Weave is very impressive, and promises to eventually sync everything (including your extensions) in future releases.
we’ve released the code in the hopes that those folks who asked for it will use it to develop something cool. For example, it would be great to see the server ported to Google App Engine, or support for Firefox 3 implemented.
You can check out the code using any Subversion client, and we have posted a short tutorial explaining how to build and run it.
So, I’ve had a little time to test out some of the options presented in a previous post and actually tried out SpaceStation (at version 0.3 at the time of this post).
I’ve included the instructions here. It works well, I found that editing and saving the preferences file, then killing the daemon with Activity Monitor works more smoothly than the recommended “killall -2″.
Its not easy to change your background images, since it requires a plist edit. It should be trivial to add a drag ‘n drop selector for each space. Let me know if you decide to write one.
Okay, SpaceStation v0.3 is available. (It’s the same link as before.)
I made a LaunchAgent, which registers the daemon with launchd. This will run the daemon automatically when you login, and also restart it if it dies for whatever reason.
I also made a little installer script. This will copy the LaunchAgent and daemon to where they need to live, and give you a dummy pref file if you don’t already have one. (It won’t clobber an existing pref file.) You can also use it to uninstall, which will move the LaunchAgent and daemon to the Trash, but will leave your prefs alone in case you want to use it again later. Once you run the installer, you’ll need to logout to make the changes take effect. (Sorry about that, but I’m still deciphering the intricacies of launchctl.) Just FYI, the daemon goes in to /Library/Application Support/SpaceStation, the LaunchAgent goes in to ~/Library/LaunchAgents, and the pref file goes in to ~/Library/Preferences. This means the daemon will be available to all users, but it will only work for users that have the LaunchAgent and pref file. You’re welcome to install everything manually, if you prefer. (All the installer does is copy and delete files, as appropriate.)
Double-clicking the pref file should open the Property List Editor. The numeric properties in the Pictures dictionary correspond to the various Spaces. The “Default” property is used if a numeric property is missing or blank. (You can define a different Default Picture, if you’d like.) I’m pretty sure that if you try to set the Desktop Picture to a file that doesn’t exist, you’ll just wind up with DefaultDesktop.jpg, which is the default Default Picture. (That’s a function of the OS, not something that I’m doing.) The ScanInterval is how often SpaceStation checks for a Space change, in seconds. The default value is 0.1s, but you can tweak this as you see fit. A little editing tip: If you drag a picture from the Finder to the value field in Property List Editor, it will insert the whole path. (Copying and pasting only gets the file name.) This should save you some typing.
To make preference changes take effect, you need to issue a killall -2 spacestationd in the Terminal. (You can leave out the -2, but doing so will actually kill the daemon instead of making it reread the prefs file, but again, launchd will just relaunch it if it dies.) Make sure you save the changes in Property List Editor before issuing the killall.
Monitor account activity and log out remote GMail sessions.
With this information, I can quickly verify that all the Gmail activity was indeed mine. I remember using Gmail at the times and locations listed. Being extra cautious, I can also click on the “Sign out all other sessions” button to sign out of the account I left open at home.