Meteor!

mwarren2

@rstoenescu I’d like to help in any way I can.

So of course I will try again if you can work on a fix for start.js, and certainly I will help you with the starter pack for meteor.

rstoenescu

Great. Tell me your Github username and I’ll create the repo and add you.

mwarren2

@rstoenescu I’m mwarren2 there as well.

rstoenescu

Created https://github.com/quasarframework/app-template-meteor and added you. Will give you a heads-up after I fix that issue. Feel free to push to the repo. Let’s make this work!

mwarren2

@rstoenescu sounds good! Look forward to hearing from you. Meanwhile I shall look into the starter kit.

mwarren2

@rstoenescu
I forgot, there are some messages during the meteor build (they’re always the same messages), but they don’t stop meteor from starting or from working on desktop. Something appears to write what look like md5 strings in a couple of quasar components during the build:

[ ‘- invalid expression: :class="{active: (!mouseModel && model __v3526c1452685d1042a961c804897cdc640f6cca6cdd471b629fbc6de38756ab7>= index) || (mouseModel && mouseModel >= index)}"’ ]
[ ‘- invalid expression: :class="{incomplete: step __v06909b10feb6b30b0edd6334bda8e34fa4c548289fce08e7d4a98c73f334ef12> stepper.currentStep}"’,
‘- invalid expression: v-show=“step __v06909b10feb6b30b0edd6334bda8e34fa4c548289fce08e7d4a98c73f334ef12>= stepper.currentStep”’,
‘- invalid expression: v-if=“step __v06909b10feb6b30b0edd6334bda8e34fa4c548289fce08e7d4a98c73f334ef12> 1”’ ]

mwarren2

@rstoenescu Actually this last problem probably is not for you. I’m guessing that it’s the Vue - Meteor integration code. I shall follow it up there.

rstoenescu

Feels like some preprocess is messing things up…

mwarren2

@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.

rstoenescu

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

joaopaulofilho

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: https://iamlawrence.me/agnostic-meteor

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!!

mwarren2

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

mwarren2

@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.

rstoenescu

@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.

mwarren2

@rstoenescu No worries !

mwarren2

This post is deleted!

mwarren2

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

rstoenescu

@mwarren2 Use “dev” branch.

mwarren2

@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?

rstoenescu

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