I was playing around with my trusty multi-select dropdown earlier today and a colleague of mine pointed out that changing the selected items outside of the directive would not actually deselect previously selected items. This was a curious bug since I knew I had a watcher on the ngModel selections.
In my previous posts regarding advanced Angular navigation, I showed how to create a menu and use the $state provider(s) to track the current state, which menu option is active, and how to move between states using ui-sref. This particular demo used an in-line service called “menuService.”
This is a pretty solid mechanism for navigation, but I wanted to also take a look at doing something similar with the same navigationService, ui-router, and ui-bootstrap tabs.
Last month, I made a blog post detailing how to use CSS arrows as a progress indicator. I really like this and use it whenever I’m asked to create a wizard-like interface.
However, I discovered, after finally updating from IE9 to IE11 that there is a specific IE11 bug that reared its ugly head.
Writing web-based line of business applications entails creating a lot of views with tables.
There are many jQuery table plugins and Angular directives for rendering tables, but I created my own for, primarily, read only tables.
I’ve been using the jQuery plug-in “toastr” for quite some time as a basic growl/notification system. As a basic service, it’s dead simple to wire up. If you don’t know what this plug-in does, check out the demo of it.
But, I found that I needed more interactivity than basic hide/show messaging scenarios. I needed to be able to render full templates inside of the toast messages to allow for interactivity bound to DOM events.
Ok, I couldn’t think of a good title for this post. But, I found this concept to be pretty interesting.
Basically, I wanted a directive that would allow me to watch AND set a property as if it were a state changing bool. This needs a bit more explaining, I’m sure.