From: Matthew M. <ma...@tu...> - 2002-12-04 13:00:19
|
Greetings, First a short unpleasantness. I write to this list for opinions. Recently, I haven't really heard many. Not to be harsh, but if I don't receive feedback from this channel, I will start asking just the hometeam developers. Realize I appreciate people's input. In fact, had it not been for this forum, we might not have sequencial numbering yet. Anyway, I am thinking of how to rid ourselves of the core_settings table. That way, when we perform a core update, it never has to worry about the database. I was thinking there should be a date time format file like the language files. Basically there would be a file named after the abbreviation (ie en.php for English, es.php for Spanish). This file would contain the time and date format for that language. phpWS would ship with a default.php for all languages that do not contain a date/time file. These files could not be with language module as they work independantly from it. Along these lines, there are core_settings for censoring and allowed tags. I think these should be put into a file as well. These do not have to be php files either. We could make them text format so textpad could edit them. Let me know what you guys/gals think and whether you prefer core_settings to remain in a table. Matt Matthew McNaney Internet Systems Architect Electronic Student Services Appalachian State University Phone: 828-262-6493 phpwebsite.appstate.edu ess.appstate.edu |