Thanks Tony Robbins for sharing this video and hope you guys love it as much as I do Happiness requires nothing other than your decision to be happy!

Yesterday I noticed some improvements in the Google Reader UI. Great, I thought, Google have finally decided to do something about the usability issues and maybe this update includes something more that a new visual candy, which is really not much different from the last one. Sharp, instead of rounded edges and the colors are also a bit different.

However, two things that really bug me really remain:

• when reading a post, it sometimes happens that while you read the post is shifted down outside the visible area and some other stuff comes in your face. This is due to the fact, that some posts have a lot of images to load and while you have positioned on a particular place, the posts above load new images, which take more space and since they cannot grow up, your visible area is shifted without you doing anything. This is really bad problem and I am sure it pisses many other people.
• second issue is pretty much the same as before: you visible area is shifted when you hide/show the left bar with the post categories.

And one more thing, what is this all hype about? For the slightly changed colours? People can really get excited about anything if someone else says it is cool!

Although the filter works fine and you would be able to get the frame data, there are some issues, which I didn’t have time to get fixed. For example, you the app might get stack when stopping the filtergraph. This is due that the client callback takes too much time to copy the data and return. This operation should be done as efficiently as possible.

Download the demo project: cameracapturedll_demoproject.dll

I am having the task to do internationalization on a software piece written in .NET. The app has to support multiple languages in the UI and the ability to change the UI language at runtime. So the task could be broken up in two parts:

• enable UI internationalization from resources files
• add the ability to change UI language at runtime

The first part seems quite easy, as Visual Studio already has built-in all of the infrastructure required: designer support for UI internationalization, .resx files with all resources in XML format, which are compiled to dlls for deployment. Although easy to do, this involves quite a bit of work with the designer, as all controls’ properties has to be set individually for every UI culture.

This is usually accomplished with the System.Resources.ResourceManager class and the GetObject method. The code looks something like this:

buttonEnvironment.Font =

((System.Drawing.Font)(resources.GetObject(class="str">"buttonEnvironment.Font")));

The line above sets the Font property of the buttonEnvironment control, given that this property is available in the resource files. Overall, this approach has several drawbacks:

• I have to set all properties individually. This sometimes requires hundreds of lines of code
• if I want move more properties to the resources instead of hardcoding them, I have to change both the resources files and the application code
• it makes it difficult to change the current UI culture, for example if I want to change the UI language in real time. This is because, all initialization code is in the *.Designer.cs file, which is generated by the designer. The code is in the InitializeComponent() method and if I call it, I would have to reset all properties of the controls, even those which are not resource-based.

Considering those points, I went for a custom solution, which includes all the benefits of the above method and doesn’t have any of the above problems. All this is done within a couple lines of code and can work with or separately from the existing internationalization methodology. This means, if you have already started translating your UI in the old-fashioned way, you can still take advantage of the new approach.

Here is the code:

        System.ComponentModel.ComponentResourceManager resources = class="kwrd">null;

        class="kwrd">public Form1()
        {
            InitializeComponent();
            class="kwrd">this.resources =
                class="kwrd">new ComponentResourceManager(class="kwrd">typeof(Form1));
        }

        class="kwrd">private class="kwrd">void radioButton_Language_CheckedChanged(class="kwrd">object sender, EventArgs e)
        {
            class="kwrd">if (radioButton_Bulgarian.Checked)
            {
                System.Threading.Thread.CurrentThread.CurrentUICulture =
                    class="kwrd">new System.Globalization.CultureInfo(class="str">"bg");
            }
            class="kwrd">else class="kwrd">if (radioButton_German.Checked)
            {
                System.Threading.Thread.CurrentThread.CurrentUICulture =
                    class="kwrd">new System.Globalization.CultureInfo(class="str">"de");
            }
            class="kwrd">else class="kwrd">if (radioButton_English.Checked)
            {
                System.Threading.Thread.CurrentThread.CurrentUICulture =
                    class="kwrd">new System.Globalization.CultureInfo(class="str">"en");
            }

            ApplyAllResources(class="kwrd">this);
        }

        class="kwrd">private class="kwrd">void ApplyAllResources(Control c)
        {
            class="rem">// do not paint control while changing it's properties
            c.SuspendLayout();

            class="rem">// apply all properties for the current UI culture from the assemble resources
            resources.ApplyResources(c, c.Name);

            class="rem">// apply all resources for child controls recursively
            class="kwrd">foreach (Control subControl class="kwrd">in c.Controls)
            {
                ApplyAllResources(subControl);
            }

            class="rem">// resume painting
            c.ResumeLayout();
        }

We take advantage of the System.ComponentModel.ComponentResourceManager class and the ApplyResources method, which accepts the control and it’s name as parameters. It then goes forward to set all properties for this control, if available in the .resx files. So if you decide that you want to initialize a new property from the resources, just add it there, and the code doesn’t need to be touched. The function ApplyAllResources goes trough all child controls recursively, so all hundreds of lines of code is now reduced to a couple of lines. Simple and beautiful

You can download a sample C# project here.

A Course In Miracles is the most incredible thing I have ever read. David Hoffmeister tries to explain the basic concepts of the mind training involved in the curriculum.

I Really like the business approach of this company. It is basically the reverse of EBay and allows customers to find the best product and sellers to bring unique offers based on a set of criteria, which they determine themselves. It eliminates advertisement cost and saves a lot of time to the consumer. Simply great!

One of the greatest Truths of life is this.

It matters not what and how much you have, but what you are grateful for. Abundance is not things, but the spirit of gratitude.

I was thinking about this, remembering a quote from Sir John Templeton. His is one of the wealthiest and greatest investors of all time.

It really matters what we think and even more what we are grateful for. Think about it. Can we get things? What does it mean to have something? To feel good or to use it? But does it really need to be had or we just get a short lease on it, even if we possess it.

I think all we want in this world is to feel good and realize the truth of life. Even people which strive for material possessions deep inside them think that those things will somehow enhance their quality of life or make them feel good. Why else bother get them.

Why am I sharing this. For those who want to hear to hear and because I know that giving and receiving is the same thing. As you do onto others, so you do onto yourself … says a famous quote and I fully agree. We know truth when we hear it!

В тази статия и видео материалът показват, как фармацевтичната компания Merck е знаела за рисковете свързани с един от техните медикаменти Vioxx и въпреки това в официалните документи посочват, че няма никакви проблеми с лекарството. В резултат на това, 9 човека умират.

На мен обаче друго нещо ми е чудно. Как е възможно да се позволява на фармацевтичните компании да контролират изцяло клиничните тестове на продуктите си, без никакво независимо потвърждение или анализ. Ако от Merck казват че техните продукти са наред, трябва да им се вярва! Егати лудостта!