Skip to content
  1. Jan 08, 2013
  2. Jan 07, 2013
  3. Dec 19, 2012
    • Rene Saarsoo's avatar
      Switch back to therubyracer 0.10. · f020e2a7
      Rene Saarsoo authored
      Let's stay on the 0.10.x until the problems with 0.11.x get resolved.
      This time though, don't specify exactly 0.10.1 but a range of versions.
      
      With the 0.11.x therubyracer is attempting to use the system libv8,
      and you have to install the libv8 gem by yourself when the system doesn't
      have the libv8 available.  Additionally the compilation of libv8 is
      quite time-taking and on some systems (like those with old Python)
      will fail.  So lets hope these things get sorted out.
      
      Although that somewhat complicates the install on Windows, as for it
      only a 0.11.x version is available - so I need to generate a special
      gem depending on 0.11.x from which I'll then build the executable.
      f020e2a7
  4. Dec 17, 2012
  5. Dec 13, 2012
  6. Dec 12, 2012
    • Scott Whittaker's avatar
      Generate full paths for images in guides · 4bc20fcf
      Scott Whittaker authored
      Suppose we're using JSDuck to generate guides from the following directory
      structure:
      
      somedir/
        guides.json
        guides/
          getting_started/
            README.md
            some-image.png
          nested/
            first_guide/
              README.md
              one.png
            second_guide/
              README.md
              one.png
      
      In JSDuck's generated HTML, image tags in the Getting Started guide will point
      to the correct path relative to the page (e.g.
      'guides/guide_getting_started/some-image.png'). However, the nested guides will
      specify the wrong paths to images: JSDuck will write
      'guides/first_guide/one.png' instead of the correct
      'guides/guide_nested_first_guide/one.png'.
      
      This patch fixes the issue by generating the image's path based on the full
      name of the guide, instead of using 'File.basename' to incorrectly crop the
      path.
      4bc20fcf
    • Rene Saarsoo's avatar
      Proper string parsing in default values and type definitions. · dfaf6057
      Rene Saarsoo authored
      The strings can now contain the ] or } char without causing the
      parsing to end at that point.  For example:
      
          @cfg {String} [foo="]"]
      dfaf6057
    • Rene Saarsoo's avatar
      67aad127
  7. Dec 08, 2012
  8. Dec 07, 2012
  9. Dec 06, 2012
  10. Dec 05, 2012
  11. Nov 29, 2012
  12. Nov 28, 2012
  13. Nov 27, 2012
  14. Nov 26, 2012
    • Rene Saarsoo's avatar
      Support for @class doc-comment right before object literal. · 8ca7c33a
      Rene Saarsoo authored
      This allows for a way to document classes that aren't created with
      a standard Ext.define:
      
          createClass("Blah", /** @class Blah */ {
              foo: 17,
              doSometing: function() {},
              doOtherThing: function() {}
          });
      
      All the members inside the object literal will end up inside the class.
      
      Additionally this is equivalent to the functionality of @lends tag in
      jsdoc-toolkit, but we achieve the same without having a separate tag.
      8ca7c33a
Loading