Install the java plugin in firefox

To install the Next-Generation Java plugin in firefox follow the instructions below which is a summary of this article. If you have been using the classic plugin, see the Notes for further information.

  1. Check if you’re using the 32-bit firefox. Select the menu item Help -> About Mozilla Firefox. At the bottom of the window is a version string line that contains either “Linux i686″ (32-bit) or “Linux x86_64″ (64-bit). If you use the 64-bit version have a look at this blog post else continue.
  2. Exit Firefox.
  3. Change to ~/.mozilla/plugins or to another firefox plugins directory.
  4. Remove all symlinks (or move them to another directory).
  5. Create a symlink for the 32-bit plugin. Execute one of the following lines
    ln -s ${JRE_HOME}/lib/i386/libnpjp2.so
    ln -s ${JAVA_HOME}/jre/lib/i386/libnpjp2.so

    depending on what environment variable you have set. If you don’t know where your java is located find it out with which java or locate java

  6. Start firefox.
  7. Type about:plugins in your location bar to confirm that the java plugin is loaded.
DeliciousDiggTechnorati FavoritesRedditLinkedInFacebookSpurlTwitterWebnewsYiGGMySpaceYahoo BookmarksFriendFeedGoogle BookmarksLiveJournalShare

What’s Erviz?

Note
I’m in the process of forking Erviz. The fork is almost done. The Linux packages are prepared and almost ready to be submitted. (27. Sep 03:47 UTC)
————————

Erviz, written by Mitsuru Kono, is a tool that makes it easy to create entity-relation models and the best thing it’s free!

You can run it on Windows, Linux and Mac but for the latter a patch is required which will be discussed later on this page.

Creating the entity-relation diagram

Only these two steps have to be followed:

  1. Create a text file and define all your entities and relationships. The syntax is simple as example shows:

    # Using Erviz 1.0.6
    {title: "Syn2Stock ERD V3"; title-size: 20}
    
    # Entities
    
    [Item] {color:red}
     *Item ID
      Type
      SimpleItem
      Bar Code
      Name
      Amount
      Owner
      Comment
      Attachments
      Sources
      Source ID*
      Location ID*
      Lending ID*
    
    [Source]
     *Source ID
      Price
      Homepage
      Manufacturer
    
    [Location]
     *Location ID
      GPS Coordinates
      Name
      Room
      Locker
    
    [Lending]
     *Lending ID
      Borrowed by
      Borrowed on
      Returned on
      Reminder ID*
    
    [Reminder]
     *Reminder ID
      Start Date
      Repeat Interval
      End Date
      Active
      Action
      Email
      Phone
      Message
      Item ID*
      Lending ID*
    
    [Event]
      *Event ID
      Event Type
      Date
      User
      Item ID*
    
    [Attachment]
     *Attachment ID
      File
      External URL
      Private
    
    [Electronic Part] {color:orange}
     *Electronic Part ID
      Value
      Item ID*
    
    [Book] {color:orange}
     *Book ID
      Subtitle
      Author
      Publisher
      Paperback
      Language
      Review
      Summary
      About the Author
      Item ID*
    
    # Relationships
    [Item] *--* [Source]
    [Item] 1--1 [Location]
    [Item] 1--* [Lending]
    [Item] *--* [Attachment]
    [Reminder] ---- [Item]
    [Event] *--1 [Item] <contains ->
    [Electronic Part] ---- [Item] <is a->
    [Book] ---- [Item] </is><is a->
    </is></contains>
    
  2. Then turn the text file into the ERD image by calling the convert-files script.

Continue reading »

DeliciousDiggTechnorati FavoritesRedditLinkedInFacebookSpurlTwitterWebnewsYiGGMySpaceYahoo BookmarksFriendFeedGoogle BookmarksLiveJournalShare

Adding unsupported file extensions to QuickLook

Some file extensions were still not supported by my QuickLook. If I must edit configuration files I don’t need a preview, I open them directly in my text editor. So maybe that’s the reason why I still didn’t add their support. Anyway today I only wanted to have a quick look into some configuration files, thus I followed the steps of this tutorial by moondark. In my case I added the following UTExportedTypeDeclarations section to TextWrangler’s Info.plist.

    <key>UTExportedTypeDeclarations</key>
	<array>
	<dict>
	  <key>UTTypeConformsTo</key>
	  <array>
		<string>public.text</string>
        <string>public.plain-text</string>
	  </array>
	  <key>UTTypeDescription</key>
	  <string>Plain text file</string>
	  <key>UTTypeIdentifier</key>
	  <string>com.barebones.textwrangler</string>
	  <key>UTTypeTagSpecification</key>
	  <dict>
		<key>com.apple.ostype</key>
		<string>TEXT</string>
		<key>public.filename-extension</key>
		<array>
		  <string>conf</string>
          <string>ini</string>
          <string>bak</string>
          <string>types</string>
		</array>
	  </dict>
	</dict>
	</array>

DeliciousDiggTechnorati FavoritesRedditLinkedInFacebookSpurlTwitterWebnewsYiGGMySpaceYahoo BookmarksFriendFeedGoogle BookmarksLiveJournalShare

Change permantly Terminal’s style for new windows

I have configured Terminal’s style as Homebrew but it’s only used for the first window if Terminal is launched. If I type the shortcut Command+N the new window has the basic style which I don’t like, it’s just white so not really stylish. I knew that defaults exist to modify an application’s settings using a shell.

defaults read com.apple.Terminal

If you type this in your shell you get the settings set for your application, in my case for Terminal. I was interested in the entry “Default Window Settings”. The value of this key was Basic though I have explicity set it to Homebrew in the configuration panel.

defaults write com.apple.Terminal "Default Window Settings" Homebrew

This line affects the style permantly. Restart Terminal to read the new settings and enjoy the new style.

DeliciousDiggTechnorati FavoritesRedditLinkedInFacebookSpurlTwitterWebnewsYiGGMySpaceYahoo BookmarksFriendFeedGoogle BookmarksLiveJournalShare

How to find the profile picture made by Adium?

This was a good question as I looked for it yesterday. Some research on the net gave me the answer. Adium stores the picture as an inline image in a .plist file. So go to ~/Library/Application Support/Adium 2.0/Users/Default and open the file Account Status.plist. In the data section you find the inline picture. Create a new html file with the content

<img src="data:image/png;base64,">

Now copy the content of the data section (without the data tags) and paste it behind base64,. Open the html file in the browser1 and save the picture on your disk. That’s it.

  1. The browser just supports a certain content length for inline images. Try another browser if the picture is not fully displayed. Firefox supports up to 100K
DeliciousDiggTechnorati FavoritesRedditLinkedInFacebookSpurlTwitterWebnewsYiGGMySpaceYahoo BookmarksFriendFeedGoogle BookmarksLiveJournalShare