MiniTree

[admin]

Just tried out the "Make Mini Tree from folders"...and...it's GREAT!

I was able to take my existing "Fav Folders" category and make a tree from it which allows me a bit more flexability than using items from Cat itself.

Wondering...could that option be added to context menu of MiniTree TB icon? That is, to use the current Catalog category as basis? Would reduce the cursor travel distance needed as I tend to be up near the Tb much more often than near Catalog...

I suggest you create a UDC/RunScript using the loadtree command. Then you have your favs tree at a keyboard shortcut.

[graham]

Just got round to trying this and like all simple ideas this is very good - one to push hard on the selling front as it is so easy to understand and gives results everyone would want to use.

It deserves a dedicated Skey.

[admin]

Skey?

[j_c_hallgren]

Skey?

I'm guessing thats a shortcut for "shortcut key" maybe?

[admin]

Skey?

I'm guessing thats a shortcut for "shortcut key" maybe?

Oh yes!

And, yes I agree it needs one. I'll see whether I find any good one left...

[serendipity]

Have been playing with minitree lately and like it a lot. And now for my projects i am using these two PFAs. It creates or adds selected list folders to minitree.

Code: Select all

"New minitree" \>:: focus; $ForMinitree= getinfo("SelectedItemsPathNames","|"); loadtree "$ForMinitree";

"Add to minitree" \>:: focus; $ForMinitree= getinfo("SelectedItemsPathNames","|"); loadtree "$ForMinitree",1;

I wanted to ask if its possible to lock minitree to specific folders?
Eg: When working in a session I might want minitree for say 4 folders, but still might want to access other folders. In this case I want minitree to be locked to only those 4 folders and ignore tree creation for others.
Any thoughts?

[admin]

I wanted to ask if its possible to lock minitree to specific folders?
Eg: When working in a session I might want minitree for say 4 folders, but still might want to access other folders. In this case I want minitree to be locked to only those 4 folders and ignore tree creation for others.
Any thoughts?

I'm not sure what you mean by "ignore tree creation for others"... you mean you want to totally block browsing to any other folders?

[serendipity]

I wanted to ask if its possible to lock minitree to specific folders?
Eg: When working in a session I might want minitree for say 4 folders, but still might want to access other folders. In this case I want minitree to be locked to only those 4 folders and ignore tree creation for others.
Any thoughts?

I'm not sure what you mean by "ignore tree creation for others"... you mean you want to totally block browsing to any other folders?

No, browsing other folders is OK, but creation of those folders in the minitree should be blocked.
Eg: If i have say 4 folders: Program files, Desktop, Windows folder and D:\, then only those and their branches will be shown in the minitree. I should still be able to browse C:\, My documents etc, but they should not show up in the minitree.
Somewhat similar in concept to locked homezone.

[admin]

I wanted to ask if its possible to lock minitree to specific folders?
Eg: When working in a session I might want minitree for say 4 folders, but still might want to access other folders. In this case I want minitree to be locked to only those 4 folders and ignore tree creation for others.
Any thoughts?

I'm not sure what you mean by "ignore tree creation for others"... you mean you want to totally block browsing to any other folders?

No, browsing other folders is OK, but creation of those folders in the minitree should be blocked.
Eg: If i have say 4 folders: Program files, Desktop, Windows folder and D:\, then only those and their branches will be shown in the minitree. I should still be able to browse C:\, My documents etc, but they should not show up in the minitree.
Somewhat similar in concept to locked homezone.

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.

[jacky]

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...

[admin]

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...

Okay, got it.

[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.

[admin]

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.

The combination of MiniTree-ON with Autosynch-OFF does it, right? I think all that's missing is that the tree at least synchs (highlights) those paths that are already present/expanded in it anyway. I think the latter should generally be added to Autosynch-OFF behavior.

[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.

[jacky]

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. One of the reason to use that option was to browse to a different location but keep the Tree untouched, including where it was (scrol position).

But now, the Tree will just scroll as usual -- granted, only if the nodes are shown/loaded on (Mini)Tree, but still. I'm not sure I like that. In fact, I'm sure I don't. Yes, for the use described above it might be exactly what you expect : (Mini)Tree in sync unless the nodes aren't loaded/shown, and I like it.

But to me, the use of option to disable Auto-Sync Tree is to keep my Tree as-is while going somewhere else, regardless of whether the nodes are available on Tree or not. I like serendipity's idea and would probably use it (Well I do right now already), but I often liked/would like to disable Auto-Sync Tree to go somewhere without having my Tree to scroll at all, should it be manually or running a script (with setting "AutoSyncTree", 0;)

So what I'm saying is, I think when auto-sync Tree is OFF there should be no auto-scrolling, the rest can stay but no auto-scrolling/putting into view the selected node; and there should be an additional option to do that, "Auto-Scroll Tree" or something? (also available from scripting)

EDIT: Gotta go now, but I wanted to add maybe it should be done differently, so that scripts using setting "AutoSyncTree", 0; to go do stuff somewhere without affecting Tree need no changes (i.e. to in addition/do instead a setting "AutoScrollTree", 0;), idn?