-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a core meteor-wizard and put autoform-wizard in a separate package. #54
Comments
I'm open for suggestions ofcourse, right now I won't start on abstraction the package myself. |
Well Blaze was dead: https://forums.meteor.com/t/next-steps-on-blaze-and-the-view-layer/13561 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. |
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! |
Which brings me to, which other functionalities could be useful? I'm thinking
|
Well this is really ambitious 👍 The 'core' package should be:
Then all other usecase can be build over this like:
|
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?
The text was updated successfully, but these errors were encountered: