利用Adobe Flash CS4制作旋转的立方体

Flash是一款非常优秀的交互式动画制作工具软件,较之以前版本,Flash CS4增加了诸多新的的功能。本文主要使用Flash CS4中的工具、面板、形状提示等制作形变动画旋转的立方体。     

Flash二维动画的制作技巧与方法

在二维动画制作过程中,经常使用到Flash软件,它可以将不同动画元素结合起来,使动画制作的效果更加直观、立体、逼真。在Flash软件中,媒体播放技术和矢量图形可以很轻松地制作出多个小动画文件,并可以在观看动画文件的过程中进行下载。而且人们还可以将Flash中制作的动画直接用于网页设计中,从而大大提高了制作二维动画的工作效率。因此,笔者着重研究了当前Flash二维动画制作的技巧与方法,对制作二维动画具有重要的借鉴价值。     

基于Flash的简易钢琴的制作

制作钢琴动画的方法很多,但是使用Flash可以说是一种通用的非常有效的方法。使用Flash制作钢琴动画,不仅可以实现简易钢琴的功能,而且界面更加美观、生动,充分发挥了Flash软件的优势。     

Flash软件在制作音乐动画短片中应用研究

随着Flash软件被在多媒体制作中的广泛应用,它集声音、动画、文本等交互作用于一体的特殊性也进一步被体现,而且是现代多媒体设计技术和短片中运用最广泛的设计软件之一,本文首先介绍Flash软件的概述和前景;其次通过音乐短片的制作流程,对Flash软件制作中的一些技巧和手法进行深入细致的分析,从而更好的在实践过程中较顺利的应用Flash软件进行多媒体动画短片和作品的制作,使得多媒体的创作和设计有更好的发展前景。     

Flash动画在工控软件中的应用

作为富媒体的Flash动画,已经在各个方面都得到了极广泛的应用。工控软件如果也能采用Flash动画,必将极大提高工控软件的界面友好性。以VB中使用Flash动画为例,介绍了Flash动画控件的用法,在软件中将Flash动画作为背景、按钮等交互元素及位置等棒状图类元素时的Flash制作和用法,为同类软件实现更生动的界面设计提供一种有价值的参考。     

Flash动画短片的制作

Flash是当今Internet上最流行的动画作品制作工具,是一种交互式动画设计工具,可以制作丰富多彩的矢量动画,并且用它可以将音乐、声效、动画以及富有新意的界面融合在一起,以制作出高品质的动画效果。通过掌握二维动画短片的设计与制作原理,结合Flash软件进行二维动画短片的设计与制作,完成从初期的剧本创意,造型、场景设计,绘制脚本、设计稿、元件,到最终在Flash软件中实现二维动画短片。     

网页制作技术与Flash动画制作技术的融合

网页可以向人们传递丰富的信息,在实际制作网页的过程中,科学融合Flash动画制作技术将能够起到良好效果。笔者主要从Flash动画的基本情况分析入手,重点介绍了其应用功能和优势,阐述了网页制作技术与Flash动画制作技术的融合意义,并提出了一些科学有效的融合方式,旨在为不断提升Flash动画网页制作水平提供借鉴。     

Flash动画制作技巧

通过Flash软件可以将文字、图形图像、音频、视频等多种媒体编辑组合在一起,制作出具有交互功能的高品质的SWF动画作品。由于采用矢量图形和流式播放技术,生成的动画文件非常精小,可一边下载一边播放,适合制作网页设计中的动画。阐述了Flash软件制作动画时的各种技巧。随着网络传输速度的加快,Flash动画的应用领域会越来越广。     

课件制作软件不兼容? 驯服有术!

随着近几年电脑硬件、软件和网络的迅速发展和逐步完善,为我们在教育领域从事多媒体课件制作带来了极大的便利。现在的优秀课件非常多,从网上搜索一下能找到很多不同软件制作的精美课件。我平时也喜欢利用一些软件来制作教学课件,通常使用Authorware(以下简称AW)、Photoshop(以下简称PS)、Flash这几款软件相互配合制作课件,其中PS可以进行平面图片的处理,制作课件中需要的背景图片;Flash可以制作课件需要的动画,起到画龙点睛的作用;最后使用AW将图片、动画、文字等内容按照不同的结构连接起来,形成一个完整的课件。     

利用Flash制作拼图游戏

Flash是现在最流行的动画制作软件之一．它可以将文字、图形图像、音乐、声音、视频等融合在一起制作出高品质的动画效果。其中,利用Flash制作的游戏动画体积小、操作方便、娱乐性强,极易在网络中传播,尤其受人们喜爱。利用Flash技术及其脚本ActionScript对两款拼图游戏进行设计与实现。     

Biomechanical and physiological comparison of conventional webbing and the M83 assault vest

This study compared the effect of load distribution using two different webbing designs on oxygen consumption and running kinematics of soldiers. It was hypothesised that running with webbing that distributes the load closer to the body (M83 Assault Vest) would expend less energy compared to running with conventional webbing (CON). Seven soldiers randomly completed three treadmill trials; an unloaded VO(2)max test, and two loaded (8 kg) efficiency tests using either the M83 or CON webbing. The VO(2)max test and the loaded efficiency tests had 4-min stages at 5, 8, 10 and 12 km h(-1). Energy expenditure was measured via indirect calorimetry and video analysis was used to determine stride frequency (SF) and stride length (SL) during each trial. Participants using the M83 webbing expended significantly (p<0.05) less energy at all four running velocities compared to the CON trials. The M83 webbing resulted in smaller changes to SL and SF from the unloaded trial when compared to the CON trial. These results indicate that the M83 vest that is designed to distribute the load closer to the body may have an energy efficiency advantage over conventional webbing when soldiers are running.     

提高嵌入式系统可靠性的软件技术

软件抗干扰技术是提高嵌入式系统可靠性的重要手段。结合实践,文章分析了嵌入式系统软件的基本要求及软件抗干扰的特点,并从软件工程开发方法和故障自诊断技术等方面提出了若干行之有效的软件抗干扰技术。     

基于Visual FoxPro的U盘物理序列号与盘符的获取方法

基于Visual FoxPro环境,针对目前性价比高、可移性强的U盘,给出了其物理序列号与对应盘符的析出算法。该方法在软件保护和共享软件注册等方面具有一定的应用价值。     

基于模型的嵌入式开发环境——LambdaMDE

面向嵌入式软件的开发工具目前正在从基于代码的传统开发环境向基于模型的开发环境发展。为此,研究了一个基于模型的嵌入式开发环境LambdaMDE,在LambdaPro的基础上集成OSATE和Simulink模型开发工具以及其他相关工具,包含了建模、仿真验证、代码生成和测试等嵌入式软件开发的全过程。符合嵌入式软件开发工具发展趋势,具备了相应的理论、技术和产品基础。     

An Essay on Software Reuse

This paper explores software reuse. It discusses briefly some economic incentives for developing effective software reuse technology and notes that different kinds of software reuse, such as direct use without modification and reuse of abstract software modules after refinement, have different technological implications. It sketches some problem areas to be addressed if we are to achieve the goal of devising practical software reuse systems. These include information retrieval problems and finding effective methods to aid us in understanding how programs work. There is a philosophical epilogue which stresses the importance of having realistic expectations about the benefits of software reuse.     

Understanding service-oriented software

Many hail service-oriented software as the next revolution in software development. Web services' capabilities are constantly expanding from simple message passing toward the construction of full-fledged applications such as those envisaged by the UK's Pennine Group in their Software as a Service (SaaS) framework. These new, service-oriented approaches appear to many to solve the significant issue of software inflexibility that arises during maintenance and evolution. While they address sonic aspects of the problem, however, understanding the software still poses some difficulty. This shift toward service orientation compels us to consider its implications for software understanding, which is potentially the primary cost in software engineering. Using an example of on-the-fly software services construction, we discuss the problems software engineers still face when working with service-oriented software. We also introduce some new issues that they must consider, including how to address service provision difficulties and failures.     

OO metrics in practice

While it has long been recognized that software process improvement requires measuring both the process and its performance, experience has also shown that few universal metrics exist. The most effective measurement tools are specialized to some aspect of the task or domain being measured. The metrics as measures of code have often been related to external factors, such as software quality in the sense of defects. Software metrics studies often use single snapshots of a software project. Examining a project over a longer time frame allows consideration of other software quality facets, such as reuse and maintainability.     

Metaphor, myth and mimicry: The bases of software engineering

The term software engineering has had a problematic history since its appearance in the 1960s. At first seen as a euphemism for programming, it has now come to encompass a wide range of activities. At its core lies the desire of software developers to mimic ‘real’ engineers, and claim the status of an engineering discipline. Attempts to establish such a discipline, however, confront pressing commercial demands for cheap and timely software products. This paper briefly examines some of the claims for the engineering nature of software development, before moving to argue that the term ‘engineering’ itself carries with it some unwanted baggage. This contributes to the intellectual quandary in which software development finds itself, and this is exacerbated by many writers who rely upon and propagate a mythical view of ‘engineering.’ To complicate matters further, our understanding of software development is grounded in a series of metaphors that highlight some key aspects of the field, but push other important issues into the shadows. A re‐reading of Brooks' “No Silver Bullet” paper indicates that the metaphorical bases of software development have been recognized for some time. They cannot simply be jettisoned, but perhaps they need widening to incorporate others such as Brooks' concepts of growth and nurture of software. Two examples illustrate the role played by metaphor in software development, and the paper concludes with the idea that perhaps we need to adopt a more critical stance to the ‘engineering’ roots of our endeavours*. *I should like to express my thanks to the anonymous reviewers of the first draft of this paper. Two of them offered useful advice to enhance the finished version; the third gave vent to a perfectly valid concern, that the argument as stated could have grave side effects if it was used as a point of leverage in arguments over ownership of the term ‘engineering.’ I understand this concern and the potential financial implications that prompt its expression; but in the longer term I see this exercise in clarification as a contribution to such discussions, inasmuch as it helps defuse the potency of terms such as ‘engineering.’ This revised version was published online in June 2006 with corrections to the Cover Date.     

面向航天嵌入式软件的形式化建模方法

航天嵌入式软件是航天型号任务成败的关键之一.航天嵌入式软件是一种周期性、多模式的软件.软件的每个模式表示系统处于一定的状态,并进行相应的复杂计算.因此,提出了一种名为SPARDL的形式化建模方法.为了满足型号应用的需求,对这一方法进行了若干改进.为了表达航天器的时序性质,提出了一种基于区间逻辑的性质规范语言.为了支持工业应用,还设计了代码生成方法.这一建模方法已在航天工业领域得到了应用.