search

Anniepoo / swiplsitedesign

design documents for the SWI-Prolog website redesign
3 stars 1 forks source link

[pldoc/pldoc_man] Error upon assembling the content tree for `Contents.html` #7

Open wouterbeek opened 10 years ago

wouterbeek commented 10 years ago

Visiting http://localhost:3040/pldoc/refman/ brings up the following in the console:

ERROR: [Thread 9] Failed to translate to HTML: \man_nav_tree(section(_G276,_G277,_G278,swi(doc/Manual/Contents.html)),[])

The listing of man_child_of/4 shows no entry for Contents.html.

JanWielemaker commented 10 years ago

That is a known todo. The other is to make this work for real PlOoc pages that do not go through the LaTeX manual cycle. The tree is there now to allow you to see what needs to be done further. Is the decision on what to expand correct? Do we need JS/Ajax interactive expansion, or is the static tree good enough? Should we add a title to the predicates to show the summary line?

Anniepoo commented 10 years ago

The static tree is probably a best initial decision. If it proves a nuisance for users, we can make it ajax in a later release. 

Should we add atitle to the predicates to show the summary line?

See the doc I checked in last night in swiplsitedesign/comps/122513.

Since the actual module name was moved to the title by Jessica, I moved the four buttons usually on the right of that line  to the UR corner. 

From: Jan Wielemaker notifications@github.com To: Anniepoo/swiplsitedesign swiplsitedesign@noreply.github.com Sent: Thursday, December 26, 2013 3:38 AM Subject: Re: [swiplsitedesign] [pldoc/pldoc_man] Error upon assembling the content tree for Contents.html (#7)

That is a known todo. The other is to make this work for real PlOoc pages that do not go through the LaTeX manual cycle. The tree is there now to allow you to see what needs to be done further. Is the decision on what to expand correct? Do we need JS/Ajax interactive expansion, or is the static tree good enough? Should we add a title to the predicates to show the summary line? — Reply to this email directly or view it on GitHub.

JanWielemaker commented 10 years ago

Fixed the top of the content tree in PlDoc. Also changed the way the layout is done. Not sure about this. I used a table. Now, I use a left floating div for the tree and a div-with-margin. The last has position relative to make absolute-positioned elements such as footnotes work fine. Seems this is what Annie was after with the nested span, but here we must ensure that PlDoc should also be able to function outside the website.

The CSS for the overall page layout has high priority now

Anniepoo commented 10 years ago

You can make the tree float: left, then make the central content area float:left and it'll do the right thing.

I was going to pull the table myself, but wanted to talk with you first.

From: Jan Wielemaker notifications@github.com To: Anniepoo/swiplsitedesign swiplsitedesign@noreply.github.com Cc: Anne Ogborn annie66us@yahoo.com Sent: Friday, December 27, 2013 8:57 AM Subject: Re: [swiplsitedesign] [pldoc/pldoc_man] Error upon assembling the content tree for Contents.html (#7)

Fixed the top of the content tree in PlDoc. Also changed the way the layout is done. Not sure about this. I used a table. Now, I use a left floating div for the tree and a div-with-margin. The last has position relative to make absolute-positioned elements such as footnotes work fine. Seems this is what Annie was after with the nested span, but here we must ensure that PlDoc should also be able to function outside the website. The CSS for the overall page layout has high priority now — Reply to this email directly or view it on GitHub.