comparison TODO @ 12680:134e570b3688

[gaim-migrate @ 15023] heise2k mentioned that the TODO was not up to date. now it is. committer: Tailor Script <tailor@pidgin.im>
author Luke Schierer <lschiere@pidgin.im>
date Fri, 30 Dec 2005 15:31:33 +0000
parents 99548d90257e
children 4b5822e48b53
comparison
equal deleted inserted replaced
12679:b18738b03b35 12680:134e570b3688
36 * a second way would be to actually try to aggregate them in some way. I really don't know how 36 * a second way would be to actually try to aggregate them in some way. I really don't know how
37 possible this is, but it would allow us to do things like set a pounce on everyone in a group 37 possible this is, but it would allow us to do things like set a pounce on everyone in a group
38 or define sounds on a per-group basis. 38 or define sounds on a per-group basis.
39 * we could look at replacing the UI ops with signals/call backs 39 * we could look at replacing the UI ops with signals/call backs
40 * bugs 40 * bugs
41 * buddy shows as group on add until gaim restart
42 * buddy shows as online when offline
43 * buddy shows as offline when online
44 * wrong buddy given priority 41 * wrong buddy given priority
45 * so on and so forth
46 }}} 42 }}}
47 * build targets {{{ 43 * build targets {{{
48 * this is not a blocker 44 * this is not a blocker
49 * we need build targets for libgaim, we need to test them, and make sure they work. 45 * we need build targets for libgaim, we need to test them, and make sure they work.
50 * we ought to use our own build targets to build the executable itself. 46 * we ought to use our own build targets to build the executable itself.
51 * due to the limitations of cvs, this cannot accompany moving files to other directories at this time. 47 * due to the limitations of cvs, this cannot accompany moving files to other directories at this time.
52 }}} 48 }}}
53 * status {{{ 49 * status {{{
54 * Sean's segment of the UI needs to be finished. We need to have support for the (new) default case 50 * Error messages aren't particularly usable currently. we need to be able to see the full text of
55 of one global status at all times. we currently do not, unless that happens to be "online/present" 51 the error, and what account is in that error condition.
56 * Tim's modifications to Sean's ui should be included to allow exceptions. refer to gaim-devel 52 * No way to see accounts not in the global state.
57 archives for this. 53 * Easier access to saved states is needed.
58 }}}
59 * account editor {{{
60 * this is not a blocker for 2.0.0
61 * account editor is not intuitive, users do not find it.
62 * Luke: my temptation is to get rid of this entirely, in favor of deryni's account menu. {{{
63 * at this point, tools->accounts is only used for add/delete account, modify account, and
64 enable account.
65 * most users do not have the 15+ accounts that some gaim developers do. a menu scales well for
66 anything from 2 to n, n "small" accounts.
67 * this would allow ready access to the buddy icon stuff, and account actions could go here
68 * status is handled as per the new api, status stuff need not go here beyond enabled.
69 * the account modify dialog is already too big. this would let us split it, for instance
70 buddy icon need not be in it this way. Similarly, alias need not be in it.
71 * splitting the account modify dialog to tabs seems to work nicely. Still, I think
72 that the menu would be nicer.
73 }}}
74 }}} 54 }}}
75 * Privacy {{{ 55 * Privacy {{{
76 * this is not a blocker for 2.0.0 56 * this is not a blocker for 2.0.0
77 * Privacy sucks. it doesn't handle many of the protocols in a way that users understand. notably 57 * Privacy sucks. it doesn't handle many of the protocols in a way that users understand. notably
78 msn, but also yahoo, jabber, and icq. 58 msn, but also yahoo, jabber, and icq.
84 that each protocol define certain capabilities & defaults, with accounts.xml holding exceptions 64 that each protocol define certain capabilities & defaults, with accounts.xml holding exceptions
85 to the defaults. 65 to the defaults.
86 }}} 66 }}}
87 * Perl {{{ 67 * Perl {{{
88 * Block for 2.0.0 or remove perl: 68 * Block for 2.0.0 or remove perl:
89 * Summer of Code seems to have largely solved this.
90 * Extended testing and resolving the inevitable bugs remains. 69 * Extended testing and resolving the inevitable bugs remains.
91 * Test each call to make sure it actually works 70 * Test each call to make sure it actually works
92 * Make it work with G_MODULE_BIND_LOCAL 71 * Make it work with G_MODULE_BIND_LOCAL
93 }}} 72 }}}
94 * Prefs {{{ 73 * Prefs {{{
95 * this blocks for 2.0.0 74 * on upgrade from 1.x, the timestamp preference often gets lost.
96 * Prefs cannot stay as-is. the dialog is far too wide and not at all usable.
97 * The biggest problem is that each new plugin creates horizontal space. {{{
98 * I do not see it as a solution to remove the posability of plugin preferences.
99 * In the past, we had a separate plugin management dialog. People never found it,
100 and were often surprised to learn that gaim had plugins at all. I am unsure that
101 people find the current plugin page of preferences any more frequently, but I
102 *suspect* that it is the case. This leads to a conundrum, how do plugins
103 display preferences?
104 }}}
105 * Currently the window is, at my font size, 1129x505 (or should that be 505x1129?). It *should* fit
106 in 800x600 at worst, I'm unsure that 480x640 is a reasonable goal. still, this leaves us with
107 something either considerably wider or considerably taller than we are currently using (on any
108 given pane, the tabs force the width, not the contents). Further, taking "Message Text" as an
109 example, it has 3 preferences and a text area, each in its own category (the text area sharing a
110 category with 1 preference). obvious waste of space here. All 3 could clearly be uncategorised
111 without loss of meaning, categories only make sense for groups of preferences. It may even be
112 possible to combine this with "Conversations" entirely.
113 }}} 75 }}}
114 76