用java写的一个小程序，模拟操作系统的PV操作

告诉你如何利用排序算法简单的编java程序-tell you how to use a simple algorithm series java programs

使用 Swing 控件，实现上图所示的图形化界面，并完成初步功能-The use of Swing controls, to achieve the figure shown in graphical interface, and complete the initial function

J2me Gaming Chapter04 源代码-J2me Gaming Chapter04 source code

just a test code -just a test code

采用java技术开发的控制面板，用于安排控件的位置，方便系统的布局与管理。-Using java technology development of the control panel for the location of the control arrangements to facilitate the system layout and management.

这是实际使用中的项目，应用Struts技术，视图-模型-控制机制，运用软件工程思想，是学习Struts的很好例子-this is the actual use of the project, application Struts, View-model-control mechanism, using software engineering thinking and learning is a good example of Struts

关于文件处理的类，可以直接使用-on the document type, and can directly use

这是一个通过多平太编写的俄罗斯方块游戏源文件-through Taheita sheet prepared by the Russian source games

　一款改造的J2me手机游戏项目，三国战纪游戏的源代码，游戏界面略显粗糙。不过游戏基本框架已经具备。一小部分功能没有实现。 　　项目源码可以在eclipse中直接运行。如果拿到wtk中测试的话，请修改源代码中的文件路径，譬如把"/res"去掉即可。 游戏名称：《三国战纪》手机版 游戏类型：横版过关 游戏支持屏幕：176*208 游戏支持需求：MIDP2.0，CLDC1.1 开发平台：J2ME+eclipse3.2+wtk2.5+jdk1.6 -A transformation of the mobile J2me Games project, the source code of the game Knights of Valor, a little rough game interface. But the basic framework of the game in place. NOT a small part of the functional implementation. Project source code can be run directly in the eclipse. Wtk get tested if so, please modify the source code of the file path, for example, put "/res " can be removed. Game Name: " Knights of Valor" mobile version of Game type: Games in support of cross-boundary version of the screen: 176* 208 games support needs: MIDP2.0, CLDC1.1 development platforms: J2ME+ eclipse3.2+ wtk2.5+ jdk1.6

计时器服务依赖于加载 Timer 类的主机的系统日期。如果侦听器主机具有不同的系统日期，则侦听器可能会不合时宜地接收到通知。为了避免此类问题，要 ... 定期通知的默认行为是固定延迟执行，这一点已在 Timer 中指定。-Services depends on the load timer Timer class of mainframe-based systems date. If the listener has a different host system date, the listener may receive untimely notice. In order to avoid this problem, should be informed on a regular basis ... the default behavior is a fixed delay in the implementation and this has already been specified in Timer.