No More Posting New Topics!

If you have a question or an issue, please start a thread in our Github Discussions Forum.
This forum is closed for new threads/ topics.

Navigation

    Quasar Framework

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    1. Home
    2. clwd
    C
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 10
    • Best 2
    • Groups 0

    clwd

    @clwd

    2
    Reputation
    2
    Profile views
    10
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    clwd Follow

    Best posts made by clwd

    • RE: Can't ad meta title dynamically following docs

      I did not find a better integrated solution after considerable research and experimentation. However, I did take a different approach.

      Vue-Meta, prerendering (using history mode), and sitemap generation really did everything I needed for Google searches. Google renders the pages and could easily find the meta tags. This is great, for people using Google and Ask for searches. However, for the other search engines and the test tool that you noted, the meta data is not found because these engines do not crawl through the javascript.

      After a lot of reading, I noticed a dismissive attitude on the part of some for this meta tag rendering problem, because Google accounts for the overhelmingly majority of the searches. I get it, but avoiding the challenge is not the solution in order to reach all customers. SPA, by design, is at best a 90% baked solution for all search engines.

      Since I did not need dymanic meta tags, I took the post-build approach of inserting the meta tags into the index.html file for each page that was produced by prerendering. I also removed the Vue-Meta tag code from each page to remove any conflict. I inserted the meta tags into JSON, along with some basic informatoin (i.e. file path), and after the quasar build completes I run a lightweight tool to read thorugh the JSON and insert the tags on the appropriate page. The tags are human readable and readily availalbe for the test tool and for all of the search engines. The best part of this solution is that all of the tags are in a single document, easy to review and quick to modify. This took a couple of hours to setup and test.

      Thanks for your suggestion, which may help someone else.

      posted in Help
      C
      clwd
    • RE: QMediaPlayer - When the video ends return to poster image display

      I will experiment with this a bit. Thanks for the suggestion!

      posted in [v1] App Extensions
      C
      clwd

    Latest posts made by clwd

    • QMediaPlayer - Is the RTSP protocol supported?

      Can QMediaPlayer play a RTSP stream? It appears not, but wanted to double-check.

      Thanks!

      posted in [v1] App Extensions
      C
      clwd
    • RE: QMediaPlayer - When the video ends return to poster image display

      I will experiment with this a bit. Thanks for the suggestion!

      posted in [v1] App Extensions
      C
      clwd
    • QMediaPlayer - When the video ends return to poster image display

      Running QMediaPlayer video on a page. The current behavior:

      • On a fresh page load, a poster image is displayed instead of the video.
      • After playing the video, the last frame of the video is displayed until the full page is reloaded.

      Once the video has finished, is it possible set the video to the beginning and display the poster image (in other words, back to the initial state after loading the page)?

      Thanks!

      posted in [v1] App Extensions
      C
      clwd
    • RE: Can't ad meta title dynamically following docs

      I did not find a better integrated solution after considerable research and experimentation. However, I did take a different approach.

      Vue-Meta, prerendering (using history mode), and sitemap generation really did everything I needed for Google searches. Google renders the pages and could easily find the meta tags. This is great, for people using Google and Ask for searches. However, for the other search engines and the test tool that you noted, the meta data is not found because these engines do not crawl through the javascript.

      After a lot of reading, I noticed a dismissive attitude on the part of some for this meta tag rendering problem, because Google accounts for the overhelmingly majority of the searches. I get it, but avoiding the challenge is not the solution in order to reach all customers. SPA, by design, is at best a 90% baked solution for all search engines.

      Since I did not need dymanic meta tags, I took the post-build approach of inserting the meta tags into the index.html file for each page that was produced by prerendering. I also removed the Vue-Meta tag code from each page to remove any conflict. I inserted the meta tags into JSON, along with some basic informatoin (i.e. file path), and after the quasar build completes I run a lightweight tool to read thorugh the JSON and insert the tags on the appropriate page. The tags are human readable and readily availalbe for the test tool and for all of the search engines. The best part of this solution is that all of the tags are in a single document, easy to review and quick to modify. This took a couple of hours to setup and test.

      Thanks for your suggestion, which may help someone else.

      posted in Help
      C
      clwd
    • RE: Can't ad meta title dynamically following docs

      Sorry, I have been pulled away for publishing. Thus far I have not found a better solution, and I have looked at this from a lot of angles. I will start working on this again tomorrow and let you know if I find a better solution.

      Thank you for detailing how you were able to work around this problem!!

      posted in Help
      C
      clwd
    • RE: Can't ad meta title dynamically following docs

      How did you implement the meta and verify that it worked? Thanks!

      posted in Help
      C
      clwd
    • RE: Can't ad meta title dynamically following docs

      How did you solve this problem?

      posted in Help
      C
      clwd
    • RE: Overlay UI elements - best approach?

      Applied custom CSS per the below article and everything else is easily aligned through Flexbox. Way to go Quasar team!!

      https://stackoverflow.com/questions/60032018/setting-a-background-image-in-quasar-that-dont-overlay-the-card

      posted in Framework
      C
      clwd
    • RE: Overlay UI elements - best approach?

      Thanks for the suggestion. I have explored this and I can’t see it working for stacking two images (larger background and inner-placed foreground) and some text. I am still looking at other options, including custom CSS, which feels wrong.

      posted in Framework
      C
      clwd
    • Overlay UI elements - best approach?

      I am new to Quasar and really finding it useful. I have a new challenge. What is the best way to overlay several UI elements in this framework. I have background image that I would like to wrap across the page and over that image lay other UI elements (for example, another image(s) and text.

      I thought about simply creating overlapping flex grid rows of elements, but this does not seem to be possible.

      Any guidance would be greatly appreciated.

      Thanks!

      posted in Framework
      C
      clwd