Xport开发中文指导

Ext入门基础
get,getDOM,getCmp的区别 DOM的增删改查
尺寸&大小,定位
动画
事件 类编程 AJAX
Ext入门基础
要学习及应用好Ext框架，必须需要理解Html DOM、Ext Element及 Component三者之间的区别。 每一个HTML页面都有一个层次分明的DOM树模型，浏览器中的所有内容都 有相应的DOM对象，动态改变页面的内容，正是通过使用脚本语言来操作 DOM对象实现。(通常使用getElementById/Ext.getDOM获得DOM对象) 仅仅有DOM是不够的，比如要把页面中的某一个节点移到其它位置，要给某 一个节点添加阴影效果，要隐藏或显示某一个节点等，我们都需要通过几句 javascript才能完成。因此，Ext在DOM的基础上，创建了Ext Element，可以 使用Element来包装任何DOM，Element对象中添加了一系列快捷、简便的实 用方法。(通常使用Ext.get获得Element对象) 对于终端用户来说，仅仅有Element是不够的，比如用户要显示一个表格、要 显示一棵树、要显示一个弹出窗口等。因此，除了Element以外，Ext 还建立 了一系列的客户端界面组件Component，我们在编程时，只要使用这些组件 Componet即可实现相关数据展示及交互等，而 Component是较高层次的抽 象，每一个组件在渲染render的时候，都会依次通过Element、DOM来生成 最终的页面效果。(通常使用Ext.getCmp获得Component对象)
方位、尺寸（如getHeight、getWidth）
Ext入门基础

DOM查询
获取下一个侧边节点，跳过文本节点。可选地可送入一个期待的选择符。 Ext.get('elId').next(); 类似的还有: Ext.get(„elId‟).prev();//上一个侧边节点 Ext.get(„elId‟).first();//第一个节点 Ext.get(„elId‟).last();//最后一个节点 Ext.get(„elId‟).parent();//父节点 比如要获取页面上所有的p标签,则可以使用: var ps = Ext.select('p'); 这样你就可以对所要获取的元素进行操作了,select()方法返回的是 positeElement对象,可以通过其中的each()方法对其所包含的元素进行遍历: ps.each(function(el) { el.highlight();//高亮 }); 当然,如果你要是对获取的所有元素进行相同的操作,可以直接应用于CompositeElement 对象上,如: ps.highlight();//select方法返回的结果可直接如同Element般地操作 或是: Ext.select('p').highlight(); 当然,select参数还可以更复杂一些,其中可以包括CSS选择符,基本的XPath,HTML属性等

Processing中文开发教程Processing 是一种基于 Java 编程语言的开源编程环境和图形库。

它可以使用户方便地创建图形化应用程序、动态艺术作品和交互式图像。

Processing 由 Casey Reas 和 Ben Fry 在2001年推出，它的目标是为了帮助非专业编程人员学习编程，并且在视觉艺术领域中找到一个创造性的解决方案。

在这个中文开发教程中，我将介绍 Processing 的基础知识和用法，并提供一些常见的例子和项目来帮助你更好地理解和应用 Processing。

Processing 的程序最小单位是一个绘图窗口，你可以在其中画出各种形状、图形和动画。

在程序的起始位置，你需要定义一个 `setup(` 函数，该函数仅在程序开始时运行一次。

在 `setup(` 函数中，你可以设置你的绘图窗口的大小、背景颜色等。

例如，下面是一个简单的 Processing 程序，它创建了一个大小为500x500 像素的绘图窗口，并且将背景颜色设置为黑色：```void setusize(500, 500);background(0);```接下来，你可以在 `draw(` 函数中编写需要重复执行的代码，该函数在 `setup(` 执行完成后会反复执行。

你可以使用各种图形和颜色函数来绘制你想要的图形和效果。

例如，下面是一个绘制一个移动的圆的例子：```float x = 0;void setusize(500, 500);background(0);void drabackground(0);fill(255);ellipse(x, height/2, 50, 50);x+=1;```在这个例子中，`ellipse(` 函数用于绘制一个圆形，`fill(` 函数设置圆的填充颜色。

`x` 的值在每一次的 `draw(` 函数中增加 1，使得圆向右移动。

`height` 是一个全局变量，它代表绘图窗口的高度。

1toolGuidelines for developing application programs in 1ToolGuidelinesContent1.General (5)2.Programming style on Strategy (5)yout of the objects on the page (5)4.Variable names (6)5.References (6)6.Pages (7)7.Migrated project (7)8.Programming style in User interface (7)9.Miscellaneous (10)INTRODUCTIONThe purpose of this document is to provide guidelines to be followed during the development of an application program in 1Tool.1.1 Observe all the rules described in the application program development procedure: archiving, structure of thesources on the PC, code-version: see codifica_applicativi.doc1.2 Add the properties of project like description, author, version, date1.3 Where possible, use standard Carel macroblocks.1.4 Use the same style in the entire application. When editing an existing application, copy the style used. If this iscompletely outside of these guidelines, evaluate whether it is worth reviewing the entire application.1.5 A value must be given to the Copy_Password system variable in all applications. If no value is designated in thedevelopment specifications, assign the value 0 (zero).1.6 Use the “Template_Project” to start a new Carel application.1.7 All the mean variables (use into user interface, manage via supervisory, public variable for the log…) must havethe description. That description will be use for the documentation (parameters list) and for the Pl@ntVisor.STRATEGYWhen developing an application, always remember that such application may be designed, modified or debugged by any other 1Tool developer, and therefore it must be easy to understand and read.2.1 Add remarks wherever possible for the algorithms, in particular the more complex ones.2.2 Add remarks for the main variables.2.3 No absolute timers of any kind may be used to control the sequence of operations executed. When changing todifferent hardware this causes incompatibility errors due to differences in the execution speed of the controllers. 3.1 The atoms, macroblocks and variables should be aligned in columns (see Figure 3.1).3.2 It is suggested to align the variable around the atoms/Mbk because the autorouting working better.3.3 Similar controls should always be designed in the same way, otherwise they will appear to run different functions.3.4 The paths of the wires must be "clean", avoid contorted paths (see Figure 3.1).3.5 Where possible, if a variable is created and used inside the same page, the variable should not be repeated inmore than one place, but rather a direct connection with a wire can be used. If this is not possible, indicate where the variable is created3.6 The variables and the constants must be connected to the pins with wires of the same length for reasons ofvisibility (see Figure 3.1).3.7 Use lines to divide the functions (see Figure 3.1)Figure 3.14. VARIABLE NAMES4.1 The names must be meaningful (self-explanatory) and in English.4.2 The names of the lists must have the following format: “Lst_” +LISTNAME.4.3 For variables deriving from the pCO* inputs, avoid using the same names as the inputs, e.g. B1, B2 etc. Alwaysassign names that are coherent with the function of the input / output.One exception may be applications that feature different I/O configurations (multi-platform).4.4 Characters used for the variable names: see paragraph 1.5.- It is recommended to use the same notation as the atom pins, that is, the first letter of each word in upper case and the rest lower case, with an underscore between one word and the next: Xxxxx_Yyyyyyy4.5 When names are abbreviated, maintain the plural, for example En_Compressors should become En_Cmps.5. REFERENCESPay careful attention to the order of the references used in a routine. Failure to observe the correct order means creating delays of a number of program cycles in the results5.1 The references must not be consecutive, use step at least of 10This makes it simple to enter any atoms/macroblock in the middle of a function.5.2 Add remarks to any inverted references, that is, when the sequence is not the natural left-to-right5.3 Jump for each page, avoiding the use of cumulative Jumps. The exception is the “Initial Jump”.5.4 When logging the alarms from the application, use DO_EVENT A and B in the routine.5.5 Do not put atoms belonging to different DO_EVENT statements on the same page. The exception is the alarm logfrom application.5.6 Pay attention to use atoms to manage time inside the DO_EVENT: i.e the output variable of a R_TRIG atom usedinside the DO_EVENT does not give an impulse but it became 1 only.6.1 The names must be meaningful (self-explanatory) and in English.6.2 Avoid pages with too many atoms (to make them clearer and for future modifications). Also see paragraph 3.8.One page should be created for each routine, or alternatively, if the function is complex. it can be divided into consecutive pages.6.3 Equal routines must be on the same page or on consecutive pages (see paragraph 6.4), i.e:- Special routines, for example: management of the application version and automatic installation of defaultvalues, automatic return to the menu, key_switch management, check the hardware used, En_Builtin_Keyboard management, etc.…- Analogue / digital inputs- Analogue / digital outputs- Device management- Supervisor- Log6.4 In order to have a right flow of the different managements, the pages must be arranged in logical order. If this isnot respect the application are slow to process the data and the devices are not correctly manage and protect. i.e: -inputs-alarms-devices-other functions (supervisor, log, etc.…)-outputs6.5 Use titles that identify the groups of pages by functions, alarms, master, slave, supervisor etc..7.1 Always add the new 1T atoms and macroblock, if it is possible replace the other.7.2 Delete, if it is present, the first page (usually sheet 0) that contains link to other page. Pay attention, from thesheet 0, it is possible to recover the sheet description.USER INTERFACEIf no specific requirement from the customer, to use the following rules.8.1 The interface must be respected the loop, the layout described in the User_Interface.xls8.2 If the application is standard Carel, add an index for each screen (or mask). The index is positioned in the topright corner of the screen.8.3 The index and the parameters this identifies must never be changed, once described in the manual.8.4 The index must respect be shown in the name of the screen. The suffix must also be shown in the name of thescreen.8.5 The name of the screens must be in English and must have the following format: “m_” +screen _name + screenindex, if present.8.6 The name of the screens that the “refer_to” statements refer to must have the following format: “m_ref_” +screen_name.8.7 There must be only 1 level of “refer_to”8.8 Each loop of screens must have an identifying colour (see User_Interface.xls).8.9 The first letter, and only the first, of the parameter description must be in upper case.8.10 The wording must be aligned to the left.8.11 The fields must be aligned to the right.8.12 Reach the length of the line by adding spaces between the description and the unit of measure. For example:Note that “Temperature °C” is just one string. (Not applicable for PGD23)This setting is useful when managing multi-language applications.8.13 There must not be spaces between the unit of measure and the fields.8.14 The texts used in the ASSBOOL and ASSINT statements for output fields must be: the first letter in upper-caseand the other letter in lowercase.8.15 The texts used in the ASSBOOL and ASSINT statements for the input - output fields must be in upper case.8.16 If a text needs to be enabled only in certain conditions from a field, use USE_TXT with enable in the field and notAssbool.8.17 The unit of measure must be written as follows: °C, °F, bar, PSI, kPa, s, min, h, etc...8.18 For all integer and analogue input fields, the limits for the field must be entered.8.19 There must not be any strange punctuation marks at the end of the parameter description, such as arrows“Temp.amb-->21.0°C” or dots “Temp.amb…..21.0°C” and so on8.20 The abbreviations must be easy to read. Avoid abbreviations such as: temperature -> tmp - pressure -> prs8.21 When abbreviating words, do not leave spaces between the full stop and the start of the next word. Example:“Amb.temp.”Words must be abbreviated with care, truncating the word is not always effective and at times makes it hard to understand or read8.22 The first line of an alarm screen must show the alarm code. Example: AL0008.23 In the demo applications, where possible do not use the specific features of the terminal: “°C” compacted into onecharacter, images etc.…Clearly this does not apply to demos for pGD1, pGD3.8.24 Use multiple columns on the User interface worksheet, so as to make it easier to refer to the various loops.Raccomended one loop for each columnMISCELLANEOUS9.1 Each analogue/digital input/output must have a value/status in the inputs and outputs menu.9.2 Each analogue input must be associated with the probe fault alarm.9.3 Each analogue/digital input/output must be made available, with read-only access, to the supervisory system.9.4 At least the following supervisor protocols must be implemented: Carel, Modbus, RS232, GSM, LonWorks.9.5 The automatic return to the main menu must be included. Allow a delay time of 5 minutes unless otherwiseindicated9.6 On the PGD0 and PGD1 terminals the backlighting is common to the display + Esc, up, down, enter buttons.Unless otherwise indicated, activate it when pressing any button and deactivate it automatically 5 minutes after the last button was pressed (code LED 25).9.7 Screens must be included to manage: application code, version and date, Boot and Bios version and date. Use thestandard screens proposed by Carel:9.8 Reset alarms from supervisor: use a 5 second Pulse9.9 The names of the special fields in the demos must have the following format: “dsf_” +special_field_name9.10 The mask name in the demos must have the following format: “d_” +nome_identificativo_della_funzione_del_demo.9.11 The version of the application must be managed by STRATEGY and be visible from the supervisor.9.12 For the PGD0 and PGD1 terminals, use a sliding menu to access the various submenus, compliant with the Carelstyle (see Template_Solution and User_Interface.xls).CAREL reserves the right to modify the features of its products without prior notice.1tool manual - rel. 1.2 – 11/01/2008 11CAREL S.p.A. Via dell’Industria, 11 - 35020 Brugine - Padova (Italy) Tel. (+39) 049.9716611 Fax (+39) 049.9716600 1t o o l g u i d e l i n e s - r e l. 1.2 –11/01/2008。

Xcode 帮助关于Xcode本篇文档将为您介绍Xcode，苹果公司最新的集成开发环境，用于开发Mac OS X 软件。

Xcode为用户提供了一个强大的界面允许用户使用许多基于工业标准的开放源代码工具，包括GCC，javac，jikes和GDB。

Xcode还提供了模板帮助开发人员创立应用程序，框架，共享库，plug-ins，java应用程序和小应用程序，以及命令行工具等等。

Xcode支持Cocoa和Carbon开发，允许使用C，C++，Objective-C 以及Java等编程语言。

重要本篇文档是Xcode测试版本的一个初步介绍。

尽管已经做过技术方面的校对，但是这篇文章并不是最终的版本。

本篇文档可能会包含一些不正确的或者在将来要修改的容。

Xcode 的优势Xcode在设计的时候就已经了考虑了几个目标：•易于使用。

Xcode提供了一个全新的流线型的用户界面来帮助您组织和访问您的软件工程中的所有的组成局部。

例如，工程窗口允许您从一个单一的位置访问所有的您的工程容还有数据。

在工程窗口中您可以方便的使用快速搜索，使得您查找信息更加方便快捷。

智能分组帮助您聪明的过滤和组织您工程的容和数据。

您可以在查看信息面板中检查并编辑工程里的对象。

•性能。

一些新的功能提高了编译生成的速度并且缩短了每次修改错误的时间周期。

“修改然后继续“的调试方式允许您修改您的源代码，编译，然后就在您上次离开的地方继续调试。

使用零〔Zerolink〕，您可以在开发的阶段跳过的步骤。

分布式编译允许您利用您的网络中的其它机器的处理器资源来编译生成您的产品。

•工业标准的工具。

Xcode使用与开放源代码社会以及决大多数其它的Unix 操作系统所使用的完全一样的基于工业标准的工具。

例如，当您编译C，C++，或者Objecttive-C源代码的时候，您使用GNU编译器，GCC。

当您编译Java源代码的时候，您使用Sun公司的javac或者IBM公司的jikes编译器。