MiniTree

[admin]

The whole idea is to have the nodes of my interest expanded and rest stay out of sync.

v7.80.0027 should do it with MiniTree ON and Auto-Synch OFF.

Well, it's nice but it also kinda defeats the whole auto-sync tree option in a way, at least to me it surely does. ...

I'm not sure what's good here. Rarely used the non-synched Tree in the past, might do so more often now with Mini Tree. Curious what others say...

[serendipity]

Thanks Don, 7.80.0027 does what I asked for. But like Jacky said there can be an option to enable/disable tree scroll. Because there are two kind of users here:
1) Ones who want the tree to complete freeze when auto-synch is disabled and
2) Others who want the tree scroll to get the position of current folder in tree.

[dgw]

I don't think that's a good idea (if I understood it right this time). The current path should always be present and highlighted in the tree. Otherwise it would be a very confusing picture I think.

Okay, you realize it's already possible in XY though, right?

So what he wants might be possible already... just not completely. I mean, it may not be exactly the same, but it sounds like using MiniTree and disabling Auto-Sync Tree, no? That way browsing a location not on MiniTree won't get it added.

Only I think he'd like to have the Tree stay in sync when the location has a corresponding node on MiniTree, and stops being in sync when going outside of the loaded MiniTree (instead of adding it), all automatically. Which sounds like an interesting idea to me actually...

Thanks Jacky for putting it in right words. The whole idea is to have the nodes of my interest expanded and rest stay out of sync.

If I understand this right, I can use mini tree to autosync just the folders of my choice, and never autosync others? I turn autosync off because if I open a network folder I dont want to see thousands of servers and workstations open up in the tree, but with this I could turn off autosync on network drives and a few others folders that I never want to autosync. I currently have 7.80.0000, what do I need to look at mini-tree?

[serendipity]

I don't think that's a good idea (if I understood it right this time). The current path should always be present and highlighted in the tree. Otherwise it would be a very confusing picture I think.

Okay, you realize it's already possible in XY though, right?

So what he wants might be possible already... just not completely. I mean, it may not be exactly the same, but it sounds like using MiniTree and disabling Auto-Sync Tree, no? That way browsing a location not on MiniTree won't get it added.

Only I think he'd like to have the Tree stay in sync when the location has a corresponding node on MiniTree, and stops being in sync when going outside of the loaded MiniTree (instead of adding it), all automatically. Which sounds like an interesting idea to me actually...

Thanks Jacky for putting it in right words. The whole idea is to have the nodes of my interest expanded and rest stay out of sync.

If I understand this right, I can use mini tree to autosync just the folders of my choice, and never autosync others? I turn autosync off because if I open a network folder I dont want to see thousands of servers and workstations open up in the tree, but with this I could turn off autosync on network drives and a few others folders that I never want to autosync. I currently have 7.80.0000, what do I need to look at mini-tree?

Downlaod the latest beta: v7.80.0027 and enable "Mini tree" from menu "View".

[dgw]

Downlaod the latest beta: v7.80.0027 and enable "Mini tree" from menu "View".

Thanks, I'll give it a try.

[dgw]

The whole idea is to have the nodes of my interest expanded and rest stay out of sync.

I like it. Auto sync the mini tree but if I branch outside it, don't sync it.

[admin]

...thousands of servers and workstations ...

MiniTree, and especially the LoadTree scripting command are a wonderful solution for this. You write a little one-line script like:

Code: Select all

::loadtree "\\server21|\\server56|\\server3442";

and wrap into into a UDC or catalog item. Then it's one click to see your servers and no others in the nethood.

[admin]

Conc. "Auto-Synchronize Tree": I don't like the term! It sounds terrible, makes my brain dizzy, and I'm always stumbling across the fact that I have to enable this bizarre thing to get the normal Tree behavior.

So I decided to inverse the logic/semantic and call it simply "Lock Tree"! I know that the term isn't perfect either, but it works much better intuitively IMO. Agreed?

[jacky]

Well, it's nice but it also kinda defeats the whole auto-sync tree option in a way, at least to me it surely does. ...

I'm not sure what's good here. Rarely used the non-synched Tree in the past, might do so more often now with Mini Tree. Curious what others say...

Well, I do use it and my most common uses, as said earlier, were to go somewhere without having the Tree affected at all, or about the same but within a script that needed to go places do some work.

I thought about this some more, and here's what I think :

- I feel that when MiniTree is OFF Auto-Sync Tree should work as it used to before, because then that's the whole point of that feature : browse places without having the Tree affected/auto-synced. It doesn't make much sense to say I want to browse places and have the Tree in sync, only not for collapsed nodes, feels very odd (to me). Most likely you'd want to go somewhere without having nodes expanded or just the Tree to scroll because you like it as it is, might need it there for drag&drop operations, etc Otherwise, there's the MiniTree!

It might make sense to have the current node be selected/highlighted if it is visible, but there shouldn't be no expansion nor scrolling involved.

- When MiniTree is ON however, we have something new, and that I believe should be an option of the MiniTree feature, and only be used when Auto-Sync Tree is ON : Keep Tree In Sync Only For Loaded Nodes(/Existing MiniTree)

That way, a script setting AutoSyncTree OFF ensures that Tree won't be affected, as expected and as been the case so far, MiniTree or not. And if you use MineTree, turning AST on won't add new nodes if you don't want to, since you can keep the Tree in sync, but have it to only work for the loaded nodes, going elsewhere and basically XY auto-enables option Keep Tree In Sync until either moving back to a loaded node, or loading the node.

About that, even though it's easy enough to make a script for it (::loadtree , 1;) it would make sense then to have an option "Load Current Node/Add Current Location To MiniTree" on the menu (and TB ctxt menu).

[jacky]

Conc. "Auto-Synchronize Tree": I don't like the term! It sounds terrible, makes my brain dizzy, and I'm always stumbling across the fact that I have to enable this bizarre thing to get the normal Tree behavior.

So I decided to inverse the logic/semantic and call it simply "Lock Tree"! I know that the term isn't perfect either, but it works much better intuitively IMO. Agreed?

hmm... why not. Regarding my previous post, it would mean it becomes Lock Tree that works the same whether MiniTree is enabled or not, and the additional option would be called what then? Auto-Fill MiniTree? (disabled to get what we're talking about, in sync only for loaded nodes)

[admin]

I thought about this some more...

Okay, sounds good, I'll try it, or rather I make it and you try it.

... even though it's easy enough to make a script for it (::loadtree , 1;) it would make sense then to have an option "Load Current Node/Add Current Location To MiniTree" on the menu (and TB ctxt menu).

If I got you right: This would be only meaningful when the tree is out of sync. I don't think that this feature (AST off) is used very often or by many users, so the item would hang around disabled most of the time and take precious space in the menu...

[admin]

Conc. "Auto-Synchronize Tree": I don't like the term! It sounds terrible, makes my brain dizzy, and I'm always stumbling across the fact that I have to enable this bizarre thing to get the normal Tree behavior.

So I decided to inverse the logic/semantic and call it simply "Lock Tree"! I know that the term isn't perfect either, but it works much better intuitively IMO. Agreed?

hmm... why not. Regarding my previous post, it would mean it becomes Lock Tree that works the same whether MiniTree is enabled or not, and the additional option would be called what then? Auto-Fill MiniTree? (disabled to get what we're talking about, in sync only for loaded nodes)

I understood that, when Lock Tree is ON (aka AST is OFF), you suggested to go back to the old way when MiniTree is OFF, but keep "serendipity's way" when MiniTree is ON. Would make sense to me.

[jacky]

If I got you right: This would be only meaningful when the tree is out of sync. I don't think that this feature (AST off) is used very often or by many users, so the item would hang around disabled most of the time and take precious space in the menu...

Well, it would be only with MiniTree when AST is on but with that new option on; which becomes MiniTree with Lock Tree off but that new option enabled (i.e. Auto-Fill MiniTree OFF) .
You're right, it would only be for MiniTree users who don't wish to have their Tree "autofilled", though I would imagine that sounds like the way you'd want your MiniTree to work, but admittedly that's only my opinion. On the menu it might be a bit too much yes, but not on the ctxt menu of the TB button for sure.
It just feels like something someone using this (MiniTree not "autofilled") might want to do to fill his MiniTree, and having to resort to scripting or a TB button's ctxt menu does not sound easy to find. Maybe it could be visible only when MiniTree is enabled? or in CKS|Misc?

I understood that, when Lock Tree is ON (aka AST is OFF), you suggested to go back to the old way when MiniTree is OFF, but keep "serendipity's way" when MiniTree is ON. Would make sense to me.

When MiniTree is OFF and Lock Tree is ON, back to the told way yes.
But when MiniTree is ON and Lock Tree is ON, I still vote for the old way.

Lock Tree should always do that, no matter what. "serendipity's way" should be with MiniTree ON and that new option (e.g. Auto-Fill MiniTree off)

[admin]

Thanks Don, 7.80.0027 does what I asked for. But like Jacky said there can be an option to enable/disable tree scroll. Because there are two kind of users here:
1) Ones who want the tree to complete freeze when auto-synch is disabled and
2) Others who want the tree scroll to get the position of current folder in tree.

I'll try to do it without adding a further option. Let's see how it works out.

[jacky]

Thanks Don, 7.80.0027 does what I asked for. But like Jacky said there can be an option to enable/disable tree scroll. Because there are two kind of users here:
1) Ones who want the tree to complete freeze when auto-synch is disabled and
2) Others who want the tree scroll to get the position of current folder in tree.

I'll try to do it without adding a further option. Let's see how it works out.

Well, I'm pretty sure I won't like it... Because I would like to have a MiniTree that "stays in sync" only with the nodes available, not adding any new ones (serendipity's idea), as a way for this feature to work; but I also do disable sync to go places while I don't want the Tree to be affected (including scrolled), or use scripts that disable it to do their work, and that includes in folders with and without nodes on MiniTree...

The only way to make it work for me would be to remove the MiniTree that auto-adds new nodes on browsing, thus making us require to "manually" add them, but I don't that's what will happen, is it?