Problemstilling

Nogen gange kan det være svært at få resten af verden til at forstå, at Internet Explorer ikke er den eneste browser. TDC var en af de tungnemme, da de blev sat på opgaven. Mac brugere oplever ofte at få beskeden "Vi understøtter ikke Mac med digital signatur". Det er dog ikke helt sandheden, da de fleste offentlige institutter rent faktisk godtager det, hvis man installerer den korrekt. Som regel virker det, hvis den installeres i Firefox, men det er dog ikke altid. Installering i ens Keychain er desværre ikke nok til, at det fungerer i Safari.

Løsningen er dog enkel... Når signaturen placeres korrekt på maskinen kan de fleste signatur Java applets finde signaturen uden problemer, og man behøver derfor ikke at trykke "Gennemse..", hvilket i nogen tilfælde heller ikke er muligt (eksmepelvis på dele af personregistrering.dk).

Fremgangsmåde

Åbn din signatur i Safari (f.eks. Digital Signatur for Jens Jensen.html).

Tryk på Gem Digital Signatur knappen, Tryk OK til Advarslen om formatet. En dialog om placering kommer op.

Tryk herefter CMD+Shift+G. En dialog om sti kommer op.

Tast: ~/.oces og tryk enter.

Tryk enter for at bekræfte placeringen i denne særlige mappe.

Færdig. Fremover skulle det se nogenlunde sådan ud:

I've managed to get most of the functionality you would expect from a regular mac program working and have now decided to release an alpha version for any testers that might want to get their hands dirty

Here's the changelog and features:

• Initial release
• Support for drag and drop onto the dock icon
• Support for Open With for files that are associated with jEdit
• Application menu integration
  • "Preferences" will open Global Preferences
  • "About jEdit" will open the Help -> About jEdit... dialog
• CMD-click in titlebar now displays the current buffer path in a drop down. Clicking on a folder will reveal that folder in the finder.
• The red close button now indicates the entire view's modification status. This way it will be consistent with the "save modified buffers?" dialog.

Kris (the original author of the mac plugin) is not completely without credit on this one since I used his plugin as a reference of what needed to be done.

Download plugin

Please give your comments

Apple recently released Java 6 SE through a Java update. With the release of Java 6 Mac users can now enjoy better OS X integration besides the many other improvements in Java 6.

Using Java 6 as the default JVM has implications with a standard jEdit installation on Mac. But the solution is simple...

Being a jEdit user I was eager to try out the new JVM version to see if there were any general improvements.

Since Mac users has gone long without proper OS integration, one jEdit developer (Kris Kopicki) decided to fix this with a Mac OS X plugin that included many small improvements.

With the new update Apple has completely removed the cocoa API (packages in com.apple.cocoa). The result: jEdit will fail to start with Java 6 SE.

jEdit will simply "bounce" once and then quit. This is caused by a fatal exception during startup.

The fix is simple: Remove the Mac OS X plugin.

With the improved cocoa/mac support many of the features in the plugin are unncessesary. Key-mappings are improved to use the CMD-buttons in all textareas and the menubar is now moved to the actual Mac menubar.

How to remove the plugin:

• Right click/CTRL+click the jEdit application icon
• Choose "Show Package Contents"
• Go to the Contents/Java/jars folder
• Delete the MacOS.jar file (you may need to authenticate to do this)

Launching jEdit with Java 6 SE should now be possible. Alternatively to setting Java 6 SE as your standard JVM you can set the Contents/Info.plist file property: "Root/Java/JVMVersion" to "1.6+" instead of "1.5+". Either way should work.

This is a draft of the final icon. The final icon will have modified shadows.

• Preview of the icon
• Download icon for Mac OS X

Update: The icon is now available with correct shadows for Mac OS X

Installing Firefox 3.0 I stumbled upon an article that described this exact problem and had a solution! Oh joy!

The solution

The fix the issue, apply the CSS 3 property, opacity, to the body tag, and set it to 0.99999. I recommend using the -moz-opacity attribute, which is standards compliant and only affects mozilla-based browsers like this:


body { -moz-opacity: .99999; }


But please read the rest of the article since there might be a few side effects. The fix should only be applied when the user agent reports to be Firefox 2 on Mac.