Toolbar command

[serendipity]

The new toolbar command looks promising.
Do you plan to provide a fixed button on toolbar which will allow to load toolbars?
That way users wont have to remember shortcuts or go all the way to catalog to load toolbars. Just wondering.

[admin]

What would that button do? How would the user define what it does?

[barking dog]

Maybe like the FavoriteFiles/Folders button: you press the button and a list opens where you can select the Toolbar. The management of the entries could work like it does in "List Management" now.

A similar button would also be great for the coming "Catalog switching".

[serendipity]

What would that button do? How would the user define what it does?

I was suggesting something like "load scripts" where all scripts can be loaded from one place. In the case of toolbar it would be easier for users to launch custom toolbars from inside (a button which triggers pull down menu) toolbar. That way I dont have to go searching for my toolbars in my pile of other scripts or dont have to assign shortcuts to them.

[admin]

What would that button do? How would the user define what it does?

I was suggesting something like "load scripts" where all scripts can be loaded from one place. In the case of toolbar it would be easier for users to launch custom toolbars from inside (a button which triggers pull down menu) toolbar. That way I dont have to go searching for my toolbars in my pile of other scripts or dont have to assign shortcuts to them.

I have a better idea: offer 5 (or so) fully customizable toolbar definitions, selectable from the main menu (with KS), and/or from a special toolbar button, no scripting involved. But is there demand for this? Don't want to add stuff nobody needs...

[Stefan]

I have a better idea: offer 5 (or so) fully customizable toolbar definitions, selectable from the main menu (with KS),
and/or from a special toolbar button, no scripting involved. But is there demand for this?

Yes.


What's about an drop down button with as many entries i can get.
So we would have more then five triggers.
Would use to access XY build in commands, tools and scripts. My own command bar, all *i* need at one point.

Could be configured via an user.ini

abc_Name=Run &iVew
abc_App=C:\Tools\IView\Iview.exe
abc_Para=<curitem>
abc_ToolTip=
abc_StartDir=

44L_Name=&Test Script
44L_App=<XYdir>\Scripts\test.yxs

xyz3_Name=
xyz3_App=

[admin]

I have a better idea: offer 5 (or so) fully customizable toolbar definitions, selectable from the main menu (with KS),
and/or from a special toolbar button, no scripting involved. But is there demand for this?

Yes.


What's about an drop down button with as many entries i can get.
So we would have more then five triggers.
Would use to access XY build in commands, tools and scripts. My own command bar, all *i* need at one point.

Could be configured via an user.ini

abc_Name=Run &iVew
abc_App=C:\Tools\IView\Iview.exe
abc_Para=<curitem>
abc_ToolTip=
abc_StartDir=

44L_Name=&Test Script
44L_App=<XYdir>\Scripts\test.yxs

xyz3_Name=
xyz3_App=

You get scriptable buttons soon, don't worry.

My idea, however, was a newbie-friendly non-scripting click-and-go thing.

[serendipity]

I have a better idea: offer 5 (or so) fully customizable toolbar definitions, selectable from the main menu (with KS), and/or from a special toolbar button, no scripting involved. But is there demand for this? Don't want to add stuff nobody needs...

You mean like 5 different toolbar templates which users (esp. newbies) can quickly access? Yeah, might be good for non-scripters.
I guess you will provide a dropdown list with 5 toolbar templates in them which is configurable. If so, then in addition to the 5 toolbar templates, maybe scripters can add their own toolbars to the bottom of the dropdown list.

Just an idea: maybe any script file with suffix .XYT (XY Toolbar) gets added to this list automatically.
This might be useful for the Customizable Toolbar Buttons (CTB) which is coming sometime later, .XYT has entries like:
toolbar ("back=c:\my icons\back.ico, fore=c:\my icons\fore.ico,up=c:\my icons\up.ico,refresh,");

[admin]

I have a better idea: offer 5 (or so) fully customizable toolbar definitions, selectable from the main menu (with KS), and/or from a special toolbar button, no scripting involved. But is there demand for this? Don't want to add stuff nobody needs...

You mean like 5 different toolbar templates which users (esp. newbies) can quickly access? Yeah, might be good for non-scripters.
I guess you will provide a dropdown list with 5 toolbar templates in them which is configurable. If so, then in addition to the 5 toolbar templates, maybe scripters can add their own toolbars to the bottom of the dropdown list.

Just an idea: maybe any script file with suffix .XYT (XY Toolbar) gets added to this list automatically.
This might be useful for the Customizable Toolbar Buttons (CTB) which is coming sometime later, .XYT has entries like:
toolbar ("back=c:\my icons\back.ico, fore=c:\my icons\fore.ico,up=c:\my icons\up.ico,refresh,");

Let's keep it simple. Do you really need more than 5 fully configurable toolbar layouts? That's 5 per INI file (and you can have infinite INI files...). Plus you can add any number of toolbar layouts using the toolbar() scripting command.

I'm not even sure if I should do the 5. It's a bit bloaty...

[serendipity]

Let's keep it simple. Do you really need more than 5 fully configurable toolbar layouts? That's 5 per INI file (and you can have infinite INI files...). Plus you can add any number of toolbar layouts using the toolbar() scripting command.

I'm not even sure if I should do the 5. It's a bit bloaty...

On a second thought, I think 5 toolbars is not the way to go. This is what I think users need:
One toolbar with all the buttons one needs. But since not all buttons will fit into the toolbar there needs to be a way to see other buttons by either a pull down list or an arrow on the right end to scroll to other button.
After much thought I think I will not like to launch a new toolbar everytime i need to access a button which is not shown in my current layout. I would instead use pull down list or somethign else and access that button which is much easier. Also, I have to remember which toolbar hold which of my buttons, naaah too much work. My 2 cents.

[j_c_hallgren]

On a second thought, I think 5 toolbars is not the way to go. This is what I think users need:
One toolbar with all the buttons one needs. But since not all buttons will fit into the toolbar there needs to be a way to see other buttons by either a pull down list or an arrow on the right end to scroll to other button.

Fully agree here! But with one addendum...that is: provide an selectable alternative of mutiple rows (Min of 2, maybe max of 3?) so that if user wanted to give up screen space for that, they could...those scroll/drop-downs aren't as easy to use sometimes as having them all showing...but for the space conscious, they work just fine.

The mutiple rows has been discussed numerous times here so it's not a new idea...just adding it to this thread...as the whole idea of multiple toolbars was actually a bit confusing to even me.

However, being able to add custom items to it using a selection of generic or user supplied icons is something that could be used even by a newbie.

[admin]

Thanks for the input. My original idea of selectable toolbars included the possibility of giving them meaningful names (menu captions). I thought of specific work phases where you would need a couple of otherwise rarely used buttons etc. Same idea basically as selectable Catalogs, which has been often wished here in the forum.

Anyway, it was a rather theoretical idea. Nobody ever asked for it, and me myself never really missed it (apart from when I make screenshots for XY and want to have certain buttons on the shot... ) -- so no hurry here.

Conc. the popups for excessive buttons: is planned for 8.30...