Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Pass the CommandLine option
--use-tipue-search to pasdoc (or check the Use tipue search engine box in the PasDocGui) to instantly get a working "Search" box in the HTML output. It allows full text search on the generated documentation.
--use-tipue-search option to pasdoc, everything else is done automatically and you get a working "Search" box in your HTML documentation.
Tipue is a client-side search engine
On one hand, this is comfortable, as it allows the "search" functionality to "just work", no matter how you view the documentation (through an HTTP server or not). You don’t need to configure anything. PasDoc puts all the files where they should be (Tipue, jQuery, generated index data for Tipue), and the search works.
On the other hand, the browser has to download the (potentially large) "index data" of your documentation when doing a search. Tipue search cannot show any results before this data is downloaded. You should watch the size of
tipuesearch/tipuesearch_content.jsfile (in earlier versions,
tipuesearch_data.js) in your generated documentation. If it’s too large (if downloading it takes a while), then possibly you have outgrown the Tipue capabilities, and you should look into other search implementations (e.g. your own server-side search, or using Google search box).
That said, it works quite nicely even with a large documentation in our experience (Castle Game Engine is using it with over 150 units…).
To test the speed, you can:
Search for something.
Once you’re on the "Search results" page of your documentation, hard refresh the page (Ctrl + Shift + R). You can watch the "Network" panel of developer tools in Firefox or Chrome to watch how
One day we may implement options to integrate other search solutions, see ToDoSearch.