quasarframework / quasar-framework.org

[DEPRECATED, v0.17] Quasar Framework - The Official Website

Quasar Framework Official Website

Build responsive Single Page Apps, SSR Apps, PWAs, Hybrid Mobile Apps and Electron Apps, all using the same codebase!, powered with Vue.

Quasar Docs

• Quasar Framework

Contributing

I'm excited if you want to contribute to Quasar under any form (report bugs, write a plugin, fix an issue, write a new feature).

I'm only asking that you read this first.

License

Copyright (c) Razvan Stoenescu

MIT License

quasar-framework.org's Issues

Update repo references

Spin documentation not up to date

Seems the css class .spin was changed to .animate-spin but it doesn't reflect this in the documentation.
Also goes for .blink and theres a few other classes that arent in the docs yet (pop, scale, fade)

On this page

Datetime documentation about moment().format()

Select with list demo

Breakpoints for dev

Referencing quasarframework/quasar#275

Browser support

Referencing issue quasarframework/quasar#148

Specify bleeding edge version

Documentation Reminder: set theme before Vue.use(Quasar)

SSR

Referencing quasarframework/quasar#171

Responsive table doc missing "data-th" attribute

Passing a default value for Dialog inputs is not documented

In a Dialog component, inputs can be configured with a default value by passing the 'model' attribute in the inputs objects :

Dialog.create({
          title: 'title',
          message: 'message',
          inputs: [{
            name: 'input1',
            label: '',
            model: 'default value'
          }],
          buttons: [
            'Cancel', {
              label: 'Ok',
              handler(data) {
              }
            }
          ]
        })

This is not documented in the Dialog documentation page.

Bad navigation links in /api and /components page

When we browse to the /api page or the /components page, the navigation link goes to the last subpage ("Other helper classes" for the /api page, "Video embedding" for the /components page). It should go to the first part of the first subpage of the page ("App visibility" for the /api page and "Action sheet" for the /components page)

v-model --> @input event

Menu link matching "component"

When you visit the page "Components Sharing State" in the Guide, both tthe Menu link for guide and components is highlighted. Since the title includes the word "component". This set's the menu links css to current.
the responsible part of the code is here: https://github.com/rstoenescu/quasar-site/blob/67032a07cfbc0a3afb6df80ef42c535d50c6112e/themes/quasar/layout/partials/menu.ejs#L5

We could refactor the matches to page.path.match(/\/components\//) and analog page.path.match(/\/guide\//) to include slashes.

More examples since tha matching is lazy:

• http://quasar-framework.org/guide/app-api-proxying-for-dev.html ("api")
• http://quasar-framework.org/components/search.html ("search")

CDN fonts

<link href="https://fonts.googleapis.com/css?family=Material+Icons|Roboto:100,300,400,500,700" rel="stylesheet">
https://fonts.google.com/?query=roboto

$quasar-dont-import-fonts = true

How to set color for dates and multi selection in DatePicker inline component

I want to set color for dates or date range when initialize the calendar (ex: 1-1-2017 is red, 21-1-2017 is blue) and multi selection dates on calendar. Could you please guide me how to config or implement them ??

Add notice: build might halt if template doesn't have valid HTML structure

Example: <span<>

<quasar-number>

<quasar-number> should now be <quasar-numeric> in http://quasar-framework.org/components/numeric.html

Electron wrapper documentation

Doc about prod code vs dev code

Upgrading Quasar within a project

The dialog doc page still has a reference to the "Pick ranges" deprecated feature

I believe "Pick ranges" has been deprecated/removed recently from Quasar. The documentation page for dialogs
still has a reference to this feature :

Document about: Win 10 x64 - Unexpect token import

Referencing quasarframework/quasar#67

Suggestion for improvement - Documentation of integration with Cordova.

Suggestion for improvement - Documentation of integration with Cordova.

Create or enhance documentation related to Apache Cordova integration. I keep a group on the Telegram that deals with the Quasar Framework. In it, a redundant issue is the lack of documentation on how to integrate Quasar with Apache Cordova. I needed also and the documentation is very sparse.

Is there any study of this possibility?

Thank you very much for your attention.

Disable ios rubber band effect when using Cordova.

Fix grid layout demo link

Document Gallery Slider props, methods

Tips on State component

Inline editor

Document about lists with router-link

conflicting "edit here" link

Great that your website has a 'edit this' link at the bottom of each page. Unfortunately it jumps to master, while your contributing rules say to fork `dev'.

Could the forking-branch links be fixed?

Section on how to configure Momentjs (localization, timezone etc)

areas for improvement

I am not sure whether to bother you with this or not, but it might be of help. I merely bringing this up since it kind of contrasts with the quality of docs, framework itself, etc. As a fan of the 'total quality' concept I feel like addressing it. I am on a 13 inch retina display and some parts of your website seem slightly less sharp. For sure this part:

And maybe also the fonts in the toolbar, but maybe that's a color issue or something:

This part is sharp but messy due to small font and different size and not easy on the eyes colors:

Now that I am at it, it is also a bit unclear why the top three are apart from the other features:

If you really consider these three the 'top features' then maybe give them slightly more weight in font as well or something else, as now they just have different background which 'confuses me'.

To show differences in sharpness a picture of total page on my system:

Modal docs should pass object to modal.set function instead of deprecated name/value pair

The Modal documentation page use the depracted way for setting properties on a Modal instance.

Instead of :

modal.set('minimized', true)

We have to do this :

modal.set({
    minimized: true
  })

Second potential issue, with the new 0.6.0 release, passing

.set({
 'selfDestroy': false
 })

to the modal instance disables all click events on the document.

Recommend Vuelidate

$q Vue scope injected object

Disabling iOS rubber band effect

Cordova config:

<Preference name = "DisallowOverscroll" value = "true" />

HMR particular case

quasarframework/quasar-template-default#10

Debugging production electron app

https://github.com/electron/electron/blob/master/docs/tutorial/debugging-main-process.md

Doc on .group and .full-width vs .block CSS classes

http://mobile-frameworks-comparison-chart.com/

ARM npm install

Ubuntu ARM packages for npm and node are outdated so they need to be removed via the ubuntu package manager. Install the binaries from the node site directly. Then you can install quasar-cli and start working on an app.

Prefix change

Globally replace:

• "quasar-" to "q-"
• "~q-framework" to "~quasar-framework"

Roadmap link

Improve doc on static assets handling

The mobile demo view in Quasar documentation is truncated

In Quasar documentation, the mobile demo view on the right of each page is truncated on my screen (1280 * 1024 px). I have to zoom out (90%) to reach the "View source" and "Desktop view" buttons.
This behaviour was not present a week or two ago when I discovered Quasar.

Screenshot :

Forum link for easy access through docs

Referencing quasarframework/quasar#130

Coffeescript doc

Referring to this: quasarframework/quasar#97

Keep documentation for all versions

Demo with complex drawer menu

Link to changelog