Strong-Box design

Hello Valera. Sun 13 Oct 02 Valera Selev -> All: VS> ┌[A]:{path}─────MS-DOSLABEL─MS┐┌[A]─────────────TRDOSDISKN VS> 1─TR VS> Now everything is simple: you can change the drive VS> click on [A] to display a list like: ^^^^^^^/1 VS> ┌────┐ VS> │ A: │ VS> │ B: │ VS> │ C: │ VS> │ D: │ VS> │ E: │ VS> └────┘ VS> True, in this case two problems arise: VS> - the clock will have to be moved down; ^^^^^^^^^^^^^^^^^^^^/2 VS> - it is not clear what to do with the parameters "MSDOSLABEL" and "type ^^^^^^^^^^^^^^^^^^^/3 VS> disk" / VS> It seems to me that this problem can be solved if in the menu VS> settings, set the appropriate item (whether to display VS> name non-tr-dos /4 VS> In general, I am waiting for your suggestions on this issue. Except In paragraph /4 you yourself answered all your previous ones! Let me summarize: the user interface must be configurable, i.e. the user must not only be able to on/offeach menu item, but also indicate where to display it and how! A. on/off interface elements (I don’t need length in clusters, I don’t have hours, /3 I don’t need, etc.) b. where to output: b1. relative order (thongs of different lengths, through a separator) start/sector/st.sec/st.tr b2. absolute (thongs of fixed length) up to indicating the coordinates on the screen for /2 hours at the top or below, or the number of lines in the file window or any other. region. V. how to output dec/hex, 1/3 ext, or for /1 not a click, but simply by matching the coordinates of the arrow and the menu item. Last tip: I don’t understand what you’re drawing with text, because... Lara cuts the lines, so rivet screenshots or demos. This will make further discussion of the topic easier for everyone. Thank you for your attention.

Hello, All! Strong-Box is the working title of the commander, the first thing that came to me in the head, after digging in the dictionary for 2 hours. :) Since no one has received specific proposals for regarding the placement of content at the bottom of both panels, I myself made some changes. Since there are many controversial moments, please comment on the problems outlined below. Just in case, I give a brief explanation: So, the right panel displays information about the tr-dos disk. Meaning the content of the top and middle parts should be clear, Let's focus on the bottom lines. The first line is the file name with extension, starting address, length in bytes, length in sectors. The second line is the number of free sectors and clusters (in brackets); number of files on disk. Here and below By cluster I mean 1 KB. The third line is the number of marked sectors (clusters) and files. ┌─────────────────────────── ───┐┌─────────────────────── 10:10 ┐ │ A: B: C: D: E: MS-DOSLABEL MS││ A: B: C: D: E: TR-DOS_NAME TR│ ├─A:SYSTEM───┬───────────────┤ ├─A:──────────┬───────────────┤ │ .. │ filename dat ^││ filename dat │ filename dat ^│ │ filename dat │ ▒││ │ ▒│ [Kus!] │ │ V││ │ V│ ├──────────────┴───────────────┤ ├──────────────┴───────────────┤│ filename.dat xxxxxxxx ddmmyy ││ filename.dat xxxxx xxxxx xxx │ │ Free: xxxx (xxxxxx) hh:mm:ss ││ Free: xxxxx (xxx) Files: xxx │ │ xxxxx (xxxxxxx) in xxx files ││ xxxxx (xxx) in xxx files │ └──────────────────────────────┘ └──────────────────────────────┘ (FIG. 1) It seems that there is no more useful information to cram in there. will be possible, but reducing the size of the field displaying files will not I want to. After thinking a little, I decided that it was possible reduce the size of the top part of the window to the 1st line by rewriting it in the form: ┌[A]:{path}─────MS-DOSLABEL─MS┐┌[A]─────────────TRDOSDISKN1─TR┐ Now everything is simple: to change the drive you can click on [A] so that a list like this appears: ┌────┐ │ A: │ │ B: │ │ C: │ │ D: │ │ E: │ └────┘ In this case, however, two problems arise: - the clock will have to be moved down; - it’s not clear what to do with the “MSDOSLABEL” and “disk type” parameters (MS). The fact is that if everything is left as shown above, then in the case of a highly branched directory tree on a floppy disk (or even the hard drive, because it’s worth focusing on it too) information about the path to the current subdirectory ({path}) of length 10 characters (in case the disk name takes exactly 11 characters) will tell the user little. It seems to me that this problem can be solved if you put the appropriate one in the settings menu item (whether to display the name of non-tr-dos disks), especially sincein most cases this parameter is not used or does not carry any semantic load. So this line could be like this view: ┌[A]:SYSTEM28SYSTEM29ABC─MS┐ or like this: ┌[A]:...SYSTEM29SYSTEM30─MS┐ and so on. This problem does not arise with tr-dos disks. So, we have won 2 more lines, which allows us: - for tr-dos disks - add 2 file parameters (start track/sector), add file size display in clusters; - for ms-dos disks - add size display in sectors, regroup and add some parameters; - increase the size of the field displaying files by 1 line: ├──────────────┴───────────────┤ ├──────────────┴───────────────┤ │ filename.dat xxxxxxxx (xxxx) ││ filename.dat xxxxx xxxxx │ │ Files: xxx hh:mm:ss dd-mm-yy ││ xxx (xx) xxx xxx │ │ Free: xxxxxxxxx (xxxxxxxxxx) ││ Free: xxxxx (xxx) Files: xxx │ │ xxxxx (xxxxxxx) in xxx files ││ xxxxx (xxx) in xxx files │ └──────────────────────────────┘ └──────────────────────────────┘ Summarizing the above, we get something like: ┌[A]:SYSТEM28SYSTEM29ABC─MS┐┌[A]─────────────TRDOSDISKN1─TR┐ │ .. │ filename dat ^││ filename dat │ filename dat ^│ │ filename dat │ ▒││ │ ▒│ [Kus!] │ │ V││ │ V│├──────────────┴───────────────┤ ├──────────────┴───────────────┤ │ filename.dat xxxxxxxx (xxxx) ││ filename.dat xxxxx xxxxx │ │ Files: xxx hh:mm:ss dd-mm-yy ││ xxx (xx) xxx xxx │ │ Free: xxxxxxxxx (xxxxxxxxxx) ││ Free: xxxxx (xxx) Files: xxx │ │ xxxxx (xxxxxxx) in xxx files ││ xxxxx (xxx) in xxx files │ └──────────────────────────────┘ └──────────────────────────────┘ (FIG. 2) Obviously, over the content and size of the values of some You still need to think about the parameters for panels of non-tr-dos drives. The obvious waste of space in the line immediately catches your eye. Free: xxxxxxxx (xxxxxxxxxx). Besides, I don't know what optimal size of each value (number of marked files, sectors, clusters, number of free sectors/clusters, file size in bytes/sectors). Obviously that if, for example, 12345678 clusters are marked, then the last The line should be displayed like this: ? (12345678) in 567 files In general, I look forward to your suggestions on this issue. In addition, I'm wondering if it's worth changing the original design? (FIG. 1) to design (FIG. 2)? <<< WBR, Stormbringer >>> <<< *500:322/67.64* >>> AKA <<< *2:462/162.7* >>> <<< http://cobrasoft.narod.ru >>>

Hello Valera! 13 Oct 02 22:42, Valera Selev -> All: And who will write all this? Or is he already writing? Alexander

Hello, Valera! 13 Oct 02 22:42, Valera Selev -> All: VS> Since no one has received specific proposals for VS> regarding the placement of content at the bottom of both panels, I myself VS> made some changes. Since there are many controversial VS> points, please comment on the problems outlined below. Do the setup. Something like this. ╔═[■]═══════════════ Panel settings ════════════════════╗ ║ ║ ║ Sort by... Appearance ║ ║ ( ) Name [ ] Directory size ║ ║ ( ) Long name [X] Current file ║ ║ (.) Extension [X] Marked files ║ ║ ( ) Long extension [X] Catalog information ║ ║ ( ) Size [X] Free space ║ ║ ( ) Time [X] File highlighting ║ ║ ( ) Group [X] Executed to the beginning ║ ║ ( ) Do not sort [X] Archives to the beginning ║ ║ File mask ║ ║ *.* ▐.▌ ║ ║ ║ ║. OK .▄ Cancel ▄ Help ▄ ║║ ▀▀▀▀▀▀▀▀ ▀▀▀▀▀▀▀▀ ▀▀▀▀▀▀▀▀ ║ ╚════════════════════════════ ═════════════════════════════╝ Or like in Isdos - you launch the resident, it always gives you all the necessary information displays the service (3rd from the top) line. WBR, Jason. /*e-mail: jason2000(scary dog)yandex.ru ICQ: 62235830*/ /np:/ *silence*

Hello, Alexander! 10.15.2002 at 11:23 Alexander Shushkov wrote to Valera Selev: AS> Who will write all this? Or is he already writing? One person has already volunteered. In addition, the sources will be thrown into CODE.ZX and there actively (hopefully) discussed by everyone. <<< WBR, Stormbringer >>> <<< *500:322/67.64* >>> AKA <<< *2:462/162.7* >>> <<< http://cobrasoft.narod.ru >>>

Hello, Evgeny! 4.10.2002 at 14:13 Evgeny Goljakov wrote to Valera Selev: EG> In paragraph /4 you yourself answered all your previous ones! And asked if the panel title looked like: ┌[A]:...SYSTEM29SYSTEM30─MS┐ And since there are no objections, I will focus on this option. EG> Let me summarize: the user interface must be configurable EG> i.e. the user should not only be able to on/off EG> each menu item, but also indicate where to display it and how! [skipped] It would be interesting to know the opinion of _all_ coders (in particular, Vlad Sotnikov) on this the question is whether the introduction of the features proposed by EG will lead to a sharp increase memory occupied by the commander? EG> Last tip: I don’t understand what you’re drawing with text In my opinion, it's more convenient. It is immediately clear what is being discussed. EG> because Lara cuts lines, so rivet screenshots or demos. EG> This will facilitate further discussion of the topic for all reals. Next time I will post an image of only one of the panels. <<< WBR, Stormbringer >>> <<< *500:322/67.64* >>> AKA <<< *2:462/162.7* >>> <<< http://cobrasoft.narod.ru >>>

Hello Valerij! 10/16/2002 at 05:06 Valerij Kozhevnikoff wrote to Valera Selev: VK> Make a setup. Something like this. VK> Or as in Isdos - you launch the resident, it will give you all the information you need VK> constantly outputs to the service (3rd from the top) line. Also an option. <<< WBR, Stormbringer >>> <<< *500:322/67.64* >>> AKA <<< *2:462/162.7* >>> <<< http://cobrasoft.narod.ru >>>

Hello Valera! 21 Oct 02 09:11, Valera Selev -> Evgeny Goljakov: VS> And asked if you were happy with the panel title in the form: VS> ┌[A]:...SYSTEM29SYSTEM30─MS┐ VS> And since there are no objections, I will focus on this option. In my commander (TR-DOS Navigator) I did this: A:....DIR.SYS\n where A is the name of the current drive, DIR.SYS is the name of the directory we are in, and the number of dots indicates nesting (by analogy with is-DOS). If we are in the root directory, then the line looks like this: A:\n If we are in a directory located in the root, then the line looks like this: A:DIR.SYS\n With further nesting there are points: A:..DIR.SYS Stanislav

Hello Valera! 21 Oct 02 09:11, Valera Selev -> Alexander Shushkov: Everything is clear! Let them write... Alexander

Hello, Stanislav! 11/10/2002 at 21:17 Stanislav Yudin wrote to Valera Selev: VS>> And since there are no objections, I will focus on this option. SY> In my commander (TR-DOS Navigator) I did this: SY> A:....DIR.SYS This option can also be considered. <<< WBR, Stormbringer >>> <<< *500:322/67.64* >>> AKA <<< *2:462/162.7* >>> <<< http://cobrasoft.narod.ru >>>