Thank you for picking this up.
-
Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.
If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.
- The Lone Wolf Development Team
Realm Works Output Formatter
- Thread starter Farling
- Start date
Thank you for picking this up.
gloranphile
Well-known member
Version 1.9 works excellently. This is an awesome tool, thanks so much, Farling!
It would be of great advantage if possible to optionally split the .xhtml files by Category if possible. In the below image, there would be a file for Mechanics Source, Character Creation, Creatures of Glorantha, and Mundane Weapons.
https://imgur.com/a/O5oMA
Overall great tool! This will serve me well.
It would be of great advantage if possible to optionally split the .xhtml files by Category if possible. In the below image, there would be a file for Mechanics Source, Character Creation, Creatures of Glorantha, and Mundane Weapons.
https://imgur.com/a/O5oMA
Overall great tool! This will serve me well.
Grouping them by individual category wouldn't be too difficult on the summary page (index.html).
gloranphile
Well-known member
You mean like a Table of Contents? Even better!
Version 1.10 has just been released.
All the formatting in snippets should transfer properly to the final XHTML output files.
(I've picked up the open source library GUMBO to ensure that the HTML in the snippets is decoded properly, which removes the head-ache of trying to do it myself.)
All the formatting in snippets should transfer properly to the final XHTML output files.
(I've picked up the open source library GUMBO to ensure that the HTML in the snippets is decoded properly, which removes the head-ache of trying to do it myself.)
There's already an index.xhtml file produced which has the topic containing hierarchy, but the base topics are in the order in which they appear in the RWoutput file, which might not be sorted in any particular order.
gloranphile
Well-known member
Farling, this tool saved my game last night. I've been unable to export my Story and Mechanics and import into a new realm for months (still waiting on a fix), so RW has been unusable for me. Referencing the html output made researching spells, etc. so much easier than cracking open books at the table.
I owe you a beer if I ever make it up to London. Thanks!
I owe you a beer if I ever make it up to London. Thanks!
I'm glad its a useful tool
I use a HTTP grabber to copy the paizo prd for my gaming laptop.
Version 1.11 has just been released.
The index page now arranges top-level topics under their appropriate category.
Both categories and topics with children can now be collapsed to hide their children (this doesn't work on Edge because Edge doesn't support full HTML5 - search for <details> and <summary> support, see https://wpdev.uservoice.com/forums/.../suggestions/6261266-details-summary-elements).
The tool will always generate separate topic files.
The version number of the application is displayed in the bottom status bar when first started.
The installer has been changed from the Qt Installer Framework to NSIS - the end result is that the installation file is smaller, the version more reliable, and there's less files required to support the installer.
This version returns to being a 32-bit application, since the loading of the RWoutput file has been optimised (the 900MB file will only take up 900MB of memory instead of 1900MB). It also avoids needing to the ship Visual C++ runtime installer as part of the delivery (since VC++ is required to get 64-bit support).
(I won't be making any browser-specific code in any HTML. If a browser doesn't support HTML5 properly then complain to the supplier or use a different browser!)
The index page now arranges top-level topics under their appropriate category.
Both categories and topics with children can now be collapsed to hide their children (this doesn't work on Edge because Edge doesn't support full HTML5 - search for <details> and <summary> support, see https://wpdev.uservoice.com/forums/.../suggestions/6261266-details-summary-elements).
The tool will always generate separate topic files.
The version number of the application is displayed in the bottom status bar when first started.
The installer has been changed from the Qt Installer Framework to NSIS - the end result is that the installation file is smaller, the version more reliable, and there's less files required to support the installer.
This version returns to being a 32-bit application, since the loading of the RWoutput file has been optimised (the 900MB file will only take up 900MB of memory instead of 1900MB). It also avoids needing to the ship Visual C++ runtime installer as part of the delivery (since VC++ is required to get 64-bit support).
(I won't be making any browser-specific code in any HTML. If a browser doesn't support HTML5 properly then complain to the supplier or use a different browser!)
Last edited:
This kind of puts a kibosh on things you can do more easily with a single file. Print the realm as one print job. Send it to a friend as a single PDF file. Bringing into Word or Open Office or Libre Office as a single import.
Ok, I'll look at putting back the single file option.
Maybe I've just been working on realms that are too big
If the realm has external files in it (E.g. PDF files, herolab portfolios), then those will still appear as separate files to the single HTML file. I haven't found a way to encode files inline although pictures can be inlined just fine.
Ok, I'll look at putting back the single file option.
Maybe I've just been working on realms that are too big
If the realm has external files in it (E.g. PDF files, herolab portfolios), then those will still appear as separate files to the single HTML file. I haven't found a way to encode files inline although pictures can be inlined just fine.
You can inline statblocks, as those are just HTML files. Just have to remove the the tags for document, body, title, et al. Not saying you HAVE to. Just saying you CAN.
You can inline statblocks, as those are just HTML files. Just have to remove the the tags for document, body, title, et al. Not saying you HAVE to. Just saying you CAN.
The "statblock" snippets appear to be stored in RTF format.
I haven't investigated delving inside herolab portfolio files to extract information from them.
Huh. Then there's an HTML snippet type. Or something. I know there's something in there that's HTML.
gloranphile
Well-known member
Another humble suggestion: is it possible to put an expand and contract all index bookmarks from the "index.xhtml" page? So one could do a search on the expanded index for the name of a feat, etc.?
Release 1.14 has just been released.
Just for gloranphile A global collapse/expand button now appears at the top of the navigation pane of the index page.
Each topic ends with a "Child Topics" section which links to the direct children of the topic.
Topic aliases are placed immediately below the topic title.
Provide additional export information as meta items in the head of the main page.
Replace individual style definitions with reference to a locally created CSS style (called rwStyleX), but keep the Realm Works snippet styles (Read_Aloud, Callout, Flavor, Handout) as named classes.
Just for gloranphile
A global collapse/expand button now appears at the top of the navigation pane of the index page.Each topic ends with a "Child Topics" section which links to the direct children of the topic.
Topic aliases are placed immediately below the topic title.
Provide additional export information as meta items in the head of the main page.
Replace individual style definitions with reference to a locally created CSS style (called rwStyleX), but keep the Realm Works snippet styles (Read_Aloud, Callout, Flavor, Handout) as named classes.
gloranphile
Well-known member
Thanks Farling!
V1.15 is now available
Stat Blocks, and the stat blocks hidden inside Hero Lab portfolio files, are now made available directly on the web page. They start out collapsed so as not to use up too much space.
(In fact, any external objects which have a file type HTM, HTML or RTF will be displayed in-line.)
The list of "child topics" is now spread across 3 columns instead of being a single long column.
The "generator" meta tag is now filled in properly with the name and version of the tool.
This version now incorporates the ZLIB and QUAZIP libraries (in order to extract files out of the Hero Lab portfolio files).
Stat Blocks, and the stat blocks hidden inside Hero Lab portfolio files, are now made available directly on the web page. They start out collapsed so as not to use up too much space.
(In fact, any external objects which have a file type HTM, HTML or RTF will be displayed in-line.)
The list of "child topics" is now spread across 3 columns instead of being a single long column.
The "generator" meta tag is now filled in properly with the name and version of the tool.
This version now incorporates the ZLIB and QUAZIP libraries (in order to extract files out of the Hero Lab portfolio files).