JP'zlog

Aller au contenu | Aller au menu | Aller à la recherche

mardi 15 mai 2007

Last post! / Dernier post !

English

The new location is at http://jpz-log.info/! Thanks for updating your bookmarks!

See you soon at the new JPz'log.

Français

Le nouvel emplacement est http://jpz-log.info/ ! Merci de mettre à jour vos listes de favoris !

A très bientôt sur le nouveau JPz'log.

lundi 14 mai 2007

Look and feels updates

I have just checked into to the Subversion trunk a few updates regarding the IzPack 3rd-party Swing look and feels support.

  1. Liquid and JGoodies Looks have been updated to their latest versions.
  2. Support has been added for the Toned-down Substance look and feel themes. The restriction to this themes family is due to the fact that the other families are either too dark ... or way too saturated[1] :-)

To use this new look and feel, here an extract of what you can put in your installer specification:

 <guiprefs height="600" resizable="yes" width="800">
     <laf name="substance" >
         <os family="unix"/>
         <param name="variant" value="moderate"/>
    </laf>
    (...)
 </guiprefs>

In this case, Substance will be used on Unix-like systems with the moderate theme.

You can already test those changes by checking out the current development version!

Notes

[1] I know Romain will agree with me!

vendredi 11 mai 2007

New release: IzPack 3.10.2

I am pleased to announce the release of the IzPack 3.10.2 Java installer generator. This is maintenance release which brings fixes.

Here is the full changelog:

  • Vista/Java6 fixes (Stefan Wachter via Julien Ponge)
  • Dutch Langpack fixes (Hans Aikema)
  • Fix NPE for pack.id == null in dependencies/excludes (Hans Aikema)
  • Indonesian Langpack fixes (Thomas Santosa via Hans Aikema)
  • UserInputPanel and InstallerFrame: enable the next button for search dialogs (Michael Hagedorn via Julien Ponge)
  • VariableSubstitutor: new Java source files support (Max Fedorov via Julien Ponge)
  • French langpack updates (Loic, via Julien Ponge)
  • Documentation update (Scott Plante via Julien Ponge)
  • AutomatedUninstaller.writeUninstallData() out of sync with InstallerFrame fixed (Marius Nicolae via Marc Eppelmann)

It can be downloaded from:

Many thanks to the contributors and developers who have made this release possible!

mercredi 9 mai 2007

OpenJDK is go!

The Sun JDK is now completely available under the GPL from http://openjdk.java.net/, at the exception of a few modules (font rendering and audio I think) which are distributed as blobs.

This is now the end of endless stupid flamewars against Java being unpure and not free... or even evil :-)

I am myself very happy by this complete release of the code base. I confess I was even a hard Sun-basher when they were still against the Java opensource move. My main complain was mainly the one of portability across more than the Sun-blessed platforms. I remember myself compiling the JDK on FreeBSD, having to register to download the source code from Sun under the SCCL license, then have a huge patch being applied and come back the next morning for the JDK to be installed :-) There are also many people out there running other hardware/os combinations than Windows, Linux/Intel-AMD or Mac OS X, so this move will make it even more true to say that Java actually is a universal runtime platform.

Many thanks to Sun for this move ... and thanks also to them for their overall HUGE contribution to the opensource ecosystem (think OpenOffice.org, OpenSolaris, ZFS, ...).

mardi 8 mai 2007

Ohloh.net metrics

Dennis Reil has registered IzPack on Ohloh.net, a funny website offering automated metrics on open source projects.

In a nutshell:

  • 14 Person Years
  • $773,016.

IzPack 3.10.2 to be released this friday

The next maintenance release of the IzPack Java installer is planned for this friday. This will probably the last one of the 3.10 stable branch as we should then focus of 3.11.

mardi 1 mai 2007

Exporting a DotClear v1 blog to static HTML files

Planning the migration of this blog to a new location[1], I have implemented a quick Ruby script to extract the content to static HTML files. The script is relatively small and uses ERB for the pages templates (like Ruby on Rails).

You can download it from http://www.izforge.com/dotclear2static/, it's under a MIT-style license (hence take it, fix it, scratch it, trash it, upgrade it).

This Ruby script extracts the posts from a Dotclear v1.x blog MySQL database. This is useful when you want to migrate to another blogging system without going through the hassles of making an import. Indeed, the import from Dotclear to, say WordPress, is a boring task.

Requirements:

  • A MySQL database.
  • Ruby
  • Ruby/MySQL from http://www.tmtm.org/en/ruby/mysql/

Making a successful export:

  1. Obtain a database backup of your live DotClear blog.
  2. Import the database backup into your MySQL database. I suggest that you perform the extraction from a local database rather than from the real one, but that's up to you in the end of the day ;-)
  3. Open 'dotclear2static.rb' and change the settings that are available under the license text. Make sure that you enter the right settings for MySQL!
  4. Run 'dotclear2static.rb' ... and tada! You've got your static files!
  5. Don't forget to copy the Dotclear images folder to the output directory.

Making the transition : it would be stupid to loose your pagerank! Remember that "cool URIs don't change". My advice is that you:

  • move your new blog to a new URL (say http://newblog.info/)
  • move the static files from the old blog to a subfolder of the new URL (say http://newblog.info/old)
  • put 301 redirections from the old location to the new URL (ex: http://newblog.info/old).

301 redirections can be set from a '.htaccess' file for the Apache HTTPD server. Please consult Apache documentations if you don't know how to do that...

Tip: the static filenames are of the form 'postnumber-titleurl.html', hence: you can redirect

http://oldblog.info/index.php/year/month/day/<post>

to

http://newblog.info/old/<post>.html

I'll put my htaccess files the day I make the transition to the new blog.

Edit: of course you should use HTTP 301 for redirections, not 403 :-)

Notes

[1] Who will be smart enough to guess the URL? :-)