#2022: thorn guide on et website links to pdf pages --------------------------------------+------------------------------------- Reporter: rhaas | Owner: knarf Type: defect | Status: assigned Priority: major | Milestone: Component: EinsteinToolkit website | Version: development version Resolution: | Keywords: --------------------------------------+-------------------------------------

Comment (by rhaas):

This is actually worse than that. I only see thorns up to what is in CactusWave and nothing beyond that (alphabetically). This really should be fixed soon.

#2022: thorn guide on et website links to pdf pages --------------------------------------+------------------------------------- Reporter: rhaas | Owner: knarf Type: defect | Status: closed Priority: major | Milestone: Component: EinsteinToolkit website | Version: development version Resolution: fixed | Keywords: --------------------------------------+------------------------------------- Changes (by knarf):

* status: accepted => closed * resolution: => fixed

Comment:

This has been fixed. The ThornDoc now links to the thorn html pages.

For this, the documentation has been regenerated using the current release. The other guides now also point to this new location.

For reference: the documentation is to be updated/copied 'by hand' to the webserver at the moment. Better solutions exist, but this was the fastest way to have a working documentaiton. I could imagine using a repository for this, but since this is essentially generated files, this isn't ideal.

I tried generating the documentation on the webserver itself, but the htlatex version available there is too old to handle it.

The ideal solution would be to have a major upgrade of the server OS (anyway...), and then to generate new documentation on-the-fly if something changes within the release branch of the toolkit - so there would need to be some logic that filters out those changes from those on other branches.

For now the documentation works and maintenance cost is minimal (re-run HTML generation locally and rsync that over to the webserver), so I'm closing this ticket.

For reference too, this is the location on the webserver: /var/www/einstein/documentation

#2022: thorn guide on et website links to pdf pages --------------------------------------+------------------------------------- Reporter: rhaas | Owner: knarf Type: defect | Status: closed Priority: major | Milestone: Component: EinsteinToolkit website | Version: development version Resolution: fixed | Keywords: --------------------------------------+-------------------------------------

Comment (by hinder):

The documentation for the release branch is also now available. See https ://build- test.barrywardell.net/job/EinsteinToolkitReleasedDoc/lastSuccessfulBuild/artifact/doc/HTML.tar.gz. Simpler than setting up a trigger would be to set up a daily cron job on the web server. You could do that first, and worry about making it more efficient later. That would at least get us daily updated documentation for master and the release.

#2022: thorn guide on et website links to pdf pages --------------------------------------+------------------------------------- Reporter: rhaas | Owner: knarf Type: defect | Status: reopened Priority: major | Milestone: Component: EinsteinToolkit website | Version: development version Resolution: | Keywords: --------------------------------------+------------------------------------- Changes (by rhaas):

* status: closed => reopened * resolution: fixed =>

Comment:

The attached html page does do the proper column wrap, keeping docs for each arrangement together (not with bootstrap which makes this hard).

#2022: thorn guide on et website links to pdf pages --------------------------------------+------------------------------------- Reporter: rhaas | Owner: knarf Type: defect | Status: reopened Priority: major | Milestone: Component: EinsteinToolkit website | Version: development version Resolution: | Keywords: --------------------------------------+-------------------------------------

Comment (by rhaas):

Replying to [comment:9 knarf]:

Replying to [comment:7 rhaas]:

...

Thank you Frank, Ian, Barry. I am re-opening to have the conversation

in life ticket and not a closed one so that it shows up as a changed ticket.

...

Using the auto-generated one seems like a good idea. Comments on the

current list of thorn guides (http://einsteintoolkit.org/documentation/ThornGuide.php yes its a php link):

...

• the are errors in the HTML: the closing </li> tag is missing
• the layout looks quite strange to me with lots of empty space, see

eg the attached screenshot. I don't know if his is "new" or was already the case for the old website (cannot check since I don't have a php enable web-server at hand).

Yes, I am aware of the 'uneven' lists. The only way I could imagine

breaking this up it by breaking the lists of individual arrangements - but I don't think this would be better, because then you can easily end up with the arrangement name out-of-screen and to the bottom of a corresponding thorn name. The reason why you didn't see this in the old list was that the old list was just that: one long list. I could easily do that, and in fact had it like that first, but I personally found it better to get more 'value for screen space', and broke the list into arrangements, which then are placed next to each other. This is done sorted alphabetically, but the number of columns dynamically, which is why you might end up with a setup that looks a bit odd depending on the current list of thorns and your browser width. Improvements are welcome, the script is in git.

I am providing an improvement in https://trac.einsteintoolkit.org/attachment/ticket/2022/ThornGuide.php.html which is pure css and works fine if one eg drops the file into a local checkout of the ET website git repo. I lets the browser wrap the lines based on giving it a column width as a number of "em"s ie roughly how many characters are in the column.

#2022: thorn guide on et website links to pdf pages --------------------------------------+------------------------------------- Reporter: rhaas | Owner: knarf Type: defect | Status: reopened Priority: major | Milestone: Component: EinsteinToolkit website | Version: development version Resolution: | Keywords: --------------------------------------+-------------------------------------

Comment (by knarf):

Replying to [comment:10 rhaas]:

Replying to [comment:9 knarf]: I am providing an improvement in

https://trac.einsteintoolkit.org/attachment/ticket/2022/ThornGuide.php.html which is pure css and works fine if one eg drops the file into a local checkout of the ET website git repo. I lets the browser wrap the lines based on giving it a column width as a number of "em"s ie roughly how many characters are in the column.

That's an interesting solution. It would require you to 'guess' the number of 'ems', but since this is 'ems' it shouldn't be too bad in most cases. The main difference here is the sorting. This sorts up-down first, then left-right. The current version sorts left-right, then up-down. Which is I guess a question of taste.

#2022: thorn guide on et website links to pdf pages --------------------------------------+------------------------------------- Reporter: rhaas | Owner: knarf Type: defect | Status: reopened Priority: major | Milestone: Component: EinsteinToolkit website | Version: development version Resolution: | Keywords: --------------------------------------+-------------------------------------

Comment (by rhaas):

ping.

#2022: thorn guide on et website links to pdf pages --------------------------------------+------------------------------------- Reporter: rhaas | Owner: knarf Type: defect | Status: closed Priority: major | Milestone: Component: EinsteinToolkit website | Version: development version Resolution: fixed | Keywords: --------------------------------------+------------------------------------- Changes (by rhaas):

* status: reopened => closed * resolution: => fixed

Comment:

Applied as git hash a4ac9f3 "ThornGuide: use css colums rather than bootstrap one" if einsteintoolkit/www.