BarEditor is a editor of *.bar files.
It looks like TC dialog "Change button bar".
Support some additional abilities:
Drag-And-Drop
Copy\Paste in TC clipboard format
Useful to edit bar files separately of TC.
Link you can find the next post...
BarEditor - *.bar files editor
Moderators: Hacker, petermad, Stefan2, white
BarEditor can be downloaded from http://b4rr4cuda.rxfly.net/bareditor.php
B4rr4cudaNice tool, I was waiting for such one !
Just a little problem when creating a new bar... User must first of all choice a name for the new bar...
If he begin to construct the new bar without name, when he shall choice the name all his work is gone and deleted...
Aside : Are you planning to make it translatable in a future version ?
Friendly
Paul
Ouistiti, #11943
L'important n'est pas de convaincre, mais de donner à réfléchir.
The important thing is not to convince, but to incite to think.
1,77245385090552... •
L'important n'est pas de convaincre, mais de donner à réfléchir.
The important thing is not to convince, but to incite to think.
1,77245385090552... •
BarEditor updated to v 0.8. Download it here
v 0.8
[*] replace non selected text field
[*] Double prevouse icon if current icon not exist
[+] "Wait" cursor while bar save.
[/] Options.ini renamed to BarEditor.ini
[/] paths listst moved to BarEditor.ini
[+] menu with parameters for ТС next to "Parameters" text field
v 0.7
[*] copy to clipboard with unposibility to paste as text
[+] option "On Top"
[/] Clearly save. Without empty fields.
[+] Search in "Path".
[+] Autoload icons after manual type into "Icon file" field
[+] Save dialog on OK button with no bar as param
[+] Cache in icl. To work with TCMenu.
[+] Icons cache icl. Icons's links redirected to icl file. Be careful!
[+] List of paths and aliases. Like %windir% one. Fill in paths.ini. Right click on edit field and click menu item you need.
v 0.8
[*] replace non selected text field
[*] Double prevouse icon if current icon not exist
[+] "Wait" cursor while bar save.
[/] Options.ini renamed to BarEditor.ini
[/] paths listst moved to BarEditor.ini
[+] menu with parameters for ТС next to "Parameters" text field
v 0.7
[*] copy to clipboard with unposibility to paste as text
[+] option "On Top"
[/] Clearly save. Without empty fields.
[+] Search in "Path".
[+] Autoload icons after manual type into "Icon file" field
[+] Save dialog on OK button with no bar as param
[+] Cache in icl. To work with TCMenu.
[+] Icons cache icl. Icons's links redirected to icl file. Be careful!
[+] List of paths and aliases. Like %windir% one. Fill in paths.ini. Right click on edit field and click menu item you need.
Suggestion:
New button with list (user editable, stored in BarEditor.ini )
to insert into fields:
like
[Paste items]
%COMMANDER_DRIVE%
%COMMANDER_INI%
%COMMANDER_PATH%
%U3_DEVICE_EXEC_PATH%
%$APPDATA%
%$COMMON_APPDATA%
%$COMMON_DESKTOPDIRECTORY%
%$COMMON_DOCUMENTS%
%$COMMON_PICTURES%
%$COMMON_PROGRAMS%
%$COMMON_STARTMENU%
%$COMMON_STARTUP%
%$DESKTOP%
%$FONTS%
%$LOCAL_APPDATA%
%$MYMUSIC%
%$MYPICTURES%
%$MYVIDEO%
%$PERSONAL%
%$PROGRAMS%
%$STARTMENU%
%$STARTUP%
E:\my-icons-path\
X:\Tools\
%P%O-new.txt
...
New button with list (user editable, stored in BarEditor.ini )
to insert into fields:
like
[Paste items]
%COMMANDER_DRIVE%
%COMMANDER_INI%
%COMMANDER_PATH%
%U3_DEVICE_EXEC_PATH%
%$APPDATA%
%$COMMON_APPDATA%
%$COMMON_DESKTOPDIRECTORY%
%$COMMON_DOCUMENTS%
%$COMMON_PICTURES%
%$COMMON_PROGRAMS%
%$COMMON_STARTMENU%
%$COMMON_STARTUP%
%$DESKTOP%
%$FONTS%
%$LOCAL_APPDATA%
%$MYMUSIC%
%$MYPICTURES%
%$MYVIDEO%
%$PERSONAL%
%$PROGRAMS%
%$STARTMENU%
%$STARTUP%
E:\my-icons-path\
X:\Tools\
%P%O-new.txt
...
/join #TCMD Chat at irc.freenode.net - Today's newbies are tomorrow's experts.
B4rr4cudaPlease don't forget to add on your "todo list" to make it translatable ! I'm waiting for a ".lng" file !!!
(Already partialy possible in the ini for the parameters!)
Nevertheless it's a good work
Paul
Ouistiti, #11943
L'important n'est pas de convaincre, mais de donner à réfléchir.
The important thing is not to convince, but to incite to think.
1,77245385090552... •
L'important n'est pas de convaincre, mais de donner à réfléchir.
The important thing is not to convince, but to incite to think.
1,77245385090552... •
I remember about this.Please don't forget to add on your "todo list" to make it translatable ! I'm waiting for a ".lng" file !!!
Just copy your parameters from translated TC help file.Already partialy possible in the ini for the parameters
Add your own parameters in BarEditor.ini -> [params] section.
Format is
String to insert - Description
Do not forget about "-"!!!
There you can add any things you want.
Example:
%COMMANDER_PATH% - Path to TC
or
It's a good day to die - WarCraft Cheat
or
IDDQD - DOOM cheat
B4rr4cuda wrote:Open BarEditor.ini and look section [Paths]. It is editable.New button with list (user editable, stored in BarEditor.ini )
Copy your list there than right-click on text field, enjoy.
But button is a good idea!
Perfekt.
(that should be in TC a long time ago)Feel free to include the %var% list
into the ini within your archive
so one can see this fantastic feature
(or at least remove the semicolon there from %windir%)P.S. i need no button for this, context menu is enough.
/join #TCMD Chat at irc.freenode.net - Today's newbies are tomorrow's experts.
BarEdit is a nice tool, and thank you very much for it! But I have some suggestions!
Within TC's limited "one bar displayed at a time" schema, it is helpful to think of each TC toolbar file as composed of three "regions":
Region A: Bar navigation
In this region are buttons that link to additional bars or (very importantly) return to the previous bar.
Region B: Standard buttons
In this region are buttons that should appear on every bar.
Region C: Unique buttons
This region contains the buttons unique to the specific toolbar.
The internal TC bar dialog and BarEditor both manage "Region C" buttons adequately, but neither tool offers any assistance for easily managing the interconnection links between toolbars ("Region A" buttons) or propagating groups of "standard" buttons ("Region B" buttons) between multiple toolbars.
So... my suggestions for improving BarEdit are:
1. Previous Toolbar Button
Provide some mechanism for BarEdit to automatically maintain a "previous toolbar" button on every toolbar file by appropriately updating a Previous button on every linked toolbar (except the "top" toolbar) automatically in response to user input about which toolbars link to which toolbars.
Given the limitations of TCs toolbar implementation, this means that the group of toolbars connected by "previous" buttons would necessarily be connected in an hierarchical structure (as opposed to a "network" structure). A hierarchy of toolbars is OK with me and could be modeled easily in the BarEdit dialog with a drag and drop outline control.
2. Home Toolbar Button
Use the same mechanism to automatically implement and maintain in all related toolbars a "Home" toolbar button that would link to a specific "home" toolbar.
Suggestions 1 & 2 address "Region A", above.
3. Repository of "Sub-Toolbars"
Provide for a means to define and manage multiple "boiler-plate" toolbar sections (or "partial" toolbars) that can be easily inserted into any toolbar. I conceive of a "repository" of sub bars that could be easily mixed and matched.
Suggestion 3 addresses "Region B", above.
I flow-charted a tool to offer all of this about 5 years ago but have never gotten around to implementing it. Perhaps BarEdit is the appropriate place for this functionality.
Thanks for listening!!
Within TC's limited "one bar displayed at a time" schema, it is helpful to think of each TC toolbar file as composed of three "regions":
Region A: Bar navigation
In this region are buttons that link to additional bars or (very importantly) return to the previous bar.
Region B: Standard buttons
In this region are buttons that should appear on every bar.
Region C: Unique buttons
This region contains the buttons unique to the specific toolbar.
The internal TC bar dialog and BarEditor both manage "Region C" buttons adequately, but neither tool offers any assistance for easily managing the interconnection links between toolbars ("Region A" buttons) or propagating groups of "standard" buttons ("Region B" buttons) between multiple toolbars.
So... my suggestions for improving BarEdit are:
1. Previous Toolbar Button
Provide some mechanism for BarEdit to automatically maintain a "previous toolbar" button on every toolbar file by appropriately updating a Previous button on every linked toolbar (except the "top" toolbar) automatically in response to user input about which toolbars link to which toolbars.
Given the limitations of TCs toolbar implementation, this means that the group of toolbars connected by "previous" buttons would necessarily be connected in an hierarchical structure (as opposed to a "network" structure). A hierarchy of toolbars is OK with me and could be modeled easily in the BarEdit dialog with a drag and drop outline control.
2. Home Toolbar Button
Use the same mechanism to automatically implement and maintain in all related toolbars a "Home" toolbar button that would link to a specific "home" toolbar.
Suggestions 1 & 2 address "Region A", above.
3. Repository of "Sub-Toolbars"
Provide for a means to define and manage multiple "boiler-plate" toolbar sections (or "partial" toolbars) that can be easily inserted into any toolbar. I conceive of a "repository" of sub bars that could be easily mixed and matched.
Suggestion 3 addresses "Region B", above.
I flow-charted a tool to offer all of this about 5 years ago but have never gotten around to implementing it. Perhaps BarEdit is the appropriate place for this functionality.
Thanks for listening!!
Licensed, Mouse-Centric, moving (slowly) toward Touch-centric
v 1.0
[*] clear "Button bar:"
[*] crear icon's path on click
[+] Default menu on right click. Menu with paths appears if do not release mouse right button for a part of second. (300ms)
Here
2JohnFredC. This tool can create toolbars count you need with links between created bars. Sorry, but I have no link to this tool. I took it from my soft archive.
Reading your suggestions I thought about space-shuttle.
Really, how can you imagine this automatical add button mechanism for BarEditor?
What "Prevouse button" or "Home button" link must it add in case I open the separate *.bar with F4 key? Or bar was opened with shift+click in TCMenu?
I can realize it as separate tool only. But I'm not interesed in this. Sorry.
But your idea of repositary is good. Perhaps, I'll realize it.
It is too specific...
[*] clear "Button bar:"
[*] crear icon's path on click
[+] Default menu on right click. Menu with paths appears if do not release mouse right button for a part of second. (300ms)
Here
2JohnFredC
Nested Button Bar Creator 2.00 manage "Region A" use... neither tool offers any assistance for easily managing the interconnection links between toolbars ("Region A" buttons)
. This tool can create toolbars count you need with links between created bars. Sorry, but I have no link to this tool. I took it from my soft archive.Reading your suggestions I thought about space-shuttle.
Really, how can you imagine this automatical add button mechanism for BarEditor?
What "Prevouse button" or "Home button" link must it add in case I open the separate *.bar with F4 key? Or bar was opened with shift+click in TCMenu?
I can realize it as separate tool only. But I'm not interesed in this. Sorry.
But your idea of repositary is good. Perhaps, I'll realize it.
I'm not surprised. Everyone use toolbar in his individual style. And the tool you guess is directed to your own style.I flow-charted a tool to offer all of this about 5 years ago but have never gotten around to implementing it.
It is too specific...