Quasar v1.0 - Feature freeze in effect for v0.17

metalsadman

Very nice, you guys are the best!

Ben Hayat

@rstoenescu said in Quasar v1.0 - Feature freeze in effect for v0.17:

The plan is to publish it as soon as possible, but without affecting the quality – we want you to rest easy in the knowledge that everything is perfect and you can trust Quasar 100%.

This attitude gives me a great confidence in the product and it’s creator. Thank you Razvan!!!

theara

Awesome!
I tried Quasar and Vutify, I will decide which one???

Ben Hayat

Hi Rasvan;

Are there any new features related to SPA running in Mobile Browsers for V1.x? Like new components and functionalities that are specific to Mobile environment?
Since V1 is slated for the end of the year, I’d like to plan new mobile features for our app, if V1 will have any.

Thanks!

s.molinari

@Ben-Hayat - Quasar is totally mobile ready as it is. What exactly are you missing or expecting?

Scott

Ben Hayat

@s-molinari, @rstoenescu ;
Yes, Being mobile ready was one of the main reasons I chose Quasar.
I want to maintain ONE code base to run in browser for desktop and Mobile, at least for a while when the product is stable. That’s why I don’t want to build a hybrid app with Cordova or NativeScript or React Native, to upload Google or Apple store. When user is using the app in browser, it uses the latest code from the server.

However, not using Cordova or other shells, I get to lose lots of services that the device provides.
So my question was related, if Quasar is planing to add features where we can access SOME of devices capabilities through JS without using shells ls Cordova, i.e. taking pictures or getting GPS coordinates and etc.

s.molinari

I’m no expert on this at all, but googling some and reading, it seems accessing the camera is just HTML 5 attributes for an input field and I do know QInput takes standard attributes along with its props. Also, accessing GPS data is a browser JavaScript API too. So, maybe give them a try? I don’t think Quasar needs to have anything specifically “built-in” to allow you to use those kinds of things.

Scott

metalsadman

@Ben-Hayat
u can use the platform detection feature https://quasar-framework.org/components/platform-detection.html then do something like:

<template v-if="$q.platform.is.mobile">
<!-- hide the html input using style="display:none" -->
<input ref="camera" type="file" style="display:none" accept="image/*" capture="camera" />
<!-- show a q-btn that will trigger the onClick event of the above -->
<q-btn color="primary" label="Capture" @click="$refs.camera.click()"  />
<template>

https://www.html5rocks.com/en/tutorials/getusermedia/intro/

Ben Hayat

@metalsadman ;

Thanks for the info and links. Following up on them.!

leon

@rstoenescu Nice man! thanks for the great work !

morlz

Thank you for your efforts! You make my life much easier!

Ben Hayat

Razvan, will we get any NEW components in V1? If yes, can you tell us what, if it can be public info.
Thanks!

s.molinari

You can see the development of v1 on Github. Here are the closed issues for v1 up till now.

https://github.com/quasarframework/quasar/issues?q=is%3Aissue+milestone%3Av1.0+is%3Aclosed

Notice for instance, the new QSplitter.

Scott

Ben Hayat

@s-molinari ;

Thanks Scott; I was mostly asking for V1 roadmap what Quasar team plan to offer or V1, than looking throwing issues being resolved.

Most companies, have official Version Roadmap on their website, so developers can plan ahead.

s.molinari

Well, Quasar is a two man show and not really a company. They don’t spend much time on marketing, which I think a road map would be part of.

I understand your wish for sure. If you change that link to show open v1 issues, you’ll also get sort of the future work they’ll be doing too. So, a road map of sorts.

https://github.com/quasarframework/quasar/issues?q=is%3Aissue+milestone%3Av1.0+is%3Aopen

Scott

Narmer23

@Ben-Hayat Actually there is a roadmap!

s.molinari

Yeah, but that is more an outlook and not as up-to-date as Github.

Scott

Ben Hayat

@s-molinari

Well, these two guys have done more than most big companies do. So in my book, I give them the top rating of a big company based on quality and materials in their product.

I recently looked at a product (end user product) that has been developed by an Eastern Europe company. In every aspect (design, UX, feature, implementation, performance and many others) was one of the BEST product I’ve seen over 30 years of being a developer. After finding out, it’s only 3 guys (the owner, the architect, a backend and front end developer) and the wife doing all the marketing materials. 4 people running it like a multi million $$$ product. And that’s a similar direction I get from Quasar as a dev tool.

Ben Hayat

@narmer23

You’re right. Hope to get to update it soon to have more details. As it helps us plan ahead.
For example, I need to have the ability for a table row to be able to expand to show a detail form or another child table in it. I had that feature in my previous app using Kendo UI. So if Quasar v1 offers that, I can change my plan for my V1 release as well.

Hawkeye64

@Ben-Hayat Is this what you’re interested in?
https://jsfiddle.net/fernando2684/p0k8szvj/43/
https://forum.quasar-framework.org/topic/2428/tree-table-example/2

No More Posting New Topics!

Quasar v1.0 - Feature freeze in effect for v0.17