Agora em Setembro o GUJavaSC em parceria com a V Office e a Sun Microsystem criaram uma edição local do Mês de Java, que será realizado em Florianópolis no dias 20 de setembro (sábado) no auditório da Rua Felipe Schmidt, 785, Centro. A recepção no local acontecerá a partir das 8:30hrs.

A inscrição é gratuita, porém é necessário confirmar a vaga cadastrando-se aqui, além de que no dia também será necessário levar 2kg de alimentos não perecíveis.

Working with Bluetooth and GPS: Part 1 - Reading Wireless Serial Port Data

En el artículo se muestra:

• El trabajo con Bluetooth y el API JSR-82
• Muestra cómo ejecutar y depurar aplicaciones Java ME Bluetooth desde nuestra computadora de escritorio.
• Explica cómo leer datos en un dispositivo GPS vía Bluetooth.

Espero que les sirva

Sebelum kita bisa membuat aplikasi yang ditulis dengan bahasa Java, dibutuhkan Java Platform Standard Edition (Java SE) development kit. Developemnt kit itu berisi Java Virtual Machine (JVM), core Application Programming Interface (API), dan kompiler yang digunakan untuk development.

Untuk pengguna Mac sebaiknya mengunjungi http://developer.apple.com/java/ (Mac OS X Java Runtime Environment).

Jika ingin mengerjakan dalam Integrated Development Environment (IDE), kunjungi http://java.sun.com/javase/downloads/ (untuk men-download Java SE dengan NetBeans IDE).

Untuk beberapa proyek, mungkin Anda membutuhkan berkas tambahan. Tetapi jika Anda masih belum mengetahui apa yang Anda butuhkan Java SE saja sudah cukup untuk memenuhi kebutuhan Anda sampai familiar dengan Java platform. Di bawah ini yang adalah yang populer untuk di-download.

• Java SE

  Anda bisa mendapatkan Java SE di http://java.sun.com/javase/, kit ini sangat dibutuhkan untuk menghasilkan semua aplikasi, kecuali yang dirancang khusus untuk perlengkapan konsumen (consumer devices) digunakan Java Platform Micro Edition (Java ME). Java SE terdiri dari kompiler, runtime environment, dan core API.

• Java Platform Enterprise Edition (Java EE)

  Anda bisa mendapatkannya di http://java.sun.com/javaee/. Paket ini terdiri dari application server, dan teknologi JavaServerPages (JSP). Gunakan J2EE dengan Java SE.

• Java Platform Micro Edition (Java ME)

  Anda bisa mendapatkannya di http://java.sun.com/javame/. Digunakan jika ingin menghasilkan program untuk Palm Pilots, screen phones, dan consumer device yang lainnya. Java ME menyediakan tools untuk compiling, deployment, dan konfigurasi alat (device configuration), dan API yang dikhususkan untuk setiap device.

• JavaFX Script Technology

  Anda bisa mendapatkannya di https://openjfx.dev.java.net/. JavaFX Script Technology merupakan bahasa scripting yang sangat produktif, yang memungkinkan pembuat content (content developers) untuk membuat media yang kaya dan content untuk deployment pada Java environments.

Development kit yang sudah dijelaskan diatas memasukkan API yang dibutuhkan untuk berbagai macam tipe aplikasi apapun yang Anda hasilkan dalam bahasa pemrograman Java.

Java API adalah kumpulan (libraries) dari kode yang sudah disusun, untuk menambahkan fungsionalitas yang sudah dibuat dan dapat dirubah, sehingga menghemat waktu coding.

Program-program Java dieksekusi dalam program yang dinamakan JVM (Java Virtual Machine) daripada dijalankan langsung pada sistem operasi (native operating systems), program di-interpreted oleh JVM untuk native operating systems. Hal tersebut membuat program yang ditulis dengan bahasa Java dapat berjalan dari satu platform ke platform lainnya. Dengan kata lain kita dapat membuat program di Solaris, Linux, Macintosh, atau Windows, dan dapat dijalankan pada server atau platform yang lain.

Membuat Program Java dengan Three Basic Flavors

Setelah Anda memiliki development kit yang dibutuhkan, baru kita bisa menulis program dalam bahasa Java. Kita dapat menulis program dengan tiga basic flavors, yaitu applet, aplikasi dan servlets/JSP pages. Applet berjalan dalam JVM yang ditambah ke dalam web browser, aplikasi berjalan dalam JVM yang ter-install dalam sistem komputer, dan yang terakhir servlets/JSP berjalan dalam JVM yang ter-install dalam web server.

Sedangkan applet dan aplikasi biasanya memiliki suatu antar muka (user interface) yang dipasangkan dengan fungsionalitas backend, servlet hanya menyediakan fungsionalitas backend saja.

Antar muka yang digunakan untuk servlet biasanya dalam bentuk HTML pada browser yang men-invoke servlet, tetapi setiap applet atau aplikasi yang membuka permintaan Hypertext Transfer Protocol (HTTP) dapat memanggil sebuah servlet. Dan sebaliknya, JSP, menggabungkan servlet dan HTML ke dalam satu komponen. Selain menggunakan halaman HTML dengan servlet terpisah, Anda bisa menggunakan halaman HTML dengan tag HTML yang biasa (regular) dengan gabungan scriptles, potongan-potongan pendek kode. Seluruh halaman lalu mengolahnya ke dalam servlet ketika diakses atau diserahkan dan hasilnya kembali ke halaman HTML yang sama, yang mengandung kode tersebut.

Sumber

1. Nourie, D., and Pawlan, M., “Introduction to Java Platform”, Updated July 2007, http://java.sun.com/new2java/programming/intro/

So here's my first MIDlet or mobile java mobile edition program for mobile phones.  I wanted to have a Rubik's Cube scrambler and timer application on my phone so I could cube on the road. It's very basic and doesn't include a database with highscores and averages maybe I'll include that in the future.

You can download the application here (rightclick, /saveas): http://taggle.110mb.com/CubeMobile.jar

]]> http://alyssontmv.wordpress.com/?p=71 Mon, 30 Jun 2008 16:47:50 +0000 alyssontmv http://alyssontmv.pt-br.wordpress.com/2008/06/30/java-dicas-e-tutoriais/ Outro bom site de dicas Java SE, Java EE, Java ME é o

http://www.java-tips.org/

O site é em Inglês.

Até a próxima!

"Java Platform, Enterprise Edition (Java EE) builds on the solid foundation of Java Platform, Standard Edition (Java SE) and is the industry standard for implementing enterprise-class service-oriented architecture (SOA) and next-generation web applications".

Sederhananya, ini adalah edisi Java yang dipakai untuk mengembangkan aplikasi berskala besar atau enterprise. Edisi lainnya, Java SE (Standard Edition) adalah Java yang selama ini gw pakai untuk mengembangkan aplikasi desktop kecil2an). Dan satunya lagi, Java ME (Micro Edition) sesuai namanya, untuk mengembangkan aplikasi untuk perangkat kecil seperti PDA, handphone, dll. Jadi alih2 menggunakan Java SE yang selama ini gw pakai, sekarang gw akan mulai belajar dan menggunakan Java EE. Pak Endy Muhardin berbaik hati memberikan tips bagaimana mulai belajar Java EE di sini.

Sekarang balik lagi ke Spring. Ketika bicara tentang Spring, maka akan sering sekali terdengar istilah Inversion of Control (IoC) dan Dependency Injection. Gw sebagai pendatang baru dalam dunia Spring ini tentu saja bingung dengan kedua istilah itu. Untunglah ada forum berbahasa Indonesia yang membahas mengenai hal2 tersebut. Ada juga contoh yang bagus dari http://www.devx.com/Java/Article/21665. Jadi mari lihat contoh berikut ini.

Misalnya gw mo buat suatu class yang bertugas memproses data, dalam arti membaca data dari suatu file dan memberikan data dari file tersebut pada class yang memanggilnya. Namanya class DataProcessor.

class DataProcessor
{
public Result processData()
{
FileDataReader dataReader = new FileDataReader("/data/file1.data");
Data data = dataReader.readData(); //membaca data
return data.calculateResult(); //mengembalikan data pada class yang memanggilnya
}
}

Ini dia potongan class yang memanggil si DataProcessor (disebut client code).

//client code:
DataProcessor fileDataProcessor = new DataProcessor(); //membuat objek DataProcessor
Result result = fileDataProcessor.processData(); //meminta data dari hasil pembacaan file

Di sini terlihat DataProcessor bergantung atau dependent pada FileDataReader. Kalau mau membaca data dari sumber lain, misalnya database, class DataProcessor harus direfactor, biar bisa menerapkan pembacaan data yang lebih general. Salah satu caranya dengan menggunakan interface.

interface DataReader {
public Data readData(); }

class DataProcessor
{
private DataReader dataReader;

public DataProcessor(DataReader reader) {
this.dataReader = reader; }

public Result processData() {
Data data = dataReader.readData();
return data.calculateResult(); }
}

//client code:
FileDataReader dataReader = new FileDataReader("/data/file1.data");
DataProcessor fileDataProcessor = new DataProcessor(dataReader);
Result result = fileDataProcessor.processData();

DataProcessor tidak lagi beroperasi pada objek FileDataReader, melainkan pada interface DataReader yang diimplementasikan oleh FileDataReader sehingga lebih generic dan reusable. Masalahnya, setiap client code yang mau memproses data harus membuat objek data reader sendiri dan me-link objeknya dengan DataProcessor. Daripada begitu, kita bisa menginjeksikan kebergantungan (inject the dependency) antara DataReader dengan DataProcessor dengan factory class. Factory ini istilah yang baru gw kenal juga. Jadi ditambahankanlah class DataProcessorFactory ini dan client code-nya menggunakan jasa si factory untuk membuatkan reference ke DataProcessor.

class DataProcessorFactory
{
public static DataProcessor getFileDataProcessor()
{
DataReader reader = new FileDataReader("/data/file1.data");;
DataProcessor dataProcessor = new DataProcessor(reader);
return dataProcessor;
}
}

//client code:
DataProcessor fileDataProcessor = DataProcessorFactory.getFileDataProcessor();
Result result = fileDataProcessor.processData();

Si factory-lah yang membuatkan objek dari DataProcessor untuk client. Client tinggal meminta objek dan data hasil baca file melalui factory. Dengan ini telah terjadi apa yang namanya Inversion of Control dengan cara Dependency Injection (DI). Bentuk IoC yang lain adalah Dependency Pull, tapi gw belum ngerti itu.

Semakin besar aplikasi yang dibuat, semakin banyak factory class yang diperlukan. Ini gak menguntungkan karena kebanyakan factory itu merupakan singleton sederhana, yang tugasnya membuat dan menghubungkan objek2, nggak bisa di-inherit sehingga banyak duplikasi. Kelebihan DI dengan Spring, menurut DevX.com adalah
"... its ability to act as a factory to create objects. Spring reads a schematic defined in an external configuration file, creates and wires the objects together using reflection, and then passes the objects back to you. Think of Spring as a factory that you don't have to write any code for."

Intinya, Spring membuatkan dan menghubungkan objek2 melalui skema yang didefiniskan di configuration file eksternal, dalam hal ini file XML (gw gak tau hanya bisa XML file apa bisa yang lain). Langsung aja ke contoh kodenya. Client code akan menjadi seperti ini.

//client code:
InputStream is = new FileInputStream("src/examples/spring/beans.xml");
BeanFactory factory = new XmlBeanFactory(is);

DataProcessor dataProcessor = (DataProcessor) factory.getBean("fileDataProcessor");
Result result = dataProcessor.processData();

dan file XMLnya seperti ini.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" "http://www.springframework.org/dtd/spring-beans.dtd">

<beans>
<bean name="fileDataProcessor"
class="examples.spring.DataProcessor"
singleton="true">
<constructor-arg>
<ref bean="fileDataReader"/>
</constructor-arg>
</bean>
<bean name="fileDataReader"
class="examples.spring.FileDataReader"
singleton="true">
<constructor-arg>
<value>/data/file1.data</value>
</constructor-arg>
</bean>
</beans>

Selalu dibungkus dengan tag <beans></beans>, di dalamnya bisa ada banyak tag <bean>, yang merepresentasikan objek di code Java yang kita buat. Contohnya pada code XML di atas, bean name yang pertama adalah "fileDataProcessor", ini adalah identifier untuk objek bertipe DataProcessor (class="examples.spring.DataProcessor"). Singleton = true artinya gw rasa mirip2 static di Java, jadi setiap kali ada request dari client, Spring akan selalu memberikan instance yang sama. Kalau singleton diset false, Spring akan membuat bean (instance kali ya maksudnya) yang berbeda untuk setiap request. Dalam tag <constructor-arg>, <ref bean="fileDataReader"/> berarti passing objek dengan id "fileDataReader" untuk constructornya. Dari tag bean yang kedua bisa kita lihat bahwa "fileDatReader" ini nama instance dari class FileDataReader. Bean yang kedua ini mempassing nilai ke constructornya (lihat <value>/data/file1.data</value>).

Sampai saat ini itulah yang gw pahami. Masih belum mengerti hal2 lain seperti AOP, DAO, dan ORM. Kesimpulan tentang Spring, katanya sih framework yang satu ini sangat mantep sekali. Ini garis besarnya

• Spring bertujuan untuk meminimalkan dependency antar komponen aplikasi dan menyediakan plug-in architecture. Mungkin inilah yang mendukung terjadinya dynamic workflow seperti yang dijelaskan supervisor KP gw kemaren. Jadi kita bisa pasang komponen aplikasi saat runtime tanpa perlu bongkar kode Java-nya.
• Object linking di Spring didefinisikan di file XML, jadi kita bisa memasang komponen atau konfigurasi yang berbeda saat runtime.
• Berbeda dengan factory yang invasive, di mana client sangat tergantung pada factory karena meminta objek ke sana, Spring menyediakan reference objek ke client yang membutuhkan. Spring secara aktif merangkai dependency dari objek yang gak kenal satu sama lain menjadi aplikasi yang utuh.
• Kemampuannya ini berguna banget buat Test-Driven-Development di Xtreme Programming (gw gak terlalu ngerti ini). Tapi mungkin artinya adalah bisa memudahkan untuk testing sana sini. Karena kode2 gak saling kenal, tp kalo mau disatuin juga gampang. Client gak perlu membuat objek baru (gak pernah membuat reference dengan keyword new), gak perlu lookup ke factory, Spring yang menyediakan dependency-nya secara runtime--dengan real maupun mock object.
• Unit testing jadi mudah dilakukan karena gak ada dependecy yang hard-code, class2 yang ada saling gak kenal satu sama lain.

sumber2 bacaan:
http://dotnet.netindonesia.net/?0::21357
http://www.devx.com/Java/Article/21665
http://arfan86.blogspot.com/2007/02/chating-tentang-spring-framework.html

If you are a mobile developer, you are always being confronted with the Flash Lite vs Java discussion. You may have noticed that more devices these days are supporting Adobe Flash Lite. According to the latest figures, approximately 500 million devices in the market support some form of the Flash Lite specification. That's not that much compared to the 1.2 billion Java ME devices that are currently available

Bruce Hopkins thought that it would be worthwhile to see the strengths and weaknesses of each platform side by side. He is comparing the latest and greatest specifications for both platforms in the following categories

Graphics
Multimedia
Local Device Accessibility
Security
Network Connectivity
Miscellaneous

Definately check out the whole article.

He concludes saying each platform has its own strengths and weaknesses when it comes to mobile application development. Flash Lite-enabled devices are really good at displaying graphics and multimedia, which lends itself to several gaming applications. On the other hand, devices that support the Java ME MSA platform are the obvious choice when you need to communicate with Bluetooth devices, use location based services, capture audio/video, render 3D graphics, or perform any form of asynchronous communication.

To make your applications as ''rich'' as possible you should try to combine both technologies. Use Flash lite to build up a stunnig visual Mobile Interface and try to use Jave ME to expand your app and provide all sorts of functionalities like Reading/Writing phone data, use Bluetooth, Camera, Contact List acces..

This should already be possible using the Jarpa Framework. Created by Felipe Andrade and Alessandro Pace, Jarpa is a free of charge software solution under terms of Apache Software License. You can make richer apps using this framework but you should know it does not work on every phone.

get a list of Compatible Jarpa Devices

I'm really looking forward using/trying/exploring Jarpa, i'm just waiting for some more source code examples in their "How To" section. If you guys should read this, can you give us some more insight on that?

A while ago Sony Ericsson, has made significant progress on bridging the gap between both platforms with its Capuchin technology, which was announced in late April: "...a Java ME API that defines a bridge between the Java ME and Adobe Flash Lite programming environments. This API makes it possible to use Flash Lite as the front end and Java ME as the back end of applications, meaning that Flash tools can be used for UI design while still having access to all the phone services available to Java ME.

Looks promising!

Beberapa hari menjelang UAS nih bro. Hari hari kritis dimana sebagian besar mahasiswa digilas oleh tugas bertubi tubi sebagai sesajen pada dosen dupaya terhindar dari jurang ketidak lulusan, hehehe. Tapi disaat kritis seperti ini pun, saya masih belum sepenuhnya konsen ke kuliah  yang part-time semester ini.

Ada ajakn dari seorang teman buat bikin game mobile. Awalnya rada ragu dan keder soalnya belum pernah utak atik java mobile. For the sake of the development of indonesian IT human resource (hueeek), akhirnya saya nerima juga tawaran itu. Mulai bongkar bongkar flazx deh saya buat nyari ebook mobile development. Salah satunya yang  berhasil saya download adalah ini.

Bisa didapatkan secara gak bener disini

Setelah dapet ebooknya, mulai deh memanaskan IDE satu-untuk-semua Netbeans 6.0. Karena IDE ini sepengetahuan saya terdapat fitur Mobile Developmentnya. Oke, mulai deh oprek kecil kecilan.

Netbeans6.0 menyediakan fasilitas lengkap buat newbie seperti saya yang ingin mencoba games development pake java. Jika menginstall netbeans 6 yang full version atau yang mobile version, sudah terinclude didalamnya Sun Wireless Toolkit beserta Emulator hapenya sekalian. Dan yang menyenangkan terdapat fasilitas Visual Game Editor.

Saya mencoba buat project yang tipenya mobile. Pada source folder (/src), di klik kanan.

Visual game design

Terdapat opsi Visual game design disitu. Di dalam Visual game design terdapat 3 opsi utamayaiut Scene design, Tile design dan Sprite design. Saya masih meraba raba mengenai 3 item ini tetapi kesimpulan awal yang saya dapet Scene itu "adegan" pada satu layar didalam game, Tiles adalah background atau landmarknya dan Sprite adalah gerakan yang terjadi dalam game.

Visual game editor pada netbeans 6.0.1

Untuk pembuatan sprite misalnya, menu yang ditawarkan oleh netbeans cukup menarik. Seperti pembuatan Form Swing yang tinggal drag and drop, untuk membuat sprite tinggal geret saja gambar yang diload terlabih dahulu dan tempakan pada tiimeline canvas. Netbeans akan membuat sprite gambar tersebut secara otomatis seperti yang fitur Motion Tween pada Adobe Flash. Yang saya coba dibawah menggunakan paket gambar sample dari netbeans sendiri.

Sprite editor

Cukup Mudah ternyata untuk sekedar membuat karakter berjalan. Framerateya juga bisa diatur di sini.

Masih sebegitu ajah explore saya untuk hari ini temen temen. Masih donlot SDK Symbian, mau develop di Hape Nokia soalnya. Kalau ada hal menarik akan saya coba posting lagi. Thanx for reading temen temen.

Keep In java.

:)

After having several workshops, events and a tough competition, Swedish Game Awards 2008 final event, the Grand Finale, will take place on the 24th of May 2008, at Kulturhuset Stockholm, Hörsalen on the 3rd Floor. Here is a brief timeplan of what will happen:

Grand Finale Timeplan

11:00-16:00 – Games Career Expo
During the day, the Games Career Expo will be open to the public in Hörsalen on the 3rd floor, Kulturhuset Stockholm. At the Expo you will be able to try out the nominated games and meet our partners. During the Expo, all submitted trailers will be shown in segments, you will also be able to meet some of last years winners and see how their games have evolved.

17:00-18:30 – Prize Ceremony
The Price Ceremony starts at 17:00 in Hörsalen on the 3rd floor, Kulturhuset Stockholm. Orvar Säfström will be hosting the Prize Ceremony where the the winners of Swedish Game Awards 2008 will be announced.

19:00 – Exlusive Dinner and Afterparty
All nominees will be invited to the exlusive Dinner and Afterparty after the Price Ceremony.

Two excellent mobile games have been nominated for the Java ME/Netbeans prize for 10 000 SEK, Swarm and Blocko; both teams will show off their games during the expo.

For me the best thing is NetBenas 6.1 IDE is opening very fast, and it was the most exciting thing for me. I really suggest you to download the NetBeans 6.1 and use it, I am pretty sure that you will like it.

Berikut adalah informasi lengkap yang diambil dari website di atas :

Sony Ericsson's new Project Capuchin bridges Java ME and Flash Lite

April 30, 2008
Sony Ericsson's new Project Capuchin bridges Java ME and Flash Lite

On April 30, 2008 Sony Ericsson announced its new Project Capuchin technology which is a Java ME API that defines a bridge between the Java ME and Adobe Flash Lite programming environments. This API makes it possible to use Flash Lite as the front end and Java ME as the back end of applications, meaning that Flash tools can be used for UI design while still having access to all the phone services available to Java ME.

Below you will find an overview of this new bridging technology, a summary of how it works and usage examples.

Sony Ericsson's Project Capuchin Overview
Project Capuchin allows developers to combine the richness of both Java ME and Flash Lite by encapsulating Flash Lite content in Java ME applications making content created by Adobe Flash technology appear as Java ME applications. Project Capuchin empowers these two distinct developer communities to leverage their respective expertise to quickly and securely create highly engaging mobile content.

Project Capuchin is a bridging technology between Java ME and Flash Lite making it possible to take advantage of Flash's strengths in fast UI deployment and well established designer tools, meanwhile Java's strengths are in services, security and a well developed distribution infrastructure. Project Capuchin makes it possible to create Java applications where some or all UI components are defined in Flash Lite and where all services can be accessed through Java.

Project Capuchin is proprietary Sony Ericsson technology and will be made available for developers to use for free during the second of half of 2008.

How does Project Capuchin Work?

Project Capuchin is a Java ME API which makes it possible for Java to run a Flash Lite content file (*.swf) that is shown on the display. All system events (e.g. key events) are forwarded from Java to Flash Lite and the Flash Lite player has a choice of listening to these events. In case Flash Lite wants to access some information then it is done through Java. Communication between Flash Lite and JSRs are handled through an intermediate class that works as a translator. This class listens to Flash Lite requests, transfers these to JSR calls, and sends response back to Flash Lite. Communication between Flash Lite and Java is bi-directional meaning that Flash Lite can send requests to and receive events from Java. Requests send from Flash Lite are made in an asynchronous manner.

Project Capuchin model

Different approaches to using Project Capuchin

Project Capuchin can be used in different ways to create innovative content and here are some examples:

• Pure Flash Lite Content (Full Flash UI and services, no Java ME access):
  The simplest form of using this technology is to take pure Flash Lite content (e.g. already existing games and apps developed in Flash) and encapsulate it in MIDlet suites (*.jar) using Sony Ericsson's soon-to-be-available packaging tools. The benefit of this approach is that this Flash Lite content will be treated in the same manner as Java content, thus will use the same distribution infrastructure and system capabilities as Java ME content.
• Java MIDlet using Project Capuchin as UI presentation layer (full Flash UI, Java Services):
  More advanced use of Project Capuchin is to let Flash Lite handle the entire presentation layer and use Java as a service provider which feeds the presentation layer with necessary data.
• Java MIDlet using Project Capuchin for some UI components (Java UI and Flash UI, Java Services):
  In some cases such as 3D games, it is not feasible to use Flash Lite as a full presentation layer yet this should be handled using suitable Java technology (e.g. Mascot API, JSR 184 or JSR 239). In these cases, Project Capuchin could be used for presentation of some UI components, for example menus in 3D games.

More information, documentation and tools support will be made available on Developer World over the next few months.

More information:

• Read Sony Ericsson's official Project Capuchin press release>>

Por lo poco que he visto, la principal novedad es el soporte SVG mejorado.

Vía: NetBeans Mobility 6.1 (final) is now available

Uma dúvida me veio logo depois de ler um artigo da revista Web Mobile, edição 17 foi como colocar a midlet criada dentro do celular. Procurando por essa informação, descobri que no site da nokia, além de um FAQ, tem uma série de tutoriais muito bons. Eles ainda os classificaram em "Basic", "Intermediate" e "Advanced". Depois de clicar nela, você pode baixá-la em PDF. Vale a pena conferir!

P.S.: Ainda não aprendi a colocar a midlet dentro do celular. Se alguém souber, por favor deixe um recado aqui mesmo. Valeu!

Fiquem com Deus

Here you can watch a sample project from KTH Campus Ambassadors and Kenneth.

After the presentation some of the students asked about the presentation slides. Here you can re-check the slides. If you need more and deeper information please do not hesitate to contact with us.

[slideshare id=372475&doc=sunspot-1209143864018913-8&w=425]

• Sun Certified Programmers earn on average 8.3% more than the average programmer
• Sun Certified Developers earn on average 14.3% more than the average developer
• Sun Certified System Administrators earn on average 31% more than system administrators certified on other operating systems

Clearly, if you're looking to have an edge, technology training through the Sun Academic Initiative can offer materials for mastery of skills that will propel students into fulfilling careers right from the start.

For the online course catalog, you can check here.

Please contact with us for the registration instructions

Download Podcast 

The R1EA030 firmware includes Java Platform 8.2 and Sony Ericsson seem to have done some major screw tightening.  The main things I have noticed so far are general speed improvements and much better audio support in Java.

Hopefully all future A200 models will come with Java Platform 8.2 at least and Sony Ericsson can put some of the firmware woes that plagued early A200 phones behind it.  If you have older firmware on your W910i I highly recommend upgrading - just download the Sony Ericsson Update Service tool from http://www.sonyericsson.com/cws.

Recapitulando

GPSDemo es una aplicación para BlackBerry que hace uso de la API JSR-179 para mostrar información de la posición y velocidad obtenidas de un dispositivo GPS o similar (ver la entrada Leyendo nuestro GPS desde Java con la JavaME Location API (JSR-179) - Parte I para una explicación de las posibles fuentes de información).

Habíamos dejado pendiente de describir el método startLocationUpdate() que se llama desde el constructor de la clase GPSDemo:

private void startLocationUpdate()
{
try
{
_locationProvider = LocationProvider.getInstance(null);
if ( _locationProvider == null )
{
Dialog.alert("GPS is not supported on this platform, exiting...");
System.exit(0);
}
_locationProvider.setLocationListener(new LocationListenerImpl(), _interval, 1, 1);
}
catch (LocationException le)
{
System.err.println("Failed to add a location listener. Exiting...");
System.err.println(le);
System.exit(0);
}
}

Lo primero que hacemos es obtener un proveedor de contenidos, con los criterios por defecto. En caso de no poder obtener uno, salimos de la aplicación.
La otra cosa que hace este método es establecer el objeto responsable de escuchar la información que llega del GPS. La variable _internal se estableció previamente al valor 1, con lo que la información se actualizará aproxamadamente una vez por segundo. Los dos últimos parámetros establecen el timeout y la caducidad de los datos.
Para actuar como listener del GPS una clase debe implementar la interfaz LocationListener.

La clase LocationListenerImpl

De forma más bien descriptiva, la clase listener de nuestro ejemplo se llama LocationListenerImpl:

private class LocationListenerImpl implements LocationListener
{
// Members. --------------------------------------------------------------
private int captureCount;

public void providerStateChanged(LocationProvider provider, int newState)
{
// No operation defined.
}
...

La interfaz tiene dos métodos. providerStateChanged nos avisa de los cambios de estado de nuestro proveedor de localización, básicamente cuando deja de estar disponible por algún tipo de problema; como estamos pensando sólo en el GPS, que no va a quedar fuera de servicio, no implementamos este método.
El otro método es el que nos avisa de que el GPS ha suministrado una nueva localización:

public void locationUpdated(LocationProvider provider, Location location)
{
if(location.isValid())
{
float heading = location.getCourse();
double longitude = location.getQualifiedCoordinates().getLongitude();
double latitude = location.getQualifiedCoordinates().getLatitude();
float altitude = location.getQualifiedCoordinates().getAltitude();
float speed = location.getSpeed();
// Horizontal distance.
float horizontalDistance = speed * _interval;
_horizontalDistance += horizontalDistance;
// Horizontal distance for this waypoint.
_wayHorizontalDistance += horizontalDistance;
// Distance over the current interval.
float totalDist = 0;
// Moving average grade.
for(int i = 0; i 0) _verticalDistance = _verticalDistance + altGain;
captureCount += _interval;
// If we’re mod zero then it’s time to record this data.
captureCount %= CAPTURE_INTERVAL;
// Information to display on the device.
StringBuffer sb = new StringBuffer();
sb.append("Longitude: " + longitude+ "\n");
sb.append("Latitude: " + latitude+ "\n");
sb.append("Altitude: " + altitude + " m\n");
sb.append("Heading relative to true north: " + heading + "\n");
sb.append("Speed : " + speed + +" m/s\n");
sb.append("Grade : ");
if(Float.isNaN(grade))
sb.append(" Not available");
else
sb.append(grade+" %");
GPSDemo.this.updateLocationScreen(sb.toString());
}
}

Mucho código, pero muy simple. Se nos pasa como parámetros el LocationProvider, que no necesitamos, y un objeto Location que contiene, además de las coordenadas, la velocidad, la dirección y un método (isValid()) que nos dice si el objeto Location tiene coordenadas o no. En caso de utilizar como proveedor de contenidos un servicio de pago del operador, podríamos tener información adicional en el mismo objeto, como una dirección postal.

Código de GPSDemo.java

/**
* A GPS sample application using the JSR 179 APIs.
*
* Copyright (C) 2005 Research In Motion Limited.
*/
package com.rim.samples.docs.gpsdemo;
import net.rim.device.api.ui.*;
import net.rim.device.api.ui.component.*;
import net.rim.device.api.ui.container.*;
import com.rim.samples.docs.baseapp.*;
import net.rim.device.api.io.*;
import net.rim.device.api.system.*;
import net.rim.device.api.i18n.*;
import javax.microedition.io.*;
import java.util.*;
import java.io.*;
import javax.microedition.location.*;
import net.rim.device.api.util.*;
import com.rim.samples.docs.resource.*;
/* This application acts as a simple travel computer, recording route coordinates,
* speed, and altitude.
* Recording begins as soon as the application is invoked.
*/
public class GPSDemo extends BaseApp implements GPSDemoResResource
{
// Constants. ----------------------------------------------------------------
// The number of updates in seconds over which the altitude is calculated.
private static final int GRADE_INTERVAL=5;
// com.rim.samples.docs.gpsdemo.GPSDemo.ID
private static final long ID = 0x4e94d9bc9c54fed3L;
private static final int CAPTURE_INTERVAL=10;
// Statics. ------------------------------------------------------------------
private static ResourceBundle _resources =
ResourceBundle.getBundle(GPSDemoResResource.BUNDLE_ID, GPSDemoResResource.BUNDLE_NAME);
// The period of the position query in seconds.
private static int _interval = 1;
private static Vector _previousPoints;
private static float[] _altitudes;
private static float[] _horizontalDistances;
private static PersistentObject _store;
// Initialize or reload the persistent store.
static
{
_store = PersistentStore.getPersistentObject(ID);
if(_store.getContents()==null)
{
_previousPoints= new Vector();
_store.setContents(_previousPoints);
}
_previousPoints=(Vector)_store.getContents();
}
private long _startTime;
private float _wayHorizontalDistance;
private float _horizontalDistance;
private float _verticalDistance;
private ListField _listField;
private EditField _status;
private StringBuffer _messageString;
private String _oldmessageString;
private LocationProvider _locationProvider;
/* Instantiate the new application object and enter the event loop.
* @param args unsupported. no args are supported for this application
*/
public static void main(String[] args)
{
new GPSDemo().enterEventDispatcher();
}
// Constructors. -------------------------------------------------------------
public GPSDemo()
{
// Used by waypoints; represents the time since the last waypoint.
_startTime = System.currentTimeMillis();
_altitudes=new float[GRADE_INTERVAL];
_horizontalDistances=new float[GRADE_INTERVAL];
_messageString= new StringBuffer();
MainScreen screen = new MainScreen();
screen.setTitle(new LabelField(_resources.getString(GPSDEMO_TITLE), LabelField.USE_ALL_WIDTH));
_status = new EditField();
screen.add(_status);
screen.addKeyListener(this);
screen.addTrackwheelListener(this);
// Start the GPS thread that listens for updates.
startLocationUpdate();
// Render our screen.
pushScreen(screen);
}
/* Update the GUI with the data just received.
*/
private void updateLocationScreen(final String msg)
{
invokeLater(new Runnable()
{
public void run()
{
_status.setText(msg);
}
});
}
// Menu items. ---------------------------------------------------------------
// Cache the markwaypoint menu item for reuse.
private MenuItem _markWayPoint = new MenuItem(_resources, GPSDEMO_MENUITEM_MARKWAYPOINT, 110, 10)
{
public void run()
{
GPSDemo.this.markPoint();
}
};
// Cache the view waypoints menu item for reuse.
private MenuItem _viewWayPoints = new MenuItem(_resources, GPSDEMO_MENUITEM_VIEWWAYPOINTS, 110, 10)
{
public void run()
{
GPSDemo.this.viewPreviousPoints();
}
};
// Cache the close menu item for reuse.
private MenuItem _close = new MenuItem(_resources, GPSDEMO_MENUITEM_CLOSE, 110, 10)
{
public void run()
{
System.exit(0);
}
};
protected void makeMenu(Menu menu, int instance)
{
menu.add( _markWayPoint );
menu.add( _viewWayPoints );
menu.add( _close );
menu.addSeparator();
super.makeMenu(menu, instance);
}
/* Invokes the Location API with the default criteria.
*/
private void startLocationUpdate()
{
try
{
_locationProvider = LocationProvider.getInstance(null);
if ( _locationProvider == null )
{
Dialog.alert("GPS is not supported on this platform, exiting...");
System.exit(0);
}
// A single listener can be associated with a provider,
// and unsetting it involves the same call but with null,
// so there is no need to cache the listener instance.
// Request an update every second.
_locationProvider.setLocationListener(new LocationListenerImpl(), _interval, 1, 1);
}
catch (LocationException le)
{
System.err.println("Failed to add a location listener. Exiting...");
System.err.println(le);
System.exit(0);
}
}
/* Marks a point in the persistent store. Calculations are based on
* all data collected since the previous way point, or from the start
* of the application if no previous waypoints exist.
*/
private void markPoint()
{
long current = System.currentTimeMillis();
WayPoint p= new WayPoint(_startTime, current, _wayHorizontalDistance, _verticalDistance);
addWayPoint(p);
// Reset the waypoint variables.
_startTime = current;
_wayHorizontalDistance = 0;
_verticalDistance = 0;
}
// View the saved waypoints.
private void viewPreviousPoints()
{
PointScreen pointScreen = new PointScreen(_previousPoints, _resources);
pushScreen(pointScreen);
}
// Called by the framework when this application is losing focus.
protected void onExit()
{
if ( _locationProvider != null )
{
_locationProvider.reset();
_locationProvider.setLocationListener(null, -1, -1, -1);
}
}
/* Adds a new WayPoint and commits the set of saved waypoints
* to flash memory.
* @param p The point to add.
*/
/*package*/
synchronized static void addWayPoint(WayPoint p)
{
_previousPoints.addElement(p);
commit();
}
/* Removes a waypoint from the set of saved points and
* commits the modifed set to flash memory.
* @param p the point to remove
*/
/*package*/
synchronized static void removeWayPoint(WayPoint p)
{
_previousPoints.removeElement(p);
commit();
}
// Commit the waypoint set to flash memory.
private static void commit()
{
_store.setContents(_previousPoints);
_store.commit();
}
/* Implementation of the LocationListener interface.
*/
private class LocationListenerImpl implements LocationListener
{
// Members. --------------------------------------------------------------
private int captureCount;
// Methods. --------------------------------------------------------------
public void locationUpdated(LocationProvider provider, Location location)
{
if(location.isValid())
{
float heading = location.getCourse();
double longitude = location.getQualifiedCoordinates().getLongitude();
double latitude = location.getQualifiedCoordinates().getLatitude();
float altitude = location.getQualifiedCoordinates().getAltitude();
float speed = location.getSpeed();
// Horizontal distance.
float horizontalDistance = speed * _interval;
_horizontalDistance += horizontalDistance;
// Horizontal distance for this waypoint.
_wayHorizontalDistance += horizontalDistance;
// Distance over the current interval.
float totalDist = 0;
// Moving average grade.
for(int i = 0; i 0) _verticalDistance = _verticalDistance + altGain;
captureCount += _interval;
// If we’re mod zero then it’s time to record this data.
captureCount %= CAPTURE_INTERVAL;
// Information to display on the device.
StringBuffer sb = new StringBuffer();
sb.append("Longitude: " + longitude+ "\n");
sb.append("Latitude: " + latitude+ "\n");
sb.append("Altitude: " + altitude + " m\n");
sb.append("Heading relative to true north: " + heading + "\n");
sb.append("Speed : " + speed + +" m/s\n");
sb.append("Grade : ");
if(Float.isNaN(grade))
sb.append(" Not available");
else
sb.append(grade+" %");
GPSDemo.this.updateLocationScreen(sb.toString());
}
}
public void providerStateChanged(LocationProvider provider, int newState)
{
// No operation defined.
}
}
/* WayPoint describes a way point, a marker on a journey or point of interest.
* WayPoints are persistable.
* package
*/
static class WayPoint implements Persistable
{
public long _startTime;
public long _endTime;
public float _distance;
public float _verticalDistance;
public WayPoint(long startTime,long endTime,float distance,float verticalDistance)
{
_startTime=startTime;
_endTime=endTime;
_distance=distance;
_verticalDistance=verticalDistance;
}
}
}

Entradas relacionadas:
Un ejemplo de aplicación Java para BlackBerry - Parte I
Un ejemplo de aplicación Java para BlackBerry - Parte II
Un ejemplo de aplicación Java para BlackBerry - Parte III
Un ejemplo de aplicación Java para BlackBerry - Parte IV y final
Leyendo nuestro GPS desde Java con la JavaME Location API (JSR-179) - Parte I

And if you are already familiar with NetBeans ( we hope so :) ) , you should have a look at Netbeans Mobility Pack 6.0 and the Game Builder to create games easily. Here is a great tutorial to begin creating great games. Who knows maybe you will even win the competition !

This is also because I have been working on my own (very) simple MVC framework for Java ME applications. I made the first check-in to Google code this evening. The unit testing leaves a lot to be desired as I still trying to get to grips with unit JMUnit. Having said that, its a milestone as the code is now out there in the ether.

I had an idea there last week for a novelty application (All will be revealed soon). I thought I may as well implement MVC pattern. Then I thought - sure while I am at it, I may as well make it reusable.

Here's some rough diagrams of the MVC base classes and Calculator sample:

As mentions the frameworks is quite simple and (for the most part) self explanatory provided you are familiar with the MVC pattern.

The source code is available here. You will need Netbeans 6.0 to run the code.

I am working on a multithreaded example which I hope to post up soon. In the meantime, I would love to get some feedback or if anyone would like to contribute to the project please let me know.

I have been working a little Java ME app in which I needed to shuffle and array of objects. I may be wrong, but I seems I can't use generic collections on Java ME platform, so I am using Vectors. I am trying to use strongly typed wrappers for the Vector instances much as possible.

Anyway, in this code sample I have extended the Vector class adding the ability to shuffle the Objects it contains by calling the shuffle() method.

   1: import java.util.*;

   2:  

   3: public class ShuffleVector extends Vector {

   4:  

   5:     public void shuffle() {

   6:         int index, randomIndex;

   7:  

   8:         Random random = new Random();

   9:         for (index = 1; index < size(); index++) {

  10:             randomIndex = random.nextInt(index + 1);

  11:             swapObjects(index, randomIndex);

  12:         }

  13:     }

  14:  

  15:     private void swapObjects(int index, int randomIndex) {

  16:         Object temp = this.elementAt(index);

  17:         this.setElementAt(this.elementAt(randomIndex), index);

  18:         this.setElementAt(temp, randomIndex);

  19:     }

  20: }

O Jarpa, uma criação de Felipe Andrade e Alessandro Pace, integra funcionalidades do Flash Lite com Java ME, já o Flyer integra funcionalidades do Flash Lite e Java ME com Python S60.

O Flyer eu já conhecia e cheguei a fazer alguns testes, mas a quantidade de celulares que suporta Python S60 (que é pouca) me desanimou a continuar, agora com o Jarpa a possibilidade de criar interfaces com Flash Lite e utilizar o poder (e principalmente a penetração nos celulares) do Java ME para manipular informações do aparelho celular me animou a voltar os testes, que vão aparecer por aqui brevemente.

Esta nueva arquitectura, además de mejorar el rendimiento, permitirá a Symbian incluir nuevas librerías propias que aumenten la potencia de las aplicaciones Java para S60 (a costa de perder portabilidad a otras plataformas). Así, ya está anunciado el nuevo kit de desarrollo de interfaces de usuario eSWT, destinado a combatir las limitaciones de LCDUI permitiendo a los desarrolladores Java construir interfaces de usuario similares a las que tienen las aplicaciones nativas.

Habrá que esperar a ver la SDK de la nueva versión de S60 para comprobar qué tal funcionan eSWT y todas la novedades que la nueva Java VM incorpore.

Más información:
http://blogs.s60.com/java/2007/11/new_java_features_of_3rd_ed_fp.html
http://blogs.s60.com/java/2007/10/eswt_available_for_development.html
http://mobilephonedevelopment.com/archives/492

Lleva licencia Apache. Idóneo para fisgar un poco el código de un proyecto open-source para móviles (o incluso animarse a colaborar).

Vía:
Google ZXing (”Zebra Crossing”) is open for business

Entradas relacionadas:
Códigos de barras (barcodes) para móviles