OK, add it to the FRL.
Done...
It reminds me of Tyrantmizar's PasswordMaker Markup Language, even though it's not really related.
Wow, I somehow had missed that one... very interesting indeed...
Hmmm... off the top of my head, I think you're right, its not directlty related, except that it is simply another way of affecting the resulting password.
I think the two could be combined, somehow. Maybe the template can be specified in the markup he talks about; e.g., {A} for upper alpha, {a} for lower-case alpha, {n} for number, {o} for other, etc...
Actually, I don't think they can really be combined. The Password Template Filter, by its nature, would have to be the very last thing in the loop, but the
PasswordMaker Markup Language request would essentially be the very first thing - in fact, it would pretty much have to replace the 'When URL Contains' (and the other requests to enhance this part) function - you know, be an either-or choice - either you want to totally customize the URL components, or you use the pre-defined options.
So, imho, I think they should be kept separate... unless, it makes sense programatically? Maybe you can do them both at the same time, and so for coding convenience, want to combine them?