12/31/2023 0 Comments Indented sass codekit![]() ![]() ![]() I’ve been using CodeKit for a couple of years now and I’ve talked about it plenty. And the callback / handler / command execute function fit right into the role of the subscribed onNext function.Īdapting the emitter example fit into my framework was straight forward and I ended up with a new Emitter module that replaces both my old EventDispatcher and EventCommandMap.The following is a guest post by Bryan Jones, the creator of CodeKit. I hand’t looked at the Subject object before, but it does exactly what I need. Then I discovered this bit of sample code that demonstrated exactly what I wanted to do. I had been using it for DOM / browser events, but I couldn’t wrap my head around how to connect event strings (“magic strings”) with an Observable and use that to execute commands or callbacks. At the same time, I’ve had my eye on the excellent, and still way over my head, RxJS library. I’ve been using a simple event dispatcher for a while now. It lets you very easily separate concerns while maintaining communication between discrete parts of the application. Not sure what my next project will be but it’ll be built with those tools and when I build it, I’ll know what’s in the box.Īn global eventing system is a pretty key piece of a full fledged MVC app. I need to get that experience add it to my resume. I’ve been focusing on React and Redux for the past few months, but I’ve never actually used them, learned how to use them on a real project. I’m building to discover and know how the shit gets done. So that that’s what I’ve been doing – learning JS by looking at the internals (source, tutorials, etc.) of popular frameworks and reimplementing those in my own. I’ve always liked to take things apart and discover what’s under the hood, it’s the best way to see inside of the black box. I didn’t want to be one of those and this is still true. Looking around too many people are learning frameworks and push code with them while not spending time to grok the core language. ![]() Going back to my first post on this from April, I did it just to learn the basics of vanilla JS. However, after discovering Tero Parviainen’s talk “ Build You Own AngularJS,” I think I have a pretty good supporting reason. This is a question that I “know” the answer to, but putting it down has actually been a pretty difficult. As an e-learning developer at Red Hat, I don’t bang out code all day, but React has been great for producing apps very quickly. I’d based a lot of my methodologies on it anyway. So I quit cold turkey and started picking up React. “No, I’ve never used React/Angular but I wrote my own thing …” was going to go anywhere. I’ve been in this situation before, and long term product maintenance and support wasn’t something that I wanted to get into again.Īnd I was job hunting. I was building more apps and the realization that someone was going to come behind me and maintain these things started to hit home. But in the end I was never going to be confident in it enough to release or suggest anyone else use it. I think it’s really the best way – for me. Rolling my own solution was a great way to quickly get up to speed on modern JavaScript syntax and best practices. This post should have been written back in February! But I’m bad at blogging … ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |