|
[
Permlink
| « Hide
]
Gonzalo Silverio added a comment - 11-Jun-2008 11:06
Description of proposed changes - per screen in the attachment
The screenshots attached seem to be derived from the Forums 2.4 UI. I hope this refactor is going to be against Forums trunk and will not lose the topic icons which were added in 2.5 (which change colour for topics with unread messages).
This is a significant usability change, as in 2.4 it's very difficult to see which topics have unread messages just by reading through a long list "X messages - Y unread" next to the topic names. We also have had continuing difficulties with the markup and CSS on the default view (i.e. ability to style it as we wish without affecting other views), so hope that this gets resolved in a cleaner way. > The screenshots attached to SAK-13736 seem to be derived from the Forums 2.4
> UI. I hope this refactor is going to be against Forums trunk and will not lose > the topic icons which were added in 2.5 (which change colour for topics with > unread messages). This is against trunk. Do let us know what is an improvement and what is not! > This is a significant usability change, as in 2.4 it's very difficult to see > which topics have unread messages just by reading through a long list "X > messages - Y unread" next to the topic names. The read/unread flag is still there - it is a text flag, though - if its there, there are unread messages, if not not. > We also have had continuing difficulties with the markup and CSS on the > default view (i.e. ability to style it as we wish without affecting other > views), so hope that this gets resolved in a cleaner way. I think I understand. Most of the work involves changing the templates/markup to delineate exactly what areas are which and be able to address them via Forum's own style sheet. Forums was just too large and unique to be styled with the core sheets - I hope that is the issue you are referring to Hope this helps. -Gonzalo See
I think the problem we had with the default page was the background colours - changing those styles also affected other pages (message view pages), so we ended up editing the jsp to assign new styles so we can change them without affecting others. This is currently targeted for the 2.6 release.
All the work has been completed. Open new issues for new bugs.
The work of merging still needs to occur, if they're is sufficient interest in incorporating this for 2.6.
Reopening this until the changes are merged to trunk.
Lance, it seems there was consensus to merge this for 2.6, but it got overlooked. Is there someone on the Forums teams that could take care of it now? Thanks.
John L said this should now be pushed to 2.7.
Indiana suggestions carried out. Some unresolved issues.
Megan: they are detailed in the subtask SAK-15535 - everything has been QAd and checked into the SAK-13736 branch, so that is OK.
Also wanted to do something about thread depth as outlined in SAK-9804, but that will wait till the SAK-13736 branch is merged back into trunk. Thanks! This branch was merged together with 2.6.x@65913 on 08/18 in tracked in
The original branch in subversion incorporates this patch (
The original branch was a 2.5.x compatible version of these msgcntr UI changes https://source.sakaiproject.org/svn/msgcntr/branches/SAK-13736/ The new branch ( https://source.sakaiproject.org/svn/msgcntr/branches/SAK-16837/ The work branch for these integrating these features into a 2.6.x build was done in this branch. (
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||