Adding compatibility with flow-router?

[AlexFrazer]

the {{>yield}} regions wouldn't work without iron:router

Is it possible to also support FlowRouter?

[Sivli-Embir]

👍

[rcarter]

+1

[MartinBucko]

+1

[elGusto]

I have started to do that in this branch https://github.com/elGusto/meteor-ionic/tree/flow-integration

I am at the point where I don't have any more errors with my app, but I am not using all of the templates meteoric is offering, so there is some work to do still.

I then defined my layout like so:

<template name="layoutMobile">
  {{#ionBody}}
    {{#ionSideMenuContainer side="right"}}
      {{#ionSideMenus}}
        {{> sideMenuMobile}}
      {{/ionSideMenus}}
      {{#ionSideMenuContent}}
        {{> ionNavBar}}

        {{#ionNavView}}
          {{> Template.dynamic template=main}}
        {{/ionNavView}}
      {{/ionSideMenuContent}}
    {{/ionSideMenuContainer}}
  {{/ionBody}}
</template>

And then you can do some stuff like this in the router:

appRoutes.route('/', {
  name: 'home',
  action: function() {
    FlowLayout.render(layout, {
      headerTitle: 'homeTitle',
      headerButtonRight: 'menuButtonMobile',
      headerButtonLeft: '',
      main: 'homeMobile'
    });
  }
});

[sircharleswatson]

@elGusto I'd love to see this integrated with meteoric.

[omeid]

There is #221. @sircharleswatson.

[liaujianjie]

+1

The use of flow-router can fix ionTabs's reliance on routes causes a ionNavBackButton to navigate between tabs. If meteoric uses flow-router, we can assign a unique identifier to every ionTabs stack where tab states can be saved as url parameters instead.

This also isolates ionTabs from the ionNavigation stack (I'm not sure if this is desired) and reduces the need for stuff like this.

[achtan]

👍

[dalerka]

+1 for switching to Flow-Router (or making it router-agnostic) as we don't know when MDG will roll out their official router and if it will be better or not.

[AlexFrazer]

I only really see a few places in this whole repository that rely on Iron Router. Worst come to worst, just do some template type checking or something

[dalerka]

Just in case, the option of creating a Router-layer package (to allow using various routers) is discussed here.
If someone has the necessary skills to build such a package, please take the lead.

[nicolaslopezj]

I started a router-layer project

https://github.com/nicolaslopezj/meteor-router-layer

[achtan]

+1

[dalerka]

Can someone update about the main road blocks to switching to Flow-router or supporting it via the Router-layer?

[txs]

@elGusto Is your package still use iron layout? I use Blaze layout and have the issue that not support for contentFor. What's your layout choice?