Are collections still planned?

[wizonesolutions]

I hope they come soon. This is a cool-looking project for getting started fast on "this shouldn't take long" projects where the first few hours go into routine setup :o

[AdamBrodzinski]

Yep. I've been super swamped on some other stuff, which should be ending tonight. Planning on getting the collections and models done in the next week. I was kind of holding off on those to make sure I was happy with the layout. After 3 production apps i've changed the model/collection layout a bit.

Hoping to add custom templates with coffeescript and es.next support next month-ish as well :smile:

[wizonesolutions]

Sounds great. I'm too much of a perfectionist (despite my better efforts), and I long for the day where I can just quickly and (somewhat mindlessly) stub things out so I don't have time to get distracted and sidetracked by the shiny.

[AdamBrodzinski]

Yea same here. One of things I want to do is enable you to create a foo generator folder and then inside that you can customize your layout for controllers, page scripts, etc...

[AdamBrodzinski]

@wizonesolutions Just pushed the collections, still needs readme docs and a little clean up. Should be ready on atmosphere in a few days.

[wizonesolutions]

You mean NPM, or was I supposed install with Atmosphere? I did a npm install -g meteor-generate.

Can you explain it a bit here in this issue? I do have one more collection create in my app and could try it.

On Mon, Jun 30, 2014 at 4:53 AM, Adam Brodzinski notifications@github.com wrote:

@wizonesolutions https://github.com/wizonesolutions Just pushed the collections, still needs readme docs and a little clean up. Should be ready on atmosphere in a few days.

— Reply to this email directly or view it on GitHub https://github.com/AdamBrodzinski/meteor-generate/issues/2#issuecomment-47490765 .

[AdamBrodzinski]

Ah yea NPM, that's right. If you want to use meteor generate before it hits NPM you can clone down and run doing the following:

cd ~

git clone https://github.com/AdamBrodzinski/meteor-generate.git

cd meteor-generate

npm install

Then call the command directly from the bin file like so: cd yourProjectsPlace ~/meteor-generate/bin/mgen create foo cd foo ~/meteor-generate/bin/mgen collection listings

Calling ~/meteor-generate/bin/mgen basically replaces the mgen command by executing the local bin file directly.

If you create a collection it will output:

.
├── both
│   ├── lib
│   │   ├── _namespaces.js
│   │   └── collections.js
├── server
│   └── permissions
│       ├── foo.js
│       └── helpers.js

collections.js is created when you first create a project and then new collections are inserted, then foo.js is created for the foo collection permissions.

[wizonesolutions]

Thanks! Will have to give it a try soon and see how it does it. That's roughly equivalent to how I structure things. Nice thing with Meteor is that my old collections and mgen collections should be able to coexist without a problem.

On Tue, Jul 1, 2014 at 5:16 AM, Adam Brodzinski notifications@github.com wrote:

Ah yea NPM, that's right. If you want to use meteor generate before it hits NPM you can clone down and run doing the following:

cd ~

git clone https://github.com/AdamBrodzinski/meteor-generate.git

cd meteor-generate

npm install

Then call the command directly from the bin file like so: cd yourProjectsPlace ~/meteor-generate/bin/mgen create foo cd foo ~/meteor-generate/bin/mgen collection listings

Calling ~/meteor-generate/bin/mgen basically replaces the mgen command by executing the local bin file directly.

If you create a collection it will output:

. ├── both │ ├── lib │ │ ├── _namespaces.js │ │ └── collections.js ├── server │ └── permissions │ ├── foo.js │ └── helpers.js

collections.js is created when you first create a project and then new collections are inserted, then foo.js is created for the foo collection permissions.

— Reply to this email directly or view it on GitHub https://github.com/AdamBrodzinski/meteor-generate/issues/2#issuecomment-47612840 .

[AdamBrodzinski]

Np!

If you're using the cloned copy You can also tweak the templates folder files to match your current setup as well :)

Adding an mgen alias can help with the extra verbosity too. — Sent from Mailbox

On Tue, Jul 1, 2014 at 6:51 AM, Kevin Kaland notifications@github.com wrote:

Thanks! Will have to give it a try soon and see how it does it. That's roughly equivalent to how I structure things. Nice thing with Meteor is that my old collections and mgen collections should be able to coexist without a problem. On Tue, Jul 1, 2014 at 5:16 AM, Adam Brodzinski notifications@github.com wrote:

Ah yea NPM, that's right. If you want to use meteor generate before it hits NPM you can clone down and run doing the following:

cd ~

git clone https://github.com/AdamBrodzinski/meteor-generate.git

cd meteor-generate

npm install

Then call the command directly from the bin file like so: cd yourProjectsPlace ~/meteor-generate/bin/mgen create foo cd foo ~/meteor-generate/bin/mgen collection listings

Calling ~/meteor-generate/bin/mgen basically replaces the mgen command by executing the local bin file directly.

If you create a collection it will output:

. ├── both │ ├── lib │ │ ├── _namespaces.js │ │ └── collections.js ├── server │ └── permissions │ ├── foo.js │ └── helpers.js

collections.js is created when you first create a project and then new collections are inserted, then foo.js is created for the foo collection permissions.

— Reply to this email directly or view it on GitHub https://github.com/AdamBrodzinski/meteor-generate/issues/2#issuecomment-47612840 .

---

Reply to this email directly or view it on GitHub: https://github.com/AdamBrodzinski/meteor-generate/issues/2#issuecomment-47642210

[AdamBrodzinski]

closing, collections are now merged