"newest first". I certainly prefer the latter. How do others feel
about this? If it's equally split, can this preference be made into a
user selection on the "edit alert" page?
It is configurable on the admin level, but right now not at a user level. That functionality would be great, though.
Obviously, it's easy to forget to do so. It may be that Ben prefers oldest first (Ben?) but many prefer newest first, including me.
As far as user configurability, sure, why not? Add it as a "desired feature" using the SDM...thus far we're trying to maintain line-by-line compatibility with the ACS, and will undoubtably do so for bboard at least through ACS 4.0 because aD is rewriting the bboard module. If their rewrite picks up all the features folks want and that are deemed useful by the community, great - if not, post-4.0 would be a good time to look into adding them.
I started on this but it is time-consuming since PostgreSQL currently requires lots of create temp tables, copy, drop old table, create new modified table, copy from temp to new table. If there are other tables with ref integ pointing to that table, then you have to do the same to the other tables _before_ even starting on the table you're trying to change. I think I reached the bboard portion of the upgrade.sql and I plan on finishing it.
Also, I like the web/db forum approach where all incoming questions are in one stream and then categorized within one forum rather than being split into separate forums as is done here in OpenACS. How do others feel about this?