I hate to delay the release of this plugin but I am currently reworking some of the preferences to take advantage of Token more effectively.

The initial design for the module was that dates for the calendar entries would be determined by some process on specific CCK date fields from the node type. The module would take care of date format construction under the hood. I was initially fine with this decision until implementing it inside the project it was designed for.

Our company maintains a portal site for our clients to interact with our sales team. We can schedule jobs, track invoices and report back to the client using this portal. One of the usability decisions we have opted for on some schedule-dependent jobs is using a radio button for time ranges; “early afternoon,” or “9am to 5pm” instead of the rather clunky hour/minute select elements beside the solidly usable “Text Field with Date Pop-up calendar” which uses JQuery UI. The drop-down Hours and Minutes to the right of the date pop-up calendar were confusing our users.

Anyway, I have decided to rewrite the date handling to simply use Tokens which everyone is comfortable with already. This has the automatic benefit of allowing the user to easily specify YYYY-MM-DD as their event start datetime, which will be interpreted as an all-day event by the GData API, or specifying a start time manually.

The rework is very close to being releasable. Please be patient and Contact Me if you have any questions or requests.