Webtools/DXR User Research: Difference between revisions

Webtools/DXR User Research (view source)

615 bytes removed , 23 October 2012

m

Confirmed users

210

edits

@@ Line 45: / Line 45: @@
 === Any additional comments? ===
-* "I would like to see the project separated into components.
-Compile -> database.
-Comments + database -> database
-database -> database model
-template engines to do whatever you want that use the database model.
-database -> model <-> controller <-> view
-------
-keys should not be integers, or based on the location in the file.
-If I associate links with code objects, the links will be destroyed on every compile.
-Database of code should be able to recreate the raw source code of definitions. minus #def out sections.
-If this is all done then this tool would be much more attractive than swig / doxygen"
 * "I think I'd actually want to get this hooked into the address bar so I can have search suggestions as I go... That would be nice, but probably outside your immediate scope ;) (So I can start typing ""dxr nsIDOMWin"" and have it display ""dxr nsIDOMWindowUtils"" as one of the suggestions, even if I've never looked at it before) Oh, did I mention speed? ;)"
 * The lack of JS integration severely hinders my ability to use DXR on more than a trial basis.