<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>While I sympathize with your position, SWORD filters have always been applied in the order they are specified in the .conf file and many have order dependencies. SWORD filters are like UNIX piped commands. Order matters.<br><br>Some SWORD filter authors have used inter-dependencies and we don't have a complex system of "dependsOn" properties in the filter-set so each might know of any filters which needs to run before itself, with a manager working it all out. In fact, it is conceivable that, as with UNIX pipes, different ordering might be desired for different circumstances. Filters in SWORD are simply snippets of code which conform to a SAX processing model and are dynamically configured to be executed in whatever order is specified. The way these dependencies are specified is by order in the .conf file.<br><br>I really do sympathise with your position, Karl, and in practice, there is typically only a few order dependencies which exist. The alternative is to either remove these filter interdependencies altogether, or else to build the aforementioned "dependsOn" framework so a filter can specify its dependencies which need to run first, and then build the logic to organize all the specified dependencies for each specific filter pipeline and establish an order based on these, and then to change the principle that order in a .conf file is no longer a programmatic declaration of processing order.<br><br>Troy<br><br><br><br><div class="gmail_quote">On July 7, 2020 4:02:17 AM GMT+02:00, Karl Kleinpaste <karl@kleinpaste.org> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="moz-cite-prefix">On 7/6/20 9:12 PM, Troy A. Griffitts
wrote:<br>
</div>
<blockquote type="cite" cite="mid:c3efc27c-610d-ed97-4040-6ff9cbaeef63@crosswire.org">edit
your morphgnt.conf file and reorder the options</blockquote>
<font face="FreeSerif"><br>
I'm here to argue that, if order of GlobalFilterOption choices
matters, it's the job of the engine to enforce the correct order,
internally, regardless of their textual appearance order in .conf.<br>
<br>
I don't think I need to provide any reasoning for this argument,
because it's true by inspection: To claim otherwise is to claim
that every single module creator must be aware of required
ordering choices of a conceptually unordered list of features.<br>
</font>
</blockquote></div><br>-- <br>Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>