Oh, includes.xml - used for files referenced by more than one toc.
Addon.toc (refers to [color=yellow]modules.xml[/color])
[color=yellow]modules.xml[/color] (refers to Addon_LoD1/[color=aqua]includes.xml[/color])
Addon_LoD1.toc (refers to [color=aqua]includes.xml[/color])
The post I just typed got lost, so just saying thanks funkeh for your hard work converting exising addons to use the xml structure.
The TOC's are better now that there is some formal way to assign a purpose to what the TOC is referencing. (limited to embeds and modules) right now since those are the most common, and they get special treatment.
its not always possible to use includes.xml, especially in addons designed to be flexible so the user can delete the sub folders they don't want, which will result in addon breakage if the xml file was there. So could i request WAU to delete includes.xml if unpack ran succesfully?
Give me an example. I cant see a scenerio that couldn't be handled via the xml's but, if you can give me one. sure
1) embeds.xml (Refers to your embedded libs)
2) includes.xml (Uses relative paths, to include lua files in subfolders. includes.xml usually in the subfolder)
3) modules.xml (Refers to your optional LoD modules)
Wau deletes embeds.xml if you install an addon without externals. It deletes modules.xml if you unpack an addon into its LoD subaddons. You dont always need modules.xml to be deleted for you, because you can place it into one of the LoD addon's folders, and when its unpacked, it goes with that folder.
embeds.xml, should be in addondir/embeds.xml
modules.xml, should be in addondir/modules.xml
includes.xml should be kept in the same directory as the files it refers to.
As you can see embeds.xml is the link to the embedded library files.
It doesnt stop there:
Addon.toc (refers to Addon_LoD1/includes.xml)
Addon_LoD1.toc (refers to includes.xml)
This is a LoD module example. Both the Addon.toc and the Addon.LoD1.toc reference the same includes.xml.
If you move Addon_LoD1 up one level, then Addon.toc no longer points to a valid file, effectively removing the lua file references. You also gain centralization of your addons's file structur, instead of 2 toc's with duplicate data, you now have 2 tocs, pointing to a single file.
The general pattern is use includes.xml to reduce a directory down to a single file which contains all the lua references.
Another trick, if you have many modules with single lua files in them, pick a module, and place a 'modules.xml' there, then use relative (..\foo\foo.lua, or ..\foo\includes.xml) references to include all the other modules. Inlcude this modules.xml in your addon TOC.
If the modules are made LoD, when they are moved up into the addon directory, the reference to modules.xml is no longer valid.
WAU goes through and removes addondir/embeds.xml. Since you defined it, you control what references are removed.
Combined that .toc-cleaning and embeds.xml-commenting and FrameXML.log went down from 73kB to 3kB (MultiTips and simpleMinimap being the only "Ace" addons mentioned there).
Also, loading times improved a lot. Did not measure it, but it really is noticeable.
WTB "scriptable post processing" for WAU :D
WAU has a command line interface, and a log file (there's your scriptable post processing)