@packy Yeah I just think it’s not gonna happen anytime soon. Additionally, if you plan to go for full UX confirmity for iOS and material according to the respective guidelines and all the UI components Google and Apple mention, there’s still a lot missing or implemented slightly different. For this use case, something like framework 7 seems to be the right choice. It’s their defined goal to be 100% native conform. So a lot less customisation needed to get something working quickly.

I personally don’t try to go for that 100% native feeling and I build my transitions with animeJS timelines in JS, so I chose quasar for my personal project as it’s easier to build on top of something less tied and locked down than to refactor and redefine tons of CSS and not using 80% of a framework.

It really depends on what you’re trying to achieve. I’m aiming for a custom designed hybrid app without cordova, so this is a good fit, performance and workflow wise. Minimal bloat and fast. If you rely on cordova, there’s probably an out of the box workflow In Framework 7 as well for that. Don’t know for sure though.

Heavily subjective though.

If page transitions (with that “original native” feeling) is a key requirement for your app and you’re not planning on diving deeper (like, DIY), it’s probably better to use a different framework that already has a stable implementation. From what I understand, mobile isn’t the primary target for Quasar. Even though I think such an option would make it more popular, too.

@s.molinari said in Themeing, Stylus vs SCSS:

Or maybe you can offer a patreon backer something substantial that the drive-by consumer doesn’t have access to.

Razvan will attack bugs from Patreon donors at a higher priority. I am not sure it is a standard policy, but I know he does this. It’s sort of common sense thing to do, but maybe making it a clear objective/ expectation of being a supporter through Patreon could be a good thing?

This sounds like a win-win to me for everyone involved. However, it also creates obligations. And I’m not sure if that’s what he wants while not being able to work on it full time. It comes down to simple economics (at least from my very remote perspective).

It’s a tightrope walk. More buzz would be great, more patreon backers too. But the growth and obligations to fulfill people’s wishes that come with it would inevitably pose a scaling issue at some point, without considering turning it into a business case, like Ionic did. And reaching this point, things get exponentially more complicated.

I’m honestly in awe when I see how much time and effort Razvan already invested. That’s what makes me stick around here in the first place!

On the other hand, there’s the critical perspective: If I’d consider using it for a large project for a client, every piece of information that makes me feel more relaxed about all the possible issues (support, roadmap, LTS, etc) would certainly be positive. Will this still be maintained a year from now? And how will the ever increasing complexity of feature requests affect the project?

I personally love the idea of a crowd funded framework that doesn’t involve one large company dictating how we should do things. But taking into account that even VueJS on patreon didn’t crack the 10k mark yet with hundreds of thousands of downloads and even Weex/Alibaba being involved, Im not sure you can solely rely on goodwill. But the discussion about “free is not exactly free” is a long and opinionated one.

I wish the best for it and I already signed up for a patreon donation.

To expand this a bit:

If you’re sneaky though, you can look at the places where Ionic is being discussed and get people with simpler app propositions who are struggling with Angular 2 to take a look at quasar.

Another way to show the seriousness of the project is to offer people using it commercially a place to prominently showcase where they used it and for what. Like show&tell here but more polished.

All of these things combined are probably necessary to create more traction and adoption. This is comparable to a positive feedback loop.

Or maybe you can offer a patreon backer something substantial that the drive-by consumer doesn’t have access to. Fostering the community is a large part of the whole patreon thing and I see the chicken and egg problem present in a situation like that.

This is subjective though and I have no idea what the plan is you guys have but at the end of the day, it’s really sweet to see the progress here.

Sure, I would do that. But I left the social media circus a few months ago, so you see the “connectivity” issue there. I’ll certainly bring it up in discussions though. And I’ll probably write a few blog posts in the next months.

I greatly appreciate the work you guys put into this and I’ll sign up for a patreon donation as soon as I have a stable income again.

Talking about PR, I believe that one defining variable responsible for the surge of angular and ionic in particular is the availability of learning materials and tutorials. And especially in Ionic’s case, there’s a few Cloud services bundled with the framework. Ionic is the product of a VC funded company though.

Churning out tutorials for common use cases would certainly make it more accessible for newcomers. That generates some noise. And since learning material producers push their content, they push the framework at the same time.

Worth thinking about. Maybe.

@spectrolite yeah tell me a about it… the more i tried to get into Angular2, the less secure I felt and the more jargon and glorious concept I had to learn for the same simple thing. I liked Angular up to 1.5, and ionic was my go to to get things done quickly for prototypes but now it’s just exploding with complexity and situations where I am simply cringing in agony. if that’s what enterprise customers want, so be it. Reminds me a little of how drupal became an enterprise thing. Luckily, there’s always something there to fill the gap. Yay!

In order to have smooth transitions (slide-in on new route), I have my content wrapped in a <q-layout class=“fullscreen”>. Without that, the content of that layout only displays after the transition animation finished.

On the other hand, my content page overflows, so I need a scrolling container. That I only achieve without haveing the fullscreen class on q-layout. In order to solve this, I set .fullscreen overflow to auto on the affected page:

<style lang="stylus">
  .fullscreen
    overflow auto
</style>

Am I doing it wrong? Is this a use case where a view prop should be used instead? Do I need to add a slot prop to the main content? It’s a bit hard to follow the documentation there.

Yeah I should really dive deeper into Stylus to get the full picture. I already adapted but I can imagine that this is one of the points on people’s list when they evaluate the framework.

I’m one of the guys moving towards VueJS and it’s UI frameworks because I think Angular(2,3,4…) and therefore also Ionic is going into a direction that I can no longer handle with a good conscience. I also don’t like being pushed into (in Angular’s case, very) opinionated structures, so by that logic, I simply am interested in the reasoning behind such decisions on a rational level.

I got more done and it was more fun to work with VueJS/Quasar in the past couple of days to build a simple app and customize components than trying to do the same thing with Ionic3+. Didn’t spend a minute on tooling issues but instead was able to focus on learning both Quasar and VueJS, not how to get around it’s limitations. It feels like regaining a bit of gravity after floating in Angular space.