Posts made by rstoenescu

Have you tried <img :src="require('assets/img' + id + '.png')" /> ?

If you’re using this in a Vuex store file, then it will suffice to access “this.$router”. Just make sure you don’t define your actions with ES6 arrow syntax (because “this” will mean something else as an effect).

export const someAction(...) {
   //...
  this.$router......
}

Use boot files where you have access to the instance of the Router (as param to the default export method).

If you import and call router() you are essentially creating ANOTHER instance of the router, so nothing can actually happen to your app since your app is connected only to the initial Router.

Hi Patryck!

I’d love to see a Quasar App Extension with your component. It fits perfectly.

In this course by Danny Connel, you’ll learn how to use Quasar Framework - along with Vue.js, Vuex & Firebase - to create a real-world app using a single codebase and get this app production-ready and deployed to all the major platforms.

The app will have it’s own Firebase backend. So users can register, login and see their data sync in real-time across all their devices.

You’ll add icons and splash screens for all devices and get the app production ready for the Web, iOS, Android, Mac and Windows.

Use this link and 50% of the revenue will go to the Quasar Team: https://dannys.link/quasarf

Enjoy!
https://github.com/quasarframework/quasar/releases/tag/quasar-v1.0.5

New

• feat(QDrawer): Proxy mouseenter and mouseleave events #4639

Fixes

• fix&perf(QDrawer): Safari doesn’t render correctly the ease-in animation #4611
• fix(Screen): Properly detect screen.is.xl (#4623)
• fix(quasar): Fix $sizes usage in variables.styl (#4620)
• fix(QTab): Allow anchor related components to work inside QTab (#4626)
• feat(QIcon): Support for Material Icons Outlined/Round/Sharp #4635
• fix(QDrawer): Drawer gets stuck in certain scenarios on mobile platforms #4614
• fix(QSlideTransition): Workaround transitionend not firing when animated element is hidden (#4638)
• fix(typescript): Add Quasar Plugin Type for use with Quasar Testing extension. (#4634)
• fix(typescript): Change Quasar Plugin options to support only passing some options. (#4645)

@quasar/extras v1.2.0 – Support for Material Icons in Outlined/Round/Sharp flavours!
QIcon component will support these in Quasar 1.0.5 (unreleased yet, so watch out for it).

Fixed. Thanks for reporting.

Released quasar/app 1.0.4. Please upgrade to it ASAP — includes a security fix. https://github.com/quasarframework/quasar/releases/tag/%40quasar%2Fapp-v1.0.4

https://github.com/quasarframework/quasar/releases/tag/%40quasar%2Fapp-v1.0.3

Fix: App Extension - Install API - render interpolation #4586

https://github.com/quasarframework/quasar/releases/tag/quasar-v1.0.4

New

• feat(Platform): Detect mobile edge #4573
• feat(Platform): add $q.platform.userAgent
• feat(Platform): Improve mobile platform detection

Fixes

• fix(QSelect): Improve performance for initializing heights (#4579)
• fix(QResizeObserver): Use void 0 to reset curDocView (#4589)
• fix(VTouchPan/Swipe): Prevent dragging of a and img in Firefox (#4590)
• fix(typescript): #4411 Add tsName for Dialog Options (#4598)
• fix(QInput/QSelect): Prevent composition on android when codepoint is below 256 (#4591)

Please help people make the decision to use Quasar by writing a little bit about your stack at stackshare’s new “Decision” tool. Add all the tools you use and let’s show the world how flexible Quasar can be!

https://stackshare.io/tool/quasar-framework/decisions

Important fix for Cordova mode when enabling HTTPS and using ionic wkwebview or original wkwebview.

https://github.com/quasarframework/quasar/releases/tag/%40quasar%2Fapp-v1.0.2

Hi,

Have you set html: true?

this.$q.dialog({
        title: 'Alert<em>!</em>',
        message: '<em>I can</em> <span class="text-red">use</span> <strong>HTML</strong>',
        html: true // <<<<<<<<<<<<
      })

Enjoy!

quasar 1.0.3

https://github.com/quasarframework/quasar/releases/tag/quasar-v1.0.3

• fix(QLayout): small regression
• fix(QLayout): container should expand to 100% width and height by default #4537
• fix(ui): Platform - Look for ‘User-Agent’ form in headers (#4542)
• fix(QLayout): container should have no self-imposed min-height

@quasar/app 1.0.1

https://github.com/quasarframework/quasar/releases/tag/%40quasar%2Fapp-v1.0.1

• Upgraded babel dependencies that today suddenly stopped working.

We’re finally there! Final build for 1.0 stable is here!
Enjoy and join the celebration with us

Changelog from last rc versions to final 1.0.0:

quasar v1.0.0

• feat(QInfiniteScroll): @load param done(stop) also stops the component #4415
• feat(QColor): new prop (“palette”) for custom palette on palette tab
• feat(QTabs): new Boolean prop - “stretch”; When used on flexbox parent, tabs will stretch to parent’s height
• feat(QTable): Define scoped slots props Object as enumerable and configurable.
• feat(QSelect): Implement virtual scroll, start on selected option
• feat(QEditor) propagate all events
• feat(QDrawer): allow mini drawer to “open” as overlay through “mini-to-overlay” Boolean prop (#4500)
• feat(ui): perfect layout sizing for mobile platforms
• fix(QSelect): Prevent calling filter when selecting single options on mobile
• fix(QField): Make label use the full width when floating
• fix(QDialog): Guard inner node on focus change
• fix(QSlider/QRange): Fix @change event #4428
• fix(QColor): fix @change event
• fix(ie): QItem avatar min-width
• fix(QEditor): Cannot read property ‘isCollapsed’ of undefined #4439 #4441
• fix(QBadge): Add back pointer events when floating #4444
• fix(QBtnDropdown): don’t allow round buttons
• fix(QTable): sorting on Boolean col fails in certain scenarios #1689
• fix(QForm): Emit with original submit event to prevent errors
• fix(QInput): Fix freeze when using mask
• fix(QSelect): flicker on iOS when scrolling menu #4427
• fix(QSelect): improve menu scrolling perf on Android
• fix(QInput/QSelect): IME composition support #4482
• fix(Dialog plugin): Avoid submitting dialog if using a textarea prompt #4490
• fix(QLayout): smooth page scroll on iOS for containerized QLayout
• fix(QSpinner): on iOS
• fix(QResizeObserver): initialize correctly on iOS platform; with effects on QLayout, QDrawer, QHeader, QFooter

@quasar/app v1.0.0

• feat(app) add afterDev hooks
• feat(app): stop previous dev server before creating new one on quasar.conf build changes
• feat(quasar) pass quasar config to afterDev and afterBuild hooks
• feat(app): Improve workspaces support
• feat(app): Ability to pass extra params to underlying “cordova” or “electron” executables #4417

  $ quasar dev -m ios -- some params --and options --here
  $ quasar dev -m electron -- --no-sandbox --disable-setuid-sandbox
  

• Bump default template to Electron v5
• quasar <cmd> also looks at commands supplied by installed app extensions
• fix(ie): cssnano incorrectly transforms key values (0% -> 0) #4430
• fix(app): public path with URL not working: http(s)://… #4451
• fix(app): Remove unnecessary globalPaths for Electron in dev mode

@quasar/cli v1.0.0

• feat(cli): Workspace support for “quasar upgrade” command #4457

Docs website

• New pages: Meet the Team, Layout Gallery, Style > Breakpoints
• Reorganized top right menus
• A lot of additional components examples and various improvements regarding feature explanations

Open up a Quasar app in Edge on your desired platform and console.log this.$q.platform Object.

Example from a Win 10 with Edge when console.logging this.$q.platform.is:

{
  edge: true,
  version: 18.17763,
  versionNumber: 18,
  win: true,
  desktop: true,
  name: 'edge',
  platform: 'win'
}

@fega

1. It’s not at all misleading. Due to the way that Quasar is now way way easier to style, we actually don’t need two themes (which slow down development very significantly). Example from docs (and this is just one): https://quasar.dev/layout/header-and-footer#iOS-look-and-feel
   Try to understand Quasar behind the “it’s Material design only?” first impression. Cause it’s not. I won’t go over the technical details because I’ve done it countless times, but you’ll soon see the MANY benefits of having a base design which is years ahead more configurable than pre 1.0 was.

2. One of those immediate benefits: we are working on more themes than you can imagine (not just 2 as it was before 1.0), and you’ll be able to install them through App Extensions. It’s going to be so easy that you won’t even believe it. This is yet another place where Quasar will really shine.

3. As always, try to think of the tens of thousands of hours that have been put into the development of Quasar and visit our Why donations are important page (if you haven’t already). It puts things in perspective. The more financial resources that we have the faster the development will go.

@reath
https://quasar.dev/layout/grid/introduction-to-flexbox#Order

https://quasar.dev/style/stylus-variables