A few days ago I was working with eclipse (or more precisely with Aptana 1.5) on a project. I have accidentally closed a file, although I was not finished yet. In trying to open this file again I could have go to the „Project View“ open it through the directory list.
We know this shortcut from many other programs to open a recently closed window/tab. So why shouldn’t it work in eclipse? So I just tried to reopen the file useing the shortcut:
CTRL + SHIFT + T
I wish all my regular readers (and those who want to be) a happy new year 2011. Fortunately, the Jugendmedienschutz-Staatsvertrag has not been adopted, so that I can still safely tell you about interesting topics related to web development.
One of my regular readers is my colleague Michael, who has pointed me on a new shortcut in the office and asked me if it would be worthy of a „shortcut of the month“. He is very handy, but I’m sorry Michael, there are 2 alternatives to it, so he will not make it to a shortcut of the month. But I want to introduce him anyway:
ALT + ESC
With this shortcut you can cycle through the open programs in Windows without seeing the previews of the corresponding program. Strictly speaking, the currently active window moves to the end of the z-order, so it can’t simple be switched back to the previous program by using the shourtcut again.
Because it changes so the usual behavior when switching between programs and since Windows Vista introduced the great „Flip 3D“ function, the shortcut is probably used only by very few (if they know him at all). A detailed overview of the program switch shortcuts can be found on the Alt-Tab page in the English Wikipedia.
Now I wish once again a happy new year and enjoy reading my other blog articles!
For many of you this shortcut will not be new, but I didn’t know him for a long time and many friends who have been using Windows for decades haven’t knew him until recently. I also found him by chance.
The shortcut is at least available in Windows XP and later. Whether it existed also in earlier versions I cannot say at present, because I do not have Windows running in a previous version in a VM or a computer anymore. But now let’s introduce the shortcut and what he is good for:
ALT + SHIFT
With this shortcut you can change the input language in Windows. Those of you, using the „Input Language bar“ should see a change in the input language by using the key combination.
But why this shortcut is so important? In a German Windows version mostly German and English are set as input languages and German is set as the default. Many German users accidentally pressed that key combination, without knowing it. Then only in the program you used the combination, the input language switched to English. Since Windows can adjust the input language for each program, the confusion is complete when you switch to another program and the input language is German again.
Conclusion and tip
With this shortcut you can change the language at any time immediately, if you accidentally changed it. As many of you rarely or never use the English keyboard layout (since all the letters can be typed with the German keyboard layout), I’d give you the following advice: The best thing to do is removing the English input language via the control panel. That will protect you from accidentally switching the input language.
I don’t actually know if there will always be a shortcut of the month or even one a week, but recently I found a new shortcut, which I would like to share with you. Even after finding it, I couldn’t find any documentation about it in the internet.
But now let’s introduce the shortcut. I work a lot with eclipse (especially with the plugin Aptana). That’s where I accidently found the new shortcut:
CTRL + ALT + J
For a blog I use the Thematic Theme. It provides the basis for own so-called Child Themes and can be customized in many ways. In addition to the normal WordPress actions and filters Thematic provides its own Theme Action Hooks and Theme Filter.
Some of them are very well documented and there are examples on the net. But now I append a text to the page title (i.e. the text inside the <title> tags in <head>) of every single page of the blog. Although the function
thematic_doctitle() is discussed on the page of the Theme Filters in detail in an example, I could not imagine that it has to be written so complicated and with so many lines of source code. Therefore, I again check the source code to find the lines where the function is defined.
All of you have already tried or at least heard of the great new feature of Google, the „Instant Search“. Since this really is a great feature, I decided to program such a plugin for the WordPress community. But despite the enormous extensibility of WordPress this wasn’t an easy task. Unfortunately, for a layman, who previously had no contact with themes, it is probably difficult to get the plugin to work, as he has to go a little deeper into the source code at least twice.
First of all, the original „search loop“ must be copied into a file named
wp-instant-search-template.php. This file must then be copied into your theme directory. The „search loop“ can usually be found in a file called
search.php in your theme directory. It might for example look like this (from the old „default“ theme):
Integrates a Google Instant Search to your blog. The wp-instant plugin uses the Ajax.Updater function of script.aculo.us and the Form.Element.DelayedObserver class. A jQuery implementation will be following soon.
A more detailed instruction on how to customize the plugin can be found here: Customize the WP-Instant plugin for your theme
Integrate a browser search arrording to the Opensearch spezification.
Your visitors can do a search on your post very quickly and on any time. You don’t need to setup any information. Just install and activate the plugin!
A third release candidate for WordPress was just announced. On the developer blog post for RC3 of WordPress you can even find a small Haiku:
Last call; final bugs
Itch, scratch, contort; calmly wait
For now: RC3
There is also a request to plugin developers. They are asked to test their plugins with the new release candidate. I already checked my 3 current plugins and I couldn’t find any errors.
As there are only 9 open and active tickets left, I hope that we can use WordPress 3 very soon on our blogs. I am least looking forward to it.
Today I tested the current beta (3.0-beta2-14526) of the upcoming WordPress version. The good news for all users of some of my plugins is, that I could successfully tested all my plugins with the current beta.
As I stick to some standards while implementing my plugins and I didn’t use any DEPRECATED functions, I am pretty sure that all of the plugins will still work with the final version of WordPress 3.0 but I will check the compatibility with the latest NIGHTLY BUILD from time to time. If I find any issues with these builds, I try to solve them before the final version of WP 3.0 will be released.
If any of you has already found some issues with my plugins in combination with WP 3.0 or if you have issues with your current version of WordPress, please leave a comment on the plugins pages or on this post.
I wish all of us a lot of fun with the new upcoming features of WP 3.0 and I hope that we can enjoy the final version soon.