I'd like to see the ability to post a link that goes directly to a given summary page for a function.... makes it easier to direct people to a certain area (say for instance, posting in this mailing list)
On Jan 15, 11:43 am, Pappy <[email protected]> wrote: > My biggest issue with the new site is a lack of 'summary' screens. I > love being able to look at one page and take in all functions of a > various type. Especially when there are two that are awfully similar > and I can scan back and forth to differentiate between them. > > On Jan 14, 8:22 pm, James Van Dyke <[email protected]> wrote: > > > Does anyone else find the new API browser to be a bit cumbersome? > > > My gripes: > > > 1) No "back" link at top of vertical navigation list. You must click > > the category to cancel your choice and essentially go back. However, > > this isn't very intuitive and there aren't any affordances to this > > behavior save for a small 'x' in the highlighted category box that > > doesn't do anything on hover or even have a tooltip. > > > 2) The browser's back button is broken. Kind of a big annoyance when > > you're not used to the application. > > > 3) Recovering from a mistake is more punishing than it should be. > > Clicking on a category hide the other categories. Since the title of > > the category moved from under your mouse, you now have to scan to the > > top of the list. Once you make sure you're in the category you meant > > to click on, but don't find the function you were looking for, you > > click the category name and wait as everything moves around, then > > repeat scanning through list again. A good example of this is trying > > to find an unfamiliar selector in the Selectors category. > > > 4) Little distinction between categories, subcategories, and items. > > They're all the same color and categories and subcategories share the > > same faded 'x' icon. The only difference is that the category has bold > > text and the subcategory has a white line under the box, but not > > between it and its category. > > > 5) When hovering over a list of options for a function (e.g., $.ajax) > > only the item you're hovering over has full opacity making the others > > hard to read. I'm ok with the distinction, but I think it's a little > > extreme. I found myself avoiding hovering over the list, which is > > hard since I tend to scan the page with my eyes as my mouse follows my > > line of sight. Try scrolling through the options for $.ajax while > > trying to read them. > > > 6) The window title changes when viewing an item, which makes one > > think that the URL will map to that page. However, the URL does not > > change and I can't find a permanent link to paste to a co-worker. > > > Don't get me wrong, I think Remy has made a great step towards a > > better API, but design efforts seem to have favored neat effects over > > human factors. I deal with a lot of these design issues at work so I > > tend to have a keen eye for these things and can be too picky at > > times. > > > Has anyone else been bothered by this? If not, what do you like or > > what makes up for the negatives? Maybe we can compile a list of > > existing *good* things as well so that those features can be brought > > to the fore while the problems are resolved.
