Long ago, I blogged about integrated SignalR with AngularJS. An interesting behavior that I didn’t touch on was limiting messages being sent to specific clients. This is pretty easy to accomplish.
Integrating SignalR with Angular (Part 2)
posted on April 6, 2017 by long2know in angular, SignalR
Angular Pipes Filtering on Multiple Keys
posted on April 4, 2017 by long2know in angular, plunker
In one of my previous posts, I touched on how to build a filtered list using Angular pipes. As I’m adding more features to the table component that I’m working, I spent a little time modifying the pipe to be able to performing combinatory filtering.
Angular Custom Table Component Sorting
posted on April 3, 2017 by long2know in angular, plunker
One of the features that I had not implemented in my newer Angular component is sorting. Today I decided to go ahead and tackle this feature. Since the latest version of Angular is out, I’ve decided to simply refer to it as Angular. AngularJS will be used to refer to the older v1.x.
Angular 4.x released
posted on March 27, 2017 by long2know in angular
It appears that over the past few days that Angular 4.x (RTM) was released.
Interestingly, I was digging around to see if there is anything needed to edit in order to target the newer versions and found that my plunks that were targeting 2.x automagically work with and target 4.x.
One way to see this is to view the source of and you can note the version in the “ng-version” attribute that gets injected into your mark-up.
For my plunks, I immediately saw this attribute on the primary “app” component that is bootstrapped, for example:
ng-version="4.0.0"
It’s good to know that my prior plunks work as-is without modifications!
The release notes can be found here: https://angular.io/docs/ts/latest/
Angular Multiselect Handling Outside Clicks
posted on March 16, 2017 by long2know in angular, plunker
In my last post regarding an Angular2 Multiselect dropdown, I showed how to integrate form validation. One of the last UI interaction pieces is handling clicks outside of the component. This is necessary to close the dropdown when, for example, a user clicks the document body.
Angular File Upload Directive
posted on February 24, 2017 by long2know in angular
There have been times when I wanted a really simple file upload mechanism in my Angular 1.x apps. HTML standards provide a simple input button for file uploads. Not only is this typically not easy to style, like making it appear to be a Bootstrap button, it doesn’t lend itself to a stateful JavaScript framework like Angular. However, it’s possible to achieve the desired result with an Angular directive that wraps the standard HTML mechanism.
Angular Table Component
posted on February 1, 2017 by long2know in angular, plunker
I said it before, but I’ll say it again. Writing web-based line of business applications entails creating a lot of views with tables. I wrote a (imho) a pretty nice table directive for Angular 1.x, and now it’s time to move that directive, in concept, to an Angular2 component.
Angular tri-state checkbox
posted on January 31, 2017 by long2know in angular, plunker
While I’m in the process of converting my Angular 1.x directives into Angular2 components, the tri-state checkbox reared its head. This is a pretty common mechanism and is something I needed to have working before moving along to converting other components.
Angular Http Interceptor and Loading Indicator
posted on January 25, 2017 by long2know in angular
Long, long ago, I blogged about Angular 1.x Request Interceptors and how they can be used to display a loading indicator. I really liked that mechanism. You could intercept any request whether you made it or it was made by the framework. Fast-forward to today, and things are significantly different with Angular2.
Angular Menus, Navigation, and Dialogs
posted on January 19, 2017 by long2know in angular
In my previous post detailing how to create a DialogService for Angular2, I provided a simple service to display a confirmation dialog. The idea that I had in mind when writing that was to incorporate it into Angular2’s Routing lifecycle with a Menu system. Ultimately, it would be used to determine dirty states and display a dialog to the user asking if they want to keep or discard their changes.