nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ToolBar Deprecated at V2.3

BrianGustafson

What is replacing the toolbar control at V2.3 and 3.0?

Encontre mais publicações marcadas com

Accepted answers

All comments

ValentinFedulov

...
But the effort involved to keep your App the same is very little - download the code from Codeplex and add it to your app - 30 minutes work

ArcGIS Silverlight Toolkit Toolbar from http://esrisilverlight.codeplex.com/releases/view/60154
So, I download ArcGIS Silverlight Toolkit v2.2 sources and extract Toolbar component and make standalone lib.
This is it - Toolbar only lib from ESRI.ArcGIS.Client.Toolkit
Sources included.
https://www.arcgis.com/home/item.html?id=d0d90aae25604cdca900791589b4856a

deleted-user-ATjHIWsdQYmT

Well, it's true that the toolbar doesn't help that much. For example, I never really tried to add a combobox to a toolbar, but I don't think it was supported. It probably only supports command buttons.

On the other hand, what would really be helpful and very tied to ESRI's map functionality is to have those buttons show up as pressed-down when the tool is active and if I pick another tool from pressing other button, the former button gets back to not-pressed state. This would require closer handling of what Draw object is currently active in the map. It would work even if I have different toolbars.

Wish list? Or does anyone know of something close to it?

Why would you want to add a combo box to a toolbar? I think your statement is correct that the toolbar is primarily for tools or command buttons. If you want to add a combo box, just put the toolbar inside a stackpanel along with your combo box.

As for button state: You could listen to the TooBarItemCicked event or the ToobarIndexChanged event for the toolbar and swap out images or add a border based on the index of the tool. Another reason to keep the toolbar around - the Events have already been created.

OrlandoCarvajal

Well, it's true that the toolbar doesn't help that much. For example, I never really tried to add a combobox to a toolbar, but I don't think it was supported. It probably only supports command buttons.

On the other hand, what would really be helpful and very tied to ESRI's map functionality is to have those buttons show up as pressed-down when the tool is active and if I pick another tool from pressing other button, the former button gets back to not-pressed state. This would require closer handling of what Draw object is currently active in the map. It would work even if I have different toolbars.

Wish list? Or does anyone know of something close to it?

deleted-user-ATjHIWsdQYmT

Why is any code deprecated, someone will always be using the code in question.

But I am sure ESRI have good reasons 🙂

Maybe one less control for them to support - although a very basic control with little that can go wrong
Reduce the overall download size of the toolkit assembly
Encourage more interesting and individual websites instead of many ESRI sample site clones

Only ESRI Silverlight team can answer your question.

But the effort involved to keep your App the same is very little - download the code from Codeplex and add it to your app - 30 minutes work

Kind of a contradiction in terms, no?

ChrisSmith

I guess my point is more along the lines of, "Why take away something that's working just fine and so many people have already implemented"? I'm not really looking for any improvements as it seems to work just fine the way it is. Your comment on searching bing/google for tutorial & source code isn't even necessary with the current toolbar. It's there. You add it, wire it to your map and done. This all gets back to my main point, and I think Patrick's point too - Why take away something that aready exists and works just fine?

Why is any code deprecated, someone will always be using the code in question.

But I am sure ESRI have good reasons 🙂

Maybe one less control for them to support - although a very basic control with little that can go wrong
Reduce the overall download size of the toolkit assembly
Encourage more interesting and individual websites instead of many ESRI sample site clones

Only ESRI Silverlight team can answer your question.

But the effort involved to keep your App the same is very little - download the code from Codeplex and add it to your app - 30 minutes work

deleted-user-ATjHIWsdQYmT

To add my £0.02 worth

I'm with ESRI on this one, basic control that anyone can create I would much prefer they invested time in better and faster mapping functionality 🙂 than basic controls you can spend 5 minutes searching on google/bing and find a tutorial & source code for.

As Dominique has pointed out the code is on codeplex, so no big deal to take the code and add it to your own control library, then point your xaml to this control - very small job

Cheers

Chris

I guess my point is more along the lines of, "Why take away something that's working just fine and so many people have already implemented"? I'm not really looking for any improvements as it seems to work just fine the way it is. Your comment on searching bing/google for tutorial & source code isn't even necessary with the current toolbar. It's there. You add it, wire it to your map and done. This all gets back to my main point, and I think Patrick's point too - Why take away something that aready exists and works just fine?

ChrisSmith

To add my £0.02 worth

I'm with ESRI on this one, basic control that anyone can create I would much prefer they invested time in better and faster mapping functionality 🙂 than basic controls you can spend 5 minutes searching on google/bing and find a tutorial & source code for.

As Dominique has pointed out the code is on codeplex, so no big deal to take the code and add it to your own control library, then point your xaml to this control - very small job

Cheers

Chris

PLadd

Where is the logic in this? In the 2.2 API we have <esri:toolbar> and it works fine. If we upgrade to the 2.3 API, <esri:toolbar> will not be there and the reason it won't be there is because we can recreate it on our own? Following this logic, I can also use a calculator instead of a spreadsheet but I don't see Microsoft taking away Excel.

And now all of this code will have to be redone in some manner that doesn't quite yet exist:

<esri:Toolbar x:Name="MyToolbar" MaxItemHeight="35" MaxItemWidth="35"
                            Loaded="MyToolbar_Loaded"
                            ToolbarItemClicked="MyToolbar_ToolbarItemClicked"
                            ToolbarItemMouseLeave="MyToolbar_ToolbarItemMouseLeave"
                            ToolbarItemMouseEnter="MyToolbar_ToolbarItemMouseEnter"
                            ToolbarIndexChanged="MyToolbar_ToolbarIndexChanged">
                                    <esri:Toolbar.Items>
                                        <esri:ToolbarItemCollection>
                                            <esri:ToolbarItem Text="Zoom In">
                                                <esri:ToolbarItem.Content>
                                                    <Image Source="/images/i_zoomin.png" Margin="5" Effect="{StaticResource dropShadow}" />
                                                </esri:ToolbarItem.Content>
                                            </esri:ToolbarItem>
                                            <esri:ToolbarItem Text="Zoom Out">
                                                <esri:ToolbarItem.Content>
                                                    <Image Source="/images/i_zoomout.png" Stretch="UniformToFill" Margin="5" Effect="{StaticResource dropShadow}"/>
                                                </esri:ToolbarItem.Content>
                                            </esri:ToolbarItem>
                                            <esri:ToolbarItem Text="Pan">
                                                <esri:ToolbarItem.Content>
                                                    <Image Source="/images/i_pan1.png" Stretch="UniformToFill" Margin="5" Effect="{StaticResource dropShadow}"/>
                                                </esri:ToolbarItem.Content>
                                            </esri:ToolbarItem>
                                            <esri:ToolbarItem Text="Previous Extent" >
                                                <esri:ToolbarItem.Content>
                                                    <Image Source="/images/i_previous.png" Stretch="UniformToFill" Margin="5" Effect="{StaticResource dropShadow}"/>
                                                </esri:ToolbarItem.Content>
                                            </esri:ToolbarItem>
                                            <esri:ToolbarItem Text="Next Extent">
                                                <esri:ToolbarItem.Content>
                                                    <Image Source="/images/i_next.png" IsHitTestVisible="False" Opacity="0.3" Stretch="UniformToFill" Margin="5" Effect="{StaticResource dropShadow}"/>
                                                </esri:ToolbarItem.Content>
                                            </esri:ToolbarItem>

                                            <esri:ToolbarItem Text="Full Extent">
                                                <esri:ToolbarItem.Content>
                                                    <Image Source="/images/i_globe.png" Stretch="UniformToFill" Margin="5" Effect="{StaticResource dropShadow}"/>
                                                </esri:ToolbarItem.Content>
                                            </esri:ToolbarItem>
                                        </esri:ToolbarItemCollection>
                                    </esri:Toolbar.Items>
                                </esri:Toolbar>

deleted-user-ATjHIWsdQYmT

I'm curious to hear why the Toolbar has been depreciated. A toolbar seems to be a standard type of control in any mapping application. While it certainly is possible to create your own using a stackpanel, buttons, images, etc.. The toolbar is a lot easier and quicker.

Bad idea Esri, unless there is something around the corner that we don't know about... Just my $0.02.

DominiqueBroux

What is used to generate hover over behavior.

That is mainly done by c# code.
You can get the sources on codeplex.

GregoryDillon

What is used to generate hover over behavior.

DominiqueBroux

What is replacing the toolbar control at V2.3 and 3.0?

AFAIK : nothing.
The toolbar is a basic UI control not really tied to the core ESRI functionalities. It can be replaced by any container control such as a stackpanel.

If needed, you can get the sources on codeplex and write yours.

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.