aurelia-materialize-bridge
aurelia-materialize-bridge copied to clipboard
Update tutorial
- [x] mention reasons focusing on JSPM for the tutorial (simplicity)
- [x] add aurelia-cli installation instructions
- [ ] create an alternative tutorial using
aurelia-cli
(!! as of @DiegusMiestro :smile: ) - that's not an easy topic (https://github.com/aurelia-ui-toolkits/aurelia-materialize-bridge/issues/205#issuecomment-238844817) - [x] add installation instructions to GitBook, maybe keep a condensed version in the app (useful for quick lookup
- [x] create tutorial repo using contact-manager tutorial from aurelia hub
Gathering improvements atm. Any suggestions welcome.
Aurelia-cli please.
Sorry, but the tutorial Aurelia me seemed to give preference to aurelia-cli , I believe disoriented like me , will install it and enjoy it, because to create a project you need just a ' au new ' instead of the Skeleton use. I found more practical.
Sorry if this text seem strange . Google translator is not perfect but it is better than my English.
It may be easy initially but compatibility with other plugins and systems and its lack of maturity makes its use discouraged, especially by people who have already invested months of work in projects using Aurelia and jspm
@Kukks I get it. Better checking the situation...
@Thanood I want to change my vote.
A tutorial approaching the configuration of JSPM from Skeleton provided by Aurelia seemed like a better option. Changing the things referred to the Bootstrap Framework to Materialize .
@DiegusMiestro This is already there: https://aurelia-ui-toolkits.gitbooks.io/materialize-bridge-docs/content/app_developers_tutorial/introduction.html
Of course if you have any ideas for improvement, let me know. :smile: Aurelia-Cli is still on the list, though. So many people are using it. The most difficult thing right now is Materialize itself which does not play well with requrejs (which is used by the cli)..
Apart from that there seems to be a bug, maybe in cli, but I'm not sure. The created bundles have html and css fragments, which are not wrapped in a define. That leads to syntax errors (requirejs expects javascript). Does not always happen.
@Thanood Completed this tutorial, I will only opine that the installation page , must inform the installation is via skeleton .
I will continue my studies that way , because what interests me is the Flat / Material Design .
I think that would be very useful, yes. Thank you, @DiegusMiestro :smile:
Regarding CLI: I will base the installation instructions upon this README: https://github.com/Ullfis/aurelia-cli-materialize-bridge/blob/master/README.md
First I'll reproduce the steps myself and then add a tutorial, probably with some basic controls and aurelia-validation. To keep it consistent I'll copy the current tutorial pages and change the setup to use the required steps for aurelia-cli.
@Ullfis Does you project actually read the bridge's files from the bundle? Mine seems to load it from the server..
Oh nvm, maybe it's because I'm using a bridge version which doesn't export everything. npm update
failed me somehow.
Updating now...
Yep, that was it. 😃 (I don't like the new github emoticons)
:neckbeard:
:link: http://www.webpagefx.com/tools/emoji-cheat-sheet/
Added aurelia-cli installation instructions: http://aurelia-ui-toolkits.github.io/demo-materialize/#/installation
Contact Manager repo, using the bridge to build the contact manager from the Hub tutorial. https://github.com/Thanood/md-contact-manager
Using aurelia-cli. This will be the base for the (yet to be written) aurelia-cli tutorial.
I am quite interested in seeing what you do here - as I have this same thing pending in this repo and a plan to extend the this chapter.
I would suggest to coordinate our tasks.
I would suggest to coordinate our tasks.
That's a great idea, of course. :smiley: I could PR my contact manager into you repo if you like.
Please do - as it would help Monterey effort (I discussed the concept of using Aurelia's Contact Manager code as the tool to show many Monterey properties, including "automatic replacement of the module loader" - he really liked that idea).
My plan was to "grab your attention" to this issue in the context of Monterey - collecting ideas what to be the set of features for Monterey's next version