- May 18, 2011
-
-
Rene Saarsoo authored
-
Nick Poulden authored
-
Nick Poulden authored
-
Nick Poulden authored
-
- May 17, 2011
-
-
Rene Saarsoo authored
-
Rene Saarsoo authored
-
Rene Saarsoo authored
Resizing the browser window wasn't working due to a scope error on the resize timeout. Using Ext.Function.defer to be able to easily bind scope to the deferred function.
-
Rene Saarsoo authored
-
Rene Saarsoo authored
Don't need this for now.
-
Rene Saarsoo authored
-
Rene Saarsoo authored
-
Rene Saarsoo authored
Simply ignoring this tag for now.
-
Rene Saarsoo authored
-
- May 16, 2011
-
-
Rene Saarsoo authored
-
Rene Saarsoo authored
-
Rene Saarsoo authored
OverviewData is now in json file, which is parsed by JSDuck and checked for missing classes. After that it's written to output/overviewData.js The lot of changes in overviewData file are because the file wasn't valid JSON - it used single-quotes and some items weren't quoted at all.
-
Rene Saarsoo authored
Ordered command line options alphabetically, adjusted line lengths, and added blank line between each option. Much clearer now.
-
Rene Saarsoo authored
Also renamed write_json to write_class (it now writes jsonp instead, but writing class docs is it's primary purpose).
-
Rene Saarsoo authored
-
Rene Saarsoo authored
Parsing guides README.md files is now done inside JSDuck, and enabled when --guides=/some/path option is passed in. As an added bonus, the {@link-s} inside guides now also work. Like with class documentation, we create .js files for guides to load them over JsonP.
-
Rene Saarsoo authored
Instead of pure JSON-export JSDuck now exports a .js file for each class with the following syntax: Ext.data.JsonP.Ext_grid_Panel({...json-data-here...}); On JavaScript side we specify that the name of callback function should be "Ext_grid_Panel" - this way we can use the JsonP deterministically, knowing at JSDuck export time which names the callback functions will have. Note that we are passing callbackName option to Ext.data.JsonP.request, which is not present in ExtJS-4.0.0 - I just added it to ExtJS SDK and sent a pull request.
-
Rene Saarsoo authored
-
Rene Saarsoo authored
Docs.History now uses Ext.util.History instead of history.pushState.
-
- May 13, 2011
-
-
Rene Saarsoo authored
Brought over JSON file with class list from old docs app. Modified it a bit, to make it brain-dead easy to render. Rendering it using simple XTemplate.
-
Rene Saarsoo authored
Removed old class_search.json file, now using the JSDuck-exported members.js. Also using the search algorithm from old Ext3 docs app. The search now works quite fine.
-
Rene Saarsoo authored
-
Rene Saarsoo authored
Currently not using it, so it's just getting on my way.
-
Rene Saarsoo authored
Going to URL like #/api/Ext-method-onReady will automatically load Ext class and scroll to the onReady method.
-
Rene Saarsoo authored
These two replace the previous %M, allowing a bit more flexibility. Now we can choose whether to use "-" or "#" as separator between classname and member name. Still, even more flexible solution would probably be in order. Used the new syntax for SDK and made inline links in documentation finally work.
-
Rene Saarsoo authored
For example {@link Ext#get} will be converted to something like: <a href="Ext-method-get">Ext.get</a> To look up member types, implemented JsDuck::Class#member_type method.
-
Rene Saarsoo authored
-
Rene Saarsoo authored
-
Rene Saarsoo authored
Docs.History#push now takes the hash part of URL as input. The classname is also read from URL directly, not from pushstate data.
-
Rene Saarsoo authored
No more used.
-
Rene Saarsoo authored
Not using it now, and it's just getting on my way.
-
Rene Saarsoo authored
When initially loading and when navigating in history.
-
Rene Saarsoo authored
Removed use of req.standAloneMode. With new docs app we are always in stand alone mode, but it's a different standalone mode.
-
Rene Saarsoo authored
Turned the remaining global functions in functions.js into ClassLoader class. Removed the functions.js.
-
Rene Saarsoo authored
That's the only place it is used.
-
Rene Saarsoo authored
Instead we are using Ext.Array.forEach.
-