Here is our our now-confirm-dialog which shows up in the center of the screen:
The goal of this element is to provide a simple confirmation dialog and then have the ability to do something based on which button the user clicked.
Here lately I’ve been writing a lot of tooling in preparation for upcoming projects. This tooling is meant to lessen the amount of work to start up a new project. A while back I watched this video. That video inspired me to come up with a repository in which a front-end developer could clone, run a couple of commands and be ready to write code for the new project. Going down this route has been quite the eye opener to the complexity of what a modern progressive web app is today.
As web developers the ability to troubleshoot a web application is a very important part of the development process. To be able to see what’s happening and understand what may be causing a certain behavior is key and should be employed during the entire development process, not only when something is broken. In this series I will outline my process of troubleshooting web applications.
First off the tools. While there used to be a hand full of tools you might use now you only need one,
So adding today’s post about the now-context element I encountered a lot of weirdness. I’ve got this blog set to autoupdate the software and plugins. Well today’s update actually broke my previous theme and caused a lot of weirdness. So, I had to go hunting for a new theme. I came across the current theme and kind-of liked how it looks so opted for this one. So…. if you run into any issues please let me know.
- Performs and records all AJAX requests
- Provides a basic PubSub system
- Provides a basic Request/Response service
- Provides a global variable to interact with the context
The entire idea here is to provide a communication channel similar to that found in Backbone/Backbone Marionette for application specific communication.
Over the past few months I’ve started working pretty extensively with TypeScript. For those of you who don’t know what TypeScript is:
If you followed Peter’s series on replacing Lotus he outlined some of the pitfalls, processes and decision points to undertake for success. I wanted to point out the technical side to a lot of those decisions. The short answer is that you need a tool to surface your domino data en-masse until such a time when decisions are made on each application. I have been working on that solution for quite some time now and I have to say,
The past 1.5 years I’ve been working exclusively with Web Components and specifically Polymer. The more I use this technology the more convinced I am that this is the technology I should be using. Now, I’m not saying that Web Components and Polymer are hammers and every problem/project is a nail. However it’s quite refreshing that Polymer’s goal is to make itself irrelevant. What does that mean, Polymer is there temporarily until the browsers decide upon common standards and implement those standards.