Roger Menday wrote:
>
> Hi David,
>
> Thanks for your answer.
>
> First of all, I would like to say thanks to you and your team for
> giving us Exhibit - it absolutely rocks !
Glad you like it :-)
>> That is not supported in Exhibit 1.0, but I think it should work in
>> Exhibit 2.0 (under development):
>>
>> ex:start=".dateon"
>> ex:end="default(.dateoff, now())"
>>
>> Which means, use .dateoff if that exists, otherwise, use the current
>> time.
>>
> OK. I'm really looking forward to 2.0. For now, I'm happy with working
> around this in 1.0.
>
> Another question :)
>
> In one of my lenses I have a little bit of in-line editing, which
> AJAXly saves the updates. To prevent page re-load, I wanted to change
> the Database - just a little (just little edits to a single item - no
> new items, or schema changes). Is there a way to do this ('officially'
> or otherwise), so that as they continue to work through the different
> views in the current page the edited information is included.
>
> I did search the archives of this mailing list and I read a requests
> for this ... but just wondered if there is an unofficial way.
It won't be so easy in 1.0... If you want to try 2.0 out, here's how
http://simile.mit.edu/wiki/Exhibit/2.0/Migration
Then you can do something like
window.database.addStatement(itemID, "propertyFoo", "valueBar");
window.database.removeStatement(itemID, "propertyFoo", "valueBar");
window.exhibit.getDefaultCollection()._update(); // trigger UI updates
David
_______________________________________________
General mailing list
[email protected]
http://simile.mit.edu/mailman/listinfo/general
