Read the questions that your fellow developers had about the new feature in NetBeans Mobility Pack 4.0 that helps solve device fragmentation problems, and the answers straight from the engineers who created the module.
Tutorial Details:
Welcome to the Sun Developer Network Moderated Chat series. Today's topic is "Solving the Device Fragmentation Problem." My name is Bao Phan and I'm the moderator for this chat. Our speakers today are Greg Crawley, David Kaspar, and Adam Sotona, Software Engineers for the NetBeans Mobility Pack IDE.
Just a couple of housekeeping notes before we begin:
You are connected to our chat application, and your session must be maintained in order to stay connected. Please do not point your current browser to another URL, otherwise you will be dropped from the chat. You may open up another browser if you need to access another URL while staying connected to the chat.
When you submit a question to the speakers, your question will not immediately appear in the chat room. It is sent to the speakers and will appear when the speakers post their response to your question.
With that, I'd like to invite you to begin sending your questions to our speakers. To start things off, Greg, can you give us a quick summary of the feature in the NetBeans Mobility Pack that addresses the device fragmentation problem?
gregcrawley
I'll start off with a quick explanation as to what the device fragmentation problem is. We use the term to describe variations found between mobile platforms that prevent a single application from automatically running optimally on all phones. These differences can be physical (like screen size, screen color depth, available memory, etc.) or software-related (available APIs, CLDC/MIDP version, etc.). Fragmentation usually requires modifications to get your single application running on different mobile platforms; managing these modifications is where our solution comes in...
It has two main parts: project settings management and fragmented source code management.
Both portions of the solution are based on the concept of Project Configurations. You can create as many configurations as you'd like for each of your projects -- typically, you will have one for each distribution Jar that you plan on creating for your application. Once the configurations exist, you can update individual panels of the project properties dialog such that the settings will only apply to individual configurations.
Also, you'll be able to mark blocks of source code as being specific to a list of configurations. Individual code blocks will only apply only to those configurations that you have associated with them. An embedded preprocessor is used by NetBeans to place code blocks to a commented-in or commented-out state based on whether or not the block is appropriate to your active configuration.
So that's the solution in a nutshell.
blizzard
Does this solution eliminate the need to have a separate source file for each device I want to target?
gregcrawley
Yes, it does. Because we use a commenting pre-processor, all versions of your code can be stored in a single source file.
Read
Tutorial at: Click here to view the tutorial
Rate Tutorial: Chat Transcript: Solving the Device Fragmentation Problem
View Tutorial: Chat Transcript: Solving the Device Fragmentation Problem
Related
Tutorials:
 Java gets serial support with the new javax.comm package - JavaWorld - May 1998
Java gets serial support with the new javax.comm package - JavaWorld - May 1998
|
Java gets serial support with the new javax.comm package
Java gets serial support with the new javax.comm package
|
Multicast the chatwaves - JavaWorld October 1999
Multicast the chatwaves - JavaWorld October 1999
|
J2SE 1.4.1
boosts garbage
collection
J2SE 1.4.1
boosts garbage
collection
|
Let the mobile
games begin, Part 2
Let the mobile
games begin, Part 2
|
Clean Up Your Mess: Managing Temp Files in Java Apps
Clean Up Your Mess: Managing Temp Files in Java Apps
Creating and managing temporary files in a Java application can be a little tricky due to some open JVM bugs. Develop a workaround with some custom code and a clever design.
|
Here is the jzChat V1.0 servlet (free).
This servlet performs a 100% HTML/JavaScript chatroom. Guest users just have to enter a nickname for chatting. They can choose chat's look&feel. Root user chooses chatroom's name and subject.
|
Chat Transcript: JSP 2.1 Technology and JSF 1.2 Technology
The next release of JavaServer Pages (JSP) technology, JSP 2.1, and the next release of JavaServer Faces (JSF) technology, JSF 1.2, are designed to improve the alignment of these two technologies in the area of expression language, and to enhance their ea
|
What's New in Swing?
A new skinnable look and feel (Synth), printing support for |JTable| components, the ability to add components directly to a frame, these are a few of the new features in Swing for J2SE 5.0.
|
Chat Transcript: Project Looking Glass
Where did the original Looking Glass idea come from? Read the answer to this and other interesting questions about Project Looking Glass, a project that explores the next generation (3-dimensional) desktop.
|
Chat Transcript: New Language Features in J2SE 5.0
Java 2 Platform, Standard Edition (J2SE) 5.0. includes the biggest set of language changes since the original release of the Java programming language.
|
Develop MIDlets using the J2ME MIDP Development for NetBeans IDE 4.0
This release integrates with the J2ME Wireless Toolkit 2.2 to create a powerful environment for developing MIDP 2.0 applications.
|
USB FAQ
FAQ topics include recommended USB patches for the Solaris OS, the USBA 1.0 Framework, libusb support, and more.
|
Device Driver Tutorial for the Solaris OS
Make your hardware work with the Solaris OS on x86 or SPARC architectures. If you are a beginning Solaris kernel programmer, start with this new tutorial on docs.sun.com.
|
Porting Device Drivers for the Solaris Operating System to 64-Bit x86 Architectures
If you need to modify 32-bit device drivers to be compatible with the 64-bit Solaris 10 OS on x86 platforms, refer to this new article.
|
What is WAP? Wireless Application Protocol
What is WAP? Wireless Application Protocol
Tutorial
What is WAP?
W ireless Application Protocol or WAP for short is simply a protocol - a standerized way for delivering Internet data over wireless networks. Thus WAP links Wireless Network with
|
Chat Transcript: Solving the Device Fragmentation Problem
Read the questions that your fellow developers had about the new feature in NetBeans Mobility Pack 4.0 that helps solve device fragmentation problems, and the answers straight from the engineers who created the module.
|
Easy Emulation With New NetBeans Mobility Pack 4.0
With the click of a button, switch back and forth between different emulation environments while developing one set of code. It's never been this easy to take advantage of Java technology's cross-platform capabilities.
|
Chat Transcript: Java Web Services Developer Pack (Java WSDP) 1.5
Learn about the exciting new web services features in the recently-released Java WSDP 1.5.
|
Getting Started With the PIM APIs
This article provides a code-intensive introductory tutorial to Personal information management (PIM) APIs, JSR 75.
|
|
|
|
