Tips and Tricks to upgrading to the latest and greatest Quasar version!
At work, I just finished upgrading/porting a 17k+ lines of code Quasar SPA project from v.17 to the latest v1.2. This took just over a week (52 hours logged).
In this article, I will give you information to help you port you your own projects. Hopefully, they are not as big as mine was, so your time to completion will be faster.
First of all, Quasar v1.2 is spectacular. The code in version 1.X has been rewritten since v.17. It is faster and more suitable for development with many more components. And, there still is the added benefit of using the Quasar CLI, where a lot of the difficult grunt work of setting up and building cross-device applications is done for you. …
With Electron, you get two processes: the main process and the renderer process. You can think of the main process as your back-end code and the renderer process as your front-end code.
Quasar Framework is an up and coming MIT licensed open-source framework powered by Vue. …
TL;DR: In this article we will learn 3 things (these are the struggles I had to endure while creating my project for Github):
I am creating a section for each area, so read them all, or read the one you are just interested in.
Before we begin, a bit of information how all of this came about. Where I work, we use in-house built cameras to do analytics (like detecting oil or gas leaks). When an alert occurs, snapshots are taken from the MPEG stream. Another programmer on my team then wrote Python code to run classification on this snapshot. I was curious if the same thing could be done with Node. I have never worked with Neural Networks before, so this was going to be challenging. I started off using tensorflow.js, but I had issues trying to convert our existing model into a “web-friendly” model as required by the tfjs-node package. …
Have you ever looked at code and cringed? Every single line of code that was ever created had some thought behind it. Crappy code comes from a lack of understanding the problem and experience. The more you understand the problem, the better the solution.
You may or may not have heard of the term Dumb Code. If you haven’t, it’s “the ability to write code using the most simplest elegant solution to achieve the end result of a problem.” This is not to be confused with “dumbed-down code”, which is perhaps a topic for another day.
I’ve been programming since 1988. I passed my 50th programming language earlier this year. I have worked with many, many programmers. Some good, some, ahem, not so good. I have seen tens of dozens of styles. And, the list goes on. For the most part, I have really enjoyed my career. But what makes me unhappy the most is inheriting crappy code. I’ll be the first to admit I’ve written crappy code. All developers have. If you have to revisit your code 6 months later and wonder what you were thinking when you wrote it, then it’s time to refactor to Dumb Code. Of course, it’s best to write Dumb Code right from the start. …