Last week, we had the author of TDD for a Shopping Website LiveProject. Friday at 11am Ranch time, Steven Solomon will be hosting a live TDD session just for us. See for the agenda and registration link
Last week, we had the author of TDD for a Shopping Website LiveProject. Friday at 11am Ranch time, Steven Solomon will be hosting a live TDD session just for us. See for the agenda and registration link

Erik Kaellgren

+ Follow
since Jun 02, 2003
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Erik Kaellgren

I was testing a simple TextField on the Nokia emulator device "Nokia_S40_DP20_SDK_6230i" and it behaves exactly the way you describe.
On the Nokia Series 60 emulator it works like you wanted.

Why is it a difference? Probably only Nokia knows or our own "Nokia hacker", the moderator of this forum

Guess is not really much to do about it.

16 years ago

I might have this wrong, but if not...
In MIDP1.0 when entering text in a TextField, you'll have to do that in another "window" and the click OK. You can see this behavior with the SUN emulator WTK104.
On the contrary, with MIDP2.0 the TextField stays in place and you can enter text like a normal text editor.
These has some consequences though if you your class implements the ItemStateListener interface.
If you want to catch the changes when a user enters text, it works fine with MIDP2 but not with MIDP1 mainly because the text is entered in another "window".
You can easily try that with a simple midlet that uses a simple TextField.

public void itemStateChanged(Item item){
System.out.println("in itemStateChanged " + item.getLabel());
System.out.println("Text " + textField.getString());

Hope this explains you problem.

Erik Kaellgren
16 years ago
"Write Once, Run Anywhere" not working for phones
"Though MIDP is used in half the world's 1.4 billion phones for downloading other bits of software, writing a program that can run on any handset still isn't possible. From"

I'm currently working on a project where I have to manipulate the content of a TextField. To my surprise the behavior on the WKF21 emulator and the Nokia 6-series emulator is completely different. It works fine on the first and gives me a NullPointerException on the second.
And it's nothing I can do about it. And maybe on a Motorola handset or Samsung it will be something else.
It's really depressing

The only solution I can see today is to use a Canvas everywhere and do it yourself. And that is a thing I do not want to do or have time to do. It's like coding 15 years ago.

Other people annoyed about this "wild west" behavior from the manufactures?

Write Once, Run Once

Erik Kaellgren
16 years ago
You saved my day!
Now I see it!
Funny thoud, I could not see that thing in the user guide!
17 years ago

I've transferred a small midlet via bluetooth from my computer to my Nokia 6600. I appears in the Application Manager, but... How do you start it?
It only gives me 2 options; View and Setting.
Any ideas?
17 years ago

just checked your application for Paris! Looks nice.
A funny thing: If I wanna go from Pereire to Denfert-Rochereau it proposes one solution and if I switch destinations it proposes something else! Thourh both solutions are correct it's a bit odd, isn't it?

17 years ago
Hi Pourang,
I know they are working on it, so so please patient. When? No idea
Kathy already said back in June that this exam would not be updated for a long time!
Ko Ko,
1) for the certification you should concentrate on EJB 2.0 specification for the time being.
2) the general problem with new releases is that it takes a long time to be used in the industry.
For example, Weblogic is always faster to implement a new release of j2ee than Websphere.
Also, you might work for a company that still uses Webshpere 4.0 and then you can not even use EJB 2.0!
If you're a student you probably go for the latest version to learn, not only for a certificate, but for life.
Otherwise you need to be more pragmatic. An example, the other day I saw a customer that wanted somebody to
work on a JDK 1.0 (yes) applet to make it work in a new environment.
So you really need to be flexible!
Hope it wasn't too confusing!
hello Ko Ko,
I'm neither Kathy or Bert, but I'll give an answer anyway - hopefully it's the right one.
The SCBCD is based on the EJB 2.0 specification and will be for a long time.
That's all you need to now.
To my knowledge J2EE 1.4 is using EJB 2.1 specification, so don't use features in EJB 2.1 if you want to try it out!
Just a guess, but I'll think a new SCWCD and SCEA
Hi all,
I've just cancelled my registration for the 7th of July since it's not certain that I'm gonna be able to take the exam (as Evelyn pointed out) and I just don't want to study the hole week-end in vain!
So I'll guess that I'm gonna do it later this fall.
I can't say that I approve the policy of Sun in this case, but I accept it and therefore cancelled my registration.
Though, I'm still gonna study and work on my exam simulator with own questions. That one will be available in 3-4 weeks time I guess and will have at least 140 mock exam questions ( I'll hope so anyway)
So see you soon and good luck for everybody who's gonna take the beta before it ends!
Yes Evelyn, it does.
So if everybody is showing up, I'm in a bad situation because I'm based in Europe... ;(
But I know the rules of this game, wanted just to be sure where I stand right know.
Thanks again
just one question from my part on this subject:
1) "As for the beta. I have closed registration (ONLY REGISTRATION) because I have reached 600 candidates."
That this mean that 600 people have registerd at a prometric centre or that you have send out 600 vouchers?
For me it's not clear what ONLY REGISTRATION means. ;(