i have pretty much fixed the problem i was having; http://vispo.com/dbcinema
is working again.
the problem was caused by google having changed the format of their html image search results. the old format still obtains if the request is not from inside a browser--as is the case with server-side processing and in, say, authoring or projector mode in director. but if the google query comes from a browser, the html image search results now are quite different than what they have been the last couple of years.
since, as you point out, there is no official google api for image search, part of what that means is that programs that use google image search are hacks, if part of the definition of 'hack' is code that gets a program to do something it was never intended to do. hacks are interesting precisely because they do the unexpected, but since they are not supported, they sometimes have a short life.
Patrick Tresset pointed out that Yahoo actually has provided an image search API: http://developer.yahoo.com/search/image/V1/imageSearch.html
. In other words they support the notion of programmers using Yahoo image search. And with that support comes, presumably, a longer life for programs that use this published API.
I have fixed the dbcinema/google problem by re-writing the routine that parses the google image search html results, but i realize it's just a matter of time before i have to do that again. so i am going to use the yahoo api, make that the primary search apparatus of dbcinema, and use google as a secondary search engine; if google isn't working in dbcinema, dbcinema will still get images from yahoo.
i imagine that in the future, net art will routinely use many web services that have published api's and supply all sorts of services including text, image, sound, and video search, dictionaries, thesaurii, stock info, but also things like, oh, you send the service a sentence and the service sends back the sentence parsed into the parts of speech or sends back the sentence parsed semantically, in some sense--services that will allow us use AI in interesting ways. there is of course some of this going on now, as we see in the alice bot api. in general, there will be all sorts of (queriable) web service api's available that turn the idea of net art into something whereby we really do see interesting use of the global info databases toward an art of larger and other mind.
> -----Original Message-----
> From: email@example.com
[mailto:firstname.lastname@example.org]On Behalf Of
> Steve OR Steven Read
> Sent: June 29, 2006 12:08 PM
> To: email@example.com
> Subject: RHIZOME_RAW: Re: Re: google api for image search?
> The google search api doesn't include image search functionality,
> only web search. However, one can parse the google web search
> results for image tags. I use PHP with PEAR:SOAP package to do
> it, and its very fast. I have some html parsing code (in php)
> which does this. I would happy to share some of this code with others.
> An example of this is here at my new site:
> This site is still in dev/test, but the photo noise app and its
> code has been running strong every day for nearly 2 years (at
> I would be interested in hearing other ways that people have used
> the google apis for image capture???
> Barry Hoggard wrote:
> > On Jun 27, 2006, at 7:42 AM, Jim Andrews wrote:
> > > a question for the programmer-artists, if i may.
> > >
> > > has anyone used the google api's to retrieve images from image
> > search?
> > >
> > > ja
> > > http://vispo.com
> > What language do you want to use? If it's in Perl, I would use this:
> > http://search.cpan.org/~grousse/WWW-Google-Images-0.6.2/
> > I'm sure there are modules for Java, PHP, etc. too.