Flow integration

[timbrandin]

👍 for Flow Router and Flow Layout – though it needs some work :)

[omeid]

👍 Specially if one wants to use fast-render.

[omeid]

As flow-router doesn't provides these methods natively, the current option seems to be @arillo's meteor-flow-router-helpers.

[omeid]

Ping. Any progress here?

[elGusto]

This is really not something that can be merged like that.
I don't think @nickw would like to let go of the iron router integration just to replace it by flow (and then the next popular router). We should restructure the package, either to make two seperate packages, one for IR, the other for FR, either we redesign to have a core package with pluggable router integretion packages (which would be the best imo in the case of new (or from MDG) router).

[omeid]

I didn't ask for this pull request to be merged. Progress can be talks about the design. :)

And you're right, restructuring to have different routers in their packages seems to be the way to go, it will also be inline with how MDG is planning to go with useraccounts, meteor-useraccounts/core#308.

[elGusto]

@nickw what do you think ?
I'm happy to help with the refactoring, if you have some specific ideas let me know. I'll start working on this soon.

[nickw]

@elGusto I'm open to refactoring to allow multiple routers, but I don't have any time right now to contribute unfortunately. Also, if there are clear advantages to Flow Router over Iron Router I'm open to just switching them out as well.

[omeid]

Please don't drop Iron Router integration.
Beside breaking current Meteoric projects it will also make switching non-meteoric Iron:router based projects much harder.

The advantage of routers over each other is also pretty subjective and case specific.

I think MDG is working on an "official" router,or there is at least talks about it, so then there would be changes yet again...

I think it is best to make the router handling modular similar to useraccounts approach as linked in my previous comment.

[timothyarmes]

@elGusto Just wondering if you'd started working on a refactoring?

[rclai]

Perhaps making it router agnostic is more palatable?

[timothyarmes]

@rcmai that's excellent.

[timbrandin]

Wow, cool Lai!

I can't wait until we also make meteoric framework agnostic (react or
blaze) ;)

2015-07-27 17:34 GMT+02:00 timothyarmes notifications@github.com:

@rcmai that's excellent.

—
Reply to this email directly or view it on GitHub
#221 (comment)
.

Cheers,
// Tim Brandin @timbrandin https://twitter.com/#!/timbrandin
http://timbrandin.com
http://studiointeract.com

[elGusto]

Just saw this today https://github.com/nicolaslopezj/meteor-router-layer.
Prepare for Meteoric with router-layer on the way.