Ryan Pavlik (code - art - life) on cleardefinition.com
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
19
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
28
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
30
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
32
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
33
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
19
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
28
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
30
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
32
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
33
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
19
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
28
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
30
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
32
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
33
May 21, 2007
This summer, I’ll be working on AbiWord for the Google Summer of Code, in the AbiCollab project (”Systematically breaking and fixing AbiCollab”). Though the Summer of Code doesn’t officially start for another week, I thought I’d ease into it with a brief evaluation of the current state of AbiCollab. I had worked with the plugin a while ago (before the big rewrite), but hadn’t gotten it built recently.
Well, I can proudly announce that that’s changed. Thanks in part to the joy of virtualization (running both a Jabber server and the second AbiWord instance), I have the latest AbiWord (from SVN Trunk) compiled and running with the XMPP (Jabber) backend of the AbiCollab plugin. As the screen shot shows, it does work! I did run across a few issues already, but I definitely feel more capable and comfortable with the code now. And, I’m sure my mentor (master?) uwog will be glad to oblige my requests for explanation 
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/link-template.php on line 73
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/link-template.php on line 98
RSS feed for comments on this post. TrackBack URL
Copyright 2004-2008 Ryan Pavlik. Code released under the appropriate license to contribute.
Finally, a face to go with the name! Just noticed you have a head on the planet now.
Comment by Mikey Cooper —
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line 19
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line 28
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line 30
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line 32
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line 33
May 22, 2007 @
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line 19
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line 28
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line 30
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line 32
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line 33
4:50 am