A few days ago I wrote a simple application which helps with internationalization of Google Gadgets. There is a special format of dictionary files for gadgets – “message bundle” – shown in the picture below.
My application translates these files automatically (with the help of Google Translator of course).
Message Bundle Translator for Google Gadgets is an open source application written in Adobe FLEX AIR.
There is a problem with RTMP. It works on 1935 port. In fact it’s not a problem with RTMP but with ISP. ISP like filtering internet traffic and like packets queuing. That’s why connections on port 1935 – which is not wheel – known in Internet – work worse than connection on port 80. Adobe know that and have introduced RTMPT, which is an encapsulation of RTMP in HTTP, which works on port 80.
YouTube does something else. You see, You Tube allows recording from web cam. It uses RTMP to do that, but RTMP works on HTTP (80) port. I noticed it by using NetLimiter.
I decided to check it carefully. Is it RTMP on its unusual port or is it usual RTMPT? Using Wireshark as my oxygen supply, I dove deep in the hidden depths of the system. Wireshark allows me to sniff internet traffic. I was wondering what exactly my laptop send to YouTube. I would have expected many POST requests for RTMPT. There weren’t. It was something like
instead. rtmp:/…webcam.youtube:80/ – 99% YouTube use RTMP on port 80.
It’s an interesting idea. I can check it out to give me an idea of how to write similar routines.
If you want to ruin your blog, become a journalist.
There is a big difference between a blogger and a journalist. A blogger writes posts for fun. A journalist has to write articles for money. If you want to ruin your blog, write blog posts like regular articles. Never force yourself to writing posts. Never think, that someone is awaiting a post from you, and you are obliged to write something. Bloggers are not obligated to do anything, only journalists are.
The second rule to ruin your blog is to write on the spot. Never do it. Wait few hours after you get an idea. If your inspiration doesn’t go away, then write the post. You save your and your readers time.
The next rule to ruin your blog is to write a post based on a negative emotion. Don’t you ever do it. If you get a comment on your negative emotion post, the emotion comes to you again and again. And again on every comments. This is very tiring. Articles inspired by negative emotions bring big profits to journalists, but are no good for bloggers.
If you want to be a good blogger, became the opposite of the journalist.
Sorry, for this off-topic blog entry. It’s my English lesson. Feel free to correct me, I’m learning…
July 26, 2007
Some time ago I decided to keep track of my daily activities and schedules using Google Calendar. What I need today is an overview – to check how much time I actually spent on a particular activity. I would like to check out how much time it took me to work on my client’s project, or how many enjoyable hours were assigned to playing basketball.
Recently I have come up with a few code lines which demonstrate how to start an integration of Google Calendar and Zend Framework. Today I decided to proceed with it and get down to the project again. I started working on Google Gadget, – a tool which is supposed to perform this kind of integration. Right now the gadget is capable of downloading the tasks from an average-size calendar, calculate the total work time for all the records in a calendar, as well as for the records whose titles correspond to a given phrase. It is possible to define several phrases. All in all, it seems to be a quite promising herald of a project that a wide group of net surfers might find very useful. The project is available at: http://code.google.com/p/task-calculator/ To find the gadget you need to go here: http://task-calculator.googlecode.com/svn/trunk/TaskCalculatorGadget/WebContent/gadget.xml. Speaking from my experience, this gadget has already proved its usefulness and sufficiency. I can easily calculate the time devoted to work vice versa the blissful hours spent on entertainment. Such “searching for lost time” makes me think about getting down to work and trying to finish this project… Anyone willing to join me and pay his tribute to the internet? You are more than welcome, the project is open, the license you need is GPLv3. Its temporary name is Task Calculator but, as I have doubts about that, it seems to me that Task Report would sound better. I am not sure yet.
September 27, 2007
Some time ago I began working on a new project – Task Calculator. Its function is to create a report which would sum up the total work time – I need such data for invoicing my client. The work time data are recorded in Google Calendar. The Project is still only a proof of concept – the concept itself proved right, the calculator does all the counting – however, there are still a couple of issues to be improved.
In order to start the calendar you obviously need to have your account in Google. The Task Calculator works as a gadget embedded on Google Home Page. First you have to search for the private address of XML calendar in calendar settings.
Next you need to install the gadget Taks Calculator – click here. Then you copy the URL address from Google Calendar and place it the gadget settings. There is a possibility of adding the key words, which will appear in a report.
If everything works fine, you will see the following report on a monitor.
Now you can view the summary, the monthly report or the listing of all tasks. You are welcome to use the calculator!
