SuperScript_VILO_MasterMix_man

合集下载

大咖娱乐源码大全

大咖娱乐源码大全

大咖娱乐源码大全大家好,今天我给大家介绍一些大咖娱乐源代码。

以下是大咖娱乐的主要功能和源代码示例:1.用户注册和登录功能是大咖娱乐的核心功能之一、用户注册需要提供用户名、密码和电子邮件。

以下是注册功能的源代码示例:```pythonfrom django import formsfrom django.contrib.auth.models import Userclass UserRegistrationForm(forms.ModelForm):password = forms.CharField(label='密码',widget=forms.PasswordInput)password2 = forms.CharField(label='确认密码',widget=forms.PasswordInput)class Meta:model = Userfields = ('username', 'email')def clean_password2(self):cd = self.cleaned_dataif cd['password'] != cd['password2']:raise forms.ValidationError('密码不匹配!')return cd['password2']```2.用户登录功能是大咖娱乐的另一个重要功能。

以下是登录功能的源代码示例:```pythonfrom django import formsfrom django.contrib.auth.models import Userfrom django.contrib.auth import authenticateclass UserLoginForm(forms.Form):username = forms.CharField(label='用户名')password = forms.CharField(label='密码',widget=forms.PasswordInput)def clean(self):cd = self.cleaned_datauser = authenticate(username=cd['username'],password=cd['password'])if user is None:raise forms.ValidationError('用户名或密码错误!')return cd```3.用户发布动态是大咖娱乐的另一个重要功能。

八重洲VX-177手持电台使用手册

八重洲VX-177手持电台使用手册

VERTEX STANDARD HK LTD.
Unit 5, 20/F., Seaview Centre, 139-141 Hoi Bun Road, Kwun Tong, Kowloon, Hong Kong
Contents
General Description ......................................... 1 Accessories & Options ..................................... 2 Controls & Connections .................................. 3 Top & Front Panel .......................................... 3 LCD ................................................................ 4 Side Panel ....................................................... 5 Keypad Functions .......................................... 6 Installation of Accessories ............................... 8 Antenna Installation ....................................... 8 Installation of FNB-83 Battery Pack ............. 8 Battery Charging ........................

WOW基本宏命令

WOW基本宏命令

一、基本宏命令1.什么是宏?宏是由一组宏命令组成的。

以下是一些普通宏命令:▪/say (/s)▪/whisper(/w, /talk, /t)▪/emote(/e, /em, /me)▪/dance▪喜爱PVP的人,应该不会忘了这个:/spit利用宏,我们可以把这些宏命令放到技能栏上点击使用,而且可以同时做多个动作。

写宏的时候,每条动作写在一行上,就像在聊天界面中输入的一样。

比如,让你的角色喊一声“Everybody, dance now!”然后开始跳舞的宏:/y Everybody, dance now!/dance一个基本完整的宏命令列表可以参考这里:[《宏命令全表》],不过个别新添加的宏命令还没有被收录。

WoWWiki有很多关于宏的资料,尤其是脚本和/run命令(后面将会提到)。

注:我先在此说一下,宏的执行是立即进行的。

这意味着当你点击技能栏上的一个宏时,宏命令会一条接一条地执行,执行完后才会返回游戏控制。

这将会产生两个重要问题:第一,如果写了一个会执行很长时间的宏(如:/run for i=1, 1000000000 do end),游戏会被卡死,直到它执行结束;第二,也是更重要的一点,那就是宏命令不可能具有延时功能。

这一现象在我们熟悉/cast之类的命令后就可以很清楚地感觉到。

而一些提供了延时执行命令功能的插件,只能是能执行一些所谓的“良性命令”,如交谈、表情和对于其他插件命令的调用(不过战斗中更换武器是可以进行的)。

2.怎样写宏?首先,打开你的宏窗口:单击主菜单上的“宏”按钮,或者在聊天界面中输入/macro(/m)回车。

在宏窗口的顶端,可以看见两个标签:“通用宏”和“<你的角色名>的专用宏”。

通用宏被存储在账号专有的文件夹中,被所有角色共享。

而角色专用宏则存储在角色自己的文件夹下,是角色专用的(废话……囧)。

在标签下面是18个存放宏的栏位。

再往下是一个栏位,用于显示当前选中的宏;还有一个“修改名称/图标”的按钮,用于修改选中的宏。

罗技G系列外设宏命令编程参考文档

罗技G系列外设宏命令编程参考文档

G-series Lua API 参考文档V8.50预览与概述手册目录手册目录 (2)内容预览 (3)参考文档 (4)标准 Lua 5.1 库 (40)附录A (41)G-series Lua API 参考手册是一套使用 Lua 脚本编程语言描述并且为 G-series 系列游戏键盘提供高级脚本功能。

该文档是在假设您已初步掌握 Lua 脚本编程语言使用方法的前提下进行的。

如果您想了解更多信息请访问 。

每项 G 系列的配置文件都有一个默认的 Lua 脚本与其绑定,并且您可以根据您的喜好随意编辑或者自定义。

该脚本借助并使用一个名为OnEvent 的事件句柄。

用户可以通过检查此句柄中触发的各种事件以执行用户所希望的动作。

方法列表OnEvent (5)GetMKeyState (7)SetMKeyState (8)Sleep (9)OutputLogMessage (10)GetRunningTime (11)GetDate (12)ClearLog (13)PressKey (14)ReleaseKey (15)PressAndReleaseKey (16)IsModifierPressed (17)PressMouseButton (18)ReleaseMouseButton (19)PressAndReleaseMouseButton (20)IsMouseButtonPressed (21)MoveMouseTo (22)MoveMouseWheel (23)MoveMouseRelative (24)MoveMouseToVirtual (25)GetMousePosition (26)OutputLCDMessage (27)ClearLCD (28)PlayMacro (29)AbortMacro (30)IsKeyLockOn (31)SetBacklightColor (32)OutputDebugMessage (33)SetMouseDPITable (34)SetMouseDPITableIndex (35)EnablePrimaryMouseButtonEvents (36)G13 Programming (37)OnEventOnEvent() 方法为脚本提供了一系列事件句柄以方便用户对触发的事件进行操作,您可以使用以下代码实现此方法。

vulkanmemoryallocator用法 -回复

vulkanmemoryallocator用法 -回复

vulkanmemoryallocator用法-回复Vulkan是一种用于高性能图形和计算的跨平台API。

它允许开发人员直接访问硬件资源,为现代图形管道提供了更大的灵活性和控制力。

然而,使用Vulkan API进行内存管理可能变得复杂和繁琐。

为了解决这个问题,Vulkan Memory Allocator(VMA)就应运而生。

Vulkan Memory Allocator是一个开源的C++库,它封装了Vulkan的内存管理API,并提供了更简单和高效的内存分配和释放机制。

它可以帮助开发人员减少内存管理方面的工作量,提高应用程序的性能和稳定性。

在本文中,我将一步一步为您介绍Vulkan Memory Allocator的使用方法,包括库的安装和集成,内存分配和释放的基本用法,以及一些实用的技巧和技巧。

第一步:安装Vulkan Memory Allocator(VMA)首先,您需要将Vulkan Memory Allocator库添加到您的项目中。

您可以从GitHub上下载最新的源代码,并将其添加到项目的源代码目录中。

接下来,您需要在项目的构建脚本中添加相应的编译选项,以便正确地构建和链接VMA库。

第二步:集成Vulkan Memory Allocator(VMA)一旦您已经安装好了VMA库,接下来您需要在项目中集成它。

首先,您需要在您的代码中包含VMA的头文件。

您可以使用以下代码行实现:#include <vulkan/vulkan.h>#include <vk_mem_alloc.h>接下来,您需要在程序启动时创建一个VMA分配器对象。

您可以使用以下代码行完成此操作:VkInstance instance; 创建Vulkan实例...VmaAllocator allocator;VmaAllocatorCreateInfo allocatorInfo = {};allocatorInfo.instance = instance;vmaCreateAllocator(&allocatorInfo, &allocator);在创建分配器对象时,您需要提供一个指向VkInstance的指针。

sap bsp开发高级教程

sap bsp开发高级教程

Brian McKellar, Thomas Jung AdvancedBSP ProgrammingContentsIntroduction15Target Audience (15)On What Releases Can You Use BSP? (16)BSP vs. Web Dynpro ABAP (16)Acknowledgements (17)1What is BSP?211.1Internet Communication Manager (21)1.2Internet Communication Framework (24)1.3BSP Development Environment (25)1.4HTMLB Rendering Family (26)1.5BSP Compiler (27)1.6BSP Runtime (28)1.7BSP Debugger (29)1.8MIME Repository (30)1.9Summary (30)2HTTP and HTML312.1Viewing the HTTP Traffic (32)2.2Structure of HTTP (32)2.2.1The HTTP Request Status Line (35)2.2.2HTTP Request Headers (35)2.2.3HTTP Header/Body Separator (37)2.2.4HTTP Request Body (37)2.2.5The HTTP Response Status Line (37)2.2.6HTTP Response Headers (38)2.2.7HTTP Response Body (39)2.3Server Objects for HTTP Request and Response (39)2.4HTML Forms and Data Handling (41)2.5Mapping of HTML onto HTTP Requests (46)2.5.1Input Fields (46)2.5.2Checkboxes, Radio Buttons and Dropdown List Boxes (48)2.5.3File Upload and Download (49)5Contents2.6Cookies (54)2.7HTTP Redirects (58)2.8Handling of HTML Resources in HTTP (59)2.9Troubleshooting Examples (62)2.9.1Missing Resource (62)2.9.2Non-Secure Warnings (63)2.9.3Relative URLs That Become Invalid (63)2.9.4Estimating Performance (65)3HTTP Handler673.1URL Handling in the ICF Tree (67)3.2URL Mapping (68)3.3Sample Handler for Reading Images (69)3.3.1URL Syntax (71)3.3.2Handler Coding (72)3.4Alias Handling (74)3.5Handler Example—Table Query (77)3.5.1Table Query Handler Implementation (78)4URLs in BSP834.1URL Mangling (83)4.1.1What is URL Mangling? (83)4.1.2How is URL Mangling Done? (84)4.1.3Attempting to Hide the URL Mangling (85)4.2Fully Qualified Domain Names (89)4.2.1Motivation for FQDN (90)4.2.2ICM Configuration (91)4.2.3Browser Requirements (91)4.3Namespace Mapping (92)4.4URL Parameters (93)4.5URL Escaping (95)5Authentication975.1Basic Authentication (98)5.2Single Sign-On (102)5.3Digital Certificates (105)5.4Anonymous Services (108)5.5Form-Based Authentication (109)6Contents5.6Implementing a Simple Logon Application (110)5.7De-Authentication (113)6Session Management1156.1Session Identification (115)6.2Session Timeout (118)6.2.1Catching and Handling a Session Timeout (119)6.2.2Session Timeout in Browser (120)6.3Confusion with Processing Timeout (121)6.4Catching and Handling a Restart after Timeout (123)6.5Session Management from the Browser (125)6.6Warning the User of a Pending Timeout (128)6.7Summary (131)7Using BSP Applications in SAP GUI1337.1Using a BSP Application in a Dynpro (133)7.2Pitfalls when Using BSP Applications with SAP GUI (136)7.2.1Communication Path (136)7.2.2The Second Authentication (137)7.2.3The Second Session (138)7.2.4Window Open Behavior (139)7.2.5Effects of SAP’s New Visual Design (141)7.2.6Loading HTML Pages Directly (142)7.3Interaction between SAP GUI and BSP Applications (144)7.3.1BSP Application Event to SAP GUI (144)7.3.2SAP GUI Event to BSP Application (147)7.4Starting a New Browser Outside the SAP GUI (149)8Performance Measurements1518.1Test Applications (152)8.2Quick Sizing with HTTP Trace Tool (153)8.3Network Latency (154)8.4Server Processing Time (155)8.5Browser Rendering Time (157)8.6Determining Hotspots (159)8.7Load Testing (161)8.8SQL Traces (165)7Contents9BSP Extensions1679.1Extension Overview (167)9.1.1Extension Technology (168)9.1.2Using BSP Extensions (168)9.1.3Finding Details about the Extensions (169)9.1.4Available Extensions (172)9.1.5Extensions Designs (172)9.1.6High Level Elements (174)9.2HTMLB Event System (180)9.2.1Event Dispatching (180)9.2.2Manually Handling Events (181)9.3Common Extension Elements (186)9.3.1<htmlb:tableView> (187)9.3.2<htmlb:tree> (192)9.3.3<phtmlb:matrix> (194)9.3.4<xhtmlb:protectDoubleSubmit> (196)9.3.5<phtmlb:containerTabStrip> (197)9.3.6<phtmlb:formLayout> (200)10BSP Element Expressions and Iterators20510.1BSP Element Expressions (205)10.1.1What is a BEE? (205)10.1.2N=1, Using Any BSP Element as BEE (206)10.1.3HTML BEE (209)10.1.4Table BEE (211)10.1.5XML BEE (212)10.1.6Errors and Error Handling (215)10.2Table View Iterators (215)10.2.1What is a Table View Iterator? (217)10.2.2Method GET_COLUMN_DEFINITIONS (218)10.2.3Method RENDER_ROW_START (220)10.2.4Method RENDER_CELL_START (222)10.2.5Finished Output (225)11Creating your own BSP Extension Element22711.1Creating a BSP Extension Element (227)11.1.1Extension Framework Hierarchy (227)11.1.2User-Defined Validation (228)11.1.3Element Content (230)11.2Writing a Composite Element (231)11.2.1Designing a New Composite Element (231)11.2.2Processing Other BSP Elements (233)8Contents11.2.3Writing the Composite BSP Element (237)11.2.4Handling of Inner Data BSP Elements (238)11.3 A Deeper Look at BSP Extensions Events (239)11.3.1Introduction to BSP Extension Events (239)11.3.2Rendering Events (240)11.3.3Handling Incoming Events (243)11.3.4Rendering an Event via the <bsp:htmlbEvent> Element (243)11.4Event Handling in Composite Elements (244)11.4.1Extending the Design of the Composite Element (245)11.4.2Using the Composite Element (245)11.4.3Use of IDs (246)11.4.4Integrating into the HTMLB Manager (247)11.4.5Data-Handling (249)11.4.6Event-Handling (250)12Additional BSP Extensions25312.1Business Text Framework (253)12.1.1SAP Example (253)12.1.2BTF Functionality (254)12.1.3Database Storage (255)12.1.4BSP Extension Element (256)12.1.5BTF Editor in the Page Layout (257)12.1.6Preparing the BTF Document (258)12.1.7Retrieving BTF Content on Input (258)12.2Internet Graphics Service (260)12.2.1IGS Setup and Administration (260)12.2.2SAP Examples (261)12.2.3IGS BSP Extension (261)12.2.4Chart Data (262)12.2.5Chart Model Classes (264)12.2.6IGS Customizing (266)12.2.7Image Click Event Handling (267)12.2.8Image Conversion (268)12.3BSP Library (268)12.3.1findAndReplace Element (268)12.3.2htmlbEvent Element (269)12.3.3Portal Integration (270)13MVC—Model View Controller27513.1MVC Design Paradigm (275)13.2Application Structure (275)13.2.1Model (276)13.2.2Controller (277)13.2.3View (283)9Contents13.3.1Getter/Setter methods (286)13.4Dynamic Model Binding (288)13.5Stateless MVC (291)13.5.1XML Serialization of ABAP Objects (291)13.5.2Server Cookie Storage of the XML Stream (292)13.5.3Controller Modifications to Support Serialized Models (293)13.6Building a Pattern Engine with MVC (295)13.6.1The Final ESS Application (297)13.6.2Writing the ESS Application (298)13.6.3Writing the Pattern Engine (301)14Help Systems30714.1F1—Field Level Help (307)14.1.1The Help UI (307)14.1.2Implementing the BSP Extension Element (311)14.1.3BSP Element Properties (311)14.1.4BSP Element Attributes (312)14.1.5Element Handler Class (312)14.1.6BSP F1 Help Controller Method—DO_REQUEST (318)14.1.7Implementing the BSP F1 Help Application—Model (318)14.2Dialog Windows (319)14.3F4—Value Help (322)14.3.1Value Help Requirements (322)14.3.2The Solution (323)14.3.3The New BSP Element (324)14.3.4Input Help Controller (325)14.3.5Input Help View (326)14.3.6Input Help Model (329)15Internationalization33715.1Multiple Language Support (337)15.2Logon Language (338)15.3Unicode (341)15.3.1What is Unicode? (341)15.3.2Unicode in BSP (343)15.4Online Text Repository (OTR) (346)15.4.1Types of OTR: Alias and Long (347)15.4.2Working with OTR from ABAP Code (348)15.4.3Special Note about using OTR (349)10Contents15.5.1OTR (350)15.5.2Field Labels and Quick Info (351)15.6Date Format (352)16Document Handling in BSP35516.1MIME Repository (355)16.2ICM File Handler (357)16.3Handling Non-HTML Documents (358)16.3.1Test Program (359)16.3.2Display Document Inline (361)16.3.3Display Document Inside HTML Page (363)16.3.4Display Document in New Window (366)16.4Data Manipulation (366)16.5Microsoft Excel Download (367)16.5.1Excel Files (368)16.5.2Excel Unicode Text File (369)16.5.3Unicode Formats and Endians with Excel (369)16.5.4Conversion to Binary String (370)16.5.5Addition of the Byte Order Mark (371)16.6Pushing the Excel Content back through the browser (371)16.6.1Push Using the Current RESPONSE Object (371)16.6.2Push Using a Cached Response (372)16.7BSP Extension Element for Excel Download (374)16.7.1The Download Element User Interface (374)16.7.2The Element Properties and Attributes (375)16.7.3Compile Time and Runtime Checks (376)16.7.4Rendering Logic (377)16.7.5Trapping Events (379)16.7.6Calling the Element from a Page Layout (380)16.7.7Event Handler (381)16.7.8Get Structure Definition (385)16.7.9Process Excel Download (386)16.8Alternatives to the MIME Repository (389)16.8.1ICM File Handler (389)16.8.2SAP Content and Cache Server (390)16.9ZIP Tool (392)17Customization39517.1Customization Overview (395)17.2Export—Modify—Import (395)17.3NetWeaver Theme Editor (397)11Contents17.4ALFS—ABAP Look-and-Feel Service (398)17.4.1ALFS Tool Scope (399)17.4.2What is ALFS? (399)17.4.3How Does Customization Normally Work? (401)17.4.4 A New Theme from Five Colors (401)17.4.5Integration into Web AS (402)17.4.6The Source Code: Making It Work (404)17.4.7ALFS Theme Editor in Detail (405)17.5Configure a Theme Root (406)17.6Theme Root White List (406)17.7Error Pages (408)17.7.1Historical BSP Error Pages (408)17.7.2Error Pages—New Approach (409)17.8Logon Application (412)18Skilled in the Art41718.1Field History (417)18.1.1Working with <phtmlb:comboBox> (417)18.1.2Processing the Field History (419)18.2Server-Side Printing (422)18.2.1PRINT Method Interface (423)18.2.2PRINT Method Coding (424)18.2.3Printer Dialog (426)18.3Select-Options/Parameters (429)18.3.1UI Design (430)18.3.2Solution Structure (431)18.3.3Select-Option Controller Class Attributes (432)18.3.4Select-Option Controller Class Coding (432)18.3.5Select-Option Model Class Attributes (434)18.3.6Select-Option Model Class Coding (436)18.3.7Recreating Transaction SE16 (442)19Breaking Out of the Mold44919.1Interactive Excel (449)19.2RSS Feeds (451)19.2.1Consuming an RSS Feed (451)19.2.2HTTP Client (452)19.2.3XML (453)19.2.4BSP Output (454)19.2.5XSLT (456)19.2.6Creating an RSS Feed (457)12Contents19.3Mini-Portal (458)19.3.1Mini-Portal Example 1—Common Page Header (458)19.3.2Mini-Portal Example 2—Portal with Navigation (460)19.3.3Portal within the SAP GUI (464)19.3.4Current Weather Display (466)20Closing471A Appendix—BSP Utility Classes473B The Authors483Index48513ContentsIntroductionThe history of BSP began in the late 1990s. Back then, the SAP Internet Transac-tion Server (ITS) and the SAP Workplace—SAP’s first attempt at a portal—depended heavily on the use of external Web servers. These solutions neither lev-eraged the inherent strengths of the ABAP technology nor re-used current devel-opers’ skill sets.Therein lay the greatest technical challenge to SAP as Web-based technologies became essential to all businesses. Companies began to realize that E-business was still just business and therefore expected their ERP solutions to transition eas-ily into this brave new world.Starting with Release 6.10, SAP began a major overhaul of its ABAP technology stack. The company broke the traditional Basis layer away from the applications that ran on it and renamed this new technology layer Web Application Server (Web AS). But this name change was far more than a marketing move. With this release, SAP had begun to build native Web server technology into the ABAP Ker-nel. No longer would SAP technology be dependent upon external Web serversor programming languages. ABAP itself was now HTTP-enabled!Naturally, ABAP was extended with a new Web development environment, called Business Server Pages (BSP). Like all other ABAP programming tools, BSP is integrated into the ABAP Workbench (SE80) and fully supports the Transport Management System (TMS). And, given its recent birth, BSP also fully embracesthe new ABAP object-oriented technology.Target AudienceThe target audience for this book is anyone who is currently an ABAP developeror who is interested in becoming an ABAP developer. BSP is another tool in the developer’s tool box, one that adds value to any ABAP development team.It does not matter if you have never done BSP development, are a novice BSP developer, or have several years of BSP development under your belt; there should be something for everyone in this book. We attempted to make this the definitive work on the subject of BSP, revealing behind-the-scenes aspects and discussing features in a new way.This book is not based solely on the underlying technology. Several years of expe-rience building real-world BSP applications at a customer site were also used in writing this book. Therefore, you will find solutions and sample source code to15Introductionhelp you overcome common development hurdles. Toward that goal, you will find all the example source code presented in this book on the accompanying CD.On What Releases Can You Use BSP?BSP has been shipped as an integrated part of the ABAP technology stack since Web AS Release 6.10. Release 6.10 contains the functionality to create basic BSP pages with flow logic.With Web AS Release 6.20, SAP introduced major enhancements to the BSP technology: Model View Controller and BSP Extension Elements. With Release6.20, Service Pack 34, a new HTML rendering engine, and a complete new BSPExtension library, PHTMLB, were added. Because of these additional enhance-ments to BSP, customer development should really only be done on Web AS 6.20 with SP34 or higher.SAP continued to enhance BSP with SAP NetWeaver ’04 (Web AS 6.40) and SAP NetWeaver ’04S (Web AS 7.0); however, nearly every feature of BSP is in sync between the major releases. This means that even if you are on an older Web AS6.20, you still reap the benefits of new developments within the NetWeaverreleases. Although you will rarely find in this book that a feature is limited to a specific release, we will point this out when it occurs.With the coverage for BSP within the latest technology releases of ABAP, you will find BSP present in the equivalent releases of the SAP application components as well. This means, for instance, that R/3 Enterprise (with or without Extension Set1.10 and2.00) and mySAP ERP 2005 (also known as Enterprise Core Component5.00 or ECC 5.00) both contain the technology necessary to create BSP applica-tions.BSP vs. Web Dynpro ABAPIn the past year, much of the attention within the SAP world has focused on SAP’s next generation technology: Web Dynpro. As this book goes to print, Web Dyn-pro for ABAP is scheduled for general availability in spring of 2006.In truth, Web Dynpro contains many of the enhancements that BSP developers have always wanted. Enhancements like built-in value-help and select options will become standard in Web Dynpro, but must be added by the customer into the BSP environment. Do not worry, however: The task of adding many of these enhancements to BSP is the subject of the last one-third of this book.All this begs the question: If Web Dynpro ABAP (WDA) is so great, why continue to use BSP (or for that matter why write a book about it?). There are several archi-16Introductiontectural differences between BSP and WDA. WDA may have some more advanced features compared to BSP, but it is a far more restrictive framework. First of all, WDA is stateful only. BSP supports both stateful and stateless pro-gramming models. Stateless programming is essential to high-performance Inter-net-facing applications.WDA is also designed to be future-proof, obscuring the specific client’s rendering technology. As a consequence, the tool does not allow low-level access to include your own custom HTML, JavaScript, or other controls. WDA targets the browser today, but tomorrow it might well be running within a smart client using entirely different technologies (such as XML and native UI controls). To keep this technol-ogy switch possible, the rendering logic is completely hidden from the developer, presenting only an abstract UI layer with abstract controls. On the other hand, BSP has no such restrictions. BSP is strictly centered on browser-based deploy-ment and therefore allows an extreme level of custom rendering. This makes BSPa perfect platform for applications that require pixel-perfect layout or specializedUI elements.The other aspect to consider is that Web Dynpro ABAP will not be available until NetWeaver ’04S. Therefore, you must upgrade your existing system to be able to use these new development tools. BSP, on the other hand, has been available for several years and is included in the vast majority of supported SAP product releases. For several more years, BSP may be your only choice for Web develop-ment using the ABAP language.AcknowledgementsFirst, we would like to thank the SAP Developer Network (SDN) content team, particularly Mark Finnern and Craig Cmehil, for not only providing a great servicein the form of SDN, but also making sure that BSP has its comfortable little home there.This book itself has deep roots within SDN. In fact, it is doubtful that it would exist at all if were not for SDN. Several sections of the book have their roots as SDN weblogs. The two authors of this book (who to this day have never met in person or even spoken on the phone) would likely never have crossed paths wereit not for the virtual community that is SDN.For their support, guidance and suggestions, Thomas would like to thank co-workers and friends: Chris Cassidy, Sam Mason, Lynn Scheu, and Sandy Smith. A special thanks goes to Steffen Knoeller, who behind the scenes has influenced many chapters in this book, without even knowing it!17AcknowledgementsBrian would wish to thank the complete team that made BSP happen. There is Albert Becker, who showed a team can work across many groups, and who taught the lesson late one night that VPs still know how to debug ABAP code. There are the ICM colleagues, Oliver Luik and Bernhard Braun, who measured performance in CPU cycles and give a new appreciation for “blazing fast.” Not to be forgotten are their partners in crime, the ICF colleagues: Masoud Aghadavoodi, Christoph Hofmann, and Daniel Walz, who has helped many hours so that we could write our first Web-based logon application. Then there are the men in black, the secu-rity group: Wolfgang Janzen and Martin Rex. The last import group required to start the project was the ABAP Language Group: Andreas Blumenthal, who fights like a lion for anything with ABAP stamped on it and who did a lot for BSP (even although it was not called ABAP Server Pages!); Holger Janz, who taught me the elegance of ABAP programming; Jürgen Lehmann and Peter Januschke, who taught me the complexities of compiler writing in ABAP and that it is actually quiet easy; Klaus Ziegler and Kay Mueller-Silva, who integrated JavaScript, Ulrich Elsaesser, who always used a short pencil for the pre-compiler; and the x-team, Karsten Bohlmann (XSLT) and Rupert Hieble (XML).In building BSP itself, the Workbench needed minor tweaking, plus some hard development by: Sigrun Wintzheimer, Michael Wenz, Margarethe Czarnecki, Andreas Herrmann, and, of course, Jürgen Remmel. The runtime was done by our small group: Rüdiger Kretschmer, who had the idea (and together with a col-league wrote the first ABAP book, and always knows the answers to everything or knows someone that knows); Björn Goerke who hacked the runtime years ago;Regina Breuer who did MVC; Jutta Bindewald, and Arndt Rosenthal.And then there is Steffen Knoeller, who shared my office for years and taught me HTML. Quality management was done by Michael Lottbrein, who rolled the first sneak preview out the door, Judith Rabetge, and Rainer Liebisch. Heidi von Gei-sau and Tina Haug wrote all documentation. Our first support steps were handled by Dongyan Zhao. Not to be forgotten is our extended support troop: Artem Gratchev, Vitaly Romanko, Yulia Kuznetsova, Dmitry Vladimirov, and Andrey Ali-mov. They not only taught me two words in Russian, but they also showed each and every time that the trickiest problems are theirs to solve! Finally, a good product required a few good salesmen: Axel Kurka (who passed away unexpect-edly and before his time; we will remember him fondly) and Dirk Feeken, who came up with the BSP name over lunch!Brian can only say: It is still a great team!For his guidance and patience, we wish to thank our publisher from Galileo Press, Florian Zimniak. Although we broke every rule and deadline he gave us, he stuck18Introductionwith us till the end. We also thank John Parker of SAP PRESS America for his edi-torial skills and for also putting up with our rule-breaking nature.Finally we must thank our families who put up with us through this experience. Without the support of our wives, Shari and Anja, we would never have pulled it through.19Acknowledgements11Creating your own BSP ExtensionElementWe already have seen in the last few chapters how powerful the BSPExtension Framework is. Fortunately, this is also an open technologyframework that allows SAP’s customers to build their own BSP exten-sions and to combine existing extensions to create composite ele-ments.11.1Creating a BSP Extension ElementIn Chapter 9, we took a close look at how BSP extension elements are structuredin order to better understand how to use them. However, this only scratched the surface of what lies within the BSP extension element. Before we begin the pro-cess of writing our own elements, it is important to study in detail the most important part of an extension element: its element-handler class.11.1.1Extension Framework HierarchyThe element-handler class actually represents an inherited hierarchy of class objects that all come together to form the extension framework. It is important to build this inheritance hierarchy correctly, because much of the functionality wewill code within our handler will be placed inside of redefinitions of inherited methods.The core extension framework comprises two objects, IF_BSP_ELEMENT and CL_BSP_ELEMENT. IF_BSP_ELEMENT defines all the core methods and attributes forthe extension framework. CL_BSP_ELEMENT implements the IF_BSP_ELEMENT interface and provides the basic functions that support all BSP extension ele-ments.There are two more objects within this hierarchy, both specific to the individual extension element. The first is a generated basis class, usually created with the fol-lowing naming standard:(Z)CL G_<EXTENSION>_<ELEMENT>This class is automatically generated by the BSP development environment. Whenyou define attributes for your extension element inside the BSP extension editor, these attributes will be generated as public attributes of this basis class. This class should also inherit from CL_BSP_ELEMENT and provide the specific constructorfor the element. By dynamically generating this class, all the attributes of your ele-ment can be strictly typed and checked at compile time.227Creating your own BSP Extension ElementThe final object is the core handler class itself. It should inherit from the generated basis class, and its name is completely user definable. However it is probably good form to following a naming standard such as the following:(Z)CL_<EXTENSION>_<ELEMENT>This class is where you will be spending most of your time as an element author.This class has the method redefinitions and any specific methods or attributes needed to implement the element.11.1.2User-Defined ValidationBSP extension elements are unique among the ABAP language tools in their approach to input validation. The extension runtime gives you the opportunity to code different validation routines that will be executed at runtime and compile time. That means that the syntax check of a BSP page will fire validation code that you can write. This gives you the ability to throw compiler errors for your own elements.In order to implement user-defined validation, we must redefine two methods in our handler class that were inherited down from IF_BSP_ELEMENT.The first method is COMPILE_TIME_IS_VALID. This is where we will code our compile time checks. SAP provides a series of validation methods (in class CL_ BSP_ELEMENT_CT_ATTR_VALID), which assist in this process. In addition to pro-viding simple checks, these methods also properly convert attribute-input string values into Boolean and integers values where necessary.What follows are coding examples for the validation routines of a fictional BSP Extension Element. They contain common types of checks in order to demon-strate the different possible techniques.METHOD if_bsp_element~compile_time_is_valid .validator->to_enum( name = 'Color'enums = 'RED/BLUE/GREEN' ).validator->to_enum( name = 'alignment'enums = 'LEFT/RIGHT' ).validator->to_boolean( name = 'disabled' ).validator->to_integer( name = 'size' ).valid = validator->m_all_values_valid.ENDMETHOD.We also have the method RUNTIME_IS_VALID. This method is useful for checking attribute values that are supplied dynamically, such as through BSP expressions228Creating your own BSP Extension Element(<%=...%>) only at runtime, or for attributes whose values are transformed into another data type.METHOD if_bsp_element~runtime_is_valid.get_class_named_parent(class_name = 'CL_HTMLB_CONTENT' ).IF runtime_parms = '/*/' OR runtime_parms CS 'alignment'.alignment = m_validator->to_enum(name = 'alignment'value = alignmentenums = 'LEFT/RIGHT'required = space ).ENDIF.IF runtime_parms = '/*/' OR runtime_parms CS 'disabled'.disabled = m_validator->bindable_to_boolean(name = 'disabled'value = disabledbinding_path = _disabledpage_context = m_page_context ).ENDIF.IF runtime_parms = '/*/' OR runtime_parms CS 'size'.size = m_validator->bindable_to_integer(name = 'size'value = sizebinding_path = _sizepage_context = m_page_context ).ENDIF.ENDMETHOD.The first line in the runtime validation method checks that this BSP element is used with an <htmlb:content> element. It is not possible to check this at com-pile time, as different elements can be used in different views, and these are com-piled separately. We surround each of our dynamic value checks with an IF checkfor performance. That way we only perform validation routines on attributes that actually have values set dynamically.It is important to note that these two validation methods will only be called if the User-Defined Validation option is selected in the BSP Element Properties. That way, if you have no validations that you wish to perform in your element, you can save the time that it would have taken for the framework to make calls into simply empty methods.229Creating a BSP Extension Element。

NXP SCM-i.MX 6 Series Yocto Linux 用户指南说明书

NXP SCM-i.MX 6 Series Yocto Linux 用户指南说明书

© 2017 NXP B.V.SCM-i.MX 6 Series Yocto Linux User'sGuide1. IntroductionThe NXP SCM Linux BSP (Board Support Package) leverages the existing i.MX 6 Linux BSP release L4.1.15-2.0.0. The i.MX Linux BSP is a collection of binary files, source code, and support files that can be used to create a U-Boot bootloader, a Linux kernel image, and a root file system. The Yocto Project is the framework of choice to build the images described in this document, although other methods can be also used.The purpose of this document is to explain how to build an image and install the Linux BSP using the Yocto Project build environment on the SCM-i.MX 6Dual/Quad Quick Start (QWKS) board and the SCM-i.MX 6SoloX Evaluation Board (EVB). This release supports these SCM-i.MX 6 Series boards:• Quick Start Board for SCM-i.MX 6Dual/6Quad (QWKS-SCMIMX6DQ)• Evaluation Board for SCM-i.MX 6SoloX (EVB-SCMIMX6SX)NXP Semiconductors Document Number: SCMIMX6LRNUGUser's GuideRev. L4.1.15-2.0.0-ga , 04/2017Contents1. Introduction........................................................................ 1 1.1. Supporting documents ............................................ 22. Enabling Linux OS for SCM-i.MX 6Dual/6Quad/SoloX .. 2 2.1. Host setup ............................................................... 2 2.2. Host packages ......................................................... 23.Building Linux OS for SCM i.MX platforms .................... 3 3.1. Setting up the Repo utility ...................................... 3 3.2. Installing Yocto Project layers ................................ 3 3.3. Building the Yocto image ....................................... 4 3.4. Choosing a graphical back end ............................... 4 4. Deploying the image .......................................................... 5 4.1. Flashing the SD card image .................................... 5 4.2. MFGTool (Manufacturing Tool) ............................ 6 5. Specifying displays ............................................................ 6 6. Reset and boot switch configuration .................................. 7 6.1. Boot switch settings for QWKS SCM-i.MX 6D/Q . 7 6.2. Boot switch settings for EVB SCM-i.MX 6SoloX . 8 7. SCM uboot and kernel repos .............................................. 8 8. References.......................................................................... 8 9.Revision history (9)Enabling Linux OS for SCM-i.MX 6Dual/6Quad/SoloX1.1. Supporting documentsThese documents provide additional information and can be found at the NXP webpage (L4.1.15-2.0.0_LINUX_DOCS):•i.MX Linux® Release Notes—Provides the release information.•i.MX Linux® User's Guide—Contains the information on installing the U-Boot and Linux OS and using the i.MX-specific features.•i.MX Yocto Project User's Guide—Contains the instructions for setting up and building the Linux OS in the Yocto Project.•i.MX Linux®Reference Manual—Contains the information about the Linux drivers for i.MX.•i.MX BSP Porting Guide—Contains the instructions to port the BSP to a new board.These quick start guides contain basic information about the board and its setup:•QWKS board for SCM-i.MX 6D/Q Quick Start Guide•Evaluation board for SCM-i.MX 6SoloX Quick Start Guide2. Enabling Linux OS for SCM-i.MX 6Dual/6Quad/SoloXThis section describes how to obtain the SCM-related build environment for Yocto. This assumes that you are familiar with the standard i.MX Yocto Linux OS BSP environment and build process. If you are not familiar with this process, see the NXP Yocto Project User’s Guide (available at L4.1.15-2.0.0_LINUX_DOCS).2.1. Host setupTo get the Yocto Project expected behavior on a Linux OS host machine, install the packages and utilities described below. The hard disk space required on the host machine is an important consideration. For example, when building on a machine running Ubuntu, the minimum hard disk space required is about 50 GB for the X11 backend. It is recommended that at least 120 GB is provided, which is enough to compile any backend.The minimum recommended Ubuntu version is 14.04, but the builds for dizzy work on 12.04 (or later). Earlier versions may cause the Yocto Project build setup to fail, because it requires python versions only available on Ubuntu 12.04 (or later). See the Yocto Project reference manual for more information.2.2. Host packagesThe Yocto Project build requires that the packages documented under the Yocto Project are installed for the build. Visit the Yocto Project Quick Start at /docs/current/yocto-project-qs/yocto-project-qs.html and check for the packages that must be installed on your build machine.The essential Yocto Project host packages are:$ sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib build-essential chrpath socat libsdl1.2-devThe i.MX layers’ host packages for the Ubuntu 12.04 (or 14.04) host setup are:$ sudo apt-get install libsdl1.2-dev xterm sed cvs subversion coreutils texi2html docbook-utils python-pysqlite2 help2man make gcc g++ desktop-file-utils libgl1-mesa-dev libglu1-mesa-dev mercurial autoconf automake groff curl lzop asciidocThe i.MX layers’ host packages for the Ubuntu 12.04 host setup are:$ sudo apt-get install uboot-mkimageThe i.MX layers’ host packages for the Ubuntu 14.04 host s etup are:$ sudo apt-get install u-boot-toolsThe configuration tool uses the default version of grep that is on your build machine. If there is a different version of grep in your path, it may cause the builds to fail. One workaround is to rename the special versi on to something not containing “grep”.3. Building Linux OS for SCM i.MX platforms3.1. Setting up the Repo utilityRepo is a tool built on top of GIT, which makes it easier to manage projects that contain multiple repositories that do not have to be on the same server. Repo complements the layered nature of the Yocto Project very well, making it easier for customers to add their own layers to the BSP.To install the Repo utility, perform these steps:1.Create a bin folder in the home directory.$ mkdir ~/bin (this step may not be needed if the bin folder already exists)$ curl /git-repo-downloads/repo > ~/bin/repo$ chmod a+x ~/bin/repo2.Add this line to the .bashrc file to ensure that the ~/bin folder is in your PATH variable:$ export PATH=~/bin:$PATH3.2. Installing Yocto Project layersAll the SCM-related changes are collected in the new meta-nxp-imx-scm layer, which is obtained through the Repo sync pointing to the corresponding scm-imx branch.Make sure that GIT is set up properly with these commands:$ git config --global "Your Name"$ git config --global user.email "Your Email"$ git config --listThe NXP Yocto Project BSP Release directory contains the sources directory, which contains the recipes used to build, one (or more) build directories, and a set of scripts used to set up the environment. The recipes used to build the project come from both the community and NXP. The Yocto Project layers are downloaded to the sources directory. This sets up the recipes that are used to build the project. The following code snippets show how to set up the SCM L4.1.15-2.0.0_ga Yocto environment for the SCM-i.MX 6 QWKS board and the evaluation board. In this example, a directory called fsl-arm-yocto-bsp is created for the project. Any name can be used instead of this.Building Linux OS for SCM i.MX platforms3.2.1. SCM-i.MX 6D/Q quick start board$ mkdir fsl-arm-yocto-bsp$ cd fsl-arm-yocto-bsp$ repo init -u git:///imx/fsl-arm-yocto-bsp.git -b imx-4.1-krogoth -m scm-imx-4.1.15-2.0.0.xml$ repo sync3.2.2. SCM-i.MX 6SoloX evaluation board$ mkdir my-evb_6sxscm-yocto-bsp$ cd my-evb_6sxscm-yocto-bsp$ repo init -u git:///imx/fsl-arm-yocto-bsp.git -b imx-4.1-krogoth -m scm-imx-4.1.15-2.0.0.xml$ repo sync3.3. Building the Yocto imageNote that the quick start board for SCM-i.MX 6D/Q and the evaluation board for SCM-i.MX 6SoloX are commercially available with a 1 GB LPDDR2 PoP memory configuration.This release supports the imx6dqscm-1gb-qwks, imx6dqscm-1gb-qwks-rev3, and imx6sxscm-1gb-evb. Set the machine configuration in MACHINE= in the following section.3.3.1. Choosing a machineChoose the machine configuration that matches your reference board.•imx6dqscm-1gb-qwks (QWKS board for SCM-i.MX 6DQ with 1 GB LPDDR2 PoP)•imx6dqscm-1gb-qwks-rev3 (QWKS board Rev C for SCM-i.MX 6DQ with 1GB LPDDR2 PoP) •imx6sxscm-1gb-evb (EVB for SCM-i.MX 6SX with 1 GB LPDDR2 PoP)3.4. Choosing a graphical back endBefore the setup, choose a graphical back end. The default is X11.Choose one of these graphical back ends:•X11•Wayland: using the Weston compositor•XWayland•FrameBufferSpecify the machine configuration for each graphical back end.The following are examples of building the Yocto image for each back end using the QWKS board for SCM-i.MX 6D/Q and the evaluation board for SCM-i.MX 6SoloX. Do not forget to replace the machine configuration with what matches your reference board.3.4.1. X11 image on QWKS board Rev C for SCM-i.MX 6D/Q$ DISTRO=fsl-imx-x11 imx6dqscm-1gb-qwks-rev3 source fsl-setup-release.sh -b build-x11$ bitbake fsl-image-gui3.4.2. FrameBuffer image on evaluation board for SCM-i.MX 6SX$ DISTRO=fsl-imx-fb MACHINE=imx6sxscm-1gb-evb source fsl-setup-release.sh –b build-fb-evb_6sxscm$ bitbake fsl-image-qt53.4.3. XWayland image on QWKS board for SCM-i.MX 6D/Q$ DISTRO=fsl-imx-xwayland MACHINE=imx6dqscm-1gb-qwks source fsl-setup-release.sh –b build-xwayland$ bitbake fsl-image-gui3.4.4. Wayland image on QWKS board for SCM-i.MX 6D/Q$ DISTRO=fsl-imx-wayland MACHINE=imx6dqscm-1gb-qwks source fsl-setup-release.sh -b build-wayland$ bitbake fsl-image-qt5The fsl-setup-release script installs the meta-fsl-bsp-release layer and configures theDISTRO_FEATURES required to choose the graphical back end. The –b parameter specifies the build directory target. In this build directory, the conf directory that contains the local.conf file is created from the setup where the MACHINE and DISTRO_FEATURES are set. The meta-fslbsp-release layer is added into the bblayer.conf file in the conf directory under the build directory specified by the –e parameter.4. Deploying the imageAfter the build is complete, the created image resides in the <build directory>/tmp/deploy/images directory. The image is (for the most part) specific to the machine set in the environment setup. Each image build creates the U-Boot, kernel, and image type based on the IMAGE_FSTYPES defined in the machine configuration file. Most machine configurations provide the SD card image (.sdcard), ext4, and tar.bz2. The ext4 is the root file system only. The .sdcard image contains the U-Boot, kernel, and rootfs, completely set up for use on an SD card.4.1. Flashing the SD card imageThe SD card image provides the full system to boot with the U-Boot and kernel. To flash the SD card image, run this command:$ sudo dd if=<image name>.sdcard of=/dev/sd<partition> bs=1M && syncFor more information about flashing, see “P reparing an SD/MMC Card to Boot” in the i.MX Linux User's Guide (document IMXLUG).Specifying displays4.2. MFGTool (Manufacturing Tool)MFGTool is one of the ways to place the image on a device. To download the manufacturing tool for the SCM-i.MX 6D/Q and for details on how to use it, download the SCM-i.MX 6 Manufacturing Toolkit for Linux 4.1.15-2.0.0 under the "Downloads" tab from /qwks-scm-imx6dq. Similarly, download the manufacturing tool for the SCM-i.MX 6SoloX evaluation board under the "Downloads" tab from /evb-scm-imx6sx.5. Specifying displaysSpecify the display information on the Linux OS boot command line. It is not dependent on the source of the Linux OS image. If nothing is specified for the display, the settings in the device tree are used. Find the specific parameters in the i.MX 6 Release Notes L4.1.15-2.0.0 (available at L4.1.15-2.0.0_LINUX_DOCS). The examples are shown in the following subsections. Interrupt the auto-boot and enter the following commands.5.1.1. Display options for QWKS board for SCM-i.MX 6D/QHDMI displayU-Boot > setenv mmcargs 'setenv bootargs console=${console},${baudrate} ${smp}root=${mmcroot} video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24'U-Boot > run bootcmd5.1.2. Display options for EVB for SCM-i.MX 6SXNote that the SCM-i.MX 6SX EVB supports HDMI with a HDMI accessory card (MCIMXHDMICARD) that plugs into the LCD connector on the EVB.Accessory boards:•The LVDS connector pairs with the NXP MCIMX-LVDS1 LCD display board.•The LCD expansion connector (parallel, 24-bit) pairs with the NXP MCIMXHDMICARD adapter board.LVDS displayU-Boot > setenv mmcargs 'setenv bootargs console=${console},${baudrate} ${smp}root=${mmcroot} ${dmfc} video=mxcfb0:dev=ldb,1024x768M@60,if=RGB666 ldb=sep0'U-Boot > run bootcmdHDMI display (dual display for the HDMI as primary and the LVDS as secondary)U-Boot > setenv mmcargs 'setenv bootargs console=${console},${baudrate} ${smp}root=${mmcroot} video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24video=mxcfb1:dev=ldb,LDBXGA,if=RGB666'U-Boot > run bootcmdLCD displayu-boot > setenv mmcargs 'setenv bootargs ${bootargs}root=${mmcroot} rootwait rw video=mxcfb0:dev=lcd,if=RGB565'u-boot> run bootcmd6. Reset and boot switch configuration6.1. Boot switch settings for QWKS SCM-i.MX 6D/QThere are two push-button switches on the QWKS-SCMIMX6DQ board. SW1 (SW3 for QWKS board Rev B) is the system reset that resets the PMIC. SW2 is the i.MX 6Dual/6Quad on/off button that is needed for Android.There are three boot options. The board can boot either from the internal SPI-NOR flash inside the SCM-i.MX6Dual/6Quad or from either of the two SD card slots. The following table shows the switch settings for the boot options.Table 1.Boot configuration switch settingsBoot from top SD slot (SD3)Boot from bottom SD slot (SD2)Boot from internal SPI NORDefault1.References6.2. Boot switch settings for EVB SCM-i.MX 6SoloXThis table shows the jumper configuration to boot the evaluation board from the SD card slot SD3.7. SCM uboot and kernel repositoriesThe kernel and uboot patches for both SCM-i.MX 6 QWKS board and evaluation board are integrated in specific git repositories. Below are the git repos for SCM-i.MX 6 uboot and kernel:uBoot repo: /git/cgit.cgi/imx/uboot-imx.gitSCM Branch: scm-imx_v2016.03_4.1.15_2.0.0_gakernel repo: /git/cgit.cgi/imx/linux-imx.gitSCM branch: scm-imx_4.1.15_2.0.0_ga8. References1.For details about setting up the Host and Yocto Project, see the NXP Yocto Project User’s Guide(document IMXLXYOCTOUG).2.For information about downloading images using U-Boot, see “Downloading images usingU-Boot” in the i.MX Linux User's Guide (document IMXLUG).3.For information about setting up the SD/MMC card, see “P reparing an SD/MMC card to boot” inthe i.MX Linux User's Guide (document IMXLUG).9. Revision historyDocument Number: SCMIMX6LRNUGRev. L4.1.15-2.0.0-ga04/2017How to Reach Us: Home Page: Web Support: /supportInformation in this document is provided solely to enable system and softwareimplementers to use NXP products. There are no express or implied copyright licenses granted hereunder to design or fabricate any integrated circuits based on the information in this document. NXP reserves the right to make changes without further notice to any products herein.NXP makes no warranty, representation, or guarantee regarding the suitability of its products for any particular purpose, nor does NXP assume any liability arising out of the application or use of any product or circuit, and specifically disclaims any and all liability, including without limitation consequentia l or incidental damages. “Typical”parameters that may be provided in NXP data sheets and/or specifications can and do vary in different applications, and actual performance may vary over time. All operating parameters, including “typicals,” must be valida ted for each customer application by customer’s technical experts. NXP does not convey any license under its patent rights nor the rights of others. NXP sells products pursuant to standard terms and conditions of sale, which can be found at the following address: /SalesTermsandConditions .NXP, the NXP logo, NXP SECURE CONNECTIONS FOR A SMARTER WORLD, Freescale, and the Freescale logo are trademarks of NXP B.V. All other product or service names are the property of their respective owners.ARM, the ARM Powered logo, and Cortex are registered trademarks of ARM Limited (or its subsidiaries) in the EU and/or elsewhere. All rights reserved. © 2017 NXP B.V.。

刷Tomato简易教程-菜鸟必备

刷Tomato简易教程-菜鸟必备

刷Tomato简易教程-菜鸟必备Tomato固件因其稳定性而著称,当然,它优点绝不止这点,图形化显示流量,QOS功能效果显著(上网优先级设定功能,常用封BT,迅雷等,就算不封也能让它们尽量少对浏览网页或玩游戏造成影响),中文版作者darkpiggy达人还为我们提供了硬件信息查看功能(可以看到CPU主频,内存容量,闪存容量,有线及无线网卡详细信息等),最新的1.11版还提供了定时重启系统的功能,越来越多的朋友都加入到Tomato阵营中来了!现在网上流传刷Tomato的方法,看起来很复杂,说要刷Tomato,必须先刷DD-WRT,再用进telnet用nvram show | grep http_passwd 取得密码,再刷T omato等,这样搞得一些想用Tomato的朋友,因此望而却步了……作为Tomato中文论坛的版主,为了让我们的Tomato中文版Fans群体日益壮大,也算是为庆祝我的无线淘宝小店升钻,我想我有义务写出简易教程给朋友们了。

其实,刷Tomato哪用这么复杂?现在,我就用大家用得最多的几种环境下分别介绍如何简装快速的刷Tomato!Are you ready?Let’s go!首先,你得确定自己的机器支持Tomato固件,否则请不要尝试刷Tomato,关于哪些机器支持Tomato,请看/dispbbs.asp?b oardID=4&ID=20&page=1,如果你的机器型号及硬件版本号出现在了列表中,那么,恭喜你,你可以使用Tomato了在上下载最新的Tomato中文版,一般你会得到imag e.7z的文件(也可能会是image.rar,解压后仍会得到image.7z)。

这个文件也是个压缩文件,需要用最新版的WinRar解压缩软件下解压,如果你的WinRar不能打开image.7z,请上网下载最新版的WinRar来解压。

解压后,会得到WRT SL54GS.bin,WRT54GSv4.bin,WRT54GS.bin,WRT54G.bin,WR850G.bin,tomato. trx,readme.htm这些文件,其中tomato.trx是通用固件,在支持列表中的机器都可以用它,那我们就用它吧!因为一些固件只认bin文件,所以,请先把tomato.trx改名成tomato.bin 然后,就下面的环境刷到tomato分别进行介绍注:升级固件请用有线而不要用无线,并且在升级过程中千万不要断网断电第1种环境:从Linksys WRT54G/GL/GS等原厂固件刷到Tomato先登录路由器,默认的IP地址是192.168.1.1,密码和用户名都是admin,如果你更好了路由器的IP及密码,请用你自己的设置进行登录,在此我按默认的设置进行介绍:在浏览器中输入192.168.1.1,在弹出的输入框的两项都输入admin 后就成功登录了路由器。

python pyqt6 mcv架构 实例

python pyqt6 mcv架构 实例

python pyqt6 mcv架构实例全文共四篇示例,供读者参考第一篇示例:Python是一种广泛应用于软件开发领域的高级编程语言,而PyQt6则是Python语言的一个GUI库,用于创建图形用户界面。

在软件开发中,通常会采用一种设计模式来组织代码结构,其中MVC (Model-View-Controller)是一种常见的架构模式,用于将应用程序划分为三个部分:模型(Model)、视图(View)和控制器(Controller)。

这种分层架构更好地实现了代码的组织和复用,使得代码更易维护和扩展。

本文将介绍如何使用Python和PyQt6实现MVC架构,以创建一个简单的图形界面应用程序。

在本示例中,我们将创建一个简单的学生成绩管理系统,用户可以输入学生的姓名和成绩,然后查看所有学生的成绩信息。

我们需要安装PyQt6库,可以通过pip命令进行安装:```bashpip install PyQt6```接下来,我们创建一个名为student的Python模块,该模块包含三个类:StudentModel、StudentView和StudentController。

StudentModel用于处理数据逻辑,StudentView用于显示界面,StudentController用于处理用户输入和业务逻辑。

```python# student.pyfrom PyQt6.QtCore import QObject, Qtfrom PyQt6.QtWidgets import QApplication, QLabel, QLineEdit, QPushButton, QVBoxLayout, QWidgetclass StudentModel(QObject):def __init__(self):super().__init__()self.students = []self.setWindowTitle('Student Management System')self.setGeometry(100, 100, 400, 300)yout = QVBoxLayout()self.setLayout(yout)view.show()app.exec()```在这段代码中,我们首先定义了一个StudentModel类,其中包含一个students列表用于存储学生信息。

SIWSHMAX教程

SIWSHMAX教程

SIWSHMAX教程第一章:快速入门篇A01 swishmax操作界面介绍A02 建立第一个文字特效影片文件(movie):点击输入文字(修改大小、颜色等)——选添加效果(效果可选取多个)——保存A03 swishmax软件应用的观念A04 停格的手法A05 更替文字(演员)的用途(不同层上文字输入效果)A06 文字基本设定A07 阴影效果的制作(在2个层上输入相同文字,选用不同颜色)A08 影片超链接的设定A09 汇入位图形(插入图片)A10 对象上下顺序的调整A11 效果复制,多个对象同时套用同一效果A12 五项基本工作流程:字体——修改颜色大小——文字效果——保存——导出A13 Movie(影片)、Scenes、Timeline & frame (多个场景、时间轴、影片)A14 Templates(范本)(模板,预设好的尺寸)第二章:新功能介绍一.scripting(程序撰写)B01 进阶scripting编辑接口:2个效果,第一个效果后有停顿,并继续播放后一个效果)在第一层输入文字——添加效果(2个)——在第二层(如第10帧)增加脚本(事件——帧(onFrame从第10帧开始,然后事件——影片控制stop)——回到第一层选中文字在第增加脚本(事件——按纽on press,事件——影片控制play)B02 除错debug功能:在第一帧添加脚本,事件——帧onlad(进来做什么),然后选调试trace追踪)此时显示红色,说明有误;选专家,在trace()括号中输入文字,切记要加双引号即trace(“文学”),输入后文字变成兰色,点播放影片,在右侧出现文学二.effects(特效)B03 超过230个内建特效:特效功能强大,有230个特效B04 可以自订特效并予以储存:即自己可以添加一些喜欢常用的文字效果点击T输入文字——添加效果(如墨西哥飘动),然后双击(在时间轴特效)处,出现对话框,可调整里面的设置及颜色,然后保存,它就会自动添加到文字特效中,以便下次使用B05 特效一次可以套用给多个对象三.drawing(绘图)B06 输入文字和动态文字功能:文字有三种即静态、动态、输入文字文字——文字静态——主要用来做特效文字——输入文字——名称可随意写(如第一层),可以修改格式、颜色等,主要是对输入文字的内容能直接修改,一般选格式——进阶文字——动态文字——名称(如歌词层)——脚本,事件——帧(如在第10帧)onfrane10——点专家在onfrane10后面的大括号中输入:歌词层=“变换”,既当影片播放到第10帧时原来的文字就会变为变换;如要在第1帧改变文字,则脚本,事件——点专家,将上一步内容,即onfrane10歌词层=“变换”复制,放到最前面,改为onfrane1歌词层=“开始”,然后点影片播放,在第1帧、第10帧文字会发生变化。

XBOOT系统开发指南-V0.03

XBOOT系统开发指南-V0.03
相关网址
XBOOT官方首页 https://xboot.github.io/ XBOOT源码(完全开源),寄存在github,请直接 fork 一份代码,如需申请合并,直接 pull request 即可 https:///xboot/xboot XBOOT运行效果展示页面,首次接触的用户,建议观看,对XBOOT有个直观的感受 https:///xboot/xboot/blob/master/documents/xboot-show-case-en-US.md XBOOT系统开发指南 https:///xboot/xboot/blob/master/documents/xboot-system-development-guide-en-US.md XBOOT应用开发指南 https:///xboot/xboot/blob/master/documents/xboot-application-development-guide-enUS.md XBOOT官方QQ群,大佬聚集,请踊跃加入 658250248 (2000人)
位 系统下的 X86_64 linux
sandbox
sandbox依赖与SDL2库,在编译前需要安装libsdl2-dev,以ubuntu系统为例:
sudo apt‐get install libsdl2‐dev
make clean make CROSS_COMPILE="" PLATFORM=x64‐sandbox
│ │ │ ├── mach‐n3ds
│ │ │ ├── mach‐raspi2
│ │ │ ├── mach‐realview
│ │ │ ├── mach‐v3s
│ │ │ ├── mach‐x3128
│ │ │ ├── mach‐x3288

PowerUp SYBR Green Master Mix说明书

PowerUp SYBR Green Master Mix说明书

PowerUp™ SYBR™ Green Master MixUniversal 2X master mix for real-time PCR workflowsCatalog Numbers A25741, A25742, A25743, A25776, A25777, A25778, A25779, A25780, A25918Pub. No. MAN0028468 Rev. B.0Note: For safety and biohazard guidelines, see the “Safety” appendix in the following product documentation: PowerUp™ SYBR™ Green Master Mix User Guide (Pub. No. MAN0013511). Read the Safety Data Sheets (SDSs) and follow the handling instructions. Wear appropriate protective eyewear, clothing, and gloves.This Quick Reference is intended as a benchtop reference for experienced users of PowerUp™ SYBR™ Green Master Mix. Fordetailed instructions, supplemental procedures, and troubleshooting, see the PowerUp™ SYBR™ Green Master Mix User Guide (Pub. No. MAN0013511).GuidelinesInput DNA template requirementsUse 1–10 ng single-stranded cDNA or 10–100 ng gDNA per reaction.IMPORTANT! In some cases, cDNA generated with the SuperScript™ IV VILO™ Master Mix is not compatible with the PowerUp™ SYBR™ Green Master Mix. It can result in a high background signal. To ensure consistent results across different samples and assays, we recommend a different reverse transcription kit.For kits recommended for reverse transcription of RNA to cDNA, see PowerUp™ SYBR™ Green Master Mix User Guide (Pub.No. MAN0013511).If you use SuperScript™ IV VILO™ Master Mix and your results do not show a high background signal with your assay and sample, you can continue to use the SuperScript™ IV VILO™ Master Mix and the PowerUp™ SYBR™ Green Master Mix.PCR reactions•Four replicates of each reaction are recommended.•Reaction mixes can be prepared depending upon experimental requirements. Scale the components according to the number of reactions and include 10% overage.•If using smaller reaction volumes, scale all components proportionally. Reaction volumes <10 µL are not recommended.NTC controlsNo template control (NTC) reactions can be used to identify PCR contamination. NTC reactions contain all reaction components (PowerUp™ SYBR™ Green Master Mix, primers, water) except sample, and therefore should not return a C t value.MethodsSet up the PCR reactions1.Prepare the appropriate number of reactions, plus 10% overage.[1]For optimal performance in Fast and Standard modes, use 300–800 nM for each primer.[2]Use 1–10 ng cDNA or 10–100 ng gDNA for each reaction.For Research Use Only. Not for use in diagnostic procedures.2.Mix the components thoroughly, then centrifuge briefly to spin down the contents and eliminate any air bubbles.3.Transfer the appropriate volume of each reaction to each well of an optical plate.4.Seal the plate with an optical adhesive cover, then centrifuge briefly to spin down the contents and eliminate any air bubbles.PCR can be performed on the reaction plate up to 24 hours after completing the set-up, when stored at room temperature.Set up and run the real-time PCR instrument1.Place the reaction plate in the real-time PCR instrument.2.Set the thermal cycling conditions using the default PCR thermal cycling conditions specified in the following tables according to theinstrument cycling parameters and melting temperatures of the specific primers.Note: Standard cycling conditions are recommended for genomic DNA templates. Use only standard cycling conditions for the 7900HT Real-Time PCR Instrument and the 7500 Real‑Time PCR Instrument.Table 1 Fast cycling mode (primer T m ≥60°C)[1]When using a QuantStudio™ Real-Time PCR System or a ViiA™ 7 Real-Time PCR System.[2]When using a 7500 Fast Real-Time PCR System, 7900HT Fast Real-Time PCR Instrument, StepOnePlus™ Real-Time PCR System, or StepOne™ Real-Time PCR System.Table 2 Standard cycling mode (primer T m ≥60°C)Table 3 Standard cycling mode (primer T m <60°C)[1]Anneal temperature should be set to the melting point for your primers.3.Set the instrument to perform a default dissociation step.A dissociation step can be performed up to 72 hours after the real-time PCR run if the plate is stored in the dark and up to 24 hoursafter the real-time PCR run if the plate is exposed to light.Table 4 Dissociation curve conditions (melt curve stage)[1]Dissociation2PowerUp™ SYBR™ Green Master Mix Quick ReferenceUse the following settings for Applied Biosystems™ instruments:•Experiment type: Standard curve•Reagent: SYBR™ Green reagents•Reporter: SYBR™•Quencher: None•Passive reference dye: ROX™•Ramp speed: Standard or fast (choose the same setting as in step 2)•Melt curve ramp increment: Continuous4.Set the reaction volume appropriate for the type of plate being used for your PCR reaction.5.Start the run.Analyze results1.View the amplification plots.2.Calculate the baseline and threshold cycles (C t) for the amplification curves using the instrument software.3.Check for nonspecific amplification using dissociation curves.4.Perform relative or absolute quantitation.Thermo Fisher Scientific Baltics UAB | V.A. Graiciuno 8, LT-02241 | Vilnius, LithuaniaFor descriptions of symbols on product labels or product documents, go to /symbols-definition.Revision history: Pub. No. MAN0028468The information in this guide is subject to change without notice.DISCLAIMER: TO THE EXTENT ALLOWED BY LAW, THERMO FISHER SCIENTIFIC INC. AND/OR ITS AFFILIATE(S) WILL NOT BE LIABLE FOR SPECIAL, INCIDENTAL, INDIRECT, PUNITIVE, MULTIPLE, OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH OR ARISING FROM THIS DOCUMENT, INCLUDING YOUR USE OF IT.Important Licensing Information: This product may be covered by one or more Limited Use Label Licenses. By use of this product, you accept the terms and conditions of all applicable Limited Use Label Licenses.©2023 Thermo Fisher Scientific Inc. All rights reserved. All trademarks are the property of Thermo Fisher Scientific and its subsidiaries unless otherwise specified./support | /askaquestion19 January 2023。

V-DOSC MANUAL V4 0605 1-50

V-DOSC MANUAL V4 0605 1-50

L-ACOUSTICS V-DOSC Manual Version 4
6/29/2005
Page 4 of 158
TABLE OF CONTENTS
TABLE OF CONTENTS........................................................................................................................... 5 LIST OF FIGURES.................................................................................................................................... 8 LIST OF TABLES ....................................................................................................................................10 INTRODUCTION .................................................................................................................................. 11 WAVEFRONT SCULPTURE TECHNOLOGY FUNDAMENTALS ........................................................ 11 THE SOUND REINFORCEME

抓肉鸡就用XilMax远控

抓肉鸡就用XilMax远控
在使 用 I8的时 候 ,就 发现 了 一个 E S r c e n筛 选器 功 能 .如 果 您 的筛 mat r e S 选 器没有 打开 .那么您 可以打 开 [ 8.选 E “ 安全 — — “ a ̄ c e n筛选器 ” Sm S r e .并 在 “ ma tcre S r e n筛选 器 中选 。 开 S 打
用 I8 查 网站 E检
如果担 心 你打 开的 网站 出现 安全 威 胁 .您 可 以 在 I8当 中选 安 全 ” —— E
“t8S r i筛选器 Stf c e * l eq 3 —— “ 检查此嗣站” , 由于第一攻使 用 “ 检查此嗣站 ” ,所以在弹
获得 最新 的进 程信 息 ( 图 3) 如 。在 列表
中可以 了解到进 程的 PD I、名称 、路径等
信息 .除此 以外还可 以了解到调 用这个进
十 一 年● ●
刷 新的速 也是非常 慢的 另 该木马还 外
圈 文 饭 让 _ / E 烯
保 您 的 一
设 置 S rS re 筛选 器 mat ce n
内 容 ( 图 5k 如

I l l
除 了进 行远 程桌 面的查 看 以外 .在 窗 口的标题 栏中点击 鼠标右键 .选择右键 菜 单中的 “ 屏幕”命 令 就可 以对远程桌 面 进 行实 际 的控 制.就 好像 通过 远 程桌 面 进行操作 一样。另 外还可 以通过 快捷键 Ct + t e .可 以让远 程系统 自动 的进 d AI 1 +D 行 注销操作 。 过我发现色 差设置 的较高 , 不
就能 阻止内容提 供商的信 息
很 多时候.经 常上 网的人。 总 是 会 遇 到钓 鱼 网 站或 网 络 劫持 的情 况 ,通 过 让 你在 山囊 出 来 的 假 网 站 上 输 入 银 行 账 号 和 密 码 等 重 要 信 息 ,来 盗 取 你 的 钱 财 。 Sma t c e n筛 选器和 I P ia e rS r e n r t v 筛选为 I8的安全 提供 了保障 .发 E 现 恶意 罔站 ,可 选择报 告不安全 网 蛄, 将恶 意网蛄 上报到微 软数据库 , 避 免其 它人上 当。

supervisor编译

supervisor编译

supervisor编译全文共四篇示例,供读者参考第一篇示例:【Supervisor编译】是一个非常重要的工作,它涉及到软件的管理和监控。

Supervisor本身是一个用Python编写的进程控制系统,它可以帮助用户监控和控制多个进程,并能够在进程意外退出时自动重启。

通过Supervisor的编译,我们可以更好地管理我们的进程,确保它们稳定运行。

我们需要准备编译Supervisor的环境。

在进行编译之前,我们需要确保已经安装了Python以及一些相关的依赖库,比如setuptools 等。

为了避免一些不必要的麻烦,建议先将系统更新到最新版本,以确保所有依赖库和软件都是最新的。

接着,我们需要下载Supervisor的源码文件。

可以从Supervisor 的官方网站上下载最新的源码文件,并将其解压到本地目录中。

解压后,我们可以看到一些配置文件和Python脚本,这些文件是我们编译Supervisor所需要的。

然后,我们需要运行编译的命令。

在解压后的文件夹中,找到setup.py文件,并执行以下命令:```python setup.py build```这个命令会开始编译Supervisor的源代码,并生成编译后的文件。

编译过程中可能会出现一些警告或错误,需要根据具体情况进行调试和解决。

一旦编译完成,我们可以继续执行以下命令进行安装:这个命令会将编译后的文件安装到系统中,我们就可以开始使用Supervisor了。

安装完成后,我们可以通过以下命令来启动Supervisor进程:这个命令会启动Supervisor的主进程,并根据配置文件中的设置来管理其他进程。

我们可以通过配置文件来定义需要监控的进程以及重启策略等。

Supervisor还提供了一个Web界面,方便用户查看进程状态和进行管理操作。

我们需要在系统启动时自动启动Supervisor。

可以通过编辑系统的启动脚本,将Supervisor加入到开机自启动项中,这样就能保证Supervisor在系统启动时自动运行。

superdisplay启动唯一化+命令行连续控制

superdisplay启动唯一化+命令行连续控制
您使用的浏览器不受支持建议使用新版浏览器
superdisplay启动唯一化 +命令行连续控制
superdisplay 启动唯一化
ok--参照 SuperTools 13681612496 // 唯一化,运行一个实例 if (!FirstInstance()) { if (m_pMainWnd!=NULL) { // 加入这句话,程序就可以连续执行部分命令行(但是注意不能实现连续操作, // 如打开某个文件,指定到某页,这种操作最终还是必须用消息来实现),所以采用了方法2 // 方法1 // ::SendMessage(m_MainDlg->m_hWnd, WM_COMMAND, MAKELONG(IDOK,BN_CLICKED), NULL); // m_MainDlg->OperCmd(strCmdLine); // 方法2 -- 采用此方法就保证了将命令行,转化为消息传送,这样外部程序可以调用命令行, // 也可以直接发送消息来控制 superdisplay',不过用命令行,不需要findwindow, // 因为这个工作由superdisplay自己在FirstInstance这里做了 if (m_lpCmdLine[0] != _T('\0')) { CString strMsg(m_lpCmdLine); COPYDATASTRUCT cpd; cpd.dwData = cpd.cbData = strMsg.GetLength()*sizeof(TCHAR)+1; cpd.lpData = (void*)(strMsg.GetBuffer(0)); ::SendMessage(m_pMainWnd->m_hWnd,WM_COPYDATA,NULL,(LPARAM)&cpd); } }

python supervision 用法

python supervision 用法

python supervision 用法Python Supervision 用法本文将详细介绍 Python Supervision 的用法,包括以下几个方面:1. 什么是 Python SupervisionPython Supervision 是一种跟踪和管理 Python 代码执行的技术。

它可以帮助开发人员监督和控制 Python 程序的运行,以提高程序的可靠性和稳定性。

2. Python Supervision 的主要用途•保护进程免崩溃:Supervision 工具可以检测和处理进程的崩溃情况,即使某个进程异常退出,Supervision 也能够自动重新启动该进程,保证程序的连续运行。

•监控进程状态:Supervision 能够监控进程的状态,记录和报告进程的错误情况,以便开发人员及时采取措施进行修复。

•自动重启进程:Supervision 可以设置规则,当进程异常退出时自动重启,无需手动干预。

•并发管理:Supervision 能够管理多个并发任务,确保它们按需启动和关闭,并提供灵活的管理接口。

3. 常用的 Python Supervision 工具SupervisorSupervisor 是一个常用的 Python Supervision 工具,可以用于管理和监控进程。

它提供了一个 Web 界面,用于查看和控制进程的状态。

安装 Supervisor$ pip install supervisor配置 SupervisorSupervisor 的配置文件位于/etc/。

可以通过修改该文件来配置需要监控的进程。

启动 Supervisor$ supervisord -c /etc/CircusCircus 是另一个常用的 Python Supervision 工具,旨在提供一种灵活的进程管理方式。

安装 Circus$ pip install circus配置 CircusCircus 的配置文件位于/etc/。

esxcli software profile update 参数

esxcli software profile update 参数

`esxcli software profile update` 命令用于更新ESXi 主机的软件配置文件,其参数如下:
- `--profile` 或`-p`:指定要更新的软件配置文件的名称。

- `--source` 或`-s`:指定包含更新内容的位置,可以是ISO 映像、挂载的USB 设备或网络共享。

- `--dry-run` 或`-n`:进行模拟运行,不实际执行更新操作,用于检查命令是否正确。

- `--force` 或`-f`:强制更新,即使有警告或错误也继续执行。

使用示例:
```sh
esxcli software profile update -p [profile_name] -s [source_path] -n
```
其中,`[profile_name]` 是你要更新的软件配置文件的名称,`[source_path]` 是更新源的路径。

在进行软件更新之前,建议先查看产品的升级路径和兼容性信息,确保更新的正确性和系统的稳定性。

如果不确定如何操作,可以参考官方文档或联系技术支持获取帮助。

  1. 1、下载文档前请自行甄别文档内容的完整性,平台不提供额外的编辑、内容补充、找答案等附加服务。
  2. 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
  3. 3、如文档侵犯您的权益,请联系客服反馈,我们会尽快为您处理(人工客服工作时间:9:00-18:30)。

SuperScript® VILO™ MasterMixPart no. 100012386MAN0004286Rev. Date: 6 June 2011 Cat. nos: Size:reactions 11755-050 50reactions 11755-250 250reactions 11755-500 500Store at –20°C (non-frost-free) DescriptionSuperScript® VILO™ MasterMix provides the high-temperature capability of SuperScript® III Reverse Transcriptase (RT) in an optimized format for generating first-strand cDNA for use in real-time quantitative RT-PCR (qRT-PCR). This formulation can be used with very low and very high amounts of input RNA (up to 2.5 μg total RNA in a 20-μL reaction).SuperScript® VILO™ Master Mix includes SuperScript® III RT, RNaseOUT™Recombinant Ribonuclease Inhibitor, a proprietary helper protein, random primers, MgCl2, and dNTPs.SuperScript® III RT is an engineered version of M-MLV RT with reducedRNase H activity and increased thermal stability. The enzyme can be used to synthesize cDNA at a temperature range of 42–55°C. Because SuperScript® IIIRT is not significantly inhibited by ribosomal and transfer RNA, it can beused to synthesize cDNA from total RNA. RNaseOUT™ Recombinant Ribonuclease Inhibitor safeguards against the degradation of target RNA dueto ribonuclease contamination.Component 50 rxn kit250 rxn kit 500 rxn kit SuperScript® VILO™ MasterMix 200 μL 1000 μL 2000 μLIntended Use: For research use only.Not intended for any animal or human therapeutic or diagnostic use.2Guidelines for cDNA Synthesis•High-quality, intact RNA is essential for accurate quantification in qPCR.RNA should be devoid of RNase contamination and aseptic conditions should be maintained. RNA quality can be analyzed using a bioanalyzer or by agarose gel electrophoresis.•Starting material can range up to 2.5 μg of total RNA in a 20-μL cDNA synthesis reaction. RNA quantity can be determined using UVabsorbance at 260 nm or the Qubit® RNA Assay Kit and Qubit® 2.0Fluorometer (see page 4 for ordering information).•To isolate total RNA, we recommend TRIzol® Reagent, the PureLink®RNA Mini Kit, or the MagMAX™-96 Total RNA Isolation Kit (see page 4).Isolation of mRNA is typically not necessary, although incorporating this step may improve the yield of specific cDNAs.•DNase I, Amplification Grade, may be used to eliminate genomic DNA contamination from the total RNA (see page 4).•Shorter incubation times and/or higher temperatures may be used (e.g., 50°C for 30 minutes), but may result in reduced yields of cDNA.•For increased yields of cDNA, longer incubation times may be used (up to 120 minutes at 42°C).qPCR Using Fluorescent Primers or ProbesUp to 10% of the qPCR reaction volume may be undiluted cDNA (e.g., for a 20-μL qPCR, use up to 2 μL of undiluted cDNA).qPCR Using SYBR® Green or SYBR® GreenER™ ReagentIf you started with ≤100 ng of total RNA, up to 10% of the qPCR reaction volume may be undiluted cDNA (e.g., for a 20-μL qPCR, use up to 2 μL of undiluted cDNA).If you started with >100 ng total RNA, we recommend testing a serial dilution of cDNA in qPCR for optimal results. Higher concentrations of cDNA may affect the signal baseline in SYBR® Green and SYBR GreenER™ reactions.First-Strand cDNA SynthesisThe following protocol has been optimized for generating first-strand cDNA for use in two-step qRT-PCR. The reaction volume may be scaled as needed up to 100 μL. A negative RT control protocol is provided below.1. For a single reaction, combine the following components in a sterile PCRtube or plate well on ice.Component VolumeSuperScript® VILO™ MasterMix 4 μLRNA (up to 2.5 μg) X μLDEPC-treated water to 20 μL2. Gently mix and incubate at 25°C for 10 minutes.3. Incubate at 42°C for 60 minutes.4. Terminate the reaction at 85°C at 5 minutes.5. Use the diluted or undiluted cDNA in qPCR or store at –20°C.Negative RT Control1. For a volume of RNA = X μL, add the following to a sterile PCR tube orplate well on ice.Component VolumeSuperScript® VILO™ MasterMix 4 μLDEPC-treated water 16 – X μL2. Incubate at 65°C for 10 minutes to denature the reverse transcriptase.X μL of RNA (up to 2.5 μg) for a total reaction volume of 20 μL.3. Add4. Proceed with steps 2–5 from the “First-Strand cDNA Synthesis” protocolabove.Product QualificationThe Certificate of Analysis (CofA) provides detailed quality control information for each product. The CofA is available on our website at /cofa, and is searchable by product lot number, which is printed on each box.Additional ProductsAmount Catalog numberTRIzol® Reagent 100 ml200 ml 15596-026 15596-018PureLink® RNA Mini Kit 10 preps50 preps12183020 12183018AMagMAX™-96 Total RNA Isolation Kit96 rxns AM1830Qubit® RNA Assay Kit 500 assays Q32855Qubit® 2.0 Fluorometer 1 unit Q32866DNase I, Amplification Grade 100 units 18068-015Limited Use Label License No. 358: Research Use OnlyThe purchase of this product conveys to the purchaser the limited, non-transferable right to use the purchased amount of the product only to perform internal research for the sole benefit of the purchaser. No right to resell this product or any of its components is conveyed expressly, by implication, or by estoppel. This product is for internal research purposes only and is not for use in commercial applications of any kind, including, without limitation, quality control and commercial services such as reporting the results of purchaser’s activities for a fee or other form of consideration. For information on obtaining additional rights, please contact outlicensing@ or Out Licensing, Life Technologies, 5791 Van Allen Way, Carlsbad, California 92008.©2011 Life Technologies Corporation. All rights reserved. The trademarks mentioned herein are the property of Life Technologies Corporation or their respective owners. TRIzol is a registered trademark of Molecular Research Center, Inc.For support visit /support oremail techsupport@。

相关文档
最新文档