I am doing a project and want to integrate with jsplumb meteor , and install jsplumb with meteor, but not to call it I've read some of the documentation jsplumb but nothing related to meteor , I just need like using nothing more
jsPlumb is available as a Meteor package so it should be easy to use them together. You'll still have to learn Meteor. You can start with Discover Meteor or with the tutorial.
Related
I am new to Meteor and learning Meteorjs with Reactjs. I want to know how one can build a simple (eg. Todo App's package) meteor package that uses react-meteor, and how can I use it in our project.
There is a Meteor - React tutorial for beginners in the official Meteor page here. You should also read the official Meteor Guide for more information about React in Meteor after completing the tutorial.
I've been looking but haven't really found anything.
Wondering if anyone on SO knows something more.
The meteoric project only works on Ionic 1, sadly.
I found this atmosphere package for ionic2-meteor: https://atmospherejs.com/barbatus/ionic2-meteor
I was able to successfully create a Meteor app, add this package, and build the project.
I also found https://github.com/Muffasa/ionic2-meteor-starter that looks like it adds Meteor to an Ionic2 application which better addresses your question. I have not tried it out myself however.
I'm starting new app with meteor and I'm confuse when I have to install packages.
Meteor gives the possibility to install packages just like that:
meteor add <username>:<packagename>
Ok, very easy. The problem is that I would like use bower then, How I have to install the packages? For example angular.
meteor add urigo:angular
is the same as? what is the difference*? How I have to perform?
bower install angular
The logical conclusion could be use one of them, but I have seen in examples that they can be toguether.
*the package is recorded in different places, but the operation is the same?
With
meteor add <developer>:<packagename>
you add packages from the Meteor specific package database. Meteor packages are completely integrated into the Meteor eco-system and may contain both server and client side code.
You should use "meteor add" whenever possible.
To find Meteor packages you can use Atmosphere
Bower on the other hand is a framework independent package system for client side (mostly) JavaScript packages. It's not well integrated with Meteor - Although community packages exists to simplify usage of Bower packages with Meteor.
To answer you specific example:
meteor add urigo:angular
This command adds the Angular package of the Angular-Meteor project to your Meteor application. It's not only Angular but does also include some Angular services ($meteor) to provide integration of Meteor with Angular.
It even adds Angular support to the server side to some degree.
bower install angular
only downloads the official minified and non-minified javascript file of the latest Angular version for client side use.
You could use the Bower version with Angular but you wouldn't get the benefits of the integration.
While I don't use Bower myself, check out this package: https://atmospherejs.com/mquandalle/bower. I think it may help answer your question.
I wonder is there a way to create a new boilerplate app template and then use it like this:
meteor create simple-with-iron-router
yeoman generator for meteor https://www.npmjs.com/package/generator-meteor
iron-cli by Evented Mind https://github.com/iron-meteor/iron-cli
Meteor Kitchen - code generator for Meteor http://www.meteorkitchen.com/
"installer" atmosphere package https://atmospherejs.com/timbroddin/installer
I can add a package to a custom checkout of meteor as outlined in How to build a Meteor smart package
But this doesn't really work when developing with others.
I'm wondering if there's a way to do it within a project? A-la the old Rails vendor/plugins? If not, perhaps it could be something the devs might want to implement..
If you need others to use your package but you don't want your package in Meteor, then you could just fork the Meteor repo and work on your fork instead of Meteor itself. That way, the others can clone your repo instead of Meteor...