A new release is brewing, but it's still a week or two away from
being polished enough. But as the library has not been updated for
around 8 weeks, i just wanted to give an update what to
expect in the next release, and what is not in it.
Currently, the following features/bugfixes are there:
1.1.0.0
* To enable ASP.NET hosting in medium trust, we removed the
usage of the NetworkCredentials class. From now on, credentials are
either passed as username/password, or using the GDataCredentials.
(issue 57)
* Changed "adminUserName" to "adminEmailAddress" in AppsService
so that it's more clear what information is actually required for
this parameter.
* added GZip support for .NET 1.1, 2.0 and .NET Compact
Framework 2.0.
* fixed a Google Base issue (The server doesn't accept
scientific notations for floats)
* fixed typo in the blogger sample (www..blogger), which made
the sample hard to use
* added the ability to use authsubtokens to the ExecRequest
utility (including exchange of a onetime token to a session token).
Just run ExecRequest for the command line parameters
* make the GAuthToken property of the GAuthRequestFactory
public. It was mistakenly marked internal, so that the token could
not be retrieved by a client application for caching.
* fixed a parsing issue that resulted in Batch Upload hanging if
an unknown element was encountered
* added a helper method on AtomBase (entry and feed) to find
exensionelements by specifying a localname and an optional namespace
(issue 81)
* the extension mechanism was reworked by creating an
ExtensionElementFactory interface that takes care of parsing
elements. ElementFactories are registered on the AtomBase (entry and
feed) level.
* Fixed Issue 60, mulitple Reminders per Event. Note, that this
introduces slight changes when dealing with this. A new property,
EventEntry.Reminders, was created. The old property,
EventEntry.Reminder, still exists, and only works on the first
Reminder in the list. Setting the old property will delete all
addtional reminders.The Reminders property is of type ArrayList (this
is an artifact of being .NET 1.1 compatible, once we move to .NET 2.0
or later, if that ever happens, this could/should be typed).
* Support for Google Calendar WebContent Gadgets is included. A
WebContent element has a SortedList property to set and retrieve
those preferences. See caltest.cs for an example.
* Modified data model for Spreadsheets worksheets to make it
easier to change and construct associated meta-data
* Added the ctz parameter to the EventQuery class. This
parameter allows to specify the timezone that is used to calculate
start/end times for the returned events
* Added an AlternateUri Property on the AtomEntry class. This
property returns the AtomUri of a rel=alternate type=html LINK entry.
As this is similiar to the ill named LINK helper on the spreadsheet
entry, that helper was removed, as they do serve the same purpose,
and the link helper was read only.
* Added an FeedUri Property on the AtomEntry class. This
property returns the AtomUri of a rel=#feed type=atom+xml LINK entry.
* Added an MediaUri Property on the AtomEntry class. This
property returns the AtomUri of a rel=#edit-media type=atom+xml LINK
entry.
* Preliminary Picasa support:
o Added all media extensions (media:rss, exif and photo>
o Added a PhotoEntry and PhotoFeed class that contain all
of those extensions
o Added unittests to query an album and insert a new photo
* Added the QuickAdd feature for the Google Calendar. An
EventEntry has a QuickAdd boolean property. Setting it to true causes
an insert to be treated like a quickAdd operation.
* Moved the documentation system to SandCastle
Things that i want to get done before release:
- Picasa support done. There is not a lot missing, so this should be
ready in the next 2 weeks
- Test to see if the same support works in theory for YouTube without
major changes. While we won't have a YouTube specialized
class by then, at least the base support should work to allow you
get the authentication and the upload etc done. We mainly want to
make sure that the media support is sufficient for YouTube use cases.
- Test it more.
This release involves a nice restructuring of how extension support
is done, so future add-ons should be easier to write.
What I would like you, the community, to tell me:
- what property do you need next? Creating Calendars? YouTube?
Creating Documents?
- What's the main thing where you have to write your own code where
we could make your life easier?
- oh, and if you like, take the current subversion version for a test
drive and file bugs, if you find them?
- Overall, feedback. Feedback.... FEEEEDDDDBACCCKKKK... We need to
know what you want and need,
because our needs in developing this library, or any other client
library, is just very different from your needs
in using it. If you don't tell, we don't know - yep, we can make
educated guesses, but they can be wrong.
Happy coding
Frank Mantek
[EMAIL PROTECTED]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Data API" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/google-help-dataapi?hl=en
-~----------~----~----~----~------~----~------~--~---
