Basecamp Next: UI Preview
41–50 of 85 posts
Re: Basecamp Next: UI Preview
#42Earlier quoted context omitted.
Curious about how you're employing pushState. Is it through pjax or something similar?
We started out with pjax (which is awesome) but ended up rolling our own framework called Stacker which lets us have complete control over the UI.
Re: Basecamp Next: UI Preview
#43Re: Basecamp Next: UI Preview
#44Earlier quoted context omitted.
We started out with pjax (which is awesome) but ended up rolling our own framework called Stacker which lets us have complete control over the UI.
Any plans to open source Stacker?
Re: Basecamp Next: UI Preview
#45I love the concept (and the speed, my God! ) but one thing that really bugs me is the to-do list area -- it seems as though it could use a similar treatment as the discussion area. The long line lengths plus the inconsistent comment badge locations make it look really tough to scan.
Re: Basecamp Next: UI Preview
#46Re: Basecamp Next: UI Preview
#47Re: Basecamp Next: UI Preview
#48Nicely done. Very fast as well, never seen a webapp load that quick. Anyone with a bit of explanation on how this is done?
Re: Basecamp Next: UI Preview
#49Earlier quoted context omitted.
Can you expand on what sort of caching you are talking about? Client side caching in the JS layer, varnish or some other http level caching, some sort of server side in the Rails app itself, etc ?
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…
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?
Re: Basecamp Next: UI Preview
#50The 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…
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.
Previously I haven't preferred Basecamp but this new version is looking great so far.