"; */ ?>


25
Jun 07

Custom Keyboard Layout in Ubuntu (or just Linux :)

keyboard layout in Ubuntu LinuxSystem -> Preferences -> Keyboard -> Layouts -> Add… Right? It is all good and clean only in case if layouts, that come with Ubuntu (or other Linux), are exactly what you need. But what if you’d like to create your own layout? Or, most of the time, what if layout is ok, but you would like to change a couple of keys around, because you are used to it “that certain way”? Here is how to approach these “what if”s.

The “guy” to talk to is XKB (X KeyBoard), which is responsible for everything that is going on with keyboard(s) under X (GUI Environment).

First, let us find the layout to change/modify/customize. For that we will go to “/usr/share/X11/xkb/symbols”:

user@host:/usr/share/X11/xkb/symbols$ ls
ad      by             epo            hr      kh               mk         pl          th
af      ca             es             hu      kr               mm         pt          tj
al      capslock       eurosign       ie      kz               mn         ro          tr
altwin  cd             fi             il      la               mt         ru          ua
am      ch             fo             in      latam            mv         ru_backup   us
ara     compose        fr             inet    latin            nbsp       se          uz
az      cs             fujitsu_vndr/  iq      level3           nec_vndr/  sgi_vndr/   vn
ba      ctrl           gb             ir      level5           ng         si          xfree68_vndr/
bd      cz             ge             is      lk               nl         sk          za
be      de             gh             it      lt               no         sony_vndr/
bg      digital_vndr/  gr             jp      lv               np         srvr_ctrl
br      dk             group          keypad  macintosh_vndr/  pc         sun_vndr/
bt      ee             hp_vndr/       kg      mao              pk         sy

This is home for all layouts that XKB reads in and follows. That means that if a layout needs to be changed all the changes are written here.

Now let’s change a Russian Phonetic (for example) layout to change a couple of keys around. For that, first, make a backup of the existing Russian layout (that has all Russian Layouts):

sudo cp ru ru_backup

then let’s get to breaking through and customizing it (use your favorite text editor, “vi” here is used as an example):

sudo vi ru
 
// $XKeyboardConfig: xkbdesc/symbols/ru,v 1.11 2006/09/04 20:25:10 svu Exp $
 
// based on
// russian standard keyboard
// AEN aen@logic.ru
// 2001/12/23 by Leon Kanter leon@blackcatlinux.com
// 2005/12/09 Valery Inozemtsev shrek@altlinux.ru
//
// $XFree86: xc/programs/xkbcomp/symbols/ru,v 1.3 2003/02/15 22:27:05 dawes Exp $
 
partial default alphanumeric_keys
xkb_symbols "basic" {
 
    name[Group1]= "Russia";
 
    key    AE01 {    [        1,        exclam     ]    };
    key    AE02 {    [        2,        quotedbl    ]    };
    key    AE03 {    [        3,      numbersign    ]    };
    key    AE04 {    [        4,        asterisk    ]    };
    key    AE05 {    [        5,         colon    ]    };
    key    AE06 {    [        6,         comma    ]    };
    key    AE07 {    [        7,        period    ]    };
    key    AE08 {    [        8,     semicolon    ]    };
    key    AE09 {    [        9,     parenleft    ]    };
    key    AE10 {    [        0,    parenright    ]    };
    key    AE11 {    [        minus,    underscore    ]    };
    key    AE12 {    [        equal,          plus    ]    };
    key    BKSL {    [    backslash,             bar    ]    };
    key    AB10 {    [        slash,      question    ]    };
    key LSGT {        [           slash,             bar      ]       };
 
    key    TLDE {    [     Cyrillic_io,     Cyrillic_IO    ]    };
    key    AD01 {    [ Cyrillic_shorti, Cyrillic_SHORTI    ]    };
    key    AD02 {    [    Cyrillic_tse,    Cyrillic_TSE    ]    };
    key    AD03 {    [      Cyrillic_u,    Cyrillic_U    ]    };
    key    AD04 {    [     Cyrillic_ka,     Cyrillic_KA    ]    };
    key    AD05 {    [     Cyrillic_ie,     Cyrillic_IE    ]    };
    key    AD06 {    [     Cyrillic_en,     Cyrillic_EN    ]    };
    key    AD07 {    [    Cyrillic_ghe,    Cyrillic_GHE    ]    };
    key    AD08 {    [    Cyrillic_sha,    Cyrillic_SHA    ]    };
    key    AD09 {    [  Cyrillic_shcha,  Cyrillic_SHCHA    ]    };
    key    AD10 {    [     Cyrillic_ze,     Cyrillic_ZE    ]    };
    key    AD11 {    [     Cyrillic_ha,     Cyrillic_HA    ]    };
    key    AD12 {    [Cyrillic_hardsign,Cyrillic_HARDSIGN    ]    };
    key    AC01 {    [     Cyrillic_ef,     Cyrillic_EF    ]    };
    key    AC02 {    [   Cyrillic_yeru,   Cyrillic_YERU    ]    };
    key    AC03 {    [     Cyrillic_ve,     Cyrillic_VE    ]    };
    key    AC04 {    [      Cyrillic_a,    Cyrillic_A    ]    };
    key    AC05 {    [     Cyrillic_pe,     Cyrillic_PE    ]    };
    key    AC06 {    [     Cyrillic_er,     Cyrillic_ER    ]    };
    key    AC07 {    [      Cyrillic_o,    Cyrillic_O    ]    };
    key    AC08 {    [     Cyrillic_el,     Cyrillic_EL    ]    };
    key    AC09 {    [     Cyrillic_de,     Cyrillic_DE    ]    };
    key    AC10 {    [    Cyrillic_zhe,    Cyrillic_ZHE    ]    };
    key    AC11 {    [      Cyrillic_e,    Cyrillic_E    ]    };
    key    AB01 {    [     Cyrillic_ya,     Cyrillic_YA    ]    };
    key    AB02 {    [    Cyrillic_che,    Cyrillic_CHE    ]    };
    key    AB03 {    [     Cyrillic_es,     Cyrillic_ES    ]    };
    key    AB04 {    [     Cyrillic_em,     Cyrillic_EM    ]    };
    key    AB05 {    [      Cyrillic_i,    Cyrillic_I    ]    };
    key    AB06 {    [     Cyrillic_te,     Cyrillic_TE    ]    };
    key    AB07 {    [Cyrillic_softsign,Cyrillic_SOFTSIGN    ]    };
    key    AB08 {    [     Cyrillic_be,     Cyrillic_BE    ]    };
    key    AB09 {    [     Cyrillic_yu,     Cyrillic_YU    ]    };
 
    key.type[group1]="TWO_LEVEL";
 
    include "keypad(comma)"
};
 
partial alphanumeric_keys
xkb_symbols "winkeys" {
    include "ru(basic)"
    name[Group1]= "Russia - Winkeys";
    key AE03 {        [               3,      numerosign      ]       };
    key AE04 {        [               4,       semicolon      ]       };
    key AE05 {        [               5,         percent      ]       };
    key AE06 {        [               6,           colon      ]       };
    key AE07 {        [               7,        question      ]       };
    key AE08 {        [               8,        asterisk      ]       };
    key AB10 {        [          period,           comma      ]       };
    key BKSL {        [       backslash,           slash      ]       };
};
 
partial alphanumeric_keys
xkb_symbols "typewriter" {
    include "ru(basic)"
    name[Group1]= "Russia - Typewriter";
    key    TLDE {    [      apostrophe,      quotedbl    ]     };
    key    AE01 {    [       exclam,         1     ]    };
    key    AE02 {    [      numerosign,         2    ]    };
    key    AE03 {    [        slash,         3    ]    };
    key    AE04 {    [    semicolon,         4    ]    };
    key    AE05 {    [        colon,         5    ]    };
    key    AE06 {    [        comma,         6    ]    };
    key    AE07 {    [       period,         7    ]    };
    key    AE08 {    [      underscore,         8    ]    };
    key    AE09 {    [     question,         9    ]    };
    key    AE10 {    [      percent,
        0    ]    };
    key    BKSL {    [    parenleft,    parenright    ]    };
 
    key    AD12 {    [Cyrillic_hardsign,Cyrillic_HARDSIGN    ]    };
    key    AB10 {    [     Cyrillic_io,     Cyrillic_IO    ]    };
};
 
partial alphanumeric_keys
xkb_symbols "phonetic" {
 
    name[Group1]= "Russia - Phonetic";
 
    key    AE01 {    [        1,        exclam     ]    };
    key    AE02 {    [        2,            at    ]    };
    key    AE03 {    [        3,     Cyrillic_io     ]    };
    key    AE04 {    [        4,     Cyrillic_IO    ]    };
    key    AE05 {    [        5, Cyrillic_hardsign       ]    };
    key    AE06 {    [        6, Cyrillic_HARDSIGN    ]    };
    key    AE07 {    [        7,     ampersand    ]    };
    key    AE08 {    [        8,        asterisk    ]    };
    key    AE09 {    [        9,     parenleft    ]    };
    key    AE10 {    [        0,    parenright    ]    };
 
    key    AB09 {    [       period,       greater    ]    };
    key    AB10 {    [        slash,      question    ]    };
    key    AB08 {    [        comma,          less    ]    };
    key    AC10 {    [    semicolon,         colon    ]    };
    key    AC11 {    [      apostrophe,      quotedbl    ]    };
    key    LSGT {    [          bar,     brokenbar    ]    };
 
    key    TLDE {    [     Cyrillic_yu,     Cyrillic_YU    ]    };
    key    LatQ {    [     Cyrillic_ya,     Cyrillic_YA    ]    };
    key    LatZ {    [     Cyrillic_ze,     Cyrillic_ZE    ]    };
    key    LatS {    [     Cyrillic_es,     Cyrillic_ES    ]    };
    key    LatA {    [      Cyrillic_a,    Cyrillic_A    ]    };
    key    LatW {    [     Cyrillic_ve,     Cyrillic_VE    ]    };
    key    LatC {    [    Cyrillic_tse,    Cyrillic_TSE    ]    };
    key    LatX {    [Cyrillic_softsign,Cyrillic_SOFTSIGN    ]    };
    key    LatD {    [     Cyrillic_de,     Cyrillic_DE    ]    };
    key    LatE {    [     Cyrillic_ie,     Cyrillic_IE    ]    };
    key    LatV {    [    Cyrillic_zhe,    Cyrillic_ZHE    ]    };
    key    LatF {    [     Cyrillic_ef,     Cyrillic_EF    ]    };
    key    LatT {    [     Cyrillic_te,     Cyrillic_TE    ]    };
    key    LatR {    [     Cyrillic_er,     Cyrillic_ER    ]    };
    key    LatN {    [     Cyrillic_en,     Cyrillic_EN    ]    };
    key    LatB {    [     Cyrillic_be,     Cyrillic_BE    ]    };
    key    LatH {    [     Cyrillic_ha,     Cyrillic_HA    ]    };
 
    ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...
 
};

inside the file we’ll find the layout we are after, which is specified by the following line:

xkb_symbols "phonetic"

after this line all the mapping is done.

Now let’s look at the letters we would like to change keys for:

    key    LatX {    [Cyrillic_softsign,Cyrillic_SOFTSIGN    ]    };
    key    LatH {    [     Cyrillic_ha,     Cyrillic_HA    ]    };
    key    AE12 {    [    Cyrillic_che,    Cyrillic_CHE    ]    };

A single line above means that the “key <such and such> will map to [ small, and capital ] Russian letter”. So to change this all that needs to be done is to re-map them. For example, if we want <LatX> (just a latin X, or ‘X’ key) to map to “Cyrillic_ha, Cyrillic_HA” instead of “Cyrillic_softsign,Cyrillic_SOFTSIGN”, we just need to change it:

    key    LatX {    [     Cyrillic_ha,     Cyrillic_HA    ]    };

Here is how these three letters were changed, so they are more convinient to use as a part of the Russian Phonetic layout from the past:

    key    AE12 {    [Cyrillic_softsign,Cyrillic_SOFTSIGN    ]    };
    key    LatX {    [     Cyrillic_ha,     Cyrillic_HA    ]    };
    key    LatH {    [    Cyrillic_che,    Cyrillic_CHE    ]    };

Now just save the file and exit out from it (in vi it is “:wq”), and restart X (press “Ctrl + Alt + backspace”).

You’ve got yourself a new customized layout now that you can use – enjoy!


13
Jun 07

Haptic Clock Beats The Time Into You

Haptic Java Mobile ClockHave a mobile phone that you do not want to look at? Is it that bad, or maybe it is awesome, but you are just annoyed to look at it to find out something as simple as current time? Then here is a very interesting Java Mobile application that is written by Che-Wei Wang and makes your phone to literally beat the time into you.

The Haptic Clock is a small clock program for Java powered mobile phones.  The clock conveys time through  a sequence of vibrations so you never have to pull the phone out of your pocket to tell time.

 

Haptic Java Mobile Clock

Long vibrations are the number of hours of the current time on a 12 hour clock, so 6pm and 6am are both 6 vibrations.  The shorter vibrations are the number of minutes divided by 5. So 4 vibrations is 20 minutes and 7 vibrations is 35 minutes.  Example: (3) long vibrations and (6) short vibrations means it’s 3:30.  Just in case you do want to see the time, the screen displays the time with tick marks for hours, minutes and seconds.

Instructions: Press ‘5′ to vibrate the current time. Press ‘0′ to exit program. UP and DOWN to control the speed of vibrations. Time alerts (vibrations) will occur automatically every 15 minutes on the hour.

Version:         0.06
Released:      5.24.2007
Creator:         Che-Wei Wang
License:         GNU Public License (source coming soon)

Download BetaHaptic-Clock.zip  (includes JAR and JAD)
                                    Beta means it may not work on your phone or worse, may break your phone. Install and use at your own risk.

Tested on:            Nokia E70
Issues:                  J2ME drains the batteries. Looking for ways around it, or a more efficient platform.


09
Jun 07

Convert Date to String in Java


Just an example on how “java.text.SimpleDateFormat” can be used to convert a java date object (java.util.Date) to a string (String, StringBuffer, StringBuilder, etc..).
The whole magic is done by SimpleDateFormat, the child of “java.text.DateFormat”, which, as its name suggests, formats the date by a provided template.

This template is very flexible and provided to the formatter as a string. Here are the values which are used by SimpleDateFormat’s template:

Letter

Date or Time Component

Presentation

Examples

G

Era designator

Text

AD

y

Year

Year

1996; 96

M

Month in year

Month

July; Jul; 07

w

Week in year

Number

27

W

Week in month

Number

2

D

Day in year

Number

189

d

Day in month

Number

10

F

Day of week in month

Number

2

E

Day in week

Text

Tuesday; Tue

a

Am/pm marker

Text

PM

H

Hour in day (0-23)

Number

0

k

Hour in day (1-24)

Number

24

K

Hour in am/pm (0-11)

Number

0

h

Hour in am/pm (1-12)

Number

12

m

Minute in hour

Number

30

s

Second in minute

Number

55

S

Millisecond

Number

978

z

Time zone

General time zone

Pacific Standard Time; PST; GMT-08:00

Z

Time zone

RFC 822 time zone

-0800

Below, I wrote an example on how to implement the conversion. Here I used two different templates: “yyyyMMdd” and “MMddyyyy” to show that several letters from the table above can be used in different sequence for the desired format:

import java.util.Date;
import java.text.SimpleDateFormat;
... ... ... ...
 
    public void testConvertDateToString()    {
 
        //   Allocates a Date object and initializes it so that it represents the time
        // at which it was allocated, measured to the nearest millisecond.
        Date dateNow = new Date ();
 
        SimpleDateFormat dateformatYYYYMMDD = new SimpleDateFormat("yyyyMMdd");
        SimpleDateFormat dateformatMMDDYYYY = new SimpleDateFormat("MMddyyyy");
 
        StringBuilder nowYYYYMMDD = new StringBuilder( dateformatYYYYMMDD.format( dateNow ) );
        StringBuilder nowMMDDYYYY = new StringBuilder( dateformatMMDDYYYY.format( dateNow ) );
 
        System.out.println( "DEBUG: Today in YYYYMMDD: '" + nowYYYYMMDD + "'");
        System.out.println( "DEBUG: Today in MMDDYYYY: '" + nowMMDDYYYY + "'");
 
    }

Results:

DEBUG: Today in YYYYMMDD: ‘20070609’
DEBUG: Today in MMDDYYYY: ‘06092007’

You may also notice that in the example I used StringBuilder, and not String or StringBuffer. The reason is simple – “best practice – use the right tool for the right task”.

“String” is immutable, meaning it cannot be changed, every time you try to change it, new String object is created and the old one is released for garbage collection, therefore String can be perfect for something like constants e.g. { private static final String FORTY_TWO = “42”; }.

StringBuilder and StringBuffer can be changed (modified), and, in fact, they have exactly the same functionality with one distinct difference – StringBuffer is synchronized and StringBuilder is not. Therefore if the segment of code we are working on is not designed to be multi threaded (used by different threads in a same time), it is better to use StringBuilder, since it will work faster.

StringBuilder is available in Java 1.5.0 (Java 2 SE 5.0) and up.

KISS – Keep It Simple Stupid ;)


02
Jun 07

Switch Between Dual/Single Monitor on (Ubuntu) Linux

xorg logo ubuntuRecently I wrote a howto on dual monitor configuration, which works great for my setup. However one thing that is not that great is switching between two modes: dual and single monitor. At work I have an external monitor that I use (which means I use two monitors – my laptop’s and external one), but whenever I am not at work I only need to use my laptop’s. Since all the xorg configuration resides in xorg.conf file, and this file is a regular static text file that is used by X (window system – gdm, kdm, etc.) when it starts, it is nontrivial to change this configuration while running X without some X tools. Unfortunately, Ubuntu is not that fancy (yet) and does not provide these tools by default, so here is a way to do it (sort of) manually.

What we can do is to create two xorg.conf files – "xorg.conf.single" and "xorg.conf.dual". In "xorg.conf.single" just comment out the following line from ServerLayout section:

# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
.....
Section "ServerLayout"
        Identifier      "Default Layout"
        Screen          0 "0 Screen"
        #Screen         1 "1 Screen" Above "0 Screen"   <-- comment out this line
        Option          "Xinerama" "on"
        Option          "Clone" "off"
.....
EndSection

Here is the listing of "xorg" files that I have:

user@host:/etc/X11$ ll xorg.conf*
-rw-r--r-- 1 root root 4457 2007-06-02 15:05 xorg.conf
-rw-r--r-- 1 root root 4456 2007-05-22 22:03 xorg.conf.dual
-rw-r--r-- 1 root root 4457 2007-05-22 22:04 xorg.conf.single

Now the idea is simple - before X (I use Gnome Desktop, but it can be any desktop environment) starts, we need to copy xorg file that we need (dual or single) to "xorg.conf", which will be picked and loaded by X.

In /home/user/ directory we have a .bashrc file that is loaded whenever the user logs in (if we use bash shell, which is a most popular shell anyway). Therefore we can leverage this file to define aliases that we would like to use once we login. Since alias can be anything we'd like, why not make a dual/single commands as aliases? Here is an example:

user@host:/etc/X11$ tail -5 /home/user/.bashrc
# restart gdm with dual monitor support
alias xdual='sudo cp /etc/X11/xorg.conf.dual /etc/X11/xorg.conf; sudo /etc/init.d/gdm restart'

# restart gdm with single monitor support
alias xsingle='sudo cp /etc/X11/xorg.conf.single /etc/X11/xorg.conf; sudo /etc/init.d/gdm restart'

Now when we need to switch between dual/single monitor, we can fire up shell (by pressing Ctrl+Alt+1, or gnome-terminal, or kterm, etc.) and type xsingle or xdual whichever we need.


28
May 07

Ubuntu Dell – Three Real Models

Welcome to DELL Open Source

You asked, we listened. For advanced users and tech enthusiasts, we’re happy to offer a new open-source operating system, so you can dive in and truly enjoy a PC experience just the way you want it. In addition to the FreeDOS systems we already offer, we are proud to announce PCs with Ubuntu.

dell pcs featuring ubuntu

 
    So far only these three models are for sale with Ubuntu on them:

Dimension E520 N
Intel® Core™2 Duo Processor E4300 (1.8GHz, 800 FSB)
Ubuntu Desktop Edition version 7.04
1GB Dual Channel DDR2 SDRAM at 667MHz- 2DIMMs
250GB Serial ATA Hard Drive (7200RPM) w/DataBurst Cache™
Inspiron E1505 N
Intel® Pentium® dual-core proc T2080(1MB Cache/1.73GHz/533MHz FSB
Ubuntu Edition version 7.04
512MB Shared Dual Channel DDR2 SDRAM at 533MHz, 2 DIMM
80GB 5400rpm SATA Hard Drive
XPS 410 N
Intel® Core™ 2 Duo Processor E4300 (2MB L2 Cache,1.8GHz,800FSB)
Ubuntu Desktop Edition version 7.04
1GB Dual Channel DDR2 SDRAM at 667MHz – 2 DIMMs
250GB Serial ATA 3Gb/s Hard Drive (7200RPM) w/DataBurst Cache™