Lary, Thanks for taking the lead and giving the info.
I started working on it! Guys, please come up for the help as it will expedite the process a lot! -Brian On Oct 3, 4:16 pm, LarryK <[EMAIL PROTECTED]> wrote: > Hi Brian, > > A couple of notes in addition to David's comments: > * Please provide good wiki change messages when you make wiki changes > or additions. > * Please prefix all wiki change messages with WIKI: so we can easily > determine which svn changes were for the wiki and which were for the > various projects. > > * I suggest that you start a new section of the svn, call it > wiki_images (at same level as directory 'wiki' and other projects) in > the svn. Use the svn directory for storing the images that you > reference on the wiki pages. Eg over time we want to not be relying on > the MIT servers. But first test storing images in the svn, I'm not > sure that the mime-types are served correctly for images. It may also > be possible to explicitly store an svn property of svn:mime-type (it > looks like Google code stores that). This idea of storing images in > the svn may not work, but it should be investigated. For example, you > CAN view the jfk example via the Google svn server > athttp://simile-widgets.googlecode.com/svn/timeline/trunk/src/webapp/ex... > This is a good thing. It will enable us to use the svn repository as a > web server. We may even be able to serve up the js libraries this way > (needs further investigation and discussion first) > > On the other > hand,http://simile-widgets.googlecode.com/svn/timeline/trunk/src/webapp/ex... > is NOT served as html. I believe the issue has to do with the svn > properties for the file. > > * Note that rdq123 has been doing a great job of adding content to the > Timeline wiki pages. I've been adding a fair amount too. . > * Moving/documenting questions and answers from this group into the > wiki would be very helpful. The questions that come up on the mailing > list are all very real for someone, so documenting them for others can > be very helpful. > > * Another topic that you could research and write wiki documentation > for: Timeline spinoffs. > Timeline is used in three ways: > a) As a stand-alone widget > b) As a display method in Exhibit ("display method" is probably not > the right term) > c) As a widget in Google land > Documenting how the different uses interact with the code base would > be very useful. > Eg If someone is using the Google Timeline widget, how would they > start using a new version of the Timeline software? > If someone is using Timeline via Exhibit, what do they do to use the > latest version of the Timeline software? > > If the one trunk is not used for all three uses, what would be > required to fix that? (May not be possible or practical.) > > Thanks, > > Larry --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
