You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the built-in documentation sets appear differently depending on whether one is viewing them in Xcode or in a web browser, I think appledocs documentation should do the same.
In a web browser there is a large header at the top, as well as a table of contents on the left; whereas in Xcode the header is absent, and the table of contents is hidden in favor of the Xcode jump bar.
But with appledoc generated documentation it looks the same in both Xcode and safari, showing the web browser header and table of contents on the side, and does not take advantage of the jump bar.
The text was updated successfully, but these errors were encountered:
This would require using different html template - either automatically when enabling doc set generation or via an explicit cmd line switch. Code change would be trivial, most of the work would go to updating html template.
A quick glance at Apple's documentation shows that they check for the Xcode user agent using JavaScript and toggling of CSS classes. They also do a bunch of things using frames, so that the data model links directly to just the documentation contents that are used as the contents of a frame in the web interface, so there's another possibility.
the built-in documentation sets appear differently depending on whether one is viewing them in Xcode or in a web browser, I think appledocs documentation should do the same.
In a web browser there is a large header at the top, as well as a table of contents on the left; whereas in Xcode the header is absent, and the table of contents is hidden in favor of the Xcode jump bar.
But with appledoc generated documentation it looks the same in both Xcode and safari, showing the web browser header and table of contents on the side, and does not take advantage of the jump bar.
The text was updated successfully, but these errors were encountered: