<?xml version="1.0" encoding="UTF-8"?>
<!--Here is an example of how to edit a FileMill.xml file,
in order to create your own front end app for the command line tool(s) of your choice.

This example is based on the excellent command line tool github.com/fhanau/Efficient-Compression-Tool
(losslessly optimizes png, jpg, (g)zip files).-->
<settings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<!--Give a title to your app (will be displayed both in the taskbar, and in the app itself).
Think about adding a version number to the title, so that your users can check if there is a new version.-->
	<appTitle>sdFilemill.ECT 1.0</appTitle>
  
<!--Give a link for your users to download the latest version of your interface.
Remove this line if you don't have a web page for your interface.-->
<!-- <appLink text="home page" url="http://myFrontEndPage.com" /> -->

<!--If you set a .png file here, it will be used as both a logo in the app Window, and an icon in the taskbar.
Path is relative to the file sdFilemill.exe. You may leave this field blank.-->
	<logoPng></logoPng>
	
<!--Set which target folder should be set at app startup. Example: C:\temp
Use empty in order to default to the same folder as the source files.-->
	<defaultTargetFolder></defaultTargetFolder>
  
<!--You may configure different presets for your command line tool.
You should at least define 1 preset.-->
	<presets>
  
<!--Give a name to your preset. One of them should have the "isDefault" flag.

ParallelisationLevel: tell how many files should run in parallel.
0 (default) for "auto multi-core" (use as many instances as the cpu has cores).
1 to run only 1 command line tool instance at the same time
(usefull if your commande line tool is already optimized for multi-core CPUs).
2 to run 2 instances at the same time.
3 to run 3 instances at the same time.
... and so on.-->
		<preset name="ect -1" isDefault="true" parallelisationLevel="0">
	
<!--List all the file types that your preset can handle.
Use a single entry with extension ".*" if your command tool can handle any file type.
Longest extension are prioritized: if you have lines for both .tar.gz and .gz extensions, then .tar.gz files will use your .tar.gz config, and any other .gz file your .gz config.-->
			<supportedFiles>
	  
<!-- For each input file extension, set:

command: the command line that will handle the input file.
Command line path is relative to sdFilemill.exe.
%inputFile% and %outputFile% will be replaced with full paths for each file processed.

comment: you may add a comment, that will appear next to the command line tool name.
It can be, for example, a version number.
You only need to set it once per command line tool.

link: you may give credits to the authors of the command line tool,
and have a link to their page (ommit this parameter if the command line tool has no web page).
You only need to set it once per command line filename.

output: the type of the file that your command will create as output.
Use .*.gz (for example) if your command line adds an extension instead of changing it. -->
				<inputFile extension=".gzip" command="ect.exe -1 -strip -keep --strict %inputFile%" comment="0.9.5" link="https://github.com/fhanau/Efficient-Compression-Tool" output=".gzip" overwrite="true"/>

<!-- In order to improve readability, you may omit some settings if they are the same as in the previous entry.
ParallelisationLevel, extension, command and output
will take the values of the previous entry if ommited. -->
				<inputFile extension=".zip" output=".zip" overwrite="true"/>
				
				<inputFile extension=".png" output=".png" overwrite="true"/>
				
				<inputFile extension=".jpeg" command="ect.exe -1 -keep --strict %inputFile%" output=".jpeg" overwrite="true"/>
				
				<inputFile extension=".jpg" output=".jpg" overwrite="true"/>
			</supportedFiles>
		</preset>

<!-- Let's have another preset for the same tool, but with a bigger compression effort: -->
		<preset name="ect -9">
	
			<supportedFiles>
	  
				<inputFile extension=".gzip" command="ect.exe -9 -strip -keep --strict %inputFile%" output=".gzip" overwrite="true"/>
				
				<inputFile extension=".zip" output=".zip" overwrite="true"/>
				
				<inputFile extension=".png" output=".png" overwrite="true"/>
				
				<inputFile extension=".jpeg" command="ect.exe -9 -keep --strict %inputFile%" output=".jpeg" overwrite="true"/>
				
				<inputFile extension=".jpg" output=".jpg" overwrite="true"/>
			</supportedFiles>
		</preset>
	</presets>
	
<!--Extra attributes available:
exclude: you may add exclude=".zip,.rar" (or any other extention you'd like to exclude) to the preset section.
overwrite: by default, FileMill avoids overwriting any existing file. Caution, if you use overwrite="true" in the inputFile section, this won't be true anymore!
console8bits: if your command line tool does not support filenames with special characters, you should add console8bits="true" in the inputFile section.-->
  
</settings>
<!--Place your FileMill.xml file alongside sdFilemill.exe.
Place your command line tool also near sdFilemill.exe (it may also be in a subfolder -etc for example-).

Check their licence terms before redistributing command line tools alongside your front end app!

Use the resulting tool for yourself, or package the whole thing in a .zip or in an installer,
put it online, and let others download it!
Once you're ready, you're welcome to reach out to bsky.app/profile/sylde.net or x.com/syldenet,
and tell about it! :) -->