Mercurial > pidgin
comparison TODO @ 16177:d88f0f320c9b
merge of '07fc4db9a3c2c12596e0354b8e7959aa847f966b'
and '2e6d324c725b3e6a2c803589bca3f0ac9b9790bf'
author | Richard Laager <rlaager@wiktel.com> |
---|---|
date | Mon, 16 Apr 2007 00:44:33 +0000 |
parents | 361c15e0b320 |
children |
comparison
equal
deleted
inserted
replaced
15938:2e3eba412412 | 16177:d88f0f320c9b |
---|---|
24 }}} | 24 }}} |
25 }}} | 25 }}} |
26 }}} | 26 }}} |
27 * buddy list {{{ | 27 * buddy list {{{ |
28 * we have not committed any gobjectification, so this is not a blocker for 2.0.0 until we do. | 28 * we have not committed any gobjectification, so this is not a blocker for 2.0.0 until we do. |
29 * if we do, it is only a blocker to the extent that gaim needs to run. That is, we do not | 29 * if we do, it is only a blocker to the extent that pidgin & finch need to run. That is, we do not |
30 *necessarily* have to gobjectifiy everything as long as we preserve functionality. | 30 *necessarily* have to gobjectifiy everything as long as we preserve functionality. |
31 * That being said, my understanding of the signals mess says that it is probly more work to | 31 * That being said, my understanding of the signals mess says that it is probly more work to |
32 try to do this in stages than to start it or not start it. | 32 try to do this in stages than to start it or not start it. |
33 * This would require some sort of signal aggregation, as gobject signals are unique to the instance. | 33 * This would require some sort of signal aggregation, as gobject signals are unique to the instance. |
34 * one way to do this would be to emit the signals from a non-descript buddy object. this would | 34 * one way to do this would be to emit the signals from a non-descript buddy object. this would |
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 * wrong buddy given priority | 41 * wrong buddy given priority |
42 }}} | |
43 * build targets {{{ | |
44 * this is not a blocker | |
45 * we need build targets for libgaim, we need to test them, and make sure they work. | |
46 * we ought to use our own build targets to build the executable itself. | |
47 * due to the limitations of cvs, this cannot accompany moving files to other directories at this time. | |
48 }}} | 42 }}} |
49 * status {{{ | 43 * status {{{ |
50 * Error messages aren't particularly usable currently. we need to be able to see the full text of | 44 * Error messages aren't particularly usable currently. we need to be able to see the full text of |
51 the error, and what account is in that error condition. | 45 the error, and what account is in that error condition. |
52 * No way to see accounts not in the global state. | 46 * No way to see accounts not in the global state. |
72 }}} | 66 }}} |
73 * Prefs {{{ | 67 * Prefs {{{ |
74 * on upgrade from 1.x, the timestamp preference often gets lost. | 68 * on upgrade from 1.x, the timestamp preference often gets lost. |
75 }}} | 69 }}} |
76 * system log {{{ | 70 * system log {{{ |
77 * The system log minimally should tell me what _I_ do in gaim. It should (minimally) tell me about | 71 * The system log minimally should tell me what _I_ do in Pidgin. It should (minimally) tell me about |
78 my accounts and actions. It should thus list | 72 my accounts and actions. It should thus list |
79 * gaim start and quit | 73 * Pidgin start and quit |
80 * Account connection | 74 * Account connection |
81 * account disconnection, and reason if caused by error. | 75 * account disconnection, and reason if caused by error. |
82 * account state changes, IFF we are logging that for buddies. | 76 * account state changes, IFF we are logging that for buddies. |
83 * This might include the state message(s). | 77 * This might include the state message(s). |
84 * This might be done using one or more files. | 78 * This might be done using one or more files. |