Things every React.js beginner should know

Post by rakoo » Wed, Jan 27, 2016, 9:00 AM UTC

escherize wrote: post #100

aikah wrote: post #91

Earlier quoted context omitted.

> ... that then expand to be turing-complete and basically offer everything their primary language offered in the beginning. then they wrote template languages on top of the template language to separate layout and logic again ( PHP vs Twig/Smarty ) so maybe we need to step back a little and figure out how to write a language that wouldn't need a different syntax for logic and layout. This family of languages exists…

I'm a huge fan of Clojure's Hiccup library. It allows the user to make html like the following. Here's a function that always returns true - but it could do any kind of data access. It is just plain Clojure. (defn selected? [] true) Here is a datastructure that represents html: [:h2 {:class (when (selected?) "selected")} "Hello"] Calling the function hiccup.core/html on that datastructure yeilds an html string like t…

  function() selected { return true }
  ["h2", {class: function() {if (selected()) {return "selected"}}}, "Hello"]

Post by jjnoakes » Wed, Jan 27, 2016, 1:04 PM UTC

robmcm wrote: post #216

jjnoakes wrote: post #121

Earlier quoted context omitted.

Except this isn't about style. It's about logic. Logic isn't as optional as style, and if you separate the logic into one JS file and the DOM into another HTML file, they are still tied together by the JS binding some action to some named DOM element (by selector, etc). The separation that scales is the one that pairs a small piece of DOM (like a piece of text on the page that updates with the current stock price) to…

So this is where you enter a slippery slope from web page to application. Developing a webpage and adding progressive enhancements to HTML elements is a strongly advised best practice with numerous advantages. Developing an dynamic application at the complexity of say Photoshop it would be absurd to have a static HTML file with behavior decorated by JavaScript, or try and offer a fallback. Whilst you could in theory…

Post by Can_Not » Thu, Jan 28, 2016, 3:22 PM UTC

mattmanser wrote: post #60

ChrisArgyle wrote: post #47

Earlier quoted context omitted.

The big reason I remember from my PHP days (late 90s early 2000s) is that you want to separate design from development. Graphic designers were expected to know HTML/CSS while developers focus on PHP.

That's never really been true. Graphic designers rarely knew HTML/CSS in the old days.

Post by elado » Thu, Feb 04, 2016, 3:20 AM UTC

pkrumins wrote: post #10

I'm not a React or Angular expert, but do you really put HTML inside of your JS code? It just bothers me too much. We spent years in early web days learning that code and templates should be separate, yet here we are putting HTML inside of code, which goes against years of practice. Can anyone share their professional thoughts about this?

    ">
    ">div
    $('.toggle').click(function () { $($(this).data('target')).toggle() })

    +div
    $('.toggle').click(function () { $(this).next().toggle() })

    +
    $('.show').click(function () {
       var $this = $(this)
       var $div = $('').text($this.data('text'))
       $this.after($div)
    })

    // react

    +
    {this.state.isVisible ? div : null}

    toggle() { this.setState({ isVisible: !this.state.isVisible }) }


    // angular 1.x

    +
    div

    scope.toggle = () => scope.isVisible = !scope.isVisible