aurelia/Discuss

Aurelia 1.x Q&A - Sandbox at https://codesandbox.io/s/aurelia-javascript-sandbox-jnl6q85zq5

José A. Sachs

@jhewt

MDL from now on, easier on my fingers

There was one, now it's dated

They moved to React

However, there's an easy way to register and unregister MDL elements

and no jQuery

Patrick Walters

@PWKad

To me it is surprising that a bridge is necessary for a CSS framework to work with a JavaScript library(ies)

José A. Sachs

@jhewt

That was my #1 problem with MaterializeCSS

Indeed, I just did a CustomAttribute to register and unregister the element

with Attach and Dettach events

Patrick Walters

@PWKad

That seems pretty natural to me, the styling should be independent of the usage

Why did you need to use a bridge in the first place, just curious?

Seems that any CSS framework should be relatively agnostic of the consumer

José A. Sachs

@jhewt

export class MdlComponentCustomAttribute {
    static inject = [Element];
    constructor (element) {
        this.element = element;
    }
    attached() {
        componentHandler.upgradeElement(this.element);
    }
    detached() {
        componentHandler.downgradeElements(this.element);
    }
}

then <button mdl-component .... >

Max

@MaximBalaganskiy

@PWKad the bridge provides attributes or custom elements to initialize widgets

José A. Sachs

@jhewt

and that's all the integration I had to do

@PWKad the bad thing about MaterializeCSS was the usage of jQuery, MDL does not

Max

@MaximBalaganskiy

@PWKad also, it's nice to just bind to an attribite and it will generate options tags for example without the need to repeat-for manually

Patrick Walters

@PWKad

Doesn't seem related to Aurelia though, why did you need to use jquery for aurelia? Simply for using a CSS framework?

José A. Sachs

@jhewt

With MaterializeCSS yes, jQuery was required

Max

@MaximBalaganskiy

DateTime picker requires it at least

José A. Sachs

@jhewt

That's why I ditched it and moved to MDL

Patrick Walters

@PWKad

Usually my styling is independent of my framework choice

Doesn't seem like a good idea to have either dependent on each other

José A. Sachs

@jhewt

What, MCSS <--> jQuery with Aurelia?

Max

@MaximBalaganskiy

@PWKad that would require more typing in MCSS case

José A. Sachs

@jhewt

@MaximBalaganskiy I strongly recommend using MDL instead of MCSS

However MCSS has the most native-like drawer

Jason Sobell

@jsobell

@Vheissu It turns out that because node 4 doesn't support ES6, I have to change the wallaby.js:

        env: { type: "node", runner: "node"},

(yes, I was compiling to ES6)

Dwayne Charrington

@Vheissu

I think you can also tell Wallaby to use a different version of Node as well.

Wallaby uses v4 by default I think, but I know in Webstorm, you can change the Node install to use a different version.

Roland Quast

@rquast

anyone here using bootstrap 4 with webpack successfully?

thinking of switching from semantic ui

José A. Sachs

@jhewt

Does semantic ui requires jQuery?

Roland Quast

@rquast

yep

José A. Sachs

@jhewt

Dang

Roland Quast

@rquast

actually

I think it may not

but does by default

and I can't get it to play nice with webpack

nope.. still requires jquery Semantic-Org/Semantic-UI#1175

José A. Sachs

@jhewt

with Aurelia sometimes can be a pain in the ass to work with jQuery

With any framework tbh

Roland Quast

@rquast

yup.. rather not include it if I didn't have to

lot of animation stuff in it that people use (like semantic)

José A. Sachs

@jhewt

and things like pickdates and so on, sadly there's almost no css framework with no dependencies

That's why I use Material Design Lite, I can call the element's methods with Aurelia's html references

Max

@MaximBalaganskiy

is jquery problem only webpack specific?

Where communities thrive

People

Repo info

Activity