使用Java构建移动应用指南

Java

Mobile

需积分: 5 100 浏览量更新于2024-07-17 收藏 8.06MB PDF 举报

身份认证购VIP最低享 7 折!

30元优惠券

"Building Mobile Applications with Java.pdf" 是一本关于使用Java开发移动应用的书籍，由Joshua Marinacci撰写。这本书适用于那些希望用Java语言构建手机应用的学习者，特别是对于学术交流目的。书中可能涵盖了Java在移动平台上的基础知识、Android或Java ME开发环境的设置、用户界面设计、数据存储、网络通信以及性能优化等多个主题。虽然出版时间较早，但Java作为一种强大且广泛使用的编程语言，其在移动应用开发领域的应用仍然具有价值。书中可能讲解了如何利用Java的跨平台特性来创建可以在不同操作系统上运行的应用，包括可能的J2ME框架或者针对Android平台的开发。此外，作者可能还讨论了如何将Java与移动设备的特定功能（如GPS、相机、传感器等）集成，以及如何利用Java库和框架提升开发效率。在内容中提到了O'Reilly Media出版社，这是一家知名的技术图书出版商，通常他们的书籍质量较高，包含丰富的实践案例和深入的理论知识。书的制作团队包括编辑Shawn Wallace和Mike Hendrickson，生产编辑Teresa Elsey，以及封面和内页设计师。此外，书中的错误和更新信息可以在O'Reilly的官方网站上查询。由于书籍未提供具体内容，我们无法详细讨论各个章节的细节。不过，根据一般Java移动开发教材的结构，读者可以期待涵盖以下知识点： 1. **Java基础知识**：包括Java语法、面向对象编程概念以及异常处理。 2. **移动开发环境**：如Eclipse IDE的使用，Android Studio的配置，或者NetBeans对J2ME的支持。 3. **移动应用架构**：讲解如何设计适合移动设备的用户界面，包括触摸屏交互和响应式布局。 4. **数据管理**：介绍SQLite数据库在Android中的应用，或者J2ME中的持久化存储选项。 5. **网络通信**：如HTTP请求、JSON或XML数据交换，以及WebSocket等实时通信技术。 6. **服务与后台处理**：讲解如何在Android中创建服务，或者在J2ME中实现后台任务。 7. **设备API集成**：如何访问设备的硬件特性，如蓝牙、GPS、相机等。 8. **性能优化**：包括内存管理、代码优化和调试技巧。 9. **发布与分发**：介绍如何打包应用、签名验证，以及通过Google Play或其他应用商店发布应用。这本书对初学者和有一定Java基础的开发者来说都是很好的学习资源，它可以帮助读者理解Java在移动设备上的工作原理，并提供实际项目开发的经验指导。

资源详情

资源推荐

GWT that work with the popular Java IDE Eclipse, including nice debugger integration.

However, since the point of this book is to understand what GWT and PhoneGap are

really doing underneath the hood, I won’t use anything IDE-specific. Instead I will work

with the standalone GWT SDK from the command line. The core SDK is just a set of

command line utilities, the jars, and a visual console logger. Just know that once you

learn how it really works you may wish to install optimized tools for your favorite IDE

or Google’s GWT visual designer.

To install GWT, first download the right version for your platform then unzip the

gwt-2.4.zip file. The exact filename may be different if you downloaded a version other

than 2.4. At the time of this writing, 2.4 was the latest stable version. Move the resulting

gwt-2.4.0 directory to wherever you normally work on projects.

From the command line run

gwt-2.4.0/webAppCreator -out MyFirstApp com.mycompanyname.MyFirstApp

This is the first step to creating any new GWT project. It will generate a new project

directory with the package and name specified. It doesn’t really matter where you create

the project. GWT will set up the correct links between your project and the GWT libs.

The webAppCreator will create a new directory filled with a default app. Let’s take a

quick look at the directory structure:

• MyFirstApp, the directory containing your new app

• MyFirstApp/src contains the Java source for the app. The generated source will use

the package name specified above. For example, src/com/mycompanyname/MyFirst

App.java

• MyFirstApp/war, the directory containing the web resources for your app. Anything

in here will be bundled into a final WAR file for deploying on a Java Servlet Con-

tainer. (Don’t worry, the servlet part isn’t required. Hold on a sec). This is where

you will put additional images, CSS files, and other web resources.

• MyFirstApp/build.xml An Ant build script to build, test, and compile the app.

To test your app run ant devmode from inside the MyFirstApp directory. This will open

the GWT visual logging tool (see Figure 2-1). From here you can launch your desktop

web browser, monitor logging, and view exception stack traces. One nice feature of the

GWT tool is that it will watch for changes in your code on disk, then recompile and

relaunch the app whenever you reload in the browser. This way you can just flip be-

tween code and your web browser without any extra compiling or building step.

The first time you run the tool and launch your browser it will ask you

to install a special browser plugin. This plugin creates the link between

your browser and the logging tool. I recommend using the Chrome web

browser for GWT development as I have found it to provide the best

support.

4 | Chapter 2: Getting Started with GWT

www.it-ebooks.info

Field.setText("gwt user"). GWT follows the Java Beans naming convention so set

Text will set the text property of the nameField object.

The next line, addStyleName adds a CSS style class to the widget. Don’t worry about

this now. We will explore CSS in the mobilization chapter.

// We can add style names to widgets

sendButton.addStyleName("sendButton");

// Add the nameField and sendButton to the RootPanel

// Use RootPanel.get() to get the entire body element

RootPanel.get("nameFieldContainer").add(nameField);

RootPanel.get("sendButtonContainer").add(sendButton);

RootPanel.get("errorLabelContainer").add(errorLabel);

The last three lines above add the three widgets to objects inside of the root panel. The

RootPanel represents the actual web page. The default generated app has a few divs in

the web page named nameFieldContainer, sendButtonContainer, and errorLabelCon-

tainer. The widgets will be added to these divs. Look at war/MyFirstApp.html to see

the divs.

You don’t have to use prefab divs in your HTML, though. You could instead add them

directly to the root panel or nest them inside of another panel. For example, if you

wanted to put the widgets in a vertical panel, where the widgets are all arranged in a

vertical column, you could do it like this:

VerticalPanel vertPanel = new VerticalPanel();

vertPanel.add(nameField);

vertPanel.add(sendButton);

vertPanel.add(errorLabel);

RootPanel.get().add(vertPanel);

Notice that I changed RootPanel.get(“somename”) to RootPanel.get(). This will get the

root panel itself instead of one of the nested divs.

GWT supports mapping into parts of the markup or taking over the entire page. This

gives you a choice of how to build your application. For mobile apps I prefer to take

over the entire page and only use markup and CSS for styling.

The next few lines of MyFirstApp.java make the name field be focused when the user

first opens the web page, then selects all of the text within the name field. This means

the user will overwrite the selected text when they start typing.

// Focus the cursor on the name field when the app loads

nameField.setFocus(true);

nameField.selectAll();

The rest of the MyFirstApp class creates a remote procedure call to the server, then

displays the results in a dialog box. I won’t cover this part because we will never be

using GWT’s own remote procedure call system in this book. GWT was originally

designed to be run on Java EE app servers. It will generate both server and client side

components with a nice mapping between them. For our apps, however, we are only

Installing GWT | 7

www.it-ebooks.info

剩余83页未读，继续阅读

Tedlin1122

粉丝: 0
资源: 2

使用Java构建移动应用指南

using-liferay-portal-6.2.pdf

ebook-flutter-revolution.pdf

"building workspace\". java.lang.internalerror"

spring-boot mybatis thymeleaf

CDH6全部安装步骤与解释

reactor streams

请为我找到几个基于spring boot的优秀开源项目

请写出收录在ScienceDirect或ISI-SCI Expand的英文文献的题目，各篇内容要求分别含有PyQt、Tkinter、wxpython、kivy、Pygui、Dabo、pyui4win、pyGtk、Pyforms、PySimpleGUI、Flexx、DearPyGui技术介绍

@MapperScan("com.building.*.*.mapper") 中 * 号的作用

NameError: ERROR: buildex::build: Building failed with error... [Errno 2] No such file or directory: 'build'

javaee springboot

编译boot出现NameError: ERROR: buildex::build: Building failed with error... [Errno 2] No such file or directory

springboot+mybatisplus

nodejs+express+mongoose

select mybatis

Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package tracepath

Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package yum

spring boot

Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package yum

jakarta.servlet

最新资源

@MapperScan("com.building...mapper") 中 * 号的作用