There is not yet a demo server, let me clean the code a little, and install it in a more stable server. Right now it's on an unstable development server we are constantly reseting...
All new features check a package parameter (new for each feature) value to know if the new behavior is enabled or not, and if it's what kind of behavior is set. For instance,
I'm working now in that points:
I can capture a few screenshots, and publish them with a list of new features in a wiki, and post here a link.
Well, I can write now a list of features:
uForums (Forums enhancements for UNED)
FORUM-VIEW
- expand node(s), so...
- show expanded nodes
- collapse node(s)
- collapse all (button or list-template action)
- show unthreaded version button (sort only by date)
- "new message" highlight (using views package and/or a new table for read/unread feature)
- show only new messages button
- mark as read/unread (if views is available)
- mark thread as read/unread button (bulk action)
- mark all forum as read button
- tooltips to show more info
- preview content
- authors information details (disabled right now)
MESSAGE-VIEW
- Next thread /prev thread navigation links
- User portrait
- reply to author button (link to mail)
- forward message button (email to...)
- row.adp architecture reviewed
FORUMS ADMIN
All new features check a package parameter (new for each feature) value to know if the new behavior is enabled or not, and if it's what kind of behavior is set. For instance,
- when marking a message as unread ¿should be marked as unread all the replies or only that message?,
- When expanding a node: ¿expand all levels, or just one?
In development
I'm working now in that points:
- write tests
- test when moderated forums
- add return_url to some actions
- simple admin page (with common parameters)