Tx; looked there - we need 2.0.
This page:
  http://substrate.burnham.org/lookup/uniprot/P05067
uses:
  http://static.simile.mit.edu/exhibit/api-2.0/exhibit-api.js



On Tuesday, February 7, 2017 at 12:10:00 PM UTC-6, David Karger wrote:
>
> You can find older versions of the exhibit api at 
> http://api.simile-widgets.org/exhibit
>
> On Monday, December 12, 2016 at 4:53:02 AM UTC-5, Jay Gray wrote:
>>
>> A while back we successfully implemented a customized Exhibit Timeline 
>> using
>>     http://static.simile.mit.edu/exhibit/api-2.0/exhibit-api.js
>>     
>> http://static.simile.mit.edu/exhibit/extensions-2.0/time/time-extension.js
>>
>> The instance no longer works.
>> Fortunately, we have screen shots of the working instance, shown here:
>>     https://afdsi.org/test/protein/images.html
>>
>> Customization overrides
>>     
>> http://static.simile.mit.edu/exhibit/extensions-2.0/time/scripts/timeline-view.js
>> with start and stop 'dates' that represent the beginning and end of gene 
>> sequences.
>>
>> Withing the last six months the previously working instance stopped 
>> working.
>> Here is a site where working instances are now non-working instances:
>>     http://substrate.burnham.org/
>>
>> We have upgraded the previously working instances to Exhibit 3, as shown 
>> here:
>>     https://afdsi.org/test/protein/index.html
>> but the timeline modified to show gene sequences still does not work.
>>
>> Would it be possible to unwind the changes to Exhibit version 2 that 
>> broke the previously working instances?
>> Then we can see how to make sure those features also are present in 
>> Exhibit 3.
>>
>> /jay gray
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"SIMILE Widgets" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/simile-widgets.
For more options, visit https://groups.google.com/d/optout.

Reply via email to