This sentence is sooo very apple.
Basecamp Next: UI Preview
51–60 of 85 posts
Re: Basecamp Next: UI Preview
#52The new "sheets" UI paradigm is strange to me. Jason mentioned a few times that they wanted to provide focus by getting rid of unnecessary design elements and chrome. But with the sheets, you actually get unneeded chrome. Your main content viewport keeps getting shifted down and to the right. Why not just use breadcrumbs at the top to provide context? That way, the entire content area could be taken over whenever you…
Re: Basecamp Next: UI Preview
#53Earlier quoted context omitted.
All of the above. On the app level, each fragment of markup is free of user-specific data so all users can share the same cache. (User-specific concerns are pushed down into JavaScript and CSS.) Those cache fragments are then nested, so we can cache at all levels of display: an individual to-do item, the to-do list with all its items, all to-do lists in a project, and the entire project itself. At the HTTP level, we…
Do you mean: 1) it's a single page app 2) you're using ERB fragments (or something) as "templates" 3) MVC fat-client Is this... more or less it?
We are using a dash of Backbone here and there for cases where interaction speed is of utmost importance, but most of what you download over the wire is HTML.
Re: Basecamp Next: UI Preview
#54Re: Basecamp Next: UI Preview
#55If so: then you have the best of both worlds. Advanced users can still open tabs, hit backspace to quickly navigate back (or 'up' in this case) — and regular users get a radically faster and more spatial way to navigate.
Re: Basecamp Next: UI Preview
#56Anyone else feel the same?
Basecamp Next no longer looks like a Project Management tool to me anymore, but instead - just a centralized/group info sharing app ... which is exactly what BackPack is today.
Re: Basecamp Next: UI Preview
#57Edit: Can someone please explain to me why this was downvoted? I'm not complaining, if it was done for good reason, just curious. I'm not the world's most prolific HN user. If my tone came across as being too harsh, it wasn't intentional.
Re: Basecamp Next: UI Preview
#58Earlier quoted context omitted.
Any plans to open source Stacker?
Not for the time being. Stacker is specifically developed for this unique UI style that we're using for Next. We don't open source our UI elements.
Re: Basecamp Next: UI Preview
#59I like the tactility of this a lot. Much superior to bread crumbs. Will the back button still work? Using pushstate I presume? If so: then you have the best of both worlds. Advanced users can still open tabs, hit backspace to quickly navigate back (or 'up' in this case) — and regular users get a radically faster and more spatial way to navigate.
Re: Basecamp Next: UI Preview
#60Earlier quoted context omitted.
When you use it you'll see why breadcrumbs are inferior. Breadcrumbs don't give you a sense of place. Breadcrumbs aren't natural. It sounds like a subtle thing, but once you use it you'll see the difference. Also, sheets have a much larger click target which makes them a lot easier and faster to use.
The only purpose of breadcrumbs is to provide a sense of place. It literally tells you where you are and how you got there. And where you can easily navigate back to. In terms of being natural, they definitely don't map to a physical analogy like your sheets do. But that's a good thing to me. edit: I agree with the click target benefit. Although I think you could do some useful things design wise with breadcrumbs to…
I think moving beyond the > foo > bar style of breadcrumbing is actually a big deal. who else has even tried?