lyskomd-qa February 2003

lyskomd-qa@lists.lysator.liu.se

1 participants
6 discussions

[Bug 985] New async: text marked as read
by bugzilla-daemon＠cvs.lysator.liu.se 16 Feb '03

16 Feb '03

http://bugzilla.lysator.liu.se/show_bug.cgi?id=985 ceder(a)lysator.liu.se changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 991] New aux-item: hidden
by bugzilla-daemon＠cvs.lysator.liu.se 16 Feb '03

16 Feb '03

http://bugzilla.lysator.liu.se/show_bug.cgi?id=991 ceder(a)lysator.liu.se changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 991] New: New aux-item: hidden
by bugzilla-daemon＠cvs.lysator.liu.se 11 Feb '03

11 Feb '03

http://bugzilla.lysator.liu.se/show_bug.cgi?id=991 Summary: New aux-item: hidden Product: lyskomd Version: 2.0.7 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: server AssignedTo: ceder(a)lysator.liu.se ReportedBy: ceder(a)lysator.liu.se QAContact: lyskomd-qa(a)lists.lysator.liu.se This aux-item provides a mechanism that can be used to indicate spoilers, so that a client won't display them to the user until the user has confirmed that he wants to see it. It can also be used to hide the answer to a puzzle, and possibly for other purposes as well. Suggested definition: > Data is: > > start-char (a decimal number) > space > end-char (a decimal number) > space > reason (a hollerith-encoded UTF-8 string) > > For future compatibility, clients should ignore anything that > follows the reason. start-char and end-char refers to the > substring of the text that should be hidden; they have the same > meaning as the start-char and end-char arguments of 25=get-text. > > Clients should by default hide the portions of the text that are > referred to by the "hidden" aux item, and display the reason > string instead. The user should be able to look at the hidden > text by giving a simple command. If a part of a text is hidden by > more than one "hidden" aux item, it shouldn't be displayed until > the user has seen all the reasons to block it. (This doesn't > necessarily mean that the user must accept each reason > individually -- a client might have a command to display all > hidden fields at once.) If you are a client writer, and plan to add support for this aux-item once it exists in the server, please write a note about that and raise the priority of this bug from P5 to P2. Credits: Ragnar Ouchterlony suggested that an automatic mechanism for spoiler hiding was needed, and suggested a version that used inline text formatting to mark part of a text as a spoiler. C C Magnus Gustavsson suggested the use of an aux-item that embedds the reason for hiding the text. I merely combined the two proposals and added UTF-8. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 985] New async: text marked as read
by bugzilla-daemon＠cvs.lysator.liu.se 04 Feb '03

04 Feb '03

http://bugzilla.lysator.liu.se/show_bug.cgi?id=985 ceder(a)lysator.liu.se changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |async ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 985] New: New async: text marked as read
by bugzilla-daemon＠cvs.lysator.liu.se 04 Feb '03

04 Feb '03

http://bugzilla.lysator.liu.se/show_bug.cgi?id=985 Summary: New async: text marked as read Product: lyskomd Version: 2.0.7 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: server AssignedTo: ceder(a)lysator.liu.se ReportedBy: ceder(a)lysator.liu.se QAContact: lyskomd-qa(a)lists.lysator.liu.se If a person is logged on from more than one client at the same time, all clients should be informed via an asynchronous message when one client marks a text as read, so that they can all be kept in sync. The design should handle the changes made by mark-as-read, set-unread, set-last-read, mark-as-unread and set-read-ranges. I can think of at least two designs that would work. Design 1: async-mark-as-read [XX] (( conf-no : Conf-No; local-text-no : Local-Text-No; )) async-read-ranges-changed [XX] (( conf-no : Conf-No; )) Design 2: Set-Operation ::= SELECTION ( 0=mark-read new-marked : ARRAY Read-Range; 1=mark-unread not-marked : ARRAY Read-Range; 2=set-read marked : ARRAY Read-Range; ) async-change-read-range [XX] (( conf-no : Conf-No; operation : Set-Operation; )) ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 904] New async: presentation-changed
by bugzilla-daemon＠cvs.lysator.liu.se 03 Feb '03

03 Feb '03

http://bugzilla.lysator.liu.se/show_bug.cgi?id=904 ceder(a)lysator.liu.se changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 |P1 Target Milestone|--- |2.1.0 ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

lyskomd-qa February 2003