Aurelia 1.x Q&A - Sandbox at https://codesandbox.io/s/aurelia-javascript-sandbox-jnl6q85zq5
@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.
There's many reasons why it's awesome, types and annotations are a good thing
Would you think the same about it if it wasn't made by Microsoft ?
Transpiler
Don't think they do that now but it would be easy for them to
Code shaking?
and if you keep your core logic outside of it (in a separate library) and use typescript to transpile that, then I can deal with not using TS in aurelia code.
Did they get rid of the Babel runtime library ?
Been a while since I messed around with it
Over and out
How did that make it through testing?
Anyways, also means that until it's fixed there won't be
.d.ts files
Cause the
d.ts generator relies on them