Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 23:19
    3cp commented #772
  • 23:17
    3cp commented #772
  • 23:15
    3cp closed #772
  • 23:15
    3cp commented #772
  • 22:37
    Alexander-Taran commented #329
  • 22:23
    Alexander-Taran commented #112
  • 22:15
    Alexander-Taran commented #17
  • 22:13
    Alexander-Taran commented #52
  • 22:09
    Alexander-Taran commented #854
  • 20:48
    Alexander-Taran commented #126
  • 20:43
    Alexander-Taran commented #774
  • 20:42
    Alexander-Taran commented #772
  • 20:24
    Alexander-Taran commented #863
  • 20:22
    Alexander-Taran commented #861
  • 20:17
    Alexander-Taran commented #594
  • 20:12
    Alexander-Taran commented #726
  • 20:11
    Alexander-Taran commented #726
  • May 26 23:12
    Alexander-Taran commented #316
  • May 26 23:11
    3cp closed #680
  • May 26 23:11
    3cp commented #680
Max
@MaximBalaganskiy
ups... sorry, didn't see "lite" word, i'm using materializecss
José A. Sachs
@jhewt
hehe, I've been using materializecss
I wasn't quite happy with it
Max
@MaximBalaganskiy
any particular things?
is there a bridge for aurelia?
José A. Sachs
@jhewt
for MaterializeCSS or Material Design Lite?
Max
@MaximBalaganskiy
for Material Design Lite
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