There are many tools out there for syncronising calendar information between outlook and google calendar, but the features is limited. I will try to build up my one, and describe here the steps I followed…

In this post I will describe the first building block, and that is how to create outlook events.

Sub NewAppointment()
    Dim app As New Outlook.Application
   
    Dim objAppointment As AppointmentItem

    Set objAppointment = app.CreateItem(olAppointmentItem)

    objAppointment.Start = #5/15/2009 11:00:00 AM#
    objAppointment.Duration = 60
    objAppointment.Subject = “The first appointment created by the script”
    objAppointment.Body = “This is just to test the first appointment created by the script.”
    objAppointment.ReminderMinutesBeforeStart = 15
    objAppointment.ReminderSet = False
  
    objAppointment.Save
       
End Sub

You may have a phpbb based forum where you have protected pages, but by protecting them you miss the oportunity that google bot ranks you site as having rich content. So you may want to allow google bot to see the protected pages… Here is the solution:

I made a little change for one of the forums I host. Here is the solution. This applies particularry for version 2.*.

The idea is not to redirect the google bot to the login page, but to allow to see any content, if the request is comming from ip addresses that translate to sthg. like ***.googlebot.com

Here is the code that has to be added/changed in the viewforum.php file:

$botname=’googlebot.com’;

$hostname = gethostbyaddr($_SERVER['REMOTE_ADDR']);

if ( (!$is_auth['auth_read'] || !$is_auth['auth_view']) && strcmp( substr($hostame, strlen($botname)), $botname) != 0)

Ian Lance Taylor from google announced already one year ago a new linker which is a complete rewrite. I gave it a try on one of the projects I am working an which contains more than 2 milion lines of C++ code + lot of libraries. It links in 14 seconds, compared to 10 minutes the default linker from binutils-2.17.50.0.6 needs. There is however a patch arond for the default linker that reduces link time for the same executable from 10 minutes to 40 seconds. As I link often, it makes a difference between 40 seconds and 14 seconds…

telnic has a different approach in the hysteria of social networking sites. They try to bullshit in a different way their (potential) customers all around the world, so that they can suck out their valuable data drop by drop. Well the first drop is the public phone number. And then the private phone number. And the they will invent new fields they will call them protected, where they will tell you if you already store your phone number, why don’t you store also your credit card number. Then you start to develop your social networking by marking certain people that are known to you. Then if you know so many people, you have to do something in this damm’ virtual world. Then they will propose you to write messages, write blogs, and le voila… that is the new social networking… I wonder what will be the colour of googleface.. I mean of the big guys from google… Well they will take care to offer enough money in time… and suck telnic.

I am convinced that google’s new tool voice and video chat could mean the end of other services like skype. I doubt however that the service would be compatible with sip devices.

so will it happen? google in, skype out?

google engineers are working hard to make chrome available for linux: http://www.google.com/chrome/intl/en/linux.html

Well, there is so far no google chrome for windows mobile devices, but there is another implementation based on the same engine (http://webkit.org/) and can be found at http://www.torchmobile.com/.

Google chrome is out, I worked with it on windows xp 1 day (the first day:), and can say, that among other features it is pretty fast compared to others: firefex, internet explorer, opera.

With iris on pocket pc is also had good experience. After trying the new opera mobile beta, the firefox minimo, iris is a revelation. Google chrome is also a revelation.

I wrote a little benchmark (single threaded) to compare the overhead of allocated memory generated by different allocators for small blocks. The candidates are: thread building blocks scalable allocator, hoard,  google’s tcmalloc and the standard malloc. The benchmark allocates a total useful memory of around 300MB in random size blocks. The limit of the sizes is determined by the parameter to the program. I run a batch for each allocator for max sizes: 8, 16, 32, 64 etc. Below are the results:

./standard max_size: 8, time: 17810000 ticks, util size: 273471 kB, virt mem: 1250072 kB, overhead 357%
./tbb max_size: 8, time: 15190000 ticks, util size: 273471 kB, virt mem: 640204 kB, overhead 134%
./google max_size: 8, time: 18760000 ticks, util size: 273471 kB, virt mem: 642636 kB, overhead 134%
./hoard max_size: 8, time: 16430000 ticks, util size: 273471 kB, virt mem: 626300 kB, overhead 129%
./standard max_size: 16, time: 9680000 ticks, util size: 293005 kB, virt mem: 683792 kB, overhead 133%
./tbb max_size: 16, time: 8870000 ticks, util size: 293005 kB, virt mem: 461004 kB, overhead 57%
./google max_size: 16, time: 9270000 ticks, util size: 293005 kB, virt mem: 466380 kB, overhead 59%
./hoard max_size: 16, time: 7830000 ticks, util size: 293005 kB, virt mem: 450428 kB, overhead 53%
./standard max_size: 32, time: 5220000 ticks, util size: 302209 kB, virt mem: 472988 kB, overhead 56%
./tbb max_size: 32, time: 3520000 ticks, util size: 302209 kB, virt mem: 385228 kB, overhead 27%
./google max_size: 32, time: 4650000 ticks, util size: 302209 kB, virt mem: 393292 kB, overhead 30%
./hoard max_size: 32, time: 4320000 ticks, util size: 302209 kB, virt mem: 376508 kB, overhead 24%
./standard max_size: 64, time: 2590000 ticks, util size: 307102 kB, virt mem: 386396 kB, overhead 25%
./tbb max_size: 64, time: 1620000 ticks, util size: 307102 kB, virt mem: 351436 kB, overhead 14%
./google max_size: 64, time: 2530000 ticks, util size: 307102 kB, virt mem: 360396 kB, overhead 17%
./hoard max_size: 64, time: 2230000 ticks, util size: 307102 kB, virt mem: 343676 kB, overhead 11%
./standard max_size: 128, time: 1140000 ticks, util size: 309567 kB, virt mem: 347720 kB, overhead 12%
./tbb max_size: 128, time: 1090000 ticks, util size: 309567 kB, virt mem: 340172 kB, overhead 9%
./google max_size: 128, time: 1580000 ticks, util size: 309567 kB, virt mem: 345932 kB, overhead 11%
./hoard max_size: 128, time: 1160000 ticks, util size: 309567 kB, virt mem: 335740 kB, overhead 8%
./standard max_size: 256, time: 830000 ticks, util size: 310797 kB, virt mem: 329504 kB, overhead 6%
./tbb max_size: 256, time: 620000 ticks, util size: 310797 kB, virt mem: 347340 kB, overhead 11%
./google max_size: 256, time: 900000 ticks, util size: 310797 kB, virt mem: 344908 kB, overhead 10%

./hoard max_size: 256, time: 860000 ticks, util size: 310797 kB, virt mem: 339004 kB, overhead 9%