I found out some of the changes the hard way when I migrated the Matterhorn Engage UI. Here is a list (mainly for me to remember them):

• .attr and .prop
  • in jQuery 1.6 the handling of DOM attributes and DOM properties is split apart into separate methods
  • .attr first checks if the attribute is explicitly written in the HTML code, after that it looks at the object created by the HTML tag, and inspects its object property
  • .prop sets or gets properties on DOM elements
  • see jQuery 1.6 released
• for ajax calls there are no options like ‘yourAjaxCall.onreadystatechange = anyFunction;’ any more, you have to use ‘success’, ‘error’, etc. inside your ajax-request
• the function generation from jsonp ajax-requests now contains underscores (‘_’), so you have to adapt your save patterns on server side

Related sites:

• My Matterhorn Branch Issue Tracker for the migration
• jQuery Blog: jQuery 1.6 search results
• David Tong – Upgrading jQuery – from 1.4.x to 1.6.x

To be continued…

• macports
• The following installed macports:
  • git-core
  • cmake
  • libtool
  • libusb-devel

After installing the autocomplete into .emacs.d I inserted the following lines into my .emacs-file to enable it:

;; add .emacs.d to load path
(add-to-list 'load-path "~/.emacs.d")

;; enable autocomplete
(require 'auto-complete-config)
(add-to-list 'ac-dictionary-directories "~/.emacs.d/ac-dict")
(ac-config-default)
(global-auto-complete-mode t)
(auto-complete-mode t)

To get a lisp-specific autocomplete you’ve got to include ac-slime (found at github): put it into your .emacs.d-folder and include it in your .emacs-file via

;; add lisp autocomplete-support
(require 'ac-slime)
(add-hook 'slime-mode-hook 'set-up-slime-ac)

and to switch on autocomplete globally you have to apply a “dirty fix”:

;; dirty fix for having AC everywhere
(define-globalized-minor-mode real-global-auto-complete-mode
  auto-complete-mode (lambda ()
                       (if (not (minibufferp (current-buffer)))
                         (auto-complete-mode 1))))
(real-global-auto-complete-mode t)

Now only one thing is missing: the mentioned inserting of new words on the fly:

;; create and add new words to the dictionary on the fly
(when (require 'auto-complete-config nil 'noerror)
(add-to-list 'ac-dictionary-directories "~/.emacs.d/ac-dict")
  (setq ac-comphist-file  "~/.emacs.d/ac-comphist.dat")
  (ac-config-default))

• the “Ns Command Modifier” -> “meta” and
• the “Ns Alternate Modifier” -> “No modifier“.

Now you can use your alt and meta-keys as usual.

Second I did not remember immediately how to set my previous colors and styles (e.g. the background color or the mouse color) so I will sum up my solution:

• open your “~/.emacs“
• type in (and replace my colors with your own)

(setq default-frame-alist
    (append default-frame-alist
        '((foreground-color . "LawnGreen")
          (background-color . "Black")
          (cursor-color . "LawnGreen"))))

And of course Emacs is much better than vim!

But let’s start now. I want to demonstrate how easy it is to create a simple timetable with SQLite that looks something like this if you wrap it into a GUI:

Here are the includes:

#include <QTableView>
#include <QSqlDriver>
#include <QSqlDatabase>
#include <QSqlQuery>
#include <QSqlTableModel>
// #include <QSqlError>

At first, create the database using SQLite via

QSqlDatabase db = QSqlDatabase::addDatabase("QSQLITE");
db.setDatabaseName("databaseName");

Then open it (and check it meanwhile) with

if(!db.open()) {
   exit(0); // or do something else
}

Now insert the table using a SQL query:

QSqlQuery query;
query.exec("CREATE TABLE IF NOT EXISTS tableName ("
           "monday varchar(200), "
           "tuesday varchar(200), "
           "wednesday varchar(200), "
           "thursday varchar(200), "
           "friday varchar(200), "
           "saturday varchar(200), "
           "sunday varchar(200))");

After that create a model:

QSqlTableModel model;
model.setTable("tableName");
model.setEditStrategy(QSqlTableModel::OnManualSubmit);

If you choose “OnManualSubmit” as edit strategy you have to save the changes you make inside the model by your own (explanation comes later).
Then set the model header data (Monday-Sunday in the picture):

model.setHeaderData(0, Qt::Horizontal, "Monday");
model.setHeaderData(1, Qt::Horizontal, "Tuesday");
model.setHeaderData(2, Qt::Horizontal, "Wednesday");
model.setHeaderData(3, Qt::Horizontal, "Thursday");
model.setHeaderData(4, Qt::Horizontal, "Friday");
model.setHeaderData(5, Qt::Horizontal, "Saturday");
model.setHeaderData(6, Qt::Horizontal, "Sunday");

and set the model to the view to display it:

model.select();
QTableView view;
view.setModel(model);

But what if you want to add an additional line with an entry in every row? The best news is that you don’t have to write any SQL for adding or deleting if you don’t want to:

int rowCnt = model.rowCount();
model.insertRow(rowCnt);
for(int i = 0; i < model.columnCount(); i++) {
   model.setData(model.index(rowCnt, i), "Put this Entry in every Row");
}
model.submitAll();
model.select();
view.setModel(model);

And if you want to delete the last row:

model.removeRow(model.rowCount() - 1);
model.submitAll();
model.select();
view.setModel(model);

You have to call “submitAll” because of the selected strategy ”OnManualSubmit” that doesn’t save by it’s own.
To clear the whole database, drop the table by querying

query.exec("DROP TABLE IF EXISTS tableName");

After setting up a model and a view you can change your table inside the view, press “save” and everything else is “done by Qt”!

You can find the whole Application at CallToPower – Software – qTimeTable, have fun experimenting with it!

Icon icon;
Image image;
ClassLoader CLDR = this.getClass().getClassLoader();
String path = "src/to/images/name.png";
URL url = CLDR.getResource(path);
// An icon
if (!(url == null)) {
    icon = new ImageIcon(url);
}
// An image
try {
    image = ImageIO.read(CLDR.getResource(path));
} catch (IOException e) {
    // ExceptionHandling here
}

In Qt there is another approach:
The resources associated with an application are specified in a XML-based .qrc-file.
The specified paths are relative to the directory containing the .qrc-file (listed files must be located in the same directory or any sub-directory).
In the source-code the resources are accessible under the same name they have in the source tree, with a “:/” prefix.
Here an example:

<RCC>
    <qresource prefix="/dir/subDir" lang="en">
        <file alias="AliasName">subDir/FileName<file>
    <qresource>
</RCC>

In your source code you can access FileName (if FileName e.g. is a QFile) via

QFile file(":/dir/subdir/AliasName");

after adding the following line to your .pro-file:

RESOURCES = yourRsrcFileName.qrc

The option lang=”langCode” (here: “en”) is for the localization:
If you want to add another language to your application you have to have the file “AliasName_langCode” in your source tree.

And, of course, you don’t have to write the ressource file on your own if you use the QtCreator, there is a nice GUI included.

1. Create a project.

2. Right-click at the project-name and select “Get Info”

3. Set the “Header Search Paths” to the Folder you unzipped the library (here: “/Developer/Tools/boost”)

4. Ready to boost.

Thanks to Superlevel for the Idea!

repeat
	tell application "iChat"
		set the status message to "Status 1"
		delay (1)
		set the status message to "Status 2"
		delay (1)
	end tell
end repeat

And a similar Script for Adium:

[Applescript-editor-formatted image]

[Text]

repeat
	tell application "Adium"
		repeat with theAccount in accounts
			go away theAccount with message "Currently away..."
		end repeat
		delay (2.0)
		repeat with theAccount in accounts
			go away theAccount with message "...back in 10 minutes."
		end repeat
		delay (2.0)
	end tell
end repeat

1. Ask for finder-items
2. Combine PDF pages
3. Move Finder Items

- Update 11.10.2009 -
Created a sub-site named Automator-workflows at www.calltopower.de/automatorworkflows where you can see screenshots of the workflows and/or download the workflows and/or programs. I created among other things “Save Pictures from the current website”, “Take screenshot”, “Take image from webcam (iSight or other)”, “Pictures to PDF”, “Images to PDF”.