Aurelia 1.x Q&A - Sandbox at https://codesandbox.io/s/aurelia-javascript-sandbox-jnl6q85zq5
i think keeping things vertical rather than crossing contexts is better if possible (if it is possible)
but for communication between components... a service like that would definitely make sense
@rquast I am not trying to build a reusable system, a proper dialog system will dynamically create and inject the dialog markup like Aurelia-Dialog does, for my needs, this will work fine.
I am only going to have a few custom modal elements in the root App template, they will survive the entire instance of the app, and I just need an easy way to call them across my entire app.
@rquast I guess if there was a $root binding similar to $parent, then I could just call $root from everywhere (like rootScope and Scope in Angular), but a backing service is ok for my needs I think.
@rquast This is also probably a temporary thing.... long term I expect to use either the Aurelia Dialog or MDL Dialog modules.
would have been good to have mdl dialog
but it's not done yet :(
im actually pretty excited about AI... that should be very good for cross-platform look etc too?
@rquast I started trying to do adaptive theming with Ionic, its a lot of work.
@rquast Yeah, that is the hard lesson I have learned since I launched my startup. If you are doing full web, mobile web, and hybrid mobile, find a good UI stack that works across everything and looks good is a monstrous undertaking. Angular Material has 1000 bugs on GitHub.
@rquast They were supposed to launch v1 this summer, looks like it might be months. Look at how long it took to take Ionic from Beta to v1 - took almost a year.
@rquast Wow, ok, Angular Material now has 1,184 issues on Github
@rquast Its actually why I dropped Angular and switched to Aurelia and Material Design Lite. MDL is all I need for now and seems pretty solid, and I always hated Angular.
@rquast All I am missing for the temporary future is material dialogs and snackbars. Think I have that figured out, so gonna get it done tonight and try to get my app launched soon.
and things like date pickers, etc
someone was working on a date picker on here i think
ugh.. next ui component i have to not look forward to :)
@/all We wanted to release the Aurelia beta next week. However, Babel just released a new major version with major breaking changes. We've started looking into what the means today and I'm not optimistic. Our tooling is all broken and Babel hasn't provided sufficient documentation in order for us to quickly fix the issues...at least not upon initial investigation. So, getting our beta out may take a little bit longer. I sincerely apologize about this. Believe me when I say I'm as frustrated by the delay as you are. We've got some really cool stuff coming in the beta release...so please hang in there with us.
@rquast We have our own in house Material Design styles!.
Are you suggesting providing support for the MDL Library, styles?
If so, Do know of any benefits to using it’s markup and Styles over the Future AI’s syntax.
On a quick Note, I know you havn’t seen the Library, However If AI provided all and more than MDL, Would it still be worth using MDL?
@joelcoxokc I wouldn't use mdl if AI were available/stable. It's a stopgap solution at the moment for this project (at least until I have a prototype of it going). It hasn't been too bad except for customizing components that aren't available in it (like dialog, date picker, ui-virtualization).
@joelcoxokc would probably refactor everything later on to use AI
and I haven't done any localization yet either, so that's another thing that will force me to revisit the views
Well, I just wrote a long description in an issue about why we couldn't do that...but I'm thinking I might eat my words depending on how this upgrade goes. I'm a little upset about how it was handled. But, I'll try to be patient and we'll see what happens here. (We do use the TS compiler in our build now...we have a hybrid build process that uses Babel and TS together.)
Especially when the angular team is using it as well.