19 ms·

I'm very pleasantly surprised by this. I've always been a bit cynical about Basecamp's success, but I think this new version is going to be a genuine game-chang

I'm very pleasantly surprised by this. I've always been a bit cynical about Basecamp's success, but I think this new version is going to be a genuine game-changer. I really love the sheets idea and I'll love seeing how it works out. I'm already thinking about how I could apply the idea to e-commerce sites, hopefully the interaction isn't patented. Thinking about it now, I am wondering about a potential limitation. Sheets make sense when you have a fairly consistent starting point, ie the project overview page. But what if you're given a link to say an individual ticket? Do the sheets build up from that ticket as a starting point, rather than the project page, or do they reflect the hierarchy of the site? If it's the later, does that not mean that loading a deep page in the site is burdened by having to also load its parent pages? I assume it would be handled asynchronously, but it still seems like a lot of overhead.

joedev 15y ago
I doubt it is patented. http://twitter.com/#!/dhh/status/168725102538661891 http://twitter.com/#!/dhh/status/168725102538661891
jasonfried 15y ago
Thanks Andrew. "But what if you're given a link to say an individual ticket? Do the sheets build up from that ticket as a starting point, rather than the project page, or do they reflect the hierarchy of the site? If it's the later, does that not mean that loading a deep page in the site is burdened by having to also load its parent pages?" We'll write this up in more detail later, but the basic answer is: Every link has a default stack and that default stack is just the project page and that item's page. So if I emailed you a to-do item URL, the stack you would see would be two pages - the project the to-do is in, and the to-do itself. We put loads of time into thinking about all these scenarios. It's all very natural when you use it.
- andrewingram 15y ago
  Thanks for the reply Jason, It all sounds good, looking forward to seeing it!

joedev 15y ago

I doubt it is patented. http://twitter.com/#!/dhh/status/168725102538661891 http://twitter.com/#!/dhh/status/168725102538661891

jasonfried 15y ago

Thanks Andrew. "But what if you're given a link to say an individual ticket? Do the sheets build up from that ticket as a starting point, rather than the project page, or do they reflect the hierarchy of the site? If it's the later, does that not mean that loading a deep page in the site is burdened by having to also load its parent pages?" We'll write this up in more detail later, but the basic answer is: Every link has a default stack and that default stack is just the project page and that item's page. So if I emailed you a to-do item URL, the stack you would see would be two pages - the project the to-do is in, and the to-do itself. We put loads of time into thinking about all these scenarios. It's all very natural when you use it.

andrewingram 15y ago
Thanks for the reply Jason, It all sounds good, looking forward to seeing it!