Da ich mittlerweile Podcastsüchtig bin, muss ich da natürlich mitmachen um schneller an neuen Stoff zu kommen.

Aus diesem Anlass hier meine persönlichen Podcastcharts:

1. Not Safe For Work
2. Chaosradio Express (und auch das normale Chaosradio)
3. Bits und so (Plus natürlich)
4. Mobilemacs
5. dieGesellschafter
6. Java Posse
7. Medienradio
8. Linux Outlaws
9. Games und so
10. Küchenradio

Ich muss sagen, dass ich die NSFW-Podcasts noch besser als die Chaosradio Folgen finde. Zielloses Rumgelaber zwischen Holgi und Tim sind einfach unschlagbar.

Die CRE-Podcasts sind da natürlich deutlich informativer. Mir gefällt besonders die Mischung aus sehr techniknahen und ehr sozialen Themen.

Hier geht’s zum vorherigen Blog und hier zum nächsten.

First Try. Got the clipping slightly wrong…

After a quick fix, clipping correct, but no text…

Changing to another theme…

… the text is there!

Menu is workin.

Setting some dialog properties, and…

… displaying it.

Some more screenshots…

Performance is slow as hell, not all graphics are rendered properly, but its working at least.

iPhone Cydia Packages are Debian .deb files really and luckily there is the mvn-pkg-plugin that supports creating .deb files with Maven2. Unfortunatly the current version has a bug, so that it won’t work out of the box for creating iPhone packages. So you have to grab the latest svn-snapshot and apply the following patch.

Index: src/main/java/de/tarent/maven/plugins/pkg/map/Parser.java
===================================================================
--- src/main/java/de/tarent/maven/plugins/pkg/map/Parser.java	(revision 132)
+++ src/main/java/de/tarent/maven/plugins/pkg/map/Parser.java	(working copy)
@@ -62,7 +62,7 @@
 
       if (auxMapDocument != null)
         {
-          s = new State(packageMapDocument);
+          s = new State(auxMapDocument);
 
           s.nextMatch("package-maps");
           parsePackageMaps(s);

After applying the atch and doing a “mvn install”, we can start with the real work. Download the tutorial files from here. I will explain the contents of the archive later. For now unzip it and do a “mvn package” in its directory. It will compain about some missing dependencies, so grab the missing jars from your iPhone and install them in your Maven reposiory as directed in the error message. After you have done that another “mvn package” shoud produce a .deb file in the target subdirectory. You can upload this to your iphone and install it with dpkg. After a restart of the SpringBoard a new icon HelloMaven should be on your screen, that should start the demo program.

Now some explanation of how it works. The main part is done in the pom.xml. Here is the relavant excerpt form this file:

<plugin>
	<groupId>de.tarent.maven.plugins</groupId>
	<artifactId>maven-pkg-plugin</artifactId>
	<configuration>
		<defaultDistro>iphoneos</defaultDistro>
		<shortDescription>Arindal Tune Helper</shortDescription>
		<defaults>
			<mainClass>HelloJava</mainClass>
			<section>example</section>
			<architecture>iphoneos-arm</architecture>
			<datadir>/Applications/HelloMaven.app
			</datadir>
			<dataFiles>
				<dataFile>
					<from>Info.plist</from>
				</dataFile>
				<dataFile>
					<from>icon.png</from>
				</dataFile>
				<dataFile>
					<from>Starter</from>
				</dataFile>
			</dataFiles>
			<postinstScript>postInst.sh</postinstScript>
			<prermScript>preRm.sh</prermScript>
		</defaults>
		<auxPackageMapURL>file:${basedir}/pm-iphoneos.xml
		</auxPackageMapURL>
	</configuration>
	<executions>
		<execution>
			<phase>package</phase>
			<goals>
				<goal>pkg</goal>
			</goals>
		</execution>
	</executions>
</plugin>

The first important part is the defaultDistro tag. Here we tell the plugin, that we want to build a package for the iPhone. Unfortunatly there are no default iPhone mappings contained in the plugin. That is why we have the auxPackageMapURL tag, that tells the plugin where to look for the Maven-to-Cydia-Package-Mapping. Most other things should be pretty self explaining.

The files in the dataFiles Section have to reside in src/main/auxfiles icon.png and Info.plist should be pretty clear. The Starter entry needs some explanation though. The plugin automatically generates a start script in /usr/bin. This is good enough for console applications, but if you want to start a GUI-App some more work is needed. The Starter script sets the Java executable path to /Applications/Appname.app/Java and calls the generated script after that. For this to work the starter Script has to get executable permissions and jamvm has to be linked to /Applications/Appname.app/Java. This is done in the postInst.sh script. For more info about those scripts and what you can do there refer to the Debian documentation.

This should be enough to get you started, if cou have questions, please feel free to post them in the comments.

Its pretty easy to install Wordpress 2.5 on Ubuntu Intrepid. The Ubuntu version comes with Multiblog capabilities included. There is an example script (/usr/share/doc/wordpress/examples/setup-mysql) to create new instances of Wordpress Blogs. Unfortunatly the script was copied from Debian and some paths are wrong for Ubuntu. The script below fixes that issue. After that it worked flawlessly for me with wordpress-2.5.1-2ubuntu1.

82,83c82,83
< [ -d /srv/www ] || mkdir -p /srv/www
< ln -s /usr/share/wordpress /srv/www/$DOMAIN
---
> [ -d /var/www ] || mkdir -p /var/www
> ln -s /usr/share/wordpress /var/www/$DOMAIN
149c149
< UPLOAD="/srv/www/wp-uploads/$DOMAIN"
---
> UPLOAD="/var/www/wp-uploads/$DOMAIN"
181a182
>

Here is my result:

Patch: phoneme-cdc-darwin-x86

Binary: phoneme-cdc-personal-darwin-x86-qt3-x11-bin

Copy the files from the Patch-Archive into the correct folders of the phoneME sources. You can build the Foundation-Profile with “make”in the directory cdc/build/darwin-x86-mac and with “make J2ME_CLASSLIB=personal” the Personal-Profile. You need QT3 for the Personal-Profile. Install that with Fink.

You can try out the resulting VM with “bin/cvm -jar democlasses.jar”.

Ich benutze es zwar bisher nur für 2 Blogs(markus.heberling.net und sebastian.heberling.net), aber auch das ist schon eine Erleichterung.

Es gibt aber Dinge auf die man achten sollte:

• Das Permalink format sollte auf allen Blogs gleich sein, da sonst die .htaccess Dateien nicht passen
• Das Google XML Sitemap Plugin muss man so konfigurieren, dass es für die verschiedenen Blogs verschiedene sitemaps generiert
• Man sollte die Upload-Verzeichnisse trennen, damit jedes Blog sein eigenes hat

Ansonsten sind mir bisher keine Probleme aufgefallen.

Achtung, nix für zartbesaitete!

read more | digg story