The RxJs community has presented the idea that any series of events can be modeled as one or many asynchronous or synchronous arrays. In the following post I want to explore this by modeling a series of different user inputs as Observables.
I am still learning about Observables and their potential, but I figured it would be interesting to implement a custom text editor, from scratch, using Observables to represent keyboard and mouse events.
You can test out the editor here.
Building a perfect text editor is not really the point here, but I want to see if there is any added value from looking at input sequences as Observables. The first step when building a text editor is identifying which input events to support. In my sample I have decided to focus on adding the ability to input and delete characters. Currently I have limited the input to letters a-z and numbers, but you can obviously extend this by mapping a larger character set. From there I also wanted to add support for mouse events for cursor placement and basic text selection.
Part of my approach has been to see if there is a way to capture these input events and combine them into correlated streams.
I will start with keyboard input since that is probably the easiest form of input.
In the sample above I am creating a stream of key strokes by trapping keyup events. I then send the trapped events through a filter operator to remove any unsupported characters. This is necessary since I don't have support for all possible characters at this point. Lastly I map the events to a custom object model that will be passed on to the subscriber of this Observable.
Next I have added another Observable for keydown events. This is there to silence the effects of characters like spacebar and backspace, which would otherwise cause the browser page to jump.
One of the issues I've had is coming up with a clean way to start an Observable in Angular. One of my complaints about my code so far is that I have to make a DOM reference as a starting point for the Observable. I am not really sure how to fix that at this point, but maybe there will be an abstraction for it at some point.
Next up is mouse click which will add support for placing the cursor in arbitrary locations in the document.
Same as before, I am mapping a clicked character in the editor back to my object model, but I am filtering out click events on non characters (represented by null).
So far the events have been fairly simple since there have been no dependencies between events. However, this is no longer the case when we move to text selection. If you think about it, text selection is initiated by a mousedown, then lasts for as long as you have mousemove events until you end it with a mouseup event.
This may seem like a complicated series of events, but it turns out that we can describe it fairly easily with Observables.
What I love about this is how easy it is to correlate events and map them into a common character based object model. The fact that we are dealing with events is almost completely abstracted since this feel more like functional array code than event handlers.
The last step is to bring all these Observable into one happy family of Observables that can be subscribe to.
As you can see I am able to merge all the different streams into a single stream of events that can be subscribed to.
Anyway, this was just a simple attempt at demonstrating some of the cool things you can do with Observables. As I mentioned above, I would really like a better way to initiate the creation of the initial Observable – without DOM references.