... | ... | @@ -16,6 +16,10 @@ Not being able to provide a 100% solution, however, does not necessary make an 8 |
|
|
|
|
|
## Towards a solution
|
|
|
|
|
|
We are greedy. We know we need something that will work tolerably and usefully well, even if run with all the default settings intact and no special configuration. Running the set of stylesheets "lights out", that is (which is to say arbitrarily will no special inputs or supervision) should always be an option - and the outputs of such a process shouldn't be entirely useless.
|
|
|
|
|
|
However, we also want something that can be extended and adjusted to fit special cases and do special things - because special cases and special things are *regular* and *to be expected*.
|
|
|
|
|
|
The best way we think we can do this is at the level of the architecture. We must design from the outset with the idea that everything in XSweet should be designed for adaptation and reuse. XSweet should work like a black box but you should also be able to open it up and rewire it -- completely, if need be.
|
|
|
|
|
|
And, because we already know that 'perfect for everyone all the time' is impossible, WE AIM (first) FOR USEFUL, NOT (yet) COMPLETE OR PERFECT
|
... | ... | |