So... we are waiting...pdavit wrote:Just hold your horses for a couple of days till I post the example.
Mastering Total Commander
Moderators: Hacker, petermad, Stefan2, white
-
pdavit
- Power Member
- Posts: 1529
- Joined: 2003-02-05, 21:41 UTC
- Location: Kavala -> Greece -> Europe -> Earth -> Solar System -> Milky Way -> Space
- Contact:
Well, here it is, the example I promised to you: http://www.angelfire.com/theforce/pdavit/guide.zip
Any suggestions are welcome.
I will start soon building a doc about changing menus but this will take some time.
I’m equally waiting for other users work!
Any suggestions are welcome.
I will start soon building a doc about changing menus but this will take some time.
I’m equally waiting for other users work!
"My only reason for still using M$ Window$ as an OS is the existence of Total Commander!"
Christian Ghisler Rules!!!
Christian Ghisler Rules!!!
Nice.
Some comments (don't let them discourage you, take them as constructive criticism):
10 pages for a single feature? Who's going to read this? And when you multiply that with the number of features, who's going to read that (considering how few people actually have read the Help)?
You could also mention the possibility to include FTP dirs and explain how to remove the Accel chars for Configure, Add current dir and Remove current dir (even though it's a bit outside of the scope)
Proofreader's comments:
- You are using both CTRL and Ctrl. Rather stick to one (my choice would be Ctrl). This also applies to SHIFT.
- Table 1 - the font for the meanings is either too small or too italic comfortable to read.
- Table 1 - entry 8 - ambiguous "Saves the changes made to the file wincmd.ini in the Windows directory" - one could think you are changing some wincmd.ini, not the directory hotlist. Rather something like "Saves the Directory Hotlist".
- I personally like the "graphical" description of widimec more than the table-like description of the Dir Hotlist. However, descriptions like "Toolbar", "Drive selector", "[<<] butons" and "Text boxes" are a bit unnecessary IMHO, unless you write something about them.
HTH
Roman
Some comments (don't let them discourage you, take them as constructive criticism):
10 pages for a single feature? Who's going to read this? And when you multiply that with the number of features, who's going to read that (considering how few people actually have read the Help)? You could also mention the possibility to include FTP dirs and explain how to remove the Accel chars for Configure, Add current dir and Remove current dir (even though it's a bit outside of the scope) Proofreader's comments:- You are using both CTRL and Ctrl. Rather stick to one (my choice would be Ctrl). This also applies to SHIFT.
- Table 1 - the font for the meanings is either too small or too italic comfortable to read.
- Table 1 - entry 8 - ambiguous "Saves the changes made to the file wincmd.ini in the Windows directory" - one could think you are changing some wincmd.ini, not the directory hotlist. Rather something like "Saves the Directory Hotlist".
- I personally like the "graphical" description of widimec more than the table-like description of the Dir Hotlist. However, descriptions like "Toolbar", "Drive selector", "[<<] butons" and "Text boxes" are a bit unnecessary IMHO, unless you write something about them.
HTH
Roman
-
pdavit
- Power Member
- Posts: 1529
- Joined: 2003-02-05, 21:41 UTC
- Location: Kavala -> Greece -> Europe -> Earth -> Solar System -> Milky Way -> Space
- Contact:
2 Hacker
> 10 pages for a single feature? Who's going to read this? And when you multiply that with the number of features, who's going to read that (considering how few people actually have read the Help)?
First of all nobody is forced to read the whole manual. You selectively go to the chapter (feature) that concerns you and that’s it. If you need for example to read the syntax of the ipconfig command on a DOS book you don’t read the whole book, do you?
Now, as far as the length is concerned. It looks big because it includes a cover, a table of contents and a credits section. All these will be common in the final manual for all the features. In addition, there are some blank parts to separate sub-section. If for example the HTML approach is followed these will be also eliminated.
> You are using both CTRL and Ctrl. Rather stick to one (my choice would be Ctrl). This also applies to SHIFT.
Ctrl is also my choice. The error was sourced from the fact that, that bit was copied directly for TC’s manual, which follows the upper case style! Sorry! God, you are a perfectionist, aren’t you!!
I don’t blame you, that’s why you’re using TC anyway!
> You could also mention the possibility to include FTP dirs…
Are you talking about the different syntax for changing dirs or just a note that it's possible, or both for all I know?
> …and explain how to remove the Accel chars for Configure, Add current dir and Remove current dir (even though it's a bit outside of the scope)
Yeah, I initial thought of that but I overruled it for various reasons:
- It belongs to another section
- I didn’t want to include info that alters TC itself.
- The idea belongs to another guy (sorry that I cannot name him although I know his name; I’m not allowed you see), which I guess should be part of his contribution to this project.
> Table 1 - entry 8 – ambiguous
That’s yet again a direct copy from TC’s manual! The whole table actually is a copy from the help file. I just followed the table approach coz I think it looks better for explaining the GUI elements with the numbers.
Now, for aesthetics in general, I guess we should leave that to the standard style that should be decided. That was just my example since I hadn’t any detailed feedback on that from posts here.
> 10 pages for a single feature? Who's going to read this? And when you multiply that with the number of features, who's going to read that (considering how few people actually have read the Help)?
First of all nobody is forced to read the whole manual. You selectively go to the chapter (feature) that concerns you and that’s it. If you need for example to read the syntax of the ipconfig command on a DOS book you don’t read the whole book, do you?
Now, as far as the length is concerned. It looks big because it includes a cover, a table of contents and a credits section. All these will be common in the final manual for all the features. In addition, there are some blank parts to separate sub-section. If for example the HTML approach is followed these will be also eliminated.
> You are using both CTRL and Ctrl. Rather stick to one (my choice would be Ctrl). This also applies to SHIFT.
Ctrl is also my choice. The error was sourced from the fact that, that bit was copied directly for TC’s manual, which follows the upper case style! Sorry! God, you are a perfectionist, aren’t you!!
I don’t blame you, that’s why you’re using TC anyway! > You could also mention the possibility to include FTP dirs…
Are you talking about the different syntax for changing dirs or just a note that it's possible, or both for all I know?
> …and explain how to remove the Accel chars for Configure, Add current dir and Remove current dir (even though it's a bit outside of the scope)
Yeah, I initial thought of that but I overruled it for various reasons:
- It belongs to another section
- I didn’t want to include info that alters TC itself.
- The idea belongs to another guy (sorry that I cannot name him although I know his name; I’m not allowed you see), which I guess should be part of his contribution to this project.
> Table 1 - entry 8 – ambiguous
That’s yet again a direct copy from TC’s manual! The whole table actually is a copy from the help file. I just followed the table approach coz I think it looks better for explaining the GUI elements with the numbers.
Now, for aesthetics in general, I guess we should leave that to the standard style that should be decided. That was just my example since I hadn’t any detailed feedback on that from posts here.
"My only reason for still using M$ Window$ as an OS is the existence of Total Commander!"
Christian Ghisler Rules!!!
Christian Ghisler Rules!!!
2pdavit
Thanks Panos
Sorry I had no time to read it carefully and send you my comments before but now I've downloaded the new version and...
1. Good job (Some tips are really simple but very useful)
2. After readding the first version I wanted to suggest you to add "Last modification date" but I see you added version number now
3. I would move the forth section after the second one cause I think that both configuration sections (2 and 4) should be near each other.
4. Describing manual editing .ini file you could add information that in some cases there can also be saved "destination path"
5. You could also add information that it's possible to add to the Hotlist Directory some location of FileSystem Plugins (I don't know how to express it but hope you know what I mean).
Eg. I have added to the Hotlist my mailboxes!!! (POP3 plugin)
I also added some sortcuts to often used keys in system registry (Registry plugin)
The next ones are: calendar, versions, eventlog plugins...
I know that most people don't use the plugins but I think that these who use sometimes don't know it's possible to add them to Hotlist.
6. Saving FTPs together with destination directory is very useful when you eg. often use synchronization your local directory with ftp
Thanks Panos
Sorry I had no time to read it carefully and send you my comments before but now I've downloaded the new version and...
1. Good job (Some tips are really simple but very useful)
2. After readding the first version I wanted to suggest you to add "Last modification date" but I see you added version number now
3. I would move the forth section after the second one cause I think that both configuration sections (2 and 4) should be near each other.
4. Describing manual editing .ini file you could add information that in some cases there can also be saved "destination path"
eg.: path58=C:\Downloads\The above code (previous page) will have to outcome shown in Figure 3 (page 6). For every entry you usually see a pair of commands one corresponding to the title of the entry (e.g. menu58) and one for the command to be executed (e.g. cmd58).
5. You could also add information that it's possible to add to the Hotlist Directory some location of FileSystem Plugins (I don't know how to express it but hope you know what I mean).
Eg. I have added to the Hotlist my mailboxes!!! (POP3 plugin)
I also added some sortcuts to often used keys in system registry (Registry plugin)
The next ones are: calendar, versions, eventlog plugins...
I know that most people don't use the plugins but I think that these who use sometimes don't know it's possible to add them to Hotlist.
6. Saving FTPs together with destination directory is very useful when you eg. often use synchronization your local directory with ftp
-
pdavit
- Power Member
- Posts: 1529
- Joined: 2003-02-05, 21:41 UTC
- Location: Kavala -> Greece -> Europe -> Earth -> Solar System -> Milky Way -> Space
- Contact:
2 djk
Thanks for the tips I will update the guide with your suggestions apart from suggestion number 3 which I personally believe it’s better this way since “amateur” users know where to stop reading!
Thanks for the tips I will update the guide with your suggestions apart from suggestion number 3 which I personally believe it’s better this way since “amateur” users know where to stop reading!
"My only reason for still using M$ Window$ as an OS is the existence of Total Commander!"
Christian Ghisler Rules!!!
Christian Ghisler Rules!!!
@pdavit
About the organization of the document, as Hacker commented once you start adding more features the document size will grow, this can frighten new users. A good solution would be to split the document into a couple of documents (one per feature, or even simple feature/advanced etc.).
Another thing to consider is creating the guide in html form such that each feature/chapter can be downloaded/viewed as a standalone. Don't overdo with links in the HTML's, this might seem like a nice idea at first but can dazzle new users, as they will hop from feature to feature; a better way is to read it as a book, chapter by chapter (in no particular order), i.e. don't try to make a reference guide out of it (TC's help is good for it).
Cheers.
About the organization of the document, as Hacker commented once you start adding more features the document size will grow, this can frighten new users. A good solution would be to split the document into a couple of documents (one per feature, or even simple feature/advanced etc.).
Another thing to consider is creating the guide in html form such that each feature/chapter can be downloaded/viewed as a standalone. Don't overdo with links in the HTML's, this might seem like a nice idea at first but can dazzle new users, as they will hop from feature to feature; a better way is to read it as a book, chapter by chapter (in no particular order), i.e. don't try to make a reference guide out of it (TC's help is good for it).
Cheers.
Panos,
> You could also mention the possibility to include FTP dirs…
Are you talking about the different syntax for changing dirs or just a note that it's possible, or both for all I know?
Actually I was only thinking about mentioning that it is possible.
Check out the Ref section!
Thank you, but I personally think there is no reason I should be given credit.
Some more comments:
- I'd scrap the wincmd.ini section. Just a mention that the info is stored there. Anyone willing to mess with the INI will be intelligent enough to figure out the format himself.
- Page 8, bottom, states:
cd ftp://prividersName@userLogonName/Path1/Path2/.../PathN
e.g. cd ftp://PowerNet@JackDanniels/html/images
Apart from prividersName, the syntax usually is
ftp://username:password@ftp.domain.com/any/path/
Notice the use of forward slashes which denotes that this is probably a UNIX server.
AFAIK the forward slashes are a platform-independent FTP standard.
All,
Anyone doing anything else?
TIA
Roman
> You could also mention the possibility to include FTP dirs…
Are you talking about the different syntax for changing dirs or just a note that it's possible, or both for all I know?
Actually I was only thinking about mentioning that it is possible.
Check out the Ref section!
Thank you, but I personally think there is no reason I should be given credit.
Some more comments:
- I'd scrap the wincmd.ini section. Just a mention that the info is stored there. Anyone willing to mess with the INI will be intelligent enough to figure out the format himself.
- Page 8, bottom, states:
cd ftp://prividersName@userLogonName/Path1/Path2/.../PathN
e.g. cd ftp://PowerNet@JackDanniels/html/images
Apart from prividersName, the syntax usually is
ftp://username:password@ftp.domain.com/any/path/
Notice the use of forward slashes which denotes that this is probably a UNIX server.
AFAIK the forward slashes are a platform-independent FTP standard.
All,
Anyone doing anything else?
TIA
Roman
Mal angenommen, du drückst Strg+F, wählst die FTP-Verbindung (mit gespeichertem Passwort), klickst aber nicht auf Verbinden, sondern fällst tot um.
2pdavit
I think you coud add one more tip.
Creating submenu it's good to add as the first item - the one you use most often. When you use keyboard instead of mouse, after pressing Ctrl+D and choosing the submenu with keyboard shortcut (i.e. with &) it automatically select the first item of the submenu. Then you must only press Enter.
I know it's obvious but...it speeds up the work a little.
BTW: I've just reorganized my Hotlist
I think you coud add one more tip.
Creating submenu it's good to add as the first item - the one you use most often. When you use keyboard instead of mouse, after pressing Ctrl+D and choosing the submenu with keyboard shortcut (i.e. with &) it automatically select the first item of the submenu. Then you must only press Enter.
I know it's obvious but...it speeds up the work a little.
BTW: I've just reorganized my Hotlist
-
André Martin
- Senior Member
- Posts: 245
- Joined: 2003-02-05, 15:46 UTC
- Location: Dresden, Germany
2pdavit & all
I like this idea (the extended/advanced tc manual) very much and I could and would provide some examples and hints describing how to get the most from the POP3/SMTP Email and HTTP SmartBrowserPlugin.
Unfortunatily there are a lot exams I have to write in the next four weeks so it can take some time
Btw. I think it would be better if the manual would be xml based. xml allows to create layout/design independent content. A so called xslt stylesheet "transforms" the xml file into html and/or pdf. This would allow us to have a standardized layout and the authors don't have to take care about the design. In conjunction with a cvs server more than one author could edit and work on the content at the same time (cvs automatically merges the content)...
I like this idea (the extended/advanced tc manual) very much and I could and would provide some examples and hints describing how to get the most from the POP3/SMTP Email and HTTP SmartBrowserPlugin.
Unfortunatily there are a lot exams I have to write in the next four weeks so it can take some time
Btw. I think it would be better if the manual would be xml based. xml allows to create layout/design independent content. A so called xslt stylesheet "transforms" the xml file into html and/or pdf. This would allow us to have a standardized layout and the authors don't have to take care about the design. In conjunction with a cvs server more than one author could edit and work on the content at the same time (cvs automatically merges the content)...
Browse the web with the HTTP SmartBrowserPlugin
Check your mails with the POP3/SMTP EmailPlugin!
Check your mails with the POP3/SMTP EmailPlugin!
True but it needs a server and a person for supervising it.André Martin wrote:2pdavit & all
Btw. I think it would be better if the manual would be xml based. xml allows to create layout/design independent content. A so called xslt stylesheet "transforms" the xml file into html and/or pdf. This would allow us to have a standardized layout and the authors don't have to take care about the design. In conjunction with a cvs server more than one author could edit and work on the content at the same time (cvs automatically merges the content)...
-
André Martin
- Senior Member
- Posts: 245
- Joined: 2003-02-05, 15:46 UTC
- Location: Dresden, Germany
