The archiportal app has two uses for the iframe:
1. allow the user to get a topic view of the architect or the
building. This is nice because, well, the freebase client is really
good at dynamically displaying a topic, even in the face of schema
changes.
2. allow the user to edit a small subset of building properties:
* the architect
* the date it was built
* the address
* the geocode
So, I think one decent solution is to have built in editing forms for
this small set of properties, then use the iframes as "detailed view".
I guess the problem still remains that the user could edit those key
properties in the iframe, but they would be much less likely to do so
if a faster path were presented prominently.
Brendan
On Mar 26, 2008, at 7:05 PM, John Giannandrea wrote:
Will Moffat wrote:
you could do a tiny MQL query to the graph to check the timestamp of
the last link written by that user.
I was thinking along those lines, but it seems to be a catch-22
situation. You need access to the 'metaweb-user' cookie to get the
user name.
True. But you did send the iframe off to edit something, like a
topic, so you could check if that object had changes since the time
you launched the iframe. If someone else updated it it might be nice
to get the latest anyway.
I agree, this is all rather hard. Does your app want to edit known
properties on the topic, or just generally update it all? If the
former perhaps google code needs a form element based property update
library...
-jg
8 messages in com.freebase.developersRe: [Developers] Using the Freebase.c...
