[30 Builds] Day 23

  • Advertisement ( why? )
     

    HTML-Kit Support, 30th Aug 2013 11:54 pm

    TreeHouse build 20130812 posted.

    http://www.htmlkit.com/assistant/

    • Check the quality of JavaScript code using popular JSLint tool written
      by Douglas Crockford. To use this feature, open a *.js file and click
      "Validate JavaScript" on the bottom.

    Chami

    • bill, 31st Aug 2013 10:51 am

      On 8/31/2013 12:54 AM, HTML-Kit Support wrote:

      TreeHouse build 20130812 posted.

      http://www.htmlkit.com/assistant/

      • Check the quality of JavaScript code using popular JSLint tool
        written by Douglas Crockford. To use this feature, open a *.js
        file and click "Validate JavaScript" on the bottom.

      Chami

      would be nice if we could select and then check js embeded in a
      page rather than included.

      Some of my pages are 1/2 php and 1/2 html (written by the php to
      the page) and half of the html is .js

      bill

      • HTML-Kit Support, 31st Aug 2013 11:50 am

        On 8/31/2013 10:51 AM, bill wrote:

        On 8/31/2013 12:54 AM, HTML-Kit Support wrote:

        TreeHouse build 20130812 posted.

        http://www.htmlkit.com/assistant/

        • Check the quality of JavaScript code using popular JSLint tool
          written by Douglas Crockford. To use this feature, open a *.js
          file and click "Validate JavaScript" on the bottom.

        Chami

        would be nice if we could select and then check js embeded in a page
        rather than included.

        Some of my pages are 1/2 php and 1/2 html (written by the php to the
        page) and half of the html is .js

        bill

        I've done this myself and I know that this is what happens in the real
        world but mixed code pages are hard to maintain as they grow. They're
        also problematic, and in many cases impossible, to test at development
        time. If code is spread out and inlined it's often necessary to run it
        through a server/interpreter to piece is back together which in turn
        makes it difficult to reference back to the source. Source maps help to
        some degree but they're not universally supported.

        Having said all that, HTML-Kit is there to deal with real-world problems
        :) so I'll try tooling for some of that. You'll have to figure out if
        checking portion of code out of context makes sense on case by case basis.

        Chami

        • bill, 31st Aug 2013 12:25 pm

          On 8/31/2013 12:50 PM, HTML-Kit Support wrote:

          On 8/31/2013 10:51 AM, bill wrote:

          On 8/31/2013 12:54 AM, HTML-Kit Support wrote:

          TreeHouse build 20130812 posted.

          http://www.htmlkit.com/assistant/

          • Check the quality of JavaScript code using popular JSLint tool
            written by Douglas Crockford. To use this feature, open a *.js
            file and click "Validate JavaScript" on the bottom.

          Chami

          would be nice if we could select and then check js embeded in a
          page
          rather than included.

          Some of my pages are 1/2 php and 1/2 html (written by the php
          to the
          page) and half of the html is .js

          bill

          I've done this myself and I know that this is what happens in the
          real world but mixed code pages are hard to maintain as they
          grow. They're also problematic, and in many cases impossible, to
          test at development time. If code is spread out and inlined it's
          often necessary to run it through a server/interpreter to piece
          is back together which in turn makes it difficult to reference
          back to the source. Source maps help to some degree but they're
          not universally supported.

          Having said all that, HTML-Kit is there to deal with real-world
          problems :) so I'll try tooling for some of that. You'll have to
          figure out if checking portion of code out of context makes sense
          on case by case basis.

          Chami

          my thought was to keep it (somewhat) simple: user to highlight a
          block of code (which we presume will be a js function or stand
          alone code) from the top to the end and check that. I am not
          even envisioning being able to check a block of mixed code.

          I can't even imagine how that could be done.

          I check my combined html/php code by generating the page source,
          copying the part in which I am interested and submitting that to
          the wc3 code snippet checker.

          bill

          • HTML-Kit Support, 31st Aug 2013 1:41 pm

            On 8/31/2013 12:25 PM, bill wrote:

            On 8/31/2013 12:50 PM, HTML-Kit Support wrote:

            On 8/31/2013 10:51 AM, bill wrote:

            On 8/31/2013 12:54 AM, HTML-Kit Support wrote:

            TreeHouse build 20130812 posted.

            http://www.htmlkit.com/assistant/

            • Check the quality of JavaScript code using popular JSLint tool
              written by Douglas Crockford. To use this feature, open a *.js
              file and click "Validate JavaScript" on the bottom.

            Chami

            would be nice if we could select and then check js embeded in a
            page rather than included.

            Some of my pages are 1/2 php and 1/2 html (written by the php to
            the page) and half of the html is .js

            bill

            I've done this myself and I know that this is what happens in the
            real world but mixed code pages are hard to maintain as they grow.
            They're also problematic, and in many cases impossible, to test at
            development time. If code is spread out and inlined it's often
            necessary to run it through a server/interpreter to piece is back
            together which in turn makes it difficult to reference back to the
            source. Source maps help to some degree but they're not universally
            supported.

            Having said all that, HTML-Kit is there to deal with real-world
            problems :) so I'll try tooling for some of that. You'll have to
            figure out if checking portion of code out of context makes sense
            on case by case basis.

            Chami

            my thought was to keep it (somewhat) simple: user to highlight a
            block of code (which we presume will be a js function or stand alone
            code) from the top to the end and check that. I am not even
            envisioning being able to check a block of mixed code.

            I can't even imagine how that could be done.

            Even for pure JS code, variables other dependencies might be elsewhere
            in the page.

            I check my combined html/php code by generating the page source,
            copying the part in which I am interested and submitting that to the
            wc3 code snippet checker.

            bill

            Makes sense. Some years ago I wrote a program to go with 292 that
            validate generated page source as you browse. Might be time to make a
            modern version of it.

            Chami