ToolBar Deprecated at V2.3

[BrianGustafson]

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

[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.

[GregoryDillon]

What is used to generate hover over behavior.

[DominiqueBroux]

What is used to generate hover over behavior.

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

[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.

[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>

[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

[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]

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]

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?