@DamienDeville Thanks for your post, which brings up some good points.

The example app is not perfect as far as meteor code goes, it’s true.
But I’ve spent all my time just getting quasar working with vue and meteor, and writing perfect meteor code has been low down on the list of aims for this particular thread.

However, now that it’s all working together, I’ll look into your comments and tweak stuff some time soon.
I would also add a point 4. to your list, which is to rename the /imports/ui folder to /imports/client, so that I can remove the ‘if(Meteor.isClient) {’ line from AppLayout.vue

@rstoenescu Have updated to 0.12.0 and everything is now working, which makes installation completely straightforward.
Thankyou for all your work on this, I think we can say it is basically done.

I might add a bit more code to help Meteor people along.

One minor bug seems to be left:
On IOS the right-hand drawer still gets stuck.

@rstoenescu I’ve updated and this project is fine.

The other project is back on course.
Your framework, I have to say, is spectacular.

Ok, back on track. Thanks for the explanations.
Yes, meteor doesn’t use webpack, that was the problem.

So now I’m just doing quasar includes from quasar.es6.js which I keep in a client folder.
I’ll change the starter kit accordingly

@rstoenescu Hi. It appears that you changed the folder name on github from ‘app-template-meteor’ to ‘quasar-template-meteor’, right?

Fine by me, but this left a mismatch with the name in package.json and with the name you need to use to ‘git clone’ the repository.
So I changed the package.json name to try to solve the problem, but you still need to use the old name when using ‘git clone’.

I don’t know how to solve this, and have not found any solution after extensive googling. Would you mind taking a look at this?

My honest reply is no. Not at the moment.

1. Meteor is ready and has been for a long time.
2. Meteor / Vue, - see https://github.com/meteor-vue/vue-meteor - is a great project, but is still in beta
3. Quasar is a superb piece of work, one of the best I’ve seen, but is still in beta.
   Quasar now works with the other pieces, but I can’t say that I’ve used everything together on a sizeable project.

I’m using the mix for my personal projects, but not for other people’s.

@elavaud said in Meteor!:

Why quasar + meteor and not simply meteor + vue?

Quasar gives you a very good-looking app out of the box.
You don’t need Quasar to produce an app, but it sure looks better.
It also simplifies using many of the tools you need, such as transitions and css. And it works without much effort on PC, Ipad, and Phones.

It’s also based on Vue. So if you want Quasar, you need Vue.
Vue is easier to use than React, in my opinion. Vue is also getting a lot of traction, it’s got a good future.
Unfortunately it’s not being actively promoted by Meteor - React is - but there are a series of viable codebases that integrate with Meteor.

Meteor - many were drawn to it for its ability to reflect changes to the db on screen automatically, I was too. I like the fact that I don’t have to use Webpack… It has also made phone apps with Cordova relatively simple, so I am sold on it for good, especially since it has proved to be a permanent fixture with solid support.

The Meteor starter kit application for 0.14.7 is working with Meteor with a simple install from npm now - for those who may be watching this thread.
https://github.com/quasarframework/quasar-template-meteor

Now updated to 0.14.8 to correct a ui problem

@damiendeville said in Meteor!:

Do you mean that this ‘template’ is needed only because running the meteor CLI in the application root folder would somewhat not work? But why? Since you did not use the quasar CLI nor webpack, what is the problem? Also is the name ‘template’ arbitrary?
Could it be called ‘foo’ or ‘meteor’ and it would still work properly?

It has to be called ‘template’. That’s all I know.

@damiendeville said in Meteor!:

I also do not understand the need for transpiling. You say:
Then here we transpile two es6 .js files (one for ios, one for material design) to commonjs which meteor needs
What are those files to transpile, where are they located in your project and you are talking about transpiled from what source langage to what langage? I thought Meteor was written in and supporting es6.

There are some es6 files that currently Meteor does not automatically build correctly in es6. So they need to be transpiled. This has probably been solved in Meteor 1.6.2, which will soon be released.

@damiendeville said in Meteor!:

your starter kit contains .vue files and the quasar doc [http://quasar-framework.org/guide/index.html](link url) states that without using the quasar-cli one cannot use such files
Here’s a comparison:
Feature UMD Starter Kit
SFC (Single File Component - for Vue) - Yes

Sorry for any confusion.

No, you don’t need quasar-cli for Meteor. In fact I can’t see how it can be used, because quasar’s build uses Webpack, and Meteor doesn’t. Meteor has its own very simple build system. Webpack is considered pretty complicated to configure, and Meteor has purposely avoided it. Hence the need to avoid using quasar-cli. I can’t see how using quasar-cli can work with Meteor, though anybody is welcome to try.

There is no problem using .vue files.

@damiendeville said in Meteor!:

The ‘template’ folder is necessary for the quasar cli command to function. This extra ‘template’ folder is there because quasar-framework requires it.

I will see if I can change this phrase as maybe it is not particularly clear. I was asked to add the root ‘template’ folder by quasar’s creator - presumably one day it would be good if it fitted into the quasar starter-kit system, but at the moment I don’t think this is possible - maybe one day when Meteor can simply be installed from npm, if that happens.

For the moment you should simply ignore the template folder and change directory into it and run the usual meteor commands from there.

Now you mention it, if you go up this thread to 5 months ago, there was a post by @alexandesigner, but it was deleted.
I honestly can’t remember what happened.

What he did is certainly interesting if you want to go the webpack route and be more integrated with quasar-cli. Perhaps he will reply.

The quick answer is that I don’t really know, because I hadn’t seen the alexandesigner one.
However he seems to have found a way of using the quasar-cli with meteor which is interesting.

I decided not to use quasar-cli because it involves using webpack, which meteor avoids using completely, because webpack is rather complicated.

• That, I think, is the real difference.

If you understand and like webpack by all means go for it. Though I notice that it hasn’t been updated for 5 months, which, given the speed at which quasar-framework is currently changing, means that it is out of date. You could try to contact him to see if he will bring it up to date.

Now updated to 0.14.8 to correct a ui problem

The Meteor starter kit application for 0.14.7 is working with Meteor with a simple install from npm now - for those who may be watching this thread.
https://github.com/quasarframework/quasar-template-meteor

@elavaud said in Meteor!:

Why quasar + meteor and not simply meteor + vue?

Quasar gives you a very good-looking app out of the box.
You don’t need Quasar to produce an app, but it sure looks better.
It also simplifies using many of the tools you need, such as transitions and css. And it works without much effort on PC, Ipad, and Phones.

It’s also based on Vue. So if you want Quasar, you need Vue.
Vue is easier to use than React, in my opinion. Vue is also getting a lot of traction, it’s got a good future.
Unfortunately it’s not being actively promoted by Meteor - React is - but there are a series of viable codebases that integrate with Meteor.

Meteor - many were drawn to it for its ability to reflect changes to the db on screen automatically, I was too. I like the fact that I don’t have to use Webpack… It has also made phone apps with Cordova relatively simple, so I am sold on it for good, especially since it has proved to be a permanent fixture with solid support.

My honest reply is no. Not at the moment.

1. Meteor is ready and has been for a long time.
2. Meteor / Vue, - see https://github.com/meteor-vue/vue-meteor - is a great project, but is still in beta
3. Quasar is a superb piece of work, one of the best I’ve seen, but is still in beta.
   Quasar now works with the other pieces, but I can’t say that I’ve used everything together on a sizeable project.

I’m using the mix for my personal projects, but not for other people’s.

@DamienDeville Thanks for your post, which brings up some good points.

The example app is not perfect as far as meteor code goes, it’s true.
But I’ve spent all my time just getting quasar working with vue and meteor, and writing perfect meteor code has been low down on the list of aims for this particular thread.

However, now that it’s all working together, I’ll look into your comments and tweak stuff some time soon.
I would also add a point 4. to your list, which is to rename the /imports/ui folder to /imports/client, so that I can remove the ‘if(Meteor.isClient) {’ line from AppLayout.vue

@rstoenescu Hi. It appears that you changed the folder name on github from ‘app-template-meteor’ to ‘quasar-template-meteor’, right?

Fine by me, but this left a mismatch with the name in package.json and with the name you need to use to ‘git clone’ the repository.
So I changed the package.json name to try to solve the problem, but you still need to use the old name when using ‘git clone’.

I don’t know how to solve this, and have not found any solution after extensive googling. Would you mind taking a look at this?