In the following example we revisited the sample project where we created a Chart Object with Telerik Reporting at runtime. Every time I create Chart objects at design time, I find myself going under the hood in one way or the other, this to enhance customization. Needless to say, I am not stating that design time does not enable us for customization. However, I rather enjoy going directly to the API. My perception is that in instances this might be a faster route.
A quick glance to my previous posts would show my liking to insightful quotes. I admire those who had the wonderful ability to recite them by memory.
Unfortunately, I have never possessed such a dazzling memory. Thus, I seek the ability to making quotes accessible hoping to increase my ability of sounding more insightful.
The example I am about to introduce, elaborates on one of my favorites C# open source libraries I have found – the HTML Agility Pack. This is a .NET code library that allows you to parse "out of the web" HTML files. The parser is very tolerant with "real world" malformed HTML. The object model is very similar to what proposes System.Xml, but for HTML documents.
I used HTML Agility Pack and SQLlite, in order to build a lightweight database that I could utilized in my mobile application. SQLlite is used constantly in mobile applications today, thus it is a good storage technology to be informed about.
In a later posts, I may introduce the discussion on creating Jquery Mobile controls on the mobile applications. However, In this post I will stay within the scope of the HTML Agility Pack Library.
If you were to build a SQLlite table similar to the one presented in this post, and if building it from a .NET application, It is important to download the SQLite drivers for .NET and the SQLlite Browser
“Today I Shed my Old Skin” - Og Mandino. This statement introduces the first scroll defined in one of the most compelling books I have ever red, The Greatest Salesman in the World. It has also been said - “There ought to be a better way.” I love this statement because at times it becomes the principle for moving us forward.
Representing time in a linear axis is a very ancient exercise; even more ancient that the conception of the Cartesian plane. Linear representation of time, indisputably, will continue to be an indispensable tradition in the illustration of change.
In programming, it is a habit to use OLE Automation Date (OADate), a numerical representation of time, in order to talk to the richest APIs and bring about the graphical representation of time. The approach has been adequate and successful at times, yet in instances it has lacked the flexibility that the representation of time inheritably has by nature.
“Today I shed my old Skin.” And I introduced a slight different approach to the OADate when dealing with time and time reference. This approach consists of time indexing, or the representation of time through simple integer unit.