[3344] in BarnOwl Developers
BarnOwl UserVoice request categorization
daemon@ATHENA.MIT.EDU (Geoffrey Thomas)
Mon Feb 4 21:12:49 2013
Date: Mon, 4 Feb 2013 18:12:45 -0800 (PST)
From: Geoffrey Thomas <geofft@MIT.EDU>
To: barnowl-dev@mit.edu
We have a UserVoice thing. I don't think it's gotten much use recently. So
I figured I'd make sure everything was reflected in Trac, or already
implemented.
Here's an attempt at categorizing the open tasks-ish in it. Please make
sure I have them right; there are a couple that I don't quite understand.
http://barnowl.uservoice.com/forums/55696-general
"Persistent message list across restarts":
blocking on perlmessages/ponymessages
"Detect pasted vs. typed text and don't wrap the former": #180
"Make search faster": #29, I think. (Nelson?)
"Support limited-duration zpunts": #17
"Allow searching in popup windows": WFM. Did this get implemented
recently?
"Create a network API (ie, expose the message list via an authenticated
HTTP server)": ponymessages
"Improve the Jabber UI": This is vaguely defined ("fix annoying bugs"),
but there are a handful of Jabber bugs. I opened #236 for the concrete
part of this.
"Improve memory usage": Ill-defined, but more doable once perlmessages or
ponymessages lands. I opened #237 for a specific goal along these lines
that I vaguely want to work on at the hackathon.
"When replying, highlight the context being replied to": opened #238
"Allow searching command history": #93
"Support multiple views": I don't actually understand this ticket (I mean,
I understand that there's documented and nonexistent functionality, but I
don't understand the documentation well enough to know what the missing
functionality _is_). David?
"Automatically re-wrap incoming messages": We have :view -s wordwrap.
Should we just document that better?
Comment on the previous about format=flowed: #82
[from here on out, the suggestions have fewer than five votes]
"Automatically delete and expunge all but the last N messages": opened
#240
"Optionally auto-escape Zephyr markup when sending": #122
"Make the Jabber auto-away message configurable": #106
"Make the UI more consistent across different protocols": #84 is part of
this. The rest is probably an interesting design discussion, since Zephyr
at least doesn't really work like an "account".
"Display message authentication status in default style": Already
implemented ("UNAUTH: ").
"Make the default style more information-dense": There are zero votes for
this, so I'm not going to bother filing a ticket for it since everyone
seems happy with the default style.
--
Geoffrey Thomas
geofft@mit.edu
