Archive: NSIS 3.0a0 help broken


NSIS 3.0a0 help broken
many of the syntax items (if not all) have 0-height "textboxes" with scrollbars on them so you can't see the syntax. as it turns out, those are XHTML pre tags. somehow, those are getting I think some sort of CSS problem with overflow: or something.
for example CopyFiles, Files
if I could just see the style.css I could maybe debug this.
my default browser is not IE10, but firefox, on windows 7. don't ask me to change browsers.


Are you talking about the .chm or plain html files?

http://sourceforge.net/p/nsis/code/6...IS/trunk/Docs/


chm. I did a view source on it to try to debug it as best I could - at least I could see the syntax that way - as long as a person can read XHTML/HTML.


what's happening is that if the help window is too small, the scroll bars show on the pre tags, and the vertical scroll bar ends up with too little space, so it doesn't show.

it is possible this is something you can't fix. don't know. pre tags on my web pages can cause scroll bars on the browser, however, it is unknown to me if the html help application is capable of displaying scroll bars or not at the bottom.

it's also possible the best and only solution is to simply resize the window?


if you're talking about what you see in the attached screenshot, i'm getting this for the old 2.46 docs as well (could be my viewer though!)

Originally posted by jmichae3
it's also possible the best and only solution is to simply resize the window?
this hardly deserves being called a "solution"

on a side-note, i never understood why open source software would support a proprietary, though reverse-engineered format like .chm. the functionality of the windows help viewer can easily be replicated in html (solutions are plenty!) i hate installing a chm-viewer whenever i'm not on windows. since nsis can be compiled on non-windows platforms, a non-windows manual makes sense! a non-compiled html documentation can be viewed offline on every platform without the need of extra software.

also, i'd like to mention that the official online documentation is not up-to-date. updating it to 3.0a0 is probably a better choice than using a manual that lists commands that aren't used by any stable version or the alpha (e.g. TargetMinimalOS.)

Originally posted by Yathosho
on a side-note, i never understood why open source software would support a proprietary, though reverse-engineered format like .chm. the functionality of the windows help viewer can easily be replicated in html (solutions are plenty!) i hate installing a chm-viewer whenever i'm not on windows. since nsis can be compiled on non-windows platforms, a non-windows manual makes sense! a non-compiled html documentation can be viewed offline on every platform without the need of extra software.
When building you can generate chm and html docs at the same time if you want (Multiple pages or single page html). The docs are in the format used by the halibut generator and it could probably generate pdf and rtf if you really wanted to as well...

i'm well aware of the halibut generator, but still .chm is a rather closed format. a personal favourite of mine would be markdown, though even more than for a manual it's an ideal format for 3rd party addon developers. writing a proper documentation is often the part where developers get lazy and having to write two versions (distributed and wiki) doesn't help it. markdown is very readable in plain-text and there are many ways to render them in the browser to html, or use it for cms platforms and even wikis.

anyway, there are currently four versions of the nsis documentation: distributed chm, the html scripting reference on sf.net, the wiki and also github-hosted markdown. there are plenty of choices. unfortunately, not all are on the same level, which is something that should be looked into in the future (i've been testing out several things already, more to come!)


I see http://Jesusnjim.com/z/help-bug.png


Maybe we need to add 0.5em top&bottom padding or something like that...


Should be fixed with 3.0a1.


that fixed it! thanks!