Closed GoogleCodeExporter closed 8 years ago
This needs to be backward compatible with custom suggest services. I have
deleted the patch for now, I'll upload a new one when I have that working.
Original comment by s...@google.com
on 3 Oct 2012 at 10:33
Ok, here's the patch file. The suggest widget is now backwards compatible with
custom suggest services that emulate the old suggest API.
Original comment by s...@google.com
on 8 Oct 2012 at 8:53
Attachments:
Thanks for the patch. Is this stock Freebase Suggest 4.0 as served from
gstatic.com or has it been modified in some way?
It looks like we're currently running something 1.2.1 based which is pretty out
of date considering how long 3.1 was available before 4.0.
Original comment by tfmorris
on 8 Oct 2012 at 10:44
It is the stock suggest as served from the links below, no modifications
whatsoever. All the customization is done in custom-suggest.js
https://www.gstatic.com/freebase/suggest/4_0/suggest.min.css
https://www.gstatic.com/freebase/suggest/4_0/suggest.min.js
Original comment by s...@google.com
on 8 Oct 2012 at 10:57
Original comment by tfmorris
on 12 Oct 2012 at 1:29
It appears that the new version of the Suggest widget no longer returns
Freebase object types for matches which we're currently referencing.
http://code.google.com/p/google-refine/source/browse/trunk/main/webapp/modules/c
ore/scripts/views/data-table/cell-ui.js#333
I'll need to dig further to see if we actually use this information.
Has this patch been deployed internally at Google?
Original comment by tfmorris
on 12 Oct 2012 at 5:06
Fixed in r2575. Thanks for the patch!
The last remaining problem was an incompatible change in the returned data from
Suggest. They changed "n:type" to "notable" (and "r:score" to "score", but we
don't use that).
Original comment by tfmorris
on 12 Oct 2012 at 6:53
Original comment by tfmorris
on 12 Oct 2012 at 6:54
Original comment by tfmorris
on 12 Oct 2012 at 7:15
Original issue reported on code.google.com by
s...@google.com
on 3 Oct 2012 at 9:18