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.
- Timestamp:
-
Jun 17, 2010, 10:20:07 PM (14 years ago)
- Author:
-
Adola
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v9
|
v10
|
|
23 | 23 | ''May, Monday 31, 2010'' : I read "The C Programming Language", it was a speed run though (one night) so I'll no doubt have to go back and re-read a few things, but it's getting me through learning GTK+ 2.0. I'm going to spend the rest of the day learning GTK. |
24 | 24 | ---- |
25 | | ''June, Wednesday 9, '' : Not a lot of coding going on. I'm spending most of my time reading the previous code, and trying to understand each line of it. I attempted at just coding and brute forcing my methods through the previous functions, and ended up failing. I've decided to implement a method called "pidgin_log_show_global()" along side the previous method "pidgin_log_show()". My function should handle a lot of casting to better work with the major part of the logging engine. Regardless of the amount of molding the data into what certain functions need it to be, there will be a required amount of modification to old functions. I suspect there will be many 'skipping' of data-specific functions. I suspect that once I am able to tally all the contacts into a list, I should be able to move quickly. I feel this true as many of the utilities of the log viewer are based on "contact name | raw logs | formated logs" and adding all the contacts, and clicking on a user's name would require the _SAME_ calls as if a user had gone through the "view log process" via Buddy List. |
26 | | |
| 25 | ''June, Wednesday 9, 2010'' : Not a lot of coding going on. I'm spending most of my time reading the previous code, and trying to understand each line of it. I attempted at just coding and brute forcing my methods through the previous functions, and ended up failing. I've decided to implement a method called "pidgin_log_show_global()" along side the previous method "pidgin_log_show()". My function should handle a lot of casting to better work with the major part of the logging engine. Regardless of the amount of molding the data into what certain functions need it to be, there will be a required amount of modification to old functions. I suspect there will be many 'skipping' of data-specific functions. I suspect that once I am able to tally all the contacts into a list, I should be able to move quickly. I feel this true as many of the utilities of the log viewer are based on "contact name | raw logs | formated logs" and adding all the contacts, and clicking on a user's name would require the _SAME_ calls as if a user had gone through the "view log process" via Buddy List. |
| 26 | ---- |
| 27 | ''June, Thursday 17, 2010'' : I'm still reading through the code, I'm grasping most of it, there are still a few things that baffle me. |
27 | 28 | {{{ |
28 | 29 | CONTACT INFO |
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!