• @rstoenescu I’ve installed a basic starter kit for a meteor app.
    I’ve used a meteor/vue example, to which I’ve added one of your examples and a little meteor reactivity.

    I’ve listed three problems on the README page.
    The main one is the one we’ve talked about (document.body Is null).
    And I’ve experienced two other small problems that I have listed, but to be honest they can wait.

    I hope this will do to start the ball rolling. As things develop I’m sure it can be extended.

    So far we have simply talked about the problems here in the forum. Let me know if you prefer proper issues to be opened or whatever.

    If you need more info about installing onto an iphone using meteor/cordova and debugging or whatever let me know.

  • Admin

    Awesome work. I’ll take a look as soon as I can. Thx for your efforts!!!

  • Hi,

    I’ve came across quasar and it was awesome that it was super easy to work with it. And now I’m working with a concept of Agnostic Meteor, from Lawrence Wakefield:

    TLDR; Meteor working as a backend for reactivity, and the frontend connects with it in a websocket way, using npm asteroid.

    I was able to configure reactivity easily enough. What do you think?

    @rstoenescu awesome work!!

  • @joaopaulofilho Well, thanks for your comment, all very interesting.
    But it’s not very relevant to this post.

  • @rstoenescu On the README page for the starter kit I mentioned a problem on closing the left drawer

    3) In Chrome’s mobile simulator (or when the left and right drawers are hidden) the links in the drawer on the left don’t work properly. The called page flashes for a millisecond and then disappears

    I know where this is happening if that helps:
    Just before the drawer closes, __matToggleAnimate() is called, and window.history.go(-1) takes us back to the previous path because window.history.state.__quasar_drawer is not set.

      if (this.opened) {                                   // 2852
     } else {             // 2863     
          window.removeEventListener('resize', this.close);       // 2864
          if (!Platform.within.iframe) {               // 2865
              window.removeEventListener('popstate', this.__popState);// 2866
              if (window.history.state && !window.history.state.__quasar_drawer) {        // 2867
                **window.history.go(-1);**                       // 2868
              }                                   // 2869
        }                              // 2870
      }                         // 2871

    Hope this helps.

  • Admin

    @joaopaulofilho @mwarren2 Delaying a bit Meteor since I’m already over my head busy with releasing Electron and the new Quasar version, but will get back to this.

    @mwarren2 Fixed the initial issue and will be available in next Q.

  • @rstoenescu No worries !

  • This post is deleted!

  • @rstoenescu Is there a branch I can use to test the initial issue meanwhile? Thanks

  • Admin

    @mwarren2 Use “dev” branch.

  • @rstoenescu Sorry, I need some help with this, please.

    I can grab the dev branch of course, but there’s only the /src folder. I presumably need to end up with a /dist folder as well if it’s going to work.

    Not sure how to go about this… I can’t use quasar-cli, because I start off with a meteor/vue app. Can you help?

  • Admin

    Don’t really understand what you are trying to do, but you can also build Quasar with “npm run build” inside Quasar’s repo.

  • The meteor build has been failing all day with the same problem as this StackOverflow question. However there’s no answer there.

    TypeError: Cannot set property ‘/Users/malcolm/git/app-template-meteor/node_modules/quasar-framework/package.json’ of undefined

    I can see where it’s failing, but debugging a meteor build script is not my forte.
    Since the build fails, not even desktop is working this time.

    Don’t reckon it’s anything to do with you, so I’ll wait until the 0.9.0 release and try again.
    Sorry to take up your time like this.

  • @rstoenescu I’m simply doing a git clone and npm installing from the resulting folder

    git clone -b dev
    meteor npm install —save …/…/quasar

    This appears to install quasar-framework 0.9.0 correctly, just like it did for 0.8.2

    But this time it’s no go.

  • Admin

    @mwarren2 I’ll try to make some time next week to investigate together. Is this ok for you?

  • @rstoenescu Thankyou, that’s great.

    Meanwhile I will try to find out what’s happening in the build script.

  • @rstoenescu Ok, I’ve found the problem, and it’s more or less as I thought.

    I’m missing a /dist folder which the script is looking for, in fact it’s specifically looking for dist/quasar.common.js. The /dist folder was there in 0.8.2, but it’s missing in my 0.9.0 installation, I just have a /src folder.

    This should be easy to fix, I guess. Is there anything wrong with the way I tried to install quasar this time?

  • Admin

    @mwarren2 hi. You’ve installed Quasar from github and no dist folder is stored there. Now that v0.9.1 is out you can install it from npm, which will have that folder. Cheers.

  • @rstoenescu Ok, got beyond the initial hurdle! Still got a white screen though.

    Now I’ve got
    TypeError: FastClick.attach is not a function. (In ‘FastClick.attach(document.body)’, ‘FastClick.attach’ is undefined)

    I’m looking into it

  • @mwarren2 Ok, here’s what I know - using Safari’s debugger for my IPhone:

    This is the code where the error occurs:

    if (Platform.has.touch) { // 6413
    FastClick.attach(document.body); // 6414

    FastClick.attach at this point is undefined.
    Whereas the FastClick variable is actually pointing to FastClick.attach

    Reading the FastClick docs, you get FastClick or FastClick.attach depending on how you instantiate it, as I am sure you know.

    Does this give you any clue?
    Meteor is all es6 these days, if that’s any help.

    P.S. I see that you fixed the drawer problem, which is great.

Log in to reply