On Thu, 27 Nov 2008 19:52:17 +0100 Enrico Tröger enrico.troeger@uvena.de wrote:
Furthermore, all templates are editable and each {filename} occurrence (or whatever wildcard) can be removed.
(Not sure what you meant by this - I was talking about when the user has made a template that contains that string and wants to keep it, instead of having it replaced.)
Hmm, so using two wildcard formats? One to be replaced on file creation and to be replaced when saving the file?
No, just one format. Maybe in practice it's unlikely that {filename} would be in a template anyway.
Or we just add {BASENAME} as a template. This could work as long until someone else requests another fancy template feature.
Heh, and maybe it should be {c_header_string} or something so that chars like '-' get replaced with underscores.
Yeah and two months one comes and want somthing similar for Java or whatever and wants to get it replaced using CamelCase and yet another one wants it to be all lowercase or whatever. Anyway, to solve this for now, we could add {BASENAME} or {c_header_string} or something like this.
OK.
Regards, Nick