Actually, what he's thinking of is not the same thing you were - in his (and my) view, thread prefixes are a way of selecting a prefix from a dropdown, e.g. what I did on whatsthatgame.co.uk in particular in http://whatsthatgame.co.uk/index.php?forums/aralander-discussion/
Anyway, it's online here, what do you think? Do you like it or not?
Just check the (private) WIP Plugin topic from Dragooon to see what I mean. Also, all permalinks to posts are rewritten to have the prefixes before the link, and have the "Re: " positioned at the beginning of the link. Which leads me to ask -- what is it with that slightly fucked up $txt['response_prefix'] system... In French, there's a half-space before any colon, which is hard to do (impossible?) in HTML, so I used to have (since I also made the French version of SMF2) 'Re : ' as the prefix. Then for Wedge, for some reason I don't remember, I had to come back to a breakable space, so it's just 'Re : '... However, if you post in French on a multilingual forum, everyone will see "Re : " even if they're not using French. It would make a LOT more sense to have a meta prefix like {re} at the beginning, and have Wedge automatically convert it to $txt['response_prefix'] at runtime... What do you think?
Once again, though, it'd mean going through the database to replace all entries with {re}...
A posting template system can take two forms, either it can be for having one or more predefined blocks of content that can be easily inserted into posts, or it can take the form of being an outright form that users have to fill in to generate a post out of it, e.g. for application forms for certain things.
That's half way towards what he's talking about, incidentally.
Although we could simply use AeMe for that. I say "simply", but it'd probably be simpler to use attachments for that... :lol:
Then it needs to have less content in it if it's going to be done without tables; right now a table is the correct semantic item for it because it's tabular data.


