registerExportNode options, include library links for reference?

[celestian]

You can implement own export functionality that uses Module.export function that does everything, includes all content and images as mod file. The built-in export feature uses the same function so there is no special limitation if you would implement your own version.

I wasn't aware of "Module.export" but will look into it. Thanks for the suggestion.

Edit:
Found it here: https://www.fantasygrounds.com/refdoc/Module.xcp

Looks to do much of what I need tho I'm still not sure how to manipulate <library> entries with it for links yet but I'll play about with it to see if it can be done.

[Ikael]

DB package (https://www.fantasygrounds.com/refdoc/DB.xcp) is your friend when building these values. You can build the entire library structure using it and export it with Module.export.

I wasn't aware of "Module.export" but will look into it. Thanks for the suggestion.

Edit:
Found it here: https://www.fantasygrounds.com/refdoc/Module.xcp

Looks to do much of what I need tho I'm still not sure how to manipulate <library> entries with it for links yet but I'll play about with it to see if it can be done.

[celestian]

DB package (https://www.fantasygrounds.com/refdoc/DB.xcp) is your friend when building these values. You can build the entire library structure using it and export it with Module.export.

So I make it myself. Makes sense. That's what I've got with Author already so should just be a bit of node shuffling to make this work. I'll give it a spin tonight and see what I can come up with.

[celestian]

Okay, figured this out. I still think the amount of generic code that Moon could throw at this to make it a trivial issue for anyone else would be a better idea. Having to have your own local copy of export.lua for this seems a bit overkill. All it really needs is a setCustomExportFunction() and bit of variable handoff (I kludged around it using ExportManager.aExport) and really that's it. All the other parts already existed ... specifically registerExportNode().

This is the crux of the code I used for Author.

function onInit()
	if User.isHost() then
		Comm.registerSlashHandler("author", authorRefmanual);
                ExportManager.registerExportNode({ name = "_refmanualindex", label = "Reference Manual", export="reference.refmanualindex", sLibraryEntry="reference_manual"});
    
    -- setup custom export process for the _refmanualindex node build
    setCustomExportProcess(performRefIndexBuild);
  end
end

The custom function(s) are run right before the actual export (after the "Export" button is pressed, at the top of performExport()).

Other than the code in performRefIndexBuild that would be all anyone would need to do the same thing for any other bits tho perhaps it far to of a niche need

Anyway, this was fun to figure out. Works great and no more having to manually copy/paste/etc. All in one /export -> *.mod file with everything a /export would do.

If you want to see the code it's here in the Author extension.

[Bidmaron]

Celestian/Ikael, if I read the new 3.3.6 properly, the new ability to directly set image file names now breaks the previous dependency that ALL images had to be in the image window in order for users to build content. If that is correct, I'd recommend you build this into Author, as folks could then cut and paste file names for images. Or have you already figured out a way around this limitation?

[celestian]

Celestian/Ikael, if I read the new 3.3.6 properly, the new ability to directly set image file names now breaks the previous dependency that ALL images had to be in the image window in order for users to build content. If that is correct, I'd recommend you build this into Author, as folks could then cut and paste file names for images. Or have you already figured out a way around this limitation?

I haven't even gotten to that part of 3.36 if you can give me an example of what it looks like previously and now maybe I can implement it.

[Bidmaron]

MW hasn’t documented it yet, so not sure what to tell you. I presume if you setValue on an image node the parameter is a string file name.