Posts made by dobbel

@jraez Thanks for the sample code. Do you like to use Pug to code (Quasar templates) or is it necessary because your want to override templates?

@jraez That sounds like a very flexible solution! Would you want to share an example of extending a quasar component with ‘extend’ combined with overriding a part of the parent template with pug?

Maybe a bit of overkill if you just want a Wysiwyg JSON editor but:

https://www.forestadmin.com/

You could also use Wordpress as a headless(without a site) CMS. You write your articles in wordpress and serve the articles as JSON with the Wordpress REST-API.

@s-molinari

a very nice read. Although I don’t get the first speed comparison. Page load times are 459ms vs 249ms for React vs Svelte . In my calculations that’s not 0.15 seconds faster but 0.211 seconds. I would consider 0.2 sec a noticeable difference for (at least some) users loading a web page.

Another way to look at the speed difference is: Swelte has a 45% reduced page load times compared to React. Sounds pretty impressive to me…

Or do I miss something?

Unfortunately a lot of people are forced by their company to use only IE11, and because of that , me as developer will have to support it.

This will continue (at least) until October 14, 2025.( end of IE11 support)

The demand for IE compatibility will not disappear anytime soon i am afraid…

google page translate comes a long way.

This Stackoverflow guy says ‘extend’ is a bad idea in Vue ( the last post):

I’d avoid the “extends” feature of Vue, simply because it is a poorly named method of Vue. It doesn’t really extend anything, not in the case of inheritance. What it does is exactly what the mixin does, it merges the two components together. It has nothing to do with the template code, which isn’t extensible either. The “extend” Vue method should have been called “merge”.

https://stackoverflow.com/questions/35964116

Any thoughts?

@jraez that’s amazing. Setting the same property values( like dense outlined ect) for certain q-components is something you do over and over again in every quasar project.

Then why is everybody so focused on a composition solution for this problem (composition has it’s uses but will ‘cripple’ the ‘extended’ component, explained in the posts above) and something simple as extending is never mentioned ( Quasar docs)? Are there some untold cave pits with extending vue/quasar components this way? Just really curious …

@apavel very useful!

@patryckx Did you have to make other concessions to your applications functionality/features/UI by supporting IE beside using polyfills?

@sanjee it works on IE that’s pretty optimized

@metalsadman ah ok great. Could you help me with the following: how do you place code snippets and quotes in messages on this forum? I can’t find any info on that.

There’s only one as far as I know:

https://github.com/mayank091193/quasar-admin-crm

Webstorm extension

I am using Meteor.js + Mongodb that (mainly) uses a sub/pub system ( realtime db out of the box) instead of rest and graphql ( you can but I don’t) . There’s nothing faster in terms of backend development for medium to small apps. And meteor integrates great with quasar/vue’s reactivity to build real time app’s out of the box.

@jitendra16

this works for me, you lose the native scrollbar and the ‘reveal’ property of q-header stops working:

https://forum.quasar-framework.org/post/20122

very nice. Would love to see a Vue alternative for react admin.

https://github.com/marmelab/react-admin

very nice!

officially no…but if you really have to, VM’s can do the job if you don’t have a Mac.( xcode is essential btw ). But it’s far from ideal…