Posts in 'dotnet'
If you are a Facebook user like myself and 350 million others then you probably noticed the application bar. If you don't know what I'm talking about then check out this screenshot. The application bar is a menu fixed to the bottom of the Facebook site. It serves as navigation and also displays notifications such as updates or chat. At first I was weary of adding such an obtrusive element on top of the entire site, but have become quite fond of the idea. I really find it useful for its notification functionality. In fact, I have come to rely on it instead of refreshing the page or clicking on the "Home" tab again. It is an extremely useful UI for such an active website. There are too frequent of updates to rely on an end user to refresh the content. Using a site-wide toolbar at the bottom of every page is a great way of keeping the user aware of important updates. I began to think of how useful it could be in other web applications and decided to try to build one myself. Less talk, more code Let's walk through the process of building a Facebook-like application bar using two ComponentOne controls, our ASP.NET Menu control and our ASP.NET ToolTip control. Want to follow along? Download the code: PopularUI.zip or See it live: Application bar demo File > New Website To start I create a new ASP.NET 2.0 website in Visual Studio 2008. Keep in mind this could be done in .NET 3.0 and 4.0 as well. I just chose the lowest common denominator. I name the project PopularUI since I will be adding multiple samples in it. For this sample I will add a directory named FacebookAppBar. Inside it I create an Images folder and added a new WebForm, Default.aspx. I then add the ComponentOne Palomino dll's to the Bin directory: C1.Web.UI.2 C1.Web.UI.Controls.2 C1.Web.UI.Design.2 Make a Container The next step is to make a container to position the application bar in. I am going to use the same ID Facebook does just to make it a better reference. Here is the markup for the page so far: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head runat="server"> <title>Facebook Application Bar</title> </head><body> <form id="form1" runat="server"> <div> </div> <div id="presence"> <div id="presence_ui"> </div> </div> </form></body></html>
If you convert an existing project or solution to Visual Studio 2010 beta there should be no problem. But if you are creating new projects within VS2010 beta there are a couple things you need to know when using ComponentOne WinForms controls.
Creating data-entry forms can be very time consuming and tedious, and maintaining them can be a nightmare. However, with ComponentOne InputPanelT for WinForms creating and maintaining data-entry forms is no problem at all. The control removes all redundant tasks such as control alignment, spacing, data-binding, labeling, accelerator key generation, and tab ordering.
Check out the review of ComponentOne Studio for iPhone: Nathan Clevenger, “Developing iPhone Apps in .NET: How does MonoTouch bring Microsoft’s .NET to Apple’s iPhone?” iPhone Life, Winter 2010, 86. http://www.zinio.com/reader.jsp?issue=416107467&o=ext
Looking to win an attendee pass to the Visual Studio 2010 launch event in Las Vegas next year? If so, find your ComponentOne Control Freak hat, beanie, toque or whatever you may call it and send us a picture of you wearing it.
OK, it might not be quite that incredible, but it saves a ton of time when upgrading your bits. If you are like me, and use custom controls, then I am sure you have had a run-in or two with a license.licx file.