Hi John, Timeline and Exhibit are separate projects. Exhibit uses the Timeline software.
Both are successful, judging by their many users around the world. Both are being actively maintained and developed. Please don't have your pages link to the trunk software on Google, it'll be too slow and that's not the right use of the Google open source hosting system. Use a local copy of the trunk or a released version from the MIT server. Additional comments are below. Thanks for using the software, we'd appreciate any help you can extend to the projects: documentation, testing, development, etc. We'd also like to include links to any applications that you develop in the wiki. Please let us know as they become publicly available. Regards, Larry ________________________________ From: John Callahan <[email protected]> To: [email protected] Sent: Monday, February 23, 2009 9:51:51 AM Subject: local hosting of Exhibit and Timeline I have a few projects that will go live soon using Exhibit, some use several exhibit extensions, some use only the Timeline extension. My thought was to host the code locally. It seemed like a best practice for production services. Also, I wanted access to the latest Exhibit and Timeline trunk code. I was successful in checking out the latest trunk version for Exhibit and running it locally. A few quick thoughts: 1) Is it best practice to locally host the Exhibit/Timeline code? Or could/should I point to the trunk version on the Google Code servers? (I know "trunk" and "production" usually don't sit well with each other but that's OK for these projects for now!) [I think if you already have your own production servers then it makes sense to locally host the software for your own applications. That way you're more vertically integrated. The MIT server is a free service. It is quite reliable but has been know to fail. It does not have a dedicated support staff. On the other hand, many users of the Exhibit and Timeline software do not have their own servers or do not have the budget or expertise to keep a server running and secure. For those folks, using the MIT server is an excellent option. No one should link their html pages to the software on the Google svn repository. It will be too slow and is not set up for that usge. Use the MIT server instead. ] 2) I know the Google Maps markers depend on a painter service hosted on simile.mit.edu. Could that be part of the source code for Exhibit? OR a separate checkout? Or if useLocalResources=true, then maybe you can use a standard set of png markers that is included locally. [My understanding is that the painter service for Exhibit is already a part of the Exhibit open source code. Search this email list for more information about the painter service and its source location.] 3) As FYI, I followed this doc: http://simile.mit.edu/wiki/Exhibit/2.0/Running_Exhibit_Yourself. (http://www.stevetrefethen.com/blog/HostingMITsSimileExhibitOSProject.aspx as well but seemed a bit off in some cases.) 4) Timeline vs Exhibit Timeline extension. Are these essentially the same thing? It looks like the Exhibit Timeline extension calls the Timeline project code on static.simile.mit.edu, even when Exhibit is hosted locally. So, if I want the latest Timeline features, I would need to svn checkout the Timeline trunk and host that locally as well. Is that correct? [Yes, I believe that you're right, but others are more expert than me on these issues.] I would love to question the future of Timeline and whether it would be rolled into Exhibit or stay its own project. I just don't know about about all the pros and cons of each, and how that relates to Timeplot, Calendar/Timegrid, etc... Personally, I would prefer to work with Exhibit only with the ability to turn on/off extensions as needed. Thanks. [Timeline will stay a separate project since it has many standalone clients. Exhibit is an extremely important client of Timeline. Exhibit is very flexible and I believe that folks have added new extensions to it on their own.] - John ************************************************** John Callahan Geospatial Application Developer Delaware Geological Survey, University of Delaware 227 Academy St, Newark DE 19716-7501 Tel: (302) 831-3584 Email: [email protected] http://www.dgs.udel.edu ************************************************** --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SIMILE Widgets" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/simile-widgets?hl=en -~----------~----~----~----~------~----~------~--~---
