- Jan 08, 2013
-
-
Rene Saarsoo authored
This fixes the issue of return value docs being completely missing in case @return wasn't followed by {TypeDef}.
-
Rene Saarsoo authored
Instead of using hardcoded image with text "Sencha Docs".
-
Rene Saarsoo authored
Don't direct people right away to JSDuck issue tracker - most likely it's just a fault of a broken link and it's the authors of the documentation who should fix it.
-
- Jan 07, 2013
-
-
Rene Saarsoo authored
A silly mistake.
-
Rene Saarsoo authored
Allows for ignoring additional HTML tags which otherwise would get closed down by the new automatic tag closing mechanism. Useful for ignoring ExtJS preprocessor directives: <debug>, <locale>.
-
Rene Saarsoo authored
-
Rene Saarsoo authored
Fixes an old problem with some unclosed <b> or <div> messing up the layout of docs. In addition to automatically closing the tags, a warning gets printed.
-
- Dec 19, 2012
-
-
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.
-
- Dec 17, 2012
-
-
Rene Saarsoo authored
The offical 0.11.0 seems to have some problems compiling. So stick with the latest beta instead. For windows we also use the 0.11.0beta1, so that's ceartanly a better option than defining 0.10.1 as dependency.
-
Rene Saarsoo authored
Github no more provides hosting for downloads. So switching over to SourceForge.net.
-
- Dec 13, 2012
-
-
Rene Saarsoo authored
-
Rene Saarsoo authored
Generate full paths for images in guides
-
- Dec 12, 2012
-
-
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.
-
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="]"]
-
Rene Saarsoo authored
-
- Dec 08, 2012
-
- Dec 07, 2012
-
-
Rene Saarsoo authored
-
Rene Saarsoo authored
-
Rene Saarsoo authored
Also stars for classes with new members.
-
Rene Saarsoo authored
-
Rene Saarsoo authored
-
- Dec 06, 2012
-
- Dec 05, 2012
-
-
Rene Saarsoo authored
For some reason the 0.11.x won't compile.
-
Rene Saarsoo authored
-
Rene Saarsoo authored
External classes can be now specified as patterns. For example 'Foo.*' to ignore all classes in Foo namespace.
-
- Nov 29, 2012
-
-
Rene Saarsoo authored
It's now ignored together with all other possible tags within code example blocks.
-
Rene Saarsoo authored
-
- Nov 28, 2012
-
-
Rene Saarsoo authored
In Ruby 1.9 string[x] returns a string but in Ruby 1.8 it returns a char code. Fixed by using sting[x,y] which always returns a string.
-
Rene Saarsoo authored
One can now write doc-comment for event before the this.fireEvent() and the event name will be picked up automatically, without any need to add @event tag.
-
Rene Saarsoo authored
When encountering an unsupported @tag, JSDuck now prints a warning. To achieve this, I've enhanced the doc-comment parser to only accept @tags when they have a space in front of them. Previously this would have been detected as @method tag: /** foo@method.com */ Now it's treated as plain text as it should be. Only when separated with spaces, the @method tag gets detected: /** foo @method .com */
-
Rene Saarsoo authored
-
Rene Saarsoo authored
Previously --ext-namespaces only applied to detecting Ext.define.
-
Rene Saarsoo authored
For backwards compatibility with old ExtJS sources that contain @override to denote a method is overriding another one in parent.
-
- Nov 27, 2012
-
-
Rene Saarsoo authored
-
Rene Saarsoo authored
One can now just add an empty doc-comment before Ext.override and all the overrides will get detected: /** */ Ext.override(Some.Class, { foo: 1, doSomething: function(){} });
-
Rene Saarsoo authored
That is, allow to use the @override tag without accompaning @class tag to give a name for the override.
-
Rene Saarsoo authored
An off-by-one bug which prevented one from placing a comment right before some other code construct without leaving a space in between.
-
Rene Saarsoo authored
-
Rene Saarsoo authored
Injecting of comment expanders is now deferred until member doc is expanded. This considerably cuts down the time of initial loading of class docs. Hovewer, clicking the expand-all button is now really-really slow as clicking it triggers the injection of all those expanders. But I think that's a good trade-off for now.
-
- Nov 26, 2012
-
-
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.
-