At last JavaOne 2006 Sun promoted everyone to join Java Community Process (JCP).
I have thought about it for a long time and now I have decided to join JCP. I am now a JCP member: http://www.jcp.org/en/participation/members/N
Tuesday, September 26, 2006
Friday, September 22, 2006
eRCP 1.0 is NOW AVAILABLE!
Project ERCP - Embedded Rich Client Platform, has now released eRCP 1.0.
I think It is an interesting mobility project!
Download eRCP 1.0 now from www.eclipse.org/ercp
I think It is an interesting mobility project!
Download eRCP 1.0 now from www.eclipse.org/ercp
Thursday, September 21, 2006
AGUI(JSR-209) is finished, but don’t believe AGUI will have any success!!
Success for me means I can buy devices supporting AGUI and if look on the comments down you understand what I mean.
:-(
AGUI (JSR-000209 - Advanced Graphics and User Interface Optional Package for the J2METM Platform) have passed the Final Approval Ballot
View the ballot results here:
http://jcp.org/en/jsr/results?id=3982
Have a look these comments:
On 2006-09-18 Nokia Corporation voted Abstain with the following comment:
Nokia votes Abstain because we think the current specification does not take into account requirements of the mobile devices and is not suitable for them.
Firstly, the specification does not address use and integration with native UI toolkits well enough. Most mobile devices have a native UI toolkit used by native runtime and other runtimes and consistency between applications of different runtimes within the same device is essential.
Secondly, in its current form, the specification does not provide interoperability for look and feel modules to work across different independent implementations of the specification. The specification does not define many details accurately enough and a look and feel module needs to make assumptions that are valid possibly only on one particular implementation.
Thirdly, the specification does not adequately take into account mobile specific features and restrictions.
Even if these issues have been brought up in the EG several times the specification lead has chosen not to sufficiently address these. Therefore, in our opinion, this specification is not on a large scale suitable for mobile devices, such as mobile terminals.
------------------------------------------------------------------------------
On 2006-09-18 Ericsson AB voted Abstain with the following comment:
Ericsson would like to support any JSR going forward that also aim to bring innovation to JAva ME and the JCP. From an EC point of view there is also a need to maintain a viable/predictable evolution path for Java ME at large and currently a number of competing UI related JSRs, while still providing innovation and flexibility it may also prove to fragment the market. Ericsson would like to ask stakeholder of these JSRs to consider e.g. how JSR-209 fits in the big picture together with JSR-271, JSR-258, JSR-287 and JSR-290 etc. (to name a few examples). It should also be noted that JSR-209 may not be suitable for the "limited" part of the Java ME devices e.g. those having a native UI toolkit for speed and power effeciency etc.
:-(
AGUI (JSR-000209 - Advanced Graphics and User Interface Optional Package for the J2METM Platform) have passed the Final Approval Ballot
View the ballot results here:
http://jcp.org/en/jsr/results?id=3982
Have a look these comments:
On 2006-09-18 Nokia Corporation voted Abstain with the following comment:
Nokia votes Abstain because we think the current specification does not take into account requirements of the mobile devices and is not suitable for them.
Firstly, the specification does not address use and integration with native UI toolkits well enough. Most mobile devices have a native UI toolkit used by native runtime and other runtimes and consistency between applications of different runtimes within the same device is essential.
Secondly, in its current form, the specification does not provide interoperability for look and feel modules to work across different independent implementations of the specification. The specification does not define many details accurately enough and a look and feel module needs to make assumptions that are valid possibly only on one particular implementation.
Thirdly, the specification does not adequately take into account mobile specific features and restrictions.
Even if these issues have been brought up in the EG several times the specification lead has chosen not to sufficiently address these. Therefore, in our opinion, this specification is not on a large scale suitable for mobile devices, such as mobile terminals.
------------------------------------------------------------------------------
On 2006-09-18 Ericsson AB voted Abstain with the following comment:
Ericsson would like to support any JSR going forward that also aim to bring innovation to JAva ME and the JCP. From an EC point of view there is also a need to maintain a viable/predictable evolution path for Java ME at large and currently a number of competing UI related JSRs, while still providing innovation and flexibility it may also prove to fragment the market. Ericsson would like to ask stakeholder of these JSRs to consider e.g. how JSR-209 fits in the big picture together with JSR-271, JSR-258, JSR-287 and JSR-290 etc. (to name a few examples). It should also be noted that JSR-209 may not be suitable for the "limited" part of the Java ME devices e.g. those having a native UI toolkit for speed and power effeciency etc.
Thursday, September 07, 2006
JSR 232: Mobile Operational Management - Final Ballot Approved!!
Tuesday, September 05, 2006
Back to Karate again
Since two weeks ago I have started to practice karate again (after 10 years break).
I have change to a karate club close to where I live called Salem Shukokai Karate, the style is called shukokai. I started to practice karate at Kusano-Ha Shitoryu, the style there is called Kusano-Ha Shitoryu Kenpo Karate-Do Kai.
It is fun to be back in the Karate business again!!
I have change to a karate club close to where I live called Salem Shukokai Karate, the style is called shukokai. I started to practice karate at Kusano-Ha Shitoryu, the style there is called Kusano-Ha Shitoryu Kenpo Karate-Do Kai.
It is fun to be back in the Karate business again!!
Debugging on the SavaJe phone with Netbeans 5.5 beta 2 Mobility Pack for CDC works now
I followed the steps in http://java.savaje.com/wiki/index.php/Using_JDWP_to_debug_bundles
I was using Netbeans 5.5 beta 2 Mobility Pack for CDC.
On the phone I had installed the Early Access Update 2 for the JavaOne Jasper Edition
But I was not able to debug on the phone. I got:
Attaching to 192.168.254.2:9462
Connection refused.
I was not able to ping the phone from my PC:
ping 192.168.254.1
I have installed my Xlet on the phone by placing the bundle files on the SD card under a folder entitled /savaJe/bundles/.
Then it is not possible to start the application when the USB cable is connected. HowTo do that?
I got an answer from SavaJe:
I'm assuming that you are mounting the SD card to the PC via the USB mass storage driver. The SD card can only be seen by one device at a time (either the phone or the PC).
After you've copied the bundle files to the SD card, right click the drive letter of the SD card on the PC, and select Eject. The phone should remount the SD card, and the Xlet should show up in the My Applications
group. To dismount from the phone (and remount to the PC), pop the SD card out and then reinsert it. Any Xlets on the SD card should disappear from My Applications, and the SD drive should reappear on the PC.
If you're using an SD adapter that plugs into the PC, you don't need to worry about this (but you have to do a lot more SD card swapping)
Now it works to debugging on the SavaJe phone using Netbeans 5.5 beta 2 Mobility pack for CDC!!
:-)
I was using Netbeans 5.5 beta 2 Mobility Pack for CDC.
On the phone I had installed the Early Access Update 2 for the JavaOne Jasper Edition
But I was not able to debug on the phone. I got:
Attaching to 192.168.254.2:9462
Connection refused.
I was not able to ping the phone from my PC:
ping 192.168.254.1
I have installed my Xlet on the phone by placing the bundle files on the SD card under a folder entitled /savaJe/bundles/
Then it is not possible to start the application when the USB cable is connected. HowTo do that?
I got an answer from SavaJe:
I'm assuming that you are mounting the SD card to the PC via the USB mass storage driver. The SD card can only be seen by one device at a time (either the phone or the PC).
After you've copied the bundle files to the SD card, right click the drive letter of the SD card on the PC, and select Eject. The phone should remount the SD card, and the Xlet should show up in the My Applications
group. To dismount from the phone (and remount to the PC), pop the SD card out and then reinsert it. Any Xlets on the SD card should disappear from My Applications, and the SD drive should reappear on the PC.
If you're using an SD adapter that plugs into the PC, you don't need to worry about this (but you have to do a lot more SD card swapping)
Now it works to debugging on the SavaJe phone using Netbeans 5.5 beta 2 Mobility pack for CDC!!
:-)
Choose a tool for Java ME?
Often I get questions about Java ME tools like these:
- What's your personal favorite Java ME tool and why?
- Netbeans or Eclipse?
I work as a Java consultant and I have to use both tools at different customer.
The customer has often already selected what tools the project should use.
I think; because both Eclipse and Netbeans are free, try both!!
Eclipse and Netbeans have very friendly installations, no MS registstry changes, everything in one folder; because of that it is very easy to remove both eclipse and Netbeans.
My favorite tool is Netbeans!!!
What like with Netbeans is good/fast support for new things (like Java ME/CDC1.1) and the Netbeans community (if you have a question always someone answer).
If you would like to try Netbeans Mobility Pack for CLDC and NetBeans Mobility 5.5 Pack for CDC, install the following software on your computer:
- JDK 5.0
- NetBeans IDE 5.5 Beta 2
- NetBeans Mobility 5.5 Pack for CDC Preview version
- Sun Java Toolkit 1.0 for CDC, Early Access
Now you have support for Java ME/CDC1.1/PP1.1 and AGUI(JSR-209=Swing)
Also install:
- NetBeans Mobility Pack 5.5 beta 2
- Sun Java Wireless Toolkit 2.5 for CLDC, Beta
- Carbide.j 1.5 (add Nokia SDK:s)
Now you have support for Java ME/CLDC1.1/MIDP2.0
In the menu "tools" "Java platform Manager"you integrate different SDK’s, like these included with Carbide.j 1.5, Sun Java Wireless Toolkit 2.5 for CLDC and Sun Java Toolkit 1.0 for CDC, Early Access
- What's your personal favorite Java ME tool and why?
- Netbeans or Eclipse?
I work as a Java consultant and I have to use both tools at different customer.
The customer has often already selected what tools the project should use.
I think; because both Eclipse and Netbeans are free, try both!!
Eclipse and Netbeans have very friendly installations, no MS registstry changes, everything in one folder; because of that it is very easy to remove both eclipse and Netbeans.
My favorite tool is Netbeans!!!
What like with Netbeans is good/fast support for new things (like Java ME/CDC1.1) and the Netbeans community (if you have a question always someone answer).
If you would like to try Netbeans Mobility Pack for CLDC and NetBeans Mobility 5.5 Pack for CDC, install the following software on your computer:
- JDK 5.0
- NetBeans IDE 5.5 Beta 2
- NetBeans Mobility 5.5 Pack for CDC Preview version
- Sun Java Toolkit 1.0 for CDC, Early Access
Now you have support for Java ME/CDC1.1/PP1.1 and AGUI(JSR-209=Swing)
Also install:
- NetBeans Mobility Pack 5.5 beta 2
- Sun Java Wireless Toolkit 2.5 for CLDC, Beta
- Carbide.j 1.5 (add Nokia SDK:s)
Now you have support for Java ME/CLDC1.1/MIDP2.0
In the menu "tools" "Java platform Manager"
Subscribe to:
Posts (Atom)