Trac is being migrated to new services! Issues can be found in our new YouTrack instance and WIKI pages can be found on our website.

Changes between Initial Version and Version 1 of GSoC2009/HidingGobject/review071009


Ignore:
Timestamp:
Jul 16, 2009, 1:20:28 AM (15 years ago)
Author:
aluink
Comment:

i pulled the ui stuff, cause yeah...don't need to worry ;)

Legend:

Unmodified
Added
Removed
Modified
  • GSoC2009/HidingGobject/review071009

    v1 v1  
     1old rev: 811d6e22fc676b5d2f87ff0d8fff750662e4bc7b
     2new rev: 2ef380ad3a75f214245ca5e1a34e7fc3d4e23914
     3
     4-------------------------------------------------------------------------------
     5Notes:
     6-------------------------------------------------------------------------------
     7
     8I know you're updating finch because you're using it.  But i don't think I ever
     9explicitly told you that you don't need to worry about the ui's.  You're scope
     10is libpurple, and libpurple alone.  This only includes, libpurple, the protocol
     11plugins, and perhaps the standard plugins.  This does not include the plugin
     12loaders, the ui's or any of the gtk or gnt plugins.
     13
     14I need to run you through delegators and member methods, which for some strange
     15reason I've been calling class methods.  I understand completely now why you're
     16getting *REALLY* confused about this.
     17
     18There's quite a few instances where theres some uber long lines.  We may want
     19to use some variables to make these a bit more readable.  I'll point this out
     20where I notice it.
     21
     22I'm using a mix of line numbers and function names.  It's pretty sparadic,
     23mostly when i don't want to count a ton of lines from the start of the hunk :)
     24
     25-------------------------------------------------------------------------------
     26Files:
     27-------------------------------------------------------------------------------
     28libpurple/blist-node.h
     29 * doxygen comments are incorrect
     30
     31libpurple/buddy.h
     32 * doxygen comments are incorrect
     33
     34libpurple/chat.h
     35 * doxygen comments are incorrect
     36
     37libpurple/contact.h
     38 * doxygen comments are incorrect
     39
     40libpurple/group.h
     41 * doxygen comments are incorrect
     42
     43finch/gntblist.c
     44 * the comment starting on lines 238-239 can be deleted
     45 * line 1395 should be using PURPLE_BUDDY(node) and not typecasting directly
     46   (glib will actually check the instance for us if we use the macro)
     47 * line 1398 should be using PURPLE_GROUP(node) and not typecasting directly
     48 * line 1676 nuke the comment and it's contents
     49 * line 2387:2388 use PURPLE_CHAT(n[12]) (see above)
     50 * line 2390:2391 use PURPLE_BUDDY(n[12]) (see above)
     51 * line 2393:2394 use PURPLE_CONTACT(n[12]) (see above)
     52 * line 2424:2425 use PURPLE_BUDDY(n[12]) (see above)
     53 * line 2467:2468 use PURPLE_BUDDY(n[12]) (see above)
     54
     55finch/plugins/grouping.c
     56 * line 36 needs to be a subclass or a group instances with the names "online"
     57   and "offline".
     58   (out of scope)
     59 * line 54 should be using PURPLE_CONTACT(node) (see above)
     60 * line 59 use PURPLE_BUDDY(node) (see above)
     61 * line 67 use PURPLE_CHAT(node) (see above)
     62 * line 110 online and offline haven't been initialized yet
     63 * line 115 online hasn't been initialized yet
     64 * line 137 needs to be a subclass, or a group instance with the name "meebo"
     65   (out of scope)
     66 * line 269 looks like creating a group node instead _should_ be ok.
     67   (out of scope)
     68 * line 288 should be ok for now, but should be using PURPLE_IS_BLIST_NODE
     69   (out of scope)
     70
     71libpurple/blist-node.c
     72 * purple_blist_node_(add|remove)_node needs lots of help.  We'll cover this
     73   indepth, and it should give you a good understand of it and unconfuse you :)
     74 * purple_blist_node_finalize shouldn't be doing any unrefs, that'll be covered
     75   by the subclasses (we'll go over this indepth during the member methods
     76   discussion)
     77 * purple_blist_node_init: we may want to make settings a property, but right
     78   now it's okay where it is.
     79
     80libpurple/blist.c
     81 * line 544 use PURPLE_GROUP(cnode->parent) (see above)
     82 * line 613 lose the (PurpleBlistNode *) typecast
     83 * line 727 should use purple_blist_node_remove_node (we'll cover this in the
     84   delegator discussion)
     85 * line 1131 lose the (PurpleBlistNode *) typecast
     86 * line 1221 lose the (PurpleBlistNode *) typecast
     87 * line 1578 should be able to die
     88
     89libpurple/blist.h
     90 * line 476 the while should be able to be removed, since everything should be
     91   holding a reference to the buddy if they need it.
     92 * purple_buddy_class_init: the properties shouldn't have the names and
     93   descriptions marked for translation (right now).  We need to determine if
     94   we're going to do it as a project, and if so, how we're going to implement
     95   it.
     96 * purple_buddy_init: call new_node with PURPLE_BLIST_NODE(buddy)
     97
     98libpurple/buddyicon.c
     99 * line 863, we'll probably want to change this to if(!PURPLE_IS_BUDDY(node)) {
     100   unless i'm completely misreading this.
     101 * line 948, same as above
     102
     103libpurple/contact.c
     104 * line 260 needs a space before the ==
     105 * purple_contact_remove_buddy, we'll cover teh ops->update in our member
     106   method discussion.
     107 * line 321 should be using PURPLE_BLIST_NODE(contact), but should be removed.
     108   All we need to do is drop the ops->new_node method in purple_blist_node_init
     109   and all of the children will automatically do it.  Actually, it'll get
     110   triggered at the wrong time, so it has to stay in the instance_init or we
     111   need to create a signal or helper function.
     112
     113libpurple/group.c
     114 * struct members should be hidden
     115 * purple_group_get_accounts, replace typecasts with their PURPLE_FOO macros.
     116 * the name property should be G_PARAM_CONSTRUCT, not G_PARAM_CONSTRUCT_ONLY
     117 * purple_group_init should be using the private structure
     118
     119libpurple/plugins/perl/common/BuddyList.xs
     120 * this will need to be fixed, but is out of your scope.
     121
     122libpurple/plugins/perl/common/module.h
     123 * this will need to be fixed, but is out of your scope.
     124
     125libpurple/protocols/bonjour/bonjour_ft.c
     126 * line 862 uber line syndrome
     127
     128libpurple/protocols/jabber/roster.c
     129 * line 467 uber line syndrome
     130
     131libpurple/protocols/myspace/myspace.c
     132 * line 395 uber line syndrome
     133
     134libpurple/protocols/silc/buddy.c
     135 * line 1468 uber line syndrome
     136 * line 1534 uber line syndrome
     137
     138libpurple/protocols/zephyr/zephyr.c
     139 * line 815 uber line syndrome
     140 * line 817 uber line syndrome
     141 * line 1197 uber line syndrome
     142 * line 1199 uber line syndrome
     143
     144pidgin/gtkblist.c (out of scope)
     145 * line 1513 uber line syndrome
     146 * line 1519 uber line syndrome
     147 * line 1554 uber line syndrome
     148 * line 1582 uber line syndrome
     149 * line 1639 uber line syndrome
     150 * line 2010 uber line syndrome
     151 * line 2356 uber line syndrome
     152 * lines 2665:2666 uber line syndromes
     153 * line 2776 uber line syndrome
     154 * line 3820 uber line syndrome
     155 * line 3822 uber line syndrome
     156 * line 3830 uber line syndrome
     157 * line 3860 uber line syndrome
     158 * line 4056 uber line syndrome
     159 * grown tired of recording these...  especially since they're out of scope
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!