in reply to Navigation Menu Setting

++ for adding the feature. I don't think I'll use it because I don't like all the blank space it leaves at the top of pages. That, and the sections nodelet doesn't have links for my homenode or logging out. Adding navigation links to my personal nodelet doesn't really fit with the way I currently use it.

As artist mentioned, it might be nice if the top menu bar were configurable. I'd keep the logout and homenode links as well as ones to SuperSearch, The Monastery Gates, Seekers of Perl Wisdom, and Newest Nodes. For the most part, I end up going to the other sections only via Newest Nodes anyway.

Checking this new feature out did give me a reason to go muck with my User Settings a bit though, and I've taken the opportunity to streamline things for myself and turn off a few nodelets I don't use. Thanks for the motivation!

-sauoq
"My two cents aren't worth a dime.";

Replies are listed 'Best First'.
Re: Re: Navigation Menu Setting
by belg4mit (Prior) on Jul 05, 2003 at 22:37 UTC
    Thanks. You can always go to nodes you know the name of either by editing the URI (?node=name) or by typing it into the search field. Personally, I still think bookmarks are the most appropriate solution for frequent visitors and that a configureable set of links is 0v3rk111. But to each his own. FYI it's possible to get to the The Monastery Gates just by clicking on the PerlMonks link in the upper right.

    UPDATE: Also, it might be worth considering how you do use your personal nodelet. I used to use it to store bookmarks to interesting nodes, but that can cause the list to be rendered everytime. And I certainly didn't use, let alone glance, at the personal nodelet for the majority of page loads. You can avoid this be checking the "Collapse List" box on UserSettings. Another option, the one I favor, is to use "add to scratchpad" for interesting nodes. This would then free up the body of the nodelet for navigation links, just a thought.

    --
    I'm not belgian but I play one on TV.

      I still think bookmarks are the most appropriate solution for frequent visitors and that a configureable set of links is 0v3rk111.

      I tend to agree that it's overkill... but just the same, I'd like it. :-)

      FYI it's possible to get to the The Monastery Gates just by clicking on the PerlMonks link in the upper right.

      Ah, so you can. I don't think I've used that before. So, knowing this, if the links at the top were configurable, I'd no longer include The Monastery Gates in them.

      Also, it might be worth considering how you do use your personal nodelet.

      Well, there's how I want to use it and how I do use it. Right now, I do tend to use it mostly as a queue of nodes I want to revisit.¹ I've been meaning to get away from doing that. The way I would prefer to use it is as a list of frequently referenced links. That way, when writing a node, I'd have the links I might reference right there rather than having to open another window and search for them. I don't think I'd prefer it for navigation in any case because it would require me to scroll down. I don't want to put it above the CB, because then using that would require me to scroll down even further (and my irritation with that is bad enough already.)

      As for editing the link or typing it into the search field... well... yuck. I'm not a real fan of GUIs in the general case, but I do see the value of pointing and clicking over pointing, clicking, and typing. ;-)

      1. There are exceptions to this. I have a couple nodes in there primarily for navigation, such as nodes to consider, for example. I also have one or two (ok, several) which are just generally interesting to me but which I haven't put on my homenode yet.

      -sauoq
      "My two cents aren't worth a dime.";
      
        I think the best mechanism for keeping a big list of interesting nodes (like nodes to revisit) is the browser bookmarks. It depends on browser of course but most are designed to manage a big list of bookmarks, and you can organise them in folders on most browsers. It is a bit slower then the personal nodelet (at least on Mozilla) since the usage of drop down two level menu, but thats a tradeoff.