You've experienced unusual problems trying to share your screen on a MacBook Pro with Retina display? A black screen with a moving mouse cursor is shared?

In this case your current display resolution settings are too high for screen sharing.

To change the resolution of your display, you can use a tool like "Display Menu".

https://itunes.apple.com/gb/app/display-menu/id549083868?mt=12&ls=1

After you changed the resolution, you may have to restart your screen sharing session.


Chrome has a new flex layout support since version 29.0.1547.57, this cause a broken layout in Sencha Touch 2.2.1.

Fix this issue by changing the rule order of the st-box mixin.

Open resources/themes/stylesheets/sencha-touch/base/mixins/_Class.scss in a text editor and replace the mixin st-box with the following:

@mixin st-box($important: no) {
    @if $important == important {
        display: flex !important;
        display: -webkit-box !important;
        display: -ms-flexbox !important;
    } @else {
        display: flex;
        display: -webkit-box;
        display: -ms-flexbox;
    }
}
After re-compiling your css, your application layout should look as nice as in prior Chrome versions.
During the last view days I was evaluating the Sencha Architect (Version 2.2.2). Most of the things that I wanted to implement were not a problem. But then I wanted to add a custom property in the controller section.
config: {
        /**
         * @private
         */
        viewCache: []
}
At first I thought no problem, that is easy. But in the end it has taken some time to find this out. So here comes the trick:

Go to the "Project Inspector". Type the name of your custom property in the search field of the config pane then click the "add" button or hit your enter key. After that you can change the type. See below:


Eclipse is one of the most popular development environment for developers all over the world. Me personally have been using Eclipse for nearly 10 years for many projects. Lately, while working with an intern, I noticed that the performance of his Eclipse is quite slow.

Of course there are many factors that could influence the speed of Eclipse such as the use of poorly written plugins or the wrong user settings. Even the standard installation of Eclipse itself has performance issues.

For years I have been trying to optimise Eclipse performance in many ways. I would like to share with you one trick that I've always do when my Eclipse starts running like an 80 years old man.

Eclipse stores all the changes in a local history. When this history gets bigger, it obviously has some effect on the performance.

In this case, we should release some old entries from the history. The local history can be found at: ".metadata/.plugins/org.eclipse.core.resources/.history".

However, instead of deleting the history entries manually, there is an option to limit the size of the history file. In the "Settings" of  Eclipse, from "Preferences > General > Workspace > Local history" the number of items and days can be set.

Sencha Touch includes some notable features. The function Ext.Function.createThrottled is one of them.

This function prevents multiple function execution. The interval on which the passed function is executed can defined additionally.

Ok, let's take a look into the code:
// The function to execute at a regular time interval.
var fn = function () {

console.log('fired');
};

// The intervall in milliseconds on which 
// the passed function is executed.
var intervall = 5000; // 5 seconds

var myFunc = Ext.Function.createThrottled(fn, intervall, this);

// Excecuted immediately
myFunc();

// No matter how often myFunc() is called,
// it is only executed once and after 5 seconds
myFunc();
myFunc();
myFunc();
myFunc();
myFunc();
myFunc();
Tip: The function can be assigned to a class variable that is initialized via a constructor or init().