DiskManager

[serendipity]

A disk manager utility to click around and find out folder sizes. Useful visual information sometimes. I've been using jdiskreport myself for long, but wanted to try something on XY which I knew was possible.

Download below xys file and run it.
Download:

DiskManager_v1.xys

(3.93 KiB) Downloaded 448 times

I will be adding more stuff later.

PS: Right now if file/folder takes up >20% of space then size shows up as red. The first line in the script has value set to 20, change that if you want.

[serendipity]

DiskManager_v2

Updated few things and it looks much better now.

Download:

DiskManager_v2.xys

(5.34 KiB) Downloaded 366 times

[PeterH]

Hey - looks very nice!

Small problems:
- on "Go up" there is an error-msg "The current script appears to be recursive". Could you add a setting to allow this?
- the window for output is too big, and fixed size. It opens (as XY does) on my 2nd, smaller screen, and is much too wide for that. (And *much* wider than neccessary to display the table!)
- oh: was on e: and clicked "Go up" - this leads to an error?
- same going "Up" from Desktop, for example. You should possibly test for "my PC" (or how it's named in english). But in German it's "Arbeitsplatz"

What, for me, could be added is some optical diferentiation between files and folders. And maybe the option to show *only* folders.

But again: very good!

edit: Hey - I just see: going to Arbeitsplatz shows no error - it's meant as it's shown
OK - because there is no hint like "Arbeitsplatz not supported - select a drive or folder" I just misunderstood the situation...

[serendipity]

Hey - looks very nice!

Thanks for the feedback.

Small problems:
- on "Go up" there is an error-msg "The current script appears to be recursive". Could you add a setting to allow this?

Sorry forgot to allow recursion this, now its added.

- the window for output is too big, and fixed size. It opens (as XY does) on my 2nd, smaller screen, and is much too wide for that. (And *much* wider than neccessary to display the table!)

In v2.1 you have the option to change the screenwidth and screenheight.

You should possibly test for "my PC" (or how it's named in english). But in German it's "Arbeitsplatz" [/size]

XY has a variable %computer% which takes care of any name given to your computer, so Arbeitzplatz is covered. The problem was recursion thing which is now fixed.

What, for me, could be added is some optical diferentiation between files and folders. And maybe the option to show *only* folders.

In v2 folders have different color. And *only* folders, maybe i'll add an option later.

[serendipity]

DiskManager_v2.1

-Included recursion checker in script.
-you can now define screen width and height. Open script file in text editor and change values for $screenwidth and $screenheight. Default is 85%.

Download:

DiskManager_v2.1.xys

(5.64 KiB) Downloaded 308 times

[PeterH]

DiskManager_v2.1

-Included recursion checker in script.
-you can now define screen width and height. Open script file in text editor and change values for $screenwidth and $screenheight. Default is 85%.

Download:

DiskManager_v2.1.xys

Thanks - better again!

Recursion checker now ok.

Screensizes seems to be an XY-problem, it's always using screensize of the primary screen, even if XY is on second. I've opened a bug report - let's see what Don says.
But: the output of DiskManager is a table with a fixed width. Wouldn't it be better to define this absolute? Maybe with checking, if it doesn't exceed screen width?

You say in V2 folders have a different color? I can't see that, neither in V2.1
All text in black, only high-percent in red, and graphs in red.
Only ^Go up^ in blue.
Ouuuh - that's bad! I've found the reason: german windows! Property("Type","foldername") returns "Dateiordner" instead of "File Folder"! Any idea for an automatism here? (As is for desktop...)
Changed it for test: now folders are brown
But would not like to change this everytime you make a new version

[serendipity]

But: the output of DiskManager is a table with a fixed width. Wouldn't it be better to define this absolute? Maybe with checking, if it doesn't exceed screen width?

Thanks for your feedback.
Yup, i kept some columns fixed because they looked weird otherwise. With v2.2 i changed few things and should look better now.

I've found the reason:[/b] german windows! Property("Type","foldername") returns "Dateiordner" instead of "File Folder"! Any idea for an automatism here? (As is for desktop...)

Thanks for that, I switched to a different command (exists) and it should work for other languages now.
See next version.

[serendipity]

DiskManager_v2.2

-Now a file "DiskManager_DUMP.txt" is created inside XY's Scripts folders. All folder info is stored here for performance reasons. Noticeable in folders with many items. This file is deleted when the DiskManager window is closed.
-minor changes in display.

Download:

DiskManager_v2.2.xys

(6.07 KiB) Downloaded 317 times

[PeterH]

DiskManager_v2.2

Better again!

But again some notes:

- the defs of $screenwidth + ...height "seem" absolute, later a % is added to make them relative. Wouldn't it be more flexible not to add the % later? Then for $screenwidth I could specify 66% or 1280 to request fullscreen. (Don only supports relative screensize of the primary screen - even if XY is on secondary. For me 66% are 1267, 1280 would be whole screen width.)

- this may be personal taste? For me the colors used to differentiate files and folders could be a bit better to recognize. For example by making folders a bit more red? Or even better by softly coloring the background?
And the ^Go up^ could be a bit more eye-catching? Maybe making it look like a button?
(I'm not "the html-man" - so I don't know how difficult this would be.)

And just to report: once I had a glitch - only the 3 top folders showed sizes, the next 12 didn't. Closing the window showed the same situation in XY: those folders showed an empty Size column. I wasn't able to reproduce this a second time. Now it seems like a fata morgana...

[serendipity]

Something in 8.80.0006 is breaking my script. Back to 0005 for now. Any ideas Don?
Edit:
Actually i get this error:

Code: Select all

Error 	6 (00000006)
Desc	Overflow
Dll	0
Proc	script_Process

Source	XYplorer
XY ver	8.80.0006
OS	Windows 7
Date	1/2/2010 02:54:24

[serendipity]

DiskManager_v2.3

-Now there is a text field at the bottom where you can define a threshold value. Values above this threshold will be colored red.

Download:

DiskManager_v2.3.xys

(7.39 KiB) Downloaded 340 times

edit: does not work on 8.80.0006. see previous post.

[admin]

Something in 8.80.0006 is breaking my script. Back to 0005 for now. Any ideas Don?
Edit:
Actually i get this error:

Code: Select all

Error 	6 (00000006)
Desc	Overflow
Dll	0
Proc	script_Process

Source	XYplorer
XY ver	8.80.0006
OS	Windows 7
Date	1/2/2010 02:54:24

Yep, my bug. Fix comes...

[PeterH]

DiskManager_v2.3

-Now there is a text field at the bottom where you can define a threshold value. Values above this threshold will be colored red.

Download:

DiskManager_v2.3.xys

edit: does not work on 8.80.0006. see previous post.

NO, no

You "misuse" the script as an ini-file
That's great Really. Must remember that! An implicite ini-file with an explicite initial value :-)
(I think, you should delete the comment in line 10 ("Change below value...") as it doesn't make much sense now?)

Sorry, it seems I still got some problems - but rather exotic!

1) In a directory there's one file (143KB) and one subdirectory with 7,43GB. The file is shown as 0,00%, while the directory shows <0.01% (!) :-( Both show no bar.

2) Oh - it's the same as 1) :-) In another directory there are several files and directories from 13KB up to 74MB and *one* directory of 89GB, all are shown as 0,00%, <0,01%, and two (of MB-sizes) as 0.08% and 0.06%. Seems something in mathematics fails, if one entry exceeds 99% or so?

3) :-) The title still says DiskManager_v2.2 - maybe you should set it as a variable in the most-upper part of the script, in order to see it better?

Some word to coloring: the Threshold value leads to coloring of the Size(%)-column. If I interpret it right the bar is colored dependent from Size, in colors as shown in the heading? Does this make sense?
For me this color would possibly make sense in the Size-column, to be able to quickly differentiate the units - while in Bar I'd rather expect the color related to Threshold.

PS 8.80.0008 works again!

[serendipity]

You "misuse" the script as an ini-file
That's great Really. Must remember that! An implicite ini-file with an explicite initial value :-)

Yup, i first used it in the quicksearch script. But also, remember the downsides of this method as jacky mentioned here.

Sorry, it seems I still got some problems - but rather exotic!
1) In a directory there's one file (143KB) and one subdirectory with 7,43GB. The file is shown as 0,00%, while the directory shows <0.01% (!) :-( Both show no bar.

2) Oh - it's the same as 1) :-) In another directory there are several files and directories from 13KB up to 74MB and *one* directory of 89GB, all are shown as 0,00%, <0,01%, and two (of MB-sizes) as 0.08% and 0.06%. Seems something in mathematics fails, if one entry exceeds 99% or so?

WHOAA! i wonder how anything worked for you in the first place. I realized just now that in Germany decimal separator is "," while here we use ".". I will fix that soon. EDIT: sorry, i had already thought about that and use RAW size to start with. Will see what is causing this,.

Some word to coloring: the Threshold value leads to coloring of the Size(%)-column. If I interpret it right the bar is colored dependent from Size, in colors as shown in the heading? Does this make sense?
For me this color would possibly make sense in the Size-column, to be able to quickly differentiate the units - while in Bar I'd rather expect the color related to Threshold.

I kept bytes, KB, MB and GB in different colors because its easy to spot. And optionally provide a threshold value to color values red. Hmm but not all bars are colored because some are too small to be colored. I will think about this and see what i can do.

[PeterH]

You "misuse" the script as an ini-file
That's great Really. Must remember that! An implicite ini-file with an explicite initial value :-)

Yup, i first used it in the quicksearch script. But also, remember the downsides of this method as jacky mentioned here.

Too bad! I looked from position of a receiver of a script: that's fine. But the distributor must assure that the ini-section is unused - that can be hard! And to use it for constand values, as jacky said? I think it would be more easy just to fill a variable with that value...

Sorry, it seems I still got some problems - but rather exotic!
1) In a directory there's one file (143KB) and one subdirectory with 7,43GB. The file is shown as 0,00%, while the directory shows <0.01% (!) :-( Both show no bar.

2) Oh - it's the same as 1) :-) In another directory there are several files and directories from 13KB up to 74MB and *one* directory of 89GB, all are shown as 0,00%, <0,01%, and two (of MB-sizes) as 0.08% and 0.06%. Seems something in mathematics fails, if one entry exceeds 99% or so?

WHOAA! i wonder how anything worked for you in the first place. I realized just now that in Germany decimal separator is "," while here we use ".". I will fix that soon. EDIT: sorry, i had already thought about that and use RAW size to start with. Will see what is causing this,.

I didn't look hard enough! The problem occurs in other combinations, too! Maybe the % of an entry *following* another entry with 0.00% (often this is the first directory in list, after the files) shows "<0.01%"?? (Did you ever plan to show such a value with a less-sign?)
That's it? A dir has 3 sub-dirs: display is ok. I add an empty text-file: the first=biggest subdir now shows "<0.01%"

By the way: here (German) Size shows 60,09GB, Size(%) shows 39.71%. Can lead to irritation...

Some word to coloring: the Threshold value leads to coloring of the Size(%)-column. If I interpret it right the bar is colored dependent from Size, in colors as shown in the heading? Does this make sense?
For me this color would possibly make sense in the Size-column, to be able to quickly differentiate the units - while in Bar I'd rather expect the color related to Threshold.

I kept bytes, KB, MB and GB in different colors because its easy to spot. And optionally provide a threshold value to color values red. Hmm but not all bars are colored because some are too small to be colored. I will think about this and see what i can do.

I see the advantage of marking different units with colors. But why not doing this where the units are shown: in the Size column? (And this will never have no contents, as the Bar can have!)
And then the Bar can be colored with respect to Threshold...