Hi,

In case you missed the link in the welcome message of the group, there
is an entire forum dedicated to the Picasa Web Albums API:

http://groups.google.com/group/Google-Picasa-Data-API


Most like the issue you are running into is the photo is larger than
800 pixels and so is not embeddable in a web page:

http://code.google.com/apis/picasaweb/faq.html#embed_image

If you use the imgmax query parameter you can get a <media:content>
URL that is embeddable.

Cheers,
-Jeff


On Sep 11, 11:11 pm, "Pavel Byles" <[EMAIL PROTECTED]> wrote:
> I am not sure if this is the right group that I am posting to. But I figured
> that only people that use the picasa gdata apis would have this problem.
>
> The problem is that I cannot seem to link to a photo using the URL from the
> media:content tag in the photo feed:
> For example, I have a page test.html that contains a link to a photo: <a
> href="http://lh3.ggpht.com/username/display.jpg";>Pic</a>
> When I load the page and try to click the link I get an error:
> /username/display.jpg
> was not found on this server.
> But when I enter the same URL into the address bar I can access it.
>
> The same happens if I do this: <img 
> src="http://lh3.ggpht.com/username/display.jpg"; />
> Nothing get's displayed.
>
> Any ideas would be helpful.
>
> -Pavel
>
> On Tue, Sep 2, 2008 at 5:07 AM, Frank Mantek <[EMAIL PROTECTED]> wrote:
>
> > We just released the new version of the .NET SDK for the Google Data
> > APIs.
>
> > Get it here:
>
> >        http://code.google.com/p/google-gdata/downloads/list
>
> > Note the primary difference between the .MSI and the .ZIP download:
> > The MSI download works only on Windows but does install the project
> > templates for you automatically.
>
> > The primary focus of this release is bugfixes, some new data elements
> > and multithreaded support. Ever wanted to upload that YouTube video in
> > the background? Download all the photos in a Picasa album without
> > blocking your UI? This release implements the EventBased Async pattern
> > from MSDN, and we implemented it in the PhotoTool sample application
> > that comes with the SDK. There is a whole document explaining how this
> > works here:
>
> >http://google-gdata.googlecode.com/svn/docs/AdditionalContent/Multith...
>
> > which is included in the helpfile that ships with the SDK. You can
> > check out the PhotoTool applicatio here:
>
> >http://code.google.com/p/google-gdata/source/browse/trunk/clients/cs/...
>
> > We would really appreciate feedback on the multithreaded support and
> > hope you find that useful.
>
> > To help you in examine a release, from now on we will publish the
> > codecoverage for the release with it. You can find this information
> > here:
>
> >http://google-gdata.googlecode.com/svn/docs/CodeCoverage/CoverageRepo...
>
> > Note that there are areas that need some love, so if you use that
> > particular service and like to contribute some good tests, feel free
> > to contact us with patches :)
>
> > Here are the complete release notes:
>
> > 1.2.2.0
>
> > • Added a SetRequestFactory method on the AppsService. This allows a
> > user of the AppsService to set advanced HTTP properties for the
> > underlying service objects used (like setting a proxy server,
> > additional headers etc.) by creating a new RequestFactory object and
> > passing it into the service. To make it easy to create this factory
> > object a helper CreateRequestFactory was added to the AppsService
> > object as well.
> > • Asyncronous/background support including a sample application. You
> > can now easily fire off that long running YouTube upload, or the
> > download of a picture as a seperate thread, so that your main
> > application is no longer blocked. It uses the AsyncOperation pattern,
> > and is not available (due to missing base support in the compact
> > framework) in the Windows Mobile build.
> > The sample PhotoBrowser application was changed to use that pattern,
> > and a page in the helpfile introduces the concept.
> > • Added support for Issue 163: the calendar recently introduced
> > several new elements, this adds support for syncEvent, uui and sequence
>
> > • Bugfixes
> >        • Fixed a bug in CommentingEnabled on the PhotoAccessor, which was
> > setting internally the wrong property.
> >        • Changed the behaviour of AlbumEntry.AlbumAuthor. The setter will
> > now create a new author is no author is present.
> >        • Fixed an issue regarding content, type=text. This element was not
> > encoding correctly which could lead to server errors based on the
> > contents of the element.
> >        • Fixed issue 164, the code will now throw an exception if we get an
> > empty location header in a redirect situation
> >        • Fixed issue 161, changed the WebProxy property on the
> > RequestFactory object to IWebProxy to make this interface more flexible.
> >        • Removed an obsolete size check for the authentication response for
> > client login and login for webapplications.
> >        • Fixed issue 160, FirstName in the profile feed of YouTube was
> > spelled wrong and hence not loaded correctly.
> >        • Fixed issue 157, Slug Header encoding. This was not correctly
> > confirming to RFC5023. Fixed and introduced a new helper method in the
> > utilities class for this purpose.
> >        • Fixed issue 147, a composite feed with a comment was not loading
> >        • Fixed issue 148, RemoveAt did not remove the object from the
> > containing collection, only locally. Fixed by overriding the OnRemove
> > method.
> >        • Fixed issue 155, there was no way to create a read only youtube
> > service, or rephrased, one that did not require a developer key
> >        • Fixed issue 159, a typo in the makefile that prevented gac
> > install/
> > uninstall using the makefile
> >        • Fixed issue 156, if an exception happened during upload, the
> > resource was kept open
> >        • Fixed issue 149, the Who element failed to parse attendee status
> > if
> > a whitespace element was encountered
> >        • Fixed issue 144, recurrenceexception is not parsed correctly
> >        • Fixed issue 145, FeedLink element parser error
> >        • Fixed issue 146. Passwords containing percentage signs were not
> > properly encoded.
>
> > Regards
>
> > Frank Mantek
> > Google
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Data Protocol" 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to