Simile Widgets Server Migration and Some Application Retirements

[V. Alex Brennen]

Hello everyone,

Over the next month we are planning to migrate the Simile Widgets server to a new home in the AI Lab.

As part of this migration process we are planning to retire and shutdown some applications. Basically, we are shutting down the Java server side applications and planning to continue to serve  the Javascript for the applications that you run on your own webpages. These Javascript based applications include, for example, Timeline, Timeplot, Exhibit, etc. The Java server side applications that are being retired include Babel, Painter, etc.

I expect that there will be no noticeable impact or downtime as part of this migration process.  It should be completely transparent to you. All of your local Javascript based pages are expected to continue to work without modifications. We will not be changing the domain from simile-widgets.org.

If anyone would like to run a local copy of the Java applications that we are retiring, they are fully open source and links to the code repositories can be found on their application pages on simile-widgets.org.

If you have any questions or concerns, please feel free to reach out to me at v...@mit.edu and we can discuss them.

Thank you,

  V. Alex Brennen

  v...@mit.edu

[David Karger]

Babel has been down for a decade so hopefully nobody cares.  If you rely on painter, it is because you are using exhibit v2; you should migrate to exhibit v3 which doesn't use it.   Which I expect will be easier to do while your e2 version is still working.

--
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 simile-widget...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/simile-widgets/77d27488-d376-4083-bad5-4847d1d31f83n%40googlegroups.com.

[Roger Cutler]

I care deeply about Babel.  It is the only way that I have been able to interface between my Excel data and Exhibit displays.  Other Excel->Jason converters create Jason that looks a lot like the Babel-created Jason, but make Exhibit croak. A workaround is to use tsv/txt files, but I then lose all special characters like in "Dvořák", which Babel handled just fine.

I have been using Exhibit for a lot more than a decade for multiple purposes.  I've had repeated trouble with forced version upgrades of Exhibit that have involved losing features, but losing Babel is really hard to recover from. 

[David Karger]

when you tsv loses special characters, is that when you save the excel file as a tsv, or when you read the tsv into exhibit?

To view this discussion on the web visit https://groups.google.com/d/msgid/simile-widgets/e0fec93e-3bd9-41b0-b5dc-028b118392a4n%40googlegroups.com.

[Roger Cutler]

It's when I save the Excel file as tsv.  If I save as DOS-text I lose the special characters.  If I save as Unicode-text I get the special characters but Exhibit loses half the records.

[Roger Cutler]

Luis Miguel Morillas has showed me how to use CSV files to render special characters correctly in Exhibit, so I care a lot less about Babel now.  Thanks for responding, however.

[Luis Miguel Morillas]

Another option if you use google spreadsheets, is to publish the data
in the web as csv or tsv, so always have your data online and sync.


Saludos,

-- luismiguel (@lmorillas)

El mar, 10 sept 2024 a las 20:08, Roger Cutler
(<roger...@gmail.com>) escribió:

> To view this discussion on the web visit https://groups.google.com/d/msgid/simile-widgets/4075d15a-1503-48b8-8a6f-319de73cb83bn%40googlegroups.com.