Samstag, 9. Juni 2007

LiveHttpHeaders patch for german Mac

Eine meiner oft genutzten FireFox-Erweiterungen LiveHttpHeaders (http://livehttpheaders.mozdev.org/) hatte bisher unter meinem MacBook immer folgende Einschränkung:
Will man in einem WebFormluar eine Email-Adresse eingeben, führt das Drücken von “alt+L” zum eingeben des “@” dazu, das die LiveHttpHeaders-Sidebar aufgeht. Man kann also entweder Email-Adressen eingeben oder LiveHttpHeaders
verwenden.

Das ist doof.

Ich habe nun folgendes getan:

In der Datei : TasksOverlay.xul (zu finden im /Users/USERNAME/Library/Application Support/FireFox/Profiles/xxxxxx.default/extentions/{xxxx}/chrome/liveHttpHeaders.jar) das Element

id=”key_viewLiveHTTPSidebar” key=”L” command=”viewLiveHTTPSidebar”
modifiers=”alt”

den key auf “H” geändert.

Das Ergebnis:

Nun öffnet “alt+H” die LiveHttpHeaders-Sidebar und “alt+L” schreibt wie gewohnt das @ :)

Hier das gepatchete liveHttpHeaders.jar

Muss nach /Users/USERNAME/Library/Application Support/FireFox/Profiles/xxxxxx.default/extentions/{xxxx}/chrome/ kopiert werden

Mittwoch, 6. Juni 2007

Project Set Files and Eclipse Preference FIles

Working in a collabrative development environment presents some challenges. Once you have your source control approach ironed out and working you still have the problem of keeping every one's IDE in sync in terms of option settings.

Luckily the Eclipse platform, and WebSphere Studio Application Developer (WSAD) which inherits from Eclipse, provides two mechanisms for assiting a team of developers who wish to keep their individual environments in sync with each other. The first is project team sets and the second, eclipse preference files.

Team Project Sets (PSF) Project team sets, or PSF files, allow you to capture the setup and contents of a workspace to allow sharing with other team members. This tool is dependent upon the use of a centralized source control system such as CVS, ClearCase, or Subversion. Since the resources inside a project under version control are kept in the repository, it is possible to share projects with team members by sharing a reference to the repository specific information needed to reconstruct a project in the workspace. This is done using a special type of file export for team project sets.

Once you have the project setup properly in one workspace, you select the project and export it as a Team Project Set. Other team members can then use this PSF file to construct their workspaces.

Eclipse Preference File (EPF) The other area that can cause multiple developers working against shared source difficulties is IDE preferences. For example in WSAD with Rational XDE integration there is a code generation tool that can keep the Java code model in sync with the UML model and vice-versa. If one team member has auto-sync turned on and another team member doesn't inconsistencies in the model and source will rapidly result. Considerable time will be lost has effort will have to be expended to untangle the two views of the project.

By establishing a set of preferences and exporting them as a EPF file, and sharing that file will all team members it is possible to avoid at least some of the problems resulting from different IDE preference settings.