In the hardware maintenance manual from Lenovo for the T61, it says on page 166, that a WUXGA panel is a CTO part. Which means Configure To Order:

This provides the ability for a customer to configure an IBM® or a LenovoTM solution from an eSite, and have this configuration sent to fulfillment, where it is built and shipped directly to the customer.

I read on different sites on the internet that the Samsung panel had a lot of backlight bleeding too, so I opted for the LG panel (FRU 42T0361).

Unfortunately, because of the tsunami in Japan, these screen were hard to get. So I called IBM and asked them to send me an offer for the LG panel. Those were not in stock, but they had an alternative screen for the T61 (newer he said), with FRU 45N3310.
It’s price was too high: More than 300 euros. My is T61 is too old for that (sorry T61).

So I decided to take the plunge and ordered a new screen on Ebay. I ended up here, and ordered a 42T0361.

After a week or so, I received a 42T0613. According to this site, it’s for the (T|W)500, not T61. The 42T0613 is a LG panel as well, just like the 42T0361.

I followed this online guide: http://www.computer-adviser.com/ibm-t61-screen-replacement.html to replace my screen.
It took me 2 hours and a lot of sweat, especially for the bezel.

The screen is fitted, and I can say now that it is MUCH better (regarding to backlight bleeding) than my old screen.

So your options are for WUXGA (excluding the Samsung panel):

• 42T0361 (according to the hw maintenance manual)
• 42T0613 (according to me)
• 45N3310 (according to IBM)

• Clicking the icon shows you all the possible brightness values.
• The current value is indicated with a dot.
• Clicking a menu item sets the brightness to the desired value.
• Scroll wheel event is enabled on the icon. Scrolling up means lower brightness, scrolling down higher.

Download (for 11.04): indicator-brightness-0.0.2_all.deb
Download (for 11.10): indicator-brightness-0.0.2_all-oneiric.deb
Please let me know if the Oneiric version is OK or not.

• Max brightness steps: 15, for people who have more than 15 steps in their brightness settings. (Suggested by Tom)
• Min brightness step: 0. (Suggested by Jeff)

Download: indicator-brightness-maxsteps.py

To test it, you can start it from the command line with:
python indicator-brightness-maxsteps.py
Control-C will stop it.

Please let me know if this script works, so I can make a new deb file.

After installing the package, add the program to your startup programs:
Run System Settings » Startup Applications » ‘Add’

You may need to run chmod +x /opt/indicator-brightness/indicator-brightness.py in a terminal to make the script executable if nothing happens.
Sorry for the inconvenience, but still looking for a way to make a better deb file.

Screenshot:

Versions:
0.0.1 Initial (downloads: 549)
0.0.2 Fixed bug when indicator is not able to detect max brightness (downloads: 3314)
0.0.2-oneiric Ubuntu 11.10 replaced gnome-power-backlight-helper with gsd-backlight-helper (downloads: 3340)

DEB created with Easy DEB/RPM creator

De oorspronkelijke bron voor alle streams in dit bestand:
http://linux.softpedia.com/progDownload/Dutch-Radios-Download-55355.html

1. Sluit Rhythmbox af.
2. In Ubuntu open je het bestand ~/.local/share/rhythmbox/rhythmdb.xml
   De lokatie van dit bestand kan verschillen per systeem.
3. Voeg het gedownloade bestand toe aan rhythmdb.xml. Zorg dat het bestand onder een andere <entry> tag komt te staan (dus sibling).
4. Start Rhythmbox. Klik op “Radio”.

Alle stations moeten nu verschijnen.

Tot ziens … misschien bij de volgende app



Sinds december vorig jaar heb ik een Samsung Galaxy S met een abonnement bij Hi.
Helaas bestond er voor Hi geen Android app om je belstatus te kunnen bekijken.
Daarom heb ik er één geschreven, en ik hoop dat jullie er ook wat aan hebben.

Graag hoor ik wat jullie er van vinden.
Beter nog: Meldt in deze blog de fouten die je ongetwijfeld tegen gaat komen.
Of eventuele toevoegingen aan de app die je graag zou willen zien.

Features
Versie 1.2.3:

• App werkt nu ook voor mensen met 1 abonnement
• SDK version 9 bovenlimiet verwijderd

Versie 1.2.2:

• Op verzoek Toast notificaties als update vanaf menu gedaan wordt
• Interval wordt afgerond op dichtsbijzijnde kwartier/halfuur/uur

Versie 1.2.1:

• Op verzoek belstatus ook in het applicatie scherm weergeven
• Look-and-feel gewijzigd. Ja, ik heb uitgevonden hoe je afgeronde achtergronden kan maken, en dat zullen jullie weten ook

Versie 1.2:

• Interface aangepast
• Belstatus op widget is nu groter
• Widget heeft nu volledige 4×2 afmeting
• Voorkeur om automatische updates ‘s nachts of altijd uit of altijd aan te zetten
• Belbundel en internetbundel worden op widget weergegeven

Versie 1.1.1:

• Fixed FC na het terugkeren uit het menu

Versie 1.1:

• Ophalen updates werkt nu ook in slaapstand betrouwbaar.
• Verwacht resterend beltegoed wordt weergegeven in de widget
• Updaten status veranderd in interval
• Notificaties weergeven ja/nee
• Opgeven welke dag van de maad het beltegoed wordt opgewaardeerd. Dit om het verwachte resterende beltegoed te kunnen berekenen.

Versie 1.0:

• Automatische updates naar eigen smaak aan te passen
• Handmatig updaten van status.
• Widget, met de volgende info:
  • Je resterende beltegoed
  • Verbruik boven bundel
  • Verbruik dat niet in de bundel zit
  • Welke belbundel je hebt
  • Welke internetbundel je hebt

Screenshots

Versies
Hi beltegoed – 1.2.3
Hi-belstatus – 1.2.2
Hi belstatus – 1.2.1
Hi belstatus – 1.2
Hi belstatus – 1.1.1
Hi belstatus – 1.1
Hi belstatus – 1.0

First, define an interface:

public interface MyExampleMBean {
	public Integer getParam();
	public void setParam(Integer param);
	public String doSomething();
}

Second, implement the interface in a concrete class:

@Service(objectName = "example-mbean:service=MyExampleMBean", 
	name = "MyExampleMBean")
@Management(MyExampleMBean.class)
public class MyExample implements MyExampleMBean {
 
	private Integer param;
 
	public Integer getParam() {
		return this.param;
	}
 
	public void setParam(Integer param) {
		this.param = param;
	}
 
	public String doSomething() {
		return "Param=" + this.param;
	}
}

@Service and @Management are JBoss extensions to EJB3.
The bean should be in a jar file inside the ${serverconfig}/lib directory or your application will not find it.

Third, access the mbean from within your application:

MyExampleMBean myExample;
MBeanServer server = MBeanServerLocator.locate();
try {
  myExample = (MyExampleMBean) MBeanProxyExt.create(MyExampleMBean.class,
      "example-mbean:service=MyExampleMBean", server);
  // Access attribute
  System.out.println("Param=" + myExample.getParam());
  // Invoke method
  System.out.println(myExample.doSomething());
}
catch (MalformedObjectNameException e) {
  System.out.println("Cannot get MBean");
}

Fourth, configure your mbean with a xml file in the deploy directory. The file must end with “-service.xml” because it is a service descriptor.

<?xml version="1.0" encoding="UTF-8"?>
<server>
   <mbean code="MyExample"
      name="example-mbean:service=MyExampleMBean">
      <!-- Note the attribute name is 'Param', not 'param' -->
      <attribute name="Param">10</attribute>
   </mbean>
</server>

Another one is to modify ${serverconfig}/conf.xmdesc/org.jboss.deployment.MainDeployer-xmbean.xml
and add your application before the othes in the EnhancedSuffixOrder list.

<attribute access='read-write' setMethod='setEnhancedSuffixOrder' getMethod='getEnhancedSuffixOrder'>
   <description>Allows the override of the suffix order declared by subdeployers, using the syntax [order:]suffix
   </description>
   <name>EnhancedSuffixOrder</name>
   <type>[Ljava.lang.String;</type>
   <descriptors>
      <value value="250:.rar,300:-ds.xml,400:.jar,500:.war,550:.jse,600:myapp.ear,650:.ear,800:.bsh"/>
   </descriptors>
</attribute>

Note myapp.ear is put before the .ear suffix.

That’s why I wrote this easy to use Java equivalent of PHP’s var_dump aka print_r, or Perl’s Data::Dumper (sort of).

What it does
It takes an object (any object, Collection, Map, null, primitive, array, enum, or any combination of previous objects) as its argument, and dumps the content of the object as a html page. Included in the package is a css file to style your page, so the output has easy to distinguish colors for text, numbers, null values, warnings, errors etc.

Screenshot

What you need

• A super complicated, mind blowing, look how smart I am, object.
• Dependency: objectdumper.
• Other dependencies: commons-beanutils, commons-lang, commons-logging. (You’ll probably already have them).
• A web browser.
• A stylesheet (optional, but highly recommended)

Download
objectdumper.jar
Source files
Stylesheet

Configuration
The ObjectDumper class uses a default configuration that can be overridden by a .properties file.
The defaults are:

# The maximum number of levels ObjectDumper follows member objects.
# This is to prevent running out of memory, and because of circular
# references.

maxRecursionLevel=5

# Comma seperated list of packages the ObjectDumper should dump.
# Yes, you need to add java.util if you want Collections and Maps
# to be dumped.

dumpPackages=java.util

# Max items of arrays, Collections and Maps that need to be dumped.
maxItems=10
# Path where the css file can be found. Absolute or relative to the
# output html page.

stylesheetHref=dump.css

# If you want to incorporate the dump inside your own html page
# (I wanted that) then set this property to true (no html, head
# and body  declaration).

onlyHtmlContent=false

# Output full package+class name or only class name.

simpleClassNames=false

Usage
Inside a JSP page

<%
ObjectDumper dumper = new ObjectDumper(new StringWriter());
dumper.loadConfig(getServletContext().getRealPath("WEB-INF") + System.getProperty("file.separator") + "dump.properties"); 
%>
<%=dumper.writeObjectDump(anObject)%>

In a non web based Java application

ObjectDumper dumper = new ObjectDumper(new FileWriter("/somedir/test.html"));
dumper.loadConfig("/some_dir/dump.properties"); 
dumper.writeObjectDump(anObject);

Point your web browser to /somedir/test.html and happy debugging!

What you need:

• Eclipse
• An Eclipse ear project
• FileSync plugin for Eclipse
• Maven 2
• An application server that supports exploded archives, i.e. JBoss

Steps to take:

1. Use the unpackTypes or unpack option of the maven-ear-plugin. By setting this options, wars and ejb will be exploded inside the enclosing ear in the target directory. However, the ear itself remains packed.
2. Use the maven-dependency-plugin to copy everything unpacked to the deploy directory of your application server.
3. Create profiles in your super pom: A default profile for use during development. This profile uses the options mentioned above. An other profile is for distributing your ear files. This profiles does not unpack your wars and ejbs and the enclosing ear.
4. Configure the FileSync plugin to sync your class, jsp, (x)html, WEB-INF, properties files, etc. files with the deploy directory of the application server.

Steps 1 and 2
Change the build section of the ear:

<build>
    <finalName>${myear.finalename}</finalName>
    <defaultGoal>install</defaultGoal>
    <plugins>
        <plugin>
            <artifactId>maven-ear-plugin</artifactId>
            <configuration>
                <displayName>My EAR</displayName>
                <unpackTypes>${unpack.types}</unpackTypes>
                <modules>
                    <!-- A web module -->
                    <webModule>
                        ...
                    </webModule>
                    <!-- A ejb module -->
                    <ejbModule>
                        ...
                    </ejbModule>
                    <!-- Een jar module -->
                    <jarModule>
                        ...
                    </jarModule>
                </modules>
            </configuration>
        </plugin>
 
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-dependency-plugin</artifactId>
            <executions>
                <execution>
                    <id>unpack</id>
                    <phase>package</phase>
                    <goals>
                        <goal>unpack</goal>
                    </goals>
                    <configuration>
                        <artifactItems>
                            <artifactItem>
                                <artifactId>
                                    ${myear.artifact.id}
                                </artifactId>
                                <groupId>${myear.group.id}</groupId>
                                <version>${myear.version}</version>
                                <type>ear</type>
                                <overWrite>true</overWrite>
                                <outputDirectory>
                                    ${jboss.home}/server/${server.config}/deploy/${project.build.finalName}.ear
                                </outputDirectory>
                            </artifactItem>
                        </artifactItems>
                    </configuration>
                </execution>
            </executions>
        </plugin>
    </plugins>
</build>

Most ${} items need to be filled in by you as pom properties, or just hard wire them in your pom, some are automagically filled in by maven.
Most important here is the <unpackTypes> tag. If you want to unpack all ejbs and wars inside your ear (and why wouldn’t you during development? ) the value is “ejb,war”. See this site for more info.

An other way to configure which archive will be unpacked, is to configure it per archive with the <unpack> option. For example:

<plugin>
    <artifactId>maven-ear-plugin</artifactId>
    <configuration>
        <displayName>My EAR</displayName>
        <modules>
            <ejbModule>
                ...
            </ejbModule>
 
            <webModule>
                ...
                <unpack>${unpack}</unpack>
            </webModule>
            <jarModule>
                ...
            </jarModule>
        </modules>
    </configuration>
</plugin>

${unpack} can be either “true” or “false”.
The unpackTypes and unpack tag values are configured inside your profiles, that’s why their values are properties. Which leads to

Step 3
Create profiles in your super pom.

<profiles>
    <profile>
	<id>development</id>
	<activation>
	    <activeByDefault>true</activeByDefault>
	    <property>
		<name>unpack</name>
		<value>true</value>
	    </property>
	</activation>
	<properties>
	    <unpack.types>ejb,war</unpack.types>
	    <unpack>true</unpack>
	</properties>
    </profile>
    <profile>
	<id>release</id>
	<activation>
	    <property>
		<name>unpack</name>
		<value>false</value>
	    </property>
	</activation>
	<properties>
	    <unpack.types></unpack.types>
	    <unpack>false</unpack>
	</properties>
    </profile>
</profiles>

Notice the unpack.types and unpack properties and how they are mixed here (Mixing them should normally not be done). By default unpacking is activated, to distribute your ear without unpacking use:

mvn package -Dunpack=false

Of course there are many more ways to configure this, and my example will certainly not fit inside your project. Google is your friend.

Step 4
Configure the FileSync plugin.
Run mvn package once, and cd to the deploy directory of your application server. Examine the eploded ear, and where the ‘variable’ files reside. Click right on you Eclipse project -> Properties -> File synchronization -> Enable File Sync builder for this project, and map all files that you want to sync to the right directory.

Install with pacman -U kernel26-2.6.24.4-1-i686.pkg.tar.gz