<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Mar 11, 2011, at 9:27 AM, Dimitris Andreadis wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">I think the task oriented approach is good but what's missing from the current layout is<span class="Apple-converted-space"> </span><br>some form for visual clue of where you are within the management information tree that the<span class="Apple-converted-space"> </span><br>domain model imposes, or a way to use that to navigate quickly to the particular<span class="Apple-converted-space"> </span><br>Profile/Group/Host</span></blockquote><br></div><div><br></div><div>I agree, that it's not very obvious where you are.</div><div>But regarding the tree vs pull down suggestion:</div><div><br></div><div>I did actually begin with a tree on the left hand side, but then quickly realized on problem:</div><div>The "related tasks" sometimes require a selection first. I.e. you need to chose a host, before you get to see</div><div>it's server configurations and server instances. It's similar with profiles and subsystems. </div><div>Now if you want to reflect this using a tree, you would need to put tasks, that refer to a prior selection </div><div>in that tree structure. For hosts it would look like this:</div><div><br></div><div>HostA</div><div> + <i>Server Configurations</i></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Server 1</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Server 2</div><div>+ <i>Server Instances</i></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Instance 2.1</div><div><div>HostB</div><div> + <i>Server Configurations</i></div><div><span class="Apple-tab-span" style="white-space: pre; "> </span>- Server 3</div><div><span class="Apple-tab-span" style="white-space: pre; "> </span>- Server 4</div><div>+ <i>Server Instances</i></div><div><span class="Apple-tab-span" style="white-space: pre; "> </span>- Instance 3.1</div></div><div><br></div>What's happening is that you replicate elements for each root node.<div>Not sure if we want to do this. As the number of hosts increases, the tree becomes bigger</div><div>and thus the redundant information increases until it might become unusable.</div><div><br></div><div>The best thing would be to create a UI prototype for this case.</div><div>And then take a decision. It's hard to picture these things until you actually get your hand on it.</div><div><br></div><div>Ike</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></body></html>