Blog

Firebase offers a firsthand journey to a real time application that could be develop almost instantly. Firebase beautifully abstract away backend services. Thus, we now could create an application entirely with client side code, a venture that seemed impossible just a few years ago. For those who share AngularJS love and passion, they will find a real treat in a library created just to enjoy this feature. This library is AngularFire. A great journey start with picking the greatest path. All the developers that love Visual Studio as their main IDE have the opportunity to deep into the API of AngularFire by installing the angularfire strongly type library – angularfire.TypeScript.   Reference the API by adding the definition files 1 2 3 4 /// <reference path="../typings/angularjs/angular.d.ts" /> /// <reference path="../typings/angularfire/angularfire.d.ts" /> /// <reference path ...

The below code is in TypeScript Alerts & Notifications On The Notify Modal Functionality considered a creation of a service for the alerts @ http://cube.adbee.technology/notifications.html 1: export class Notifications 2: { 3: static layout = { growl : 'growl', attached : 'attached', bar: 'bar', other : 'other' }; 4: static effects = { 5: scale : 'scale', jelly : 'jelly', slide : 'slide', genie : 'genie', flip : 'flip', bouncyflip : 'bouncyflip', 6: slidetop : 'slidetop', exploader : 'exploader', 7: cornerexpand : 'cornerexpand', loadingcircle : 'loadingcircle', boxspinner : 'boxspinner' 8: }; 9: static types = { 10: notice : 'notice', 11: warning : 'warning', 12: error : 'error', 13: success : 'success' 14: }; 15: 16: } Then the Service Simply 1: modu ...

I had a great opportunity to blog about one of the technologies I am very much in love with and continue to embrace. It has been a little time since my previous post in which I introduced the API.

Since then, Telerik Reporting has introduced very exciting new features, HTML5 Report viewer, responsive design and Report Designer just to name a few. Telerik Reporting is yet providing us with plenty to talk about.

The Telerik company has rebrand itself and with that It has change the reporting API - although not quite significantly. Specific to Telerik Reporting, it is needless to say that the support that Telerik Reporting has out of the box, to aid create engaging reports, is very powerful.

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

This is an area of a lot of question and hassle. During the Telerik Reporting Webinar for Quarter 2, 2012. One of the areas of inquiries was the use of Telerik Reporting with MVVM pattern.

It is possible you would find yourself in a scenario of implementing Telerik Reporting into an existing MVVM project. It is also possible that the requirements of this project consist of avoiding changes to the existing WPF views. The views may play a very important role in generating the report data. Below I provided a brief strategy for bringing Telerik Reporting and MVVM pattern together, when feeding a report from an existing view is necessary.

Best practice is to create the Report in a class library, this practice apply even when producing reports for MVVM pattern. The only key variation is to create a constructor capable of receiving the report parameters or objects needed for the report to render, i.e:

Jim Rohn stated “Don’t wish it were easier, wish you were better.” Yet, I find myself resilient in desiring for things not only to be easier but also for them to be enjoyable. It is not my goal to challenge Jim Rohn wisdom, however, I believe I will adopt a similar principle “Don’t wish it were easier, wish it be enjoyable.”

In my pilgrimage as a software developer I find excitement when stumbling upon an Application Programming Interface (API) that make application development fun and enjoyable. In a previous post, I had the opportunity to show a brief task of creating a Telerik Report table. In this post, I take on a chart creation at run time. This area is one of the most enjoyable of the Teleirk Repoting API.

Like in any charting API available, it is imperative to understand the objects or components that bring about a chart object. In the section below, I attempt to explain a few chart components, although, within the context of the Telerik Report API. Understanding these will save up a substantial amount of time, this principle holds true for any API we may encounter.