- Improved Performance: Fully extensible client-side and server-side object models with faster load times.
- Latest Standards Support: CSS3 and HTML5 compliance.
- Major Browser Support: Internet Explorer, Firefox, Chrome and Safari.
- Themes: Built-in premium CSS3 themes and all Controls are compatible with jQuery UI Themeroller.
- Tightly integrated with jQuery.
If you have used the ASP.Net Ajax control and are interested in moving over to the new Wijmo control, this will be a good read. Let's take a look at the procedures involved in migrating over to our latest controls and delve into some details about some basic differences between ASP.Net Wijmo controls and their older ASP.Net Ajax controls along the way.
To get started in this migration you will need our ASP.net Wijmo controls. These can be downloaded here by clicking the orange "Download Free Trial" button.
To get things started, you should create a new ASP.net Web Application using ComponentOne's older Ajax controls. Below is the link to the quick-start guide where you will receive directions to create a web page with an accordion control and visual aid as to what the final product will look like. Once the control is set up on your web application, we can then begin to delve into the migration details for our ASP.Net Wijmo controls. During the migration process I will note changes between the Ajax and Wijmo controls.
Follow this quick-start to create the C1ToolTip using our ASP.net Ajax control.
Once you have completed the quick-start guide you can begin migrating to the new ASP.Net Wijmo control. The first thing you will want to do is add the new ASP.Net Wijmo assembly references. Go to 'Project' from the menu-bar and select 'Add Reference'. Click the 'Browse.' button and navigate to:
For .net 4.0
- For 32bit Machines: C:\Program Files\ComponentOne\Studio for ASP.NET Wijmo\bin\v4
- For 64bit Machines: C:\Program Files (x86)\ComponentOne\Studio for ASP.NET Wijmo\bin\v4
Select the C1.Web.Wijmo.Controls.4 and click "Open".
For .net 3.5
- For 32bit Machines: C:\Program Files\ComponentOne\Studio for ASP.NET Wijmo\bin\v3
- For 64bit Machines: C:\Program Files (x86)\ComponentOne\Studio for ASP.NET Wijmo\bin\v3
Select the C1.Web.Wijmo.Controls.3 and click "Open".
Then in the "Add Reference to." dialog box add click "Add". In your solution, open up your page where you have your ASP.net control in the Designer View.
???To add the new ASP.Net Wijmo Control, simply drag the C1ToolTip from the C1 Wijmo Controls ToolBox onto the page. This will display a ToolTip box with the task menu.
In our AJAX control you previously could use a tooltip designer to add child items. This would add a ToolTipTargetControl that would specify an ID and would display a value as a tooltip. In the Wijmo ToolTip the designer was not included because the user can simply create a new tooltip for each desired element. The actual ToolTip now includes the TargetSelector property where as previously, in the AJAX control, there was a separate C1ToolTipTargetControl which has a TargetSelector property. So when migrating to the Wijmo control, the user can simply take the TargetSelector from the existing Ajax C1ToolTipTargetControl and place it into the TargetSelector for your Wijmo ToolTip Control. If you have multiple elements with which you wish to use a ToolTip, the Wijmo ToolTip does this a bit differently as well.
Lets say you have a list of icons that you want to display on your web page with tooltips next to them:
<img title="Information Here" src="images/tooltip_icon_3.gif" /> <br />
<img title="Got an Idea?" src="images/icon_tooltip%20(1).gif" /> <br />
<img title="ToolTip Icon" src="images/icon_tooltip.gif" /> <br />
<img title="Need Help?" src="images/tooltip_icon.gif" /> <br />
<img title="Post a Message" src=images/c1aspnet_tooltip_16.png" /> <br />
In the older Ajax controls you would add tooltips to these one of two different ways:
- You would create a separate C1ToolTipTargetControl and assign each ToolTipTargetControl's TargetSelector property the image id. (need to add id for the above <img>s)
- You would set AutoToolTipify = true (Each element on a page with a title property will get a tooltip)
In wijmo AutoToolTipify is gone and the user can simply specify the element(s) as such:
<wijmo:C1ToolTip ID="C1ToolTip1" runat="server" TargetSelector="#iconDiv [title]">
The advantage of this is that you can specify which <div> you want to use tooltips for without worrying that a separate control on the page is generating a tooltip because of it's title property.
By default the ToolTip will appear when the user hovers over the element. In the Ajax control this was changed using the ShowEvent property. Wijmo uses the Triggers property to change this behavior.
Replacing the Ajax ToolTip with a Wijmo ToolTip is as easy as replacing its TargetSelector property. So This:
<cc1:C1ToolTip ID="C1ToolTip1" runat="server" AutoTooltipify="true">
becomes this: ?
<wijmo:C1ToolTip ID="C1ToolTip2" runat="server" TargetSelector="#Div2 [title]">
Create tooltips with nested <div> elements; multiple fonts and text colors; preformatted text; paragraph alignment; formatted and nested tables; nested, bullet and numbered lists; images; plain text; and content formatted from cascading style sheets! This and many other features can be found at the Wijmo ToolTip control product page.
In conclusion I would like to fortify how painless and straightforward migrating to the new ASP.net Wijmo Controls can be. If you would like to learn more and even see a live demo, you can go to our ASP.Net Wijmo site at: http://www.componentone.com/SuperProducts/StudioASPNET/ Please feel free to download our free trial and get started today!