QAutomate v1.0.0-alpha.2 Released!
Automatically add missing Quasar components, directives and plugins to quasar.conf.js when saving your work (using HMR)
Best posts made by Allan-EN-GB
QAutomate v1.0.0-alpha.2 Release!
QAutomate v1.0.0-alpha.2 Released!
RE: Ready to bet the business on it?
Four years ago, I left my job as a successful senior manager at a software company to start out on my own, write software and clean windows (physical, not the OS ) as a way to get by until such a time that the software paid the bills. I have a wife and 2 children.
4 years later, I’m in the core team within Quasar, I spend a considerable amount of time helping out where I can in Quasar and even my wife and kids know what Quasar is. The point? Quasar has had a big impact on a lot of people, myself included. I’m paying my bills, I’m writing software and simply put, I’m in the best position I’ve been in for a long time.
When I started writing my software (which I have since shelved in favor of doing contract work / awaiting a migration to Quasar v1) - https://www.myserviceplanner.com - I found lots of component frameworks, lots of handy standalone Vue components, lots of libraries to do what I wanted - you get my point.
THEN I found Quasar.
For me, I was sold in version 0.14. Even though the API was a lot different to the one you see now it was easy to see the dedication, the vision and the simply the genius in the framework. Quasar was on a mission to making developers lives easier and as a family man, I needed that.
I needed a JS framework - Quasar filled those boots.
I needed SPA and Mobile - Quasar did it.
I needed a community that could help in areas I fell short in (JS was very new to me at the time) - Quasar had it. (p.s If the forum is a little Quiet, try discord )
I needed a framework that provided solutions to problems I didn’t know I had - Quasar did it (things like SSR for SEO didn’t occur to me back then)
What I’m trying to say is you’re not “betting” your job on anything, I firmly believe you’re guaranteeing your position within the company by taking them in a forward thinking, secure and firm direction using Quasar.
Worth noting, I’ve just done EXACTLY the same: I’ve been on a 4 week trial for a longer term contract. My job was to build a browser extension. I could have done this in various ways but I believe in the direction of Quasar so much that even though Quasar didn’t support Browser Extensions, I sold the idea to the customer and implemented the new mode myself - I can’t share the results of that work just yet but I can say that I’ve landed that longer term contract. Because of Quasar.
It’s not just me that made this investment - it was my wife and kids and we have absolutely ZERO regrets.
What does this mean for you?
1.0 is a number. Quasar could have been 1.0 back at 0.14 and we could now be on v4.1 but Razvan and in turn his team have high standards and nothing but the best would do. IMO there are no bets using Quasar, it’s a like a secure blanket in this cold and dreary node_modules filled world
Anyways, I’ve waffled enough. Hit us up on Discord or here on the forums if you have any other questions
RE: @quasar/app v1.1.0 released! Sassy Quasar, here I come
Great - first my wife, then my kids … Now even my framework is getting sassy with me …
QAutomate v1.0.0-alpha.3 released!
I’m pleased to announce a new release, containing the following:
- Modes implemented - [Automatic | Manual | Warn] - Control how QAutomate works when detecting missing items. Manual mode will allow selection from a compiled list of missing entries.
- Sort option added - When QAutomate detects your items aren’t sorted and this option is enabled, it will sort them for you.
- Lots of code refactoring / optimisations
- Quasar.conf.js will only be saved when HMR compilation is done.
- Quasar conf file is only read on
quasar devinstead of each scan.
- Redundant code removed.
Also, I’m trying to get this battle tested for promotion into core / @quasarframework repos so please submit issues for any problems you find or suggestions you have.
@quasar/qribbon v1.0.0-alpha.9 released!
Really pleased (and proud) to announce that QRibbon has become an official Quasar Framework App Extension.
Thanks for the comments and feedback so far - please keep it coming so we can get this AE to a stable 1.0!
- Security Dep updates
- New API documentation update (thanks to @hawkeye64)
- Describe API implement (
quasar describe qribbon) (thanks to @hawkeye64)
As always, I’m open to feedback and suggestions on this AE!
@quasar/qribbon v1.0.0-beta.1 released!
We have now entered the Beta!
- Support for Quasar colors added.
- Fixed an issue on the docs where
glow-speedneeded to be a Number.
- Fixed an issue with
leaf-colornot being reactive to changes.
Note: With the Quasar colors you will now notice that all Quasar colors are registered as css variables in the format of
--q-color-grey-4etc. This shouldn’t cause any performance issues but we might need to add an option to control whether this is added or not should people not be using Quasar colors.
As always, feeback is appreciated!
@quasar/qribbon v1.0.0-alpha.10 released!
New version to fix issues with files being in the wrong location following the migration to @quasar repo.
RE: Users of Firebase, I need your help!
For me, Firebase offered me a serverless approach to my API, a noSQL db with offline functionality built in and very well documented features.
That being said, I’m very scared of the pricing model. Free sounds nice but I wonder how well that’d scale when users come in the masses.