Create a core meteor-wizard and put autoform-wizard in a separate package.

[bySabi]

Hi @Pagebakers I read meteor-wizard code many times and I think is a wonderful writed code and must be reuse for more use cases than AutoForm wizard´s. Right know I need a tabbed interface and pick this package https://github.com/meteortemplates/tabs and start to look how can do the same with meteor-wizard. I believe that next steps is create a more general core package without AutoForm and even Blaze stuff and build AutoForm Wizard on a separate package over this core.

This project can be really interesting for the meteor community What you think?

[Pagebakers]

I'm open for suggestions ofcourse, right now I won't start on abstraction the package myself. It's still not fully clear which direction meteor is heading with the view layer, and there are good packages for other use cases already.

[bySabi]

Well Blaze was dead: https://forums.meteor.com/t/next-steps-on-blaze-and-the-view-layer/13561 and back two months later: https://forums.meteor.com/t/angular-react-and-blaze/16100. We will have Blaze for a long time :-)

My motivation on this suggestion was cause your code is well done and many people can benefit it not only for AutoForm Wizards but Tabbed interface in general. I don´t see any meteor tabs package that abstract router and local storage as clean and well.

I undestand that you want not take this wagon.

Thanks anyway for your enlighten code.

[Pagebakers]

Yes, happy to hear Blaze will stick for some more time!

I'm thinking about rewriting the package to ES6 as soon as I find some time. In that case I could consider making an abstraction, I'll think about it :)

Thanks for the compliments!

[Pagebakers]

Which brings me to, which other functionalities could be useful?

I'm thinking

• Hooks, beforeNext, afterNext, beforePrevious, afterPrevious, etc
• More advanced navigation, skipping steps based on the input for example
• Animations/Transitions
• Helpers for showing wizard state like, percentComplete, stepsRemaining

[bySabi]

Well this is really ambitious :+1:

The 'core' package should be:

• simple and bare-mininum.
• a plain tabbed interface.
• navigation based on 'function calls?' and pluggable router interface
• save tab state on CacheStore
• a more functional approach

Then all other usecase can be build over this like:

• next AutoForm wizard
• extend AutoForm wizard
• Generic steps wizard
• complex tabbed UI´s