User talk:200.108.223.149

Hi,

I like the new navigation markers (<^>) that you put in. They are very simple, elegant and fairly intuitive. It also makes it simple to go through sideways through the documentation, page by page.

However, I have a few minor concerns for which you may already have a solution:


 * I wonder how well the <^> alone will work once the documentation pages become nested several layers deep. In the Menu documentation section, for example, we are starting to  go 3 layers deep in the preference section, i.e.:

Online OsiriX Documentation Table of Contents > OsiriX Menu > OsiriX General Preferences

With the <^> system, it will be clear how to go up the tree from "Here" to "There" or from side to side, but I'm not sure it will be completely clear to the user where "Here" is and how far down the tree or to the side "There" is.


 * The <^> alone doesn't seem to provide a quick way to get back to the front page, or any arbitrary distance up the tree. The original "bread crumb trail" method I started with  allows this, although it takes up a lot more screen space and doesn't allow one to move to either side.


 * As long as the documentation is only 2 layers deep, it's not hard to know which page the <^> should point to next. However, once we get deeper than that, it's less clear.  Should the > lead to the next section of the same level, or should it go to the first page of the next section no matter how far down the tree it is?


 * It also seems to me that once the documentation gets only slightly more complex, it could become a real headache to keep all of the <^> updated properly, especially if we decide to add a new page or rearrange the order of the pages.

Can you think of some way we can resolve these issues? I'd love to find some solution that keeps all the benefits of both systems. Whatever system we arrive at, I hope that it will be one that will make it easy to keep the different multilingual versions of the documents congruent.

However, perhaps I am thinking too linearly -- maybe I should be thinking more in a hypertext manner. :-) Perhaps there is already some cool Wiki solution or convention for handling this of which I am unaware.

Best Regards,

--Mrich 23:55, 8 Nov 2004 (UTC)