You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CODEBASE: Big think redesign of the vertical timeline with Alan
June 25, 2015 at 11:49AM
REPO You're gonna make my finally figure out how to get node up and running. * RE: I did not add back in the Ordering or Expanding actions. * I think this is fine. Ordering can be sold as editorial judgement and not needed for the user. Would love to know if anyone ever really expanded. I know we never set any to be collapsed. * RE: I actually have the same feelings about the Linking and Sharing of specific events. ?? * There isn't a lot of data to support anyone navigating to a specific link - a couple hundred page views out of 50-60,000. The former online editor in me likes the feature though. If only I could get a sustained effort to link to particular events in a timeline from our daily news stories. * I could always implement on a KPCC fork. I'd take hints on where in the script this makes the most sense to add. * RE: I have taken out Tabletop/G-Spreadsheet support. * I'm torn on this. I'm not opposed, but am thinking of my less technically-inclined colleagues and web producers who don't have dev environments. * For them, TT was a kind of training wheels. I'd deploy a shell, add the spreadsheet key and they could see the timeline taking shape. I need to get the current project - NODE! NODE! - and think through this part. * At this point it's three years before Google changes everything about spreadsheets again. And the proxy issue - we never ran into throttling, but remember the issue if a user hadn't signed into or didn't have a gmail account they couldn't see the project? For that I like basing things off flat csv or flat json files. * I have a python script to convert a csv to json for the timeline data and for the metadata. Seems a node-based build tool would be possible? * RE: Do we want to provide a hosted version / web interface for this? * I'm with John. I'm embellishing, but hosting moves a shop from providing legos to servicing software and customers. Though I'd argue we could host a mechanism to convert csv to json, but with Mr. Data Converter...? * RE: We had talked about a mini-timeline (way-finding) feature. Does this still sound interesting? * I still kind of like it... Alan, Louise and Noah - this is great work and I apologize if I failed to help as much as you expected me to? I'll work on getting the project up and running and let you know via issues if I run into any obstacles... Chris K.
The text was updated successfully, but these errors were encountered:
CODEBASE: Big think redesign of the vertical timeline with Alan
June 25, 2015 at 11:49AM
REPO You're gonna make my finally figure out how to get node up and running. * RE: I did not add back in the Ordering or Expanding actions. * I think this is fine. Ordering can be sold as editorial judgement and not needed for the user. Would love to know if anyone ever really expanded. I know we never set any to be collapsed. * RE: I actually have the same feelings about the Linking and Sharing of specific events. ?? * There isn't a lot of data to support anyone navigating to a specific link - a couple hundred page views out of 50-60,000. The former online editor in me likes the feature though. If only I could get a sustained effort to link to particular events in a timeline from our daily news stories. * I could always implement on a KPCC fork. I'd take hints on where in the script this makes the most sense to add. * RE: I have taken out Tabletop/G-Spreadsheet support. * I'm torn on this. I'm not opposed, but am thinking of my less technically-inclined colleagues and web producers who don't have dev environments. * For them, TT was a kind of training wheels. I'd deploy a shell, add the spreadsheet key and they could see the timeline taking shape. I need to get the current project - NODE! NODE! - and think through this part. * At this point it's three years before Google changes everything about spreadsheets again. And the proxy issue - we never ran into throttling, but remember the issue if a user hadn't signed into or didn't have a gmail account they couldn't see the project? For that I like basing things off flat csv or flat json files. * I have a python script to convert a csv to json for the timeline data and for the metadata. Seems a node-based build tool would be possible? * RE: Do we want to provide a hosted version / web interface for this? * I'm with John. I'm embellishing, but hosting moves a shop from providing legos to servicing software and customers. Though I'd argue we could host a mechanism to convert csv to json, but with Mr. Data Converter...? * RE: We had talked about a mini-timeline (way-finding) feature. Does this still sound interesting? * I still kind of like it... Alan, Louise and Noah - this is great work and I apologize if I failed to help as much as you expected me to? I'll work on getting the project up and running and let you know via issues if I run into any obstacles... Chris K.
The text was updated successfully, but these errors were encountered: