DOCSLIB.ORG

Copyrighted Material

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Copyrighted Material Index abld build 36 AVRecorder 270 with C 40 abld freeze 226 IDE 32 abort() 74, 400, 402 MFC 214 abstract base class 46 Base Class Library (BCL) Mutex 388–391 active objects 31, 94–99, 237 C classes 53, 79, 85, 87 381 battery 10, 14, 43 C Wrappers 339–340 Active Template Library Bazaar 392–393 CActive 95, 97 (ATL) 134 BCL. See Base Class Library CActiveScheduler Adapter pattern 384 Binary Runtime Environment Add() 95–96 Alerts API 166 for Wireless Start() 141 AllFiles 130, 349, 355 (BREW) 253–254 CAknAppUi 155 Alloc() 64 Blackberry 11, 17–18 calendar 186, 251 ALLOC panic 45–46, 399 bld.inf 35, 36, 38, callbacks 147, 324, 381 AllocL() 64 115–116, 186, camera 165, 185, 253 All-Tcb 117 211, 292, 293, 316 Cancel() 98 Android 11, 12, 17–18, bldmake 36, 211 capabilities 228, 348–355 244–253, Bluetooth 127, 138 Android 369–371 369–371 Boost 107, 197 trusted applications ANSI C++ standardCOPYRIGHTED 386 BREW. See Binary MATERIAL Runtime 362–363 APIs 68–71, 103–131 Environment for untrusted applications applications, portable Wireless 363–364 375–396 CAPABILITY 37, 355 ARM RealView Compilation capitalization guidelines Tools (RVCT) 34, C 21, 28, 40, 103–131, 50–51 112 214 Carbide.c++ 32, 38, 72, ATL See Active Template C++ 21, 28, 31, 50, 59, 147, 211, 214, Library 61–66, 103–131, 368–369 auto_ptr 85, 143, 144 CArray 58 391–392 abstract base class 46 CArrayFixFlat 58 412 INDEX CArrayFixSeg 58 Common Language Runtime DLL. See dynamic link CArrayVarSeg 58 (CLR) 236 library CArrayXSeg 58 compilers 34, 39–40, Document Object Model catch 72 318–322 (DOM) 184 CBase 53, 54, 82, Component Object Model DOM. See Document 100–101, 230 (COM) 230–233 Object Model CBluetoothSocket 138 Compressed Audio API Draw() 150 CCalEntry 138 165 DrawNow() 153 CCirBuf 59 COM:X 126 DRM 349, 355 CCoeControl 147, 215 Concurrent Version System dynamic link library (DLL) CConsoleBase 144–145 (CVS) 392 37, 40–41, 109, CContactDatabase 138 configuration management 352–353 CContactItem 138 392–395 COM 230 CEikConsoleScreen configure 35, 307 MFC 229 144–145 const char* 257–258 Microsoft Windows 209 certificates 233–234, Container 197 RVCT 112 359–366 CountComponent- Windows 226 character size 60 Controls() Windows Mobile 234 CHeartbeat 142 149 WSD 99–100, 111, circular buffers 59 CPeriodic 142 343–345 _cplusplus classes 40 CPolicyServer API design 382–384 352 Createpackage E32Main() 109, 246, CActive 95 286 CreateWindowEx() 248, 334 capitalization 50 208 CSendAPPUi E32USER-CBase 46 92 descriptors 61–66 138, 139 ctime 277 E32USER-CBase 71 77 naming 51–55 CTimer 142 E32USER-CBASE 90 92 cleanup stack 78–86, 393, CurrentTrust() 234 Eclipse Public License (EPL) 400 27 Check() CVS. See Concurrent 81 ECOM. See Epoc PopAndDestroy Version System Component Object (test) 80 Model PushL(TAny*) 82–83 data caging 130, 357–359 ELeave 73, 75–76 PushL(TClean- data types 41, 386–387 EPL. See Eclipse Public upItem) 84 databases 205, 222–223, License CleanupClosePushL() 253 Epoc Component Object 85 DBMS 205, 358 Model (ECOM) Close() 54, 79, 84, 85 dependencies 30, 40, 381 230–233 CLR. See Common DEPLOYMENT 286 EPOCALLOWDLLDATA 100 Language Runtime descriptors 59–60, 68–71 EPOCHEAPSIZE 123 CLSI. See Local System classes 61–66 epocheapsize 42 Interface class function parameters epocstacksize 42, 92 CMdaAudioInputStream 66–68 errno 128, 343 154 P.I.P.S. 124 error handling 71–93, Cocoa 135, 261–266, destructors 85, 90, 97–98, 128, 268 98–100, 143 142–144 code signing 227, digital signatures 359–361 eshell 119–120 359–361 DirectX 136, 203 EventReady() 303 COM. See Component DispatchMessage() exceptions 71–78, 383 Object Model 216 C++ 74 INDEX 413 floating points 198 GetUserDefaultUI- HOME 337 trap handler 85 Language API HSPA. See high-speed EXE. See executables 229 packet access exec 124, 197, 265 Git 393 HTC Dream 245 executables (EXE) 109, glib 106, 334 HTTP 252, 263 118, 350–352 glue code 109, 142, hybrid code 133–157 trusted applications 362 334–335 Windows 226 GNOME Mobile and exit() 335 Embedded 12 IAPs. See Internet Access Exiv2 311, 316–318, GNU Public License (GPL) Points 320–322 27, 135, 312 IDE. See integrated Expat 311, 315–316, Google 11, 12, 17–18, development 318–319 245. See also environment EXPORT_C 40–41, 111, Android IDispatch 221 GPL. See GNU Public 112, 119 IDL. See interface definition License extensions 185–186, language GPS 6, 14, 309–331 281–286 Images API 164 extern Net60 Mobility 111, 140, 298 ImageView 247 extern "C" Framework 236 40 IMEI 366 selective availability 8 IMPORT_C 40–41, 111, graphical user interface 112, 119 fabs() 153 (GUI) 37, 78, indirection layers 378–380 Fac¸ade pattern 384–385 379–380 Input API 167 FCL. See Framework Class graphics 14, 162 input method editors 221 Library GROUP 126 int 57 FIFOs 124, 126 GSensor 282–284 integrated development File Table 341–342 GSM 3, 9, 166, 193, 194, float 56 252, 366 environment (IDE) floating point 56, 129, GStreamer 137 Build 39 198, 386–387 GTK+ 13, 135, 146–147, C++ 32 Flush() 144 203 SIS 39 fopen() 144 GUI. See graphical user Windows 210–211 Intent FOPEN_MAX 121 interface 246 IntentFilter fork 23, 124, 197 Guitune application 247 Framework Class Library 145–157 interface definition language (FCL) 237 (IDL) 221, 230 free() 123, 402 interleaving 129, 144 FreeBSD 335 HandleCommandL() 155 Internet Access Points (IAPs) functions 41, 381–382 HandleCompletionL() 127, 185 C 51 97 inter-process capitalization 50 HandleEventL() 97 communication L 51 HandleResource- (IPC) 198–199, fwrite() 144 Change() 154 223–226 HBufC 64, 67, 82 inter-thread communication HBufC* 213, 219 (ITC) 223–226 Garden 301 heap 75–76, 122, I/O APIs 251, 261–262 GCC-E 34, 226, 297, 298 340–341, ioctl() 127 Geospatial Data Abstraction 399–407 IOStreams 107, 197 Library (GDAL) high-speed packet access IPC. See inter-process 289, 300 (HSPA) 14 communication 414 INDEX IPC server 338–339 libssl 196, 334 Mercurial 393 iPhone 11, 14, 18–19, libtiff 297, 298 message type modules 254–270, LiMo Foundation 12–13, (MTMs) 139 255–256 17–18, 193–195 messaging 139, 185, 252 security 371–372 linked lists 59 meta object compiler (MOC) UI 266–269 Linux 11–13, 17, 32, 180, 183, 256 UIKit 135 195–198, 204 MFC. See Microsoft ISO 14882 386 database 205 Foundation Classes ITC. See inter-thread security 204–205 Microsoft Compact communication UI 202–203 Framework 239 Iterator 197 Linux Phone Standards Microsoft Foundation (LiPS) 12 Classes (MFC) LiPS. See Linux Phone 134, 214, 216 JSON-C 311, 316, Standards MID. See mobile 319–320 literal descriptors 65–66 information device LoadString() 229 middleware 289–307 Local System Interface class MiniWeb 311 KERN-EXEC 46 92 (CLSI) 340 mkdir() 121 KErrAccessDenied LocalServices 129, mmap() 121, 317 352, 354 349, 364, 365 MMF 36–37 KErrNone 77, 97 Location 349, 354, 363, MMP KErrNotSupported 111 365, 367 bld.inf 316 KErrXX error 73 Location API 192 GDAL 289, 290–300 Keypad Capabilities API long 386 GUI 37 167 long int 56 libcrt0.lib 110 key_t 125 MACRO 300 KNullDesC 65 SYSTEMINCLUDE 116 M classes 54 MMP_RULES 286 MACRO 286, 300 MOAP(S) 11, 33–34 _L 65–66 Maemo 12, 13, 191–192, Mobile and Internet Linux _LEAVE_EQUALS_THROW_ 371 Project (Moblin) 74 main() 109, 264, 334, 12, 192–193 leaves 45, 71–78 335 mobile information device cleanup stack 84–86 MaiscBufferCopied() (MID) 191 PushL() 80 149 Mobile Linux 11, LeaveScan 50, 72 makekeys 368 189–206, 190 Length() 62–63, 69–70 malloc() 122–123, 398 Mobile to Market 234 Li, Harry 35 Math class 55 Moblin. See Mobile and LIB. See static library MaxLength() 62, 69–70 Internet Linux libc 104, 115, 121, 124, MDI. See multiple document Project 196, 333, 335 interface MOC. See meta object libcrypt 196, 333 MEikCommandObserver compiler libcrypto 196, 333 216 Model–View–Controller libdl 129, 196, 333, 336 Mem class 55 (MVC) 268, 385 libglib 196 memory management 60, modular code 378 libm 115, 129, 196, 333, 71–93 Mosaic 8 336 limitations and Motorola 9, 10 libpthread 105, 114, workarounds mousePressEvent() 196, 198, 333 122–124 268 INDEX 415 MTMs. See message type NSOperationQueue Openmoko 12, 13, 192, modules 265–266 371 multimedia 136–138, NSOutputStream 261, OpenSL 113–114 164–166, 204 262 OpenVG 174–175 multiple document interface NSScanner 259 operator[] 58 (MDI) 221 NSSortDescriptor 261 operator new 73, 75 munmap() 317 NSStream 261 out-of-memory (OOM) 72, Mutex 388–391 NSString 261 123, 397–408 MVC. See Model–View– NSUrlCache 263 Controller NSUrlConnection 262–263 paintEvent() 268 NSUrlCredential- Palm OS 11 namespace clashes 381 Storage 263 PAMP. See Personal naming guidelines 51–52 NTT DoCoMo 11, 33–34 Apache-MySQL- National Marine Electronics PHP Association Panic() 115 (NMEA) 314 Objective-C 135, 256 panics 91–93. See also native application 133 OHA. See Open Handset specific panics .NET 210, 239–240 Alliance parameters 51, 381–382 .NET Compact Framework onCreate() 247 patterns 384–385 236 OOM. See out-of-memory payment systems 16 Net60 Mobility Framework open() 121, 126 PCM. See pulse code 236 Open C 106–107, modulation Netscape Communications 120–131 perm 121, 126 Corporation 8 libpthread 198 Personal Apache-MySQL- networking 262–264 Linux 196–198 PHP (PAMP) limitations and S60 106 189–190, 205 workarounds Open C++ 107–108 Phonon 137, 185 126–127 Open C/C++ 21, 28 PIM 138–139 Linux 204 descriptors 60 mapping 251 mapping 252 interleaving 144 Net60 Mobility NetworkServices 129, Linux 195–196 Framework 236 349, 350–353, Microsoft Windows P.I.P.S.
Load more

Recommended publications
  • GNU/Linux AI & Alife HOWTO
    GNU/Linux AI & Alife HOWTO GNU/Linux AI & Alife HOWTO Table of Contents GNU/Linux AI & Alife HOWTO......................................................................................................................1 by John Eikenberry..................................................................................................................................1 1. Introduction..........................................................................................................................................1 2. Symbolic Systems (GOFAI)................................................................................................................1 3. Connectionism.....................................................................................................................................1 4. Evolutionary Computing......................................................................................................................1 5. Alife & Complex Systems...................................................................................................................1 6. Agents & Robotics...............................................................................................................................1 7. Statistical & Machine Learning...........................................................................................................2 8. Missing & Dead...................................................................................................................................2 1. Introduction.........................................................................................................................................2
    [Show full text]
  • IT Acronyms.Docx
    List of computing and IT abbreviations /.—Slashdot 1GL—First-Generation Programming Language 1NF—First Normal Form 10B2—10BASE-2 10B5—10BASE-5 10B-F—10BASE-F 10B-FB—10BASE-FB 10B-FL—10BASE-FL 10B-FP—10BASE-FP 10B-T—10BASE-T 100B-FX—100BASE-FX 100B-T—100BASE-T 100B-TX—100BASE-TX 100BVG—100BASE-VG 286—Intel 80286 processor 2B1Q—2 Binary 1 Quaternary 2GL—Second-Generation Programming Language 2NF—Second Normal Form 3GL—Third-Generation Programming Language 3NF—Third Normal Form 386—Intel 80386 processor 1 486—Intel 80486 processor 4B5BLF—4 Byte 5 Byte Local Fiber 4GL—Fourth-Generation Programming Language 4NF—Fourth Normal Form 5GL—Fifth-Generation Programming Language 5NF—Fifth Normal Form 6NF—Sixth Normal Form 8B10BLF—8 Byte 10 Byte Local Fiber A AAT—Average Access Time AA—Anti-Aliasing AAA—Authentication Authorization, Accounting AABB—Axis Aligned Bounding Box AAC—Advanced Audio Coding AAL—ATM Adaptation Layer AALC—ATM Adaptation Layer Connection AARP—AppleTalk Address Resolution Protocol ABCL—Actor-Based Concurrent Language ABI—Application Binary Interface ABM—Asynchronous Balanced Mode ABR—Area Border Router ABR—Auto Baud-Rate detection ABR—Available Bitrate 2 ABR—Average Bitrate AC—Acoustic Coupler AC—Alternating Current ACD—Automatic Call Distributor ACE—Advanced Computing Environment ACF NCP—Advanced Communications Function—Network Control Program ACID—Atomicity Consistency Isolation Durability ACK—ACKnowledgement ACK—Amsterdam Compiler Kit ACL—Access Control List ACL—Active Current
    [Show full text]
  • Foreign Library Interface by Daniel Adler Dia Applications That Can Run on a Multitude of Plat- Forms
    30 CONTRIBUTED RESEARCH ARTICLES Foreign Library Interface by Daniel Adler dia applications that can run on a multitude of plat- forms. Abstract We present an improved Foreign Function Interface (FFI) for R to call arbitary na- tive functions without the need for C wrapper Foreign function interfaces code. Further we discuss a dynamic linkage framework for binding standard C libraries to FFIs provide the backbone of a language to inter- R across platforms using a universal type infor- face with foreign code. Depending on the design of mation format. The package rdyncall comprises this service, it can largely unburden developers from the framework and an initial repository of cross- writing additional wrapper code. In this section, we platform bindings for standard libraries such as compare the built-in R FFI with that provided by (legacy and modern) OpenGL, the family of SDL rdyncall. We use a simple example that sketches the libraries and Expat. The package enables system- different work flow paths for making an R binding to level programming using the R language; sam- a function from a foreign C library. ple applications are given in the article. We out- line the underlying automation tool-chain that extracts cross-platform bindings from C headers, FFI of base R making the repository extendable and open for Suppose that we wish to invoke the C function sqrt library developers. of the Standard C Math library. The function is de- clared as follows in C: Introduction double sqrt(double x); We present an improved Foreign Function Interface The .C function from the base R FFI offers a call (FFI) for R that significantly reduces the amount of gate to C code with very strict conversion rules, and C wrapper code needed to interface with C.
    [Show full text]
  • The Linux Gamers' HOWTO
    The Linux Gamers’ HOWTO Peter Jay Salzman Frédéric Delanoy Copyright © 2001, 2002 Peter Jay Salzman Copyright © 2003, 2004 Peter Jay SalzmanFrédéric Delanoy 2004-11-13 v.1.0.6 Abstract The same questions get asked repeatedly on Linux related mailing lists and news groups. Many of them arise because people don’t know as much as they should about how things "work" on Linux, at least, as far as games go. Gaming can be a tough pursuit; it requires knowledge from an incredibly vast range of topics from compilers to libraries to system administration to networking to XFree86 administration ... you get the picture. Every aspect of your computer plays a role in gaming. It’s a demanding topic, but this fact is shadowed by the primary goal of gaming: to have fun and blow off some steam. This document is a stepping stone to get the most common problems resolved and to give people the knowledge to begin thinking intelligently about what is going on with their games. Just as with anything else on Linux, you need to know a little more about what’s going on behind the scenes with your system to be able to keep your games healthy or to diagnose and fix them when they’re not. 1. Administra If you have ideas, corrections or questions relating to this HOWTO, please email me. By receiving feedback on this howto (even if I don’t have the time to answer), you make me feel like I’m doing something useful. In turn, it motivates me to write more and add to this document.
    [Show full text]
  • Xildoom Final Report
    XilDoom Final Report 18545 Fall 2010 Robert Waaser Shupeng Sun Soo Hwan Kim Summary For our project, we ported the classic 1993 first-person shooter Doom to a Xilinx LX110T Field Programmable Gate Array (FPGA). We chose to use a source port known as Chocolate Doom which uses the Simple DirectMedia Layer (SDL) library to achieve cross-plaorm compability. AXer building a custom computer system on the FPGA that was capable of running the game, we wrote custom drivers for SDL that allowed Chocolate Doom to run on our hardware. The final result was a SystemAce file that could be used to configure an FPGA to run Doom on boot, complete with keyboard input and audio and video output. Networking was also implemented, but not tested before the public demo. Our Project Idea For our capstone we were required to implement a game, a game console, or one of a number of research projects. For the game route, the game had to be complete with audio and video output, some sort of user input, mulWple players, and a way to keep score. Furthermore the game could not be of our own creaon, as the course was not meant to be a course in game programming but rather a course in systems-level design. We took a look at capstone projects from the past three years and noWced that projects that ported soXware games such as Quake and Descent seemed to have a relavely high rate of success. Typically these projects focused less on designing hardware and code from scratch and more on combining and modifying exisWng code and libraries to funcWon in an embedded environment.
    [Show full text]
  • Your Paper's Title Starts Here
    Advances in Computer Science Research, volume 71 4th International Conference on Machinery, Materials and Information Technology Applications (ICMMITA 2016) Design of H.265 Streaming Media Player System Based on QT * Yu-Hua Wu1, a, Min Zhang1, b, Ting Yang1, c, Shi-Jun Lid, 1Jilin Agricultural University, Changchun 130118, Jilin, China [email protected], [email protected], [email protected], [email protected] *Shi-Jun LI Keywords: H.265, streaming media player, FFmpeg, codec. Abstract. With the continuous development of video services, video applications gradually in order to meet the high resolution, high frame rate, high compression development demand, put forward an H.265 streaming media player system based on QT. Under the QT environment, the use of FFmpeg codec library for video file processing, while the use of SDL multimedia displays library combined with multi-thread display video files. Experimental result shows that the player can play a clearly and smoothly H.265 video files, and can support 4K high-quality video playback. 1 Introduction Video data plays an important role in information interaction. According to the research, it is compared with other information, the human brain accepts 70% of the information is from the visual information[1]. However, with the development of mobile terminals and network technology, people's demand for video is growing, according to research shows that the video data will occupy 75% of the mobile data in 2020[2]. In order to provide users with high-quality video information, and reduce the video file data transmission bandwidth, the ITU-T VCEG put forward H.265 standard after H.264 standard.
    [Show full text]
  • Cross-Platform 1 Cross-Platform
    Cross-platform 1 Cross-platform In computing, cross-platform, or multi-platform, is an attribute conferred to computer software or computing methods and concepts that are implemented and inter-operate on multiple computer platforms.[1] [2] Cross-platform software may be divided into two types; one requires individual building or compilation for each platform that it supports, and the other one can be directly run on any platform without special preparation, e.g., software written in an interpreted language or pre-compiled portable bytecode for which the interpreters or run-time packages are common or standard components of all platforms. For example, a cross-platform application may run on Microsoft Windows on the x86 architecture, Linux on the x86 architecture and Mac OS X on either the PowerPC or x86 based Apple Macintosh systems. A cross-platform application may run on as many as all existing platforms, or on as few as two platforms. Platforms A platform is a combination of hardware and software used to run software applications. A platform can be described simply as an operating system or computer architecture, or it could be the combination of both. Probably the most familiar platform is Microsoft Windows running on the x86 architecture. Other well-known desktop computer platforms include Linux/Unix and Mac OS X (both of which are themselves cross-platform). There are, however, many devices such as cellular telephones that are also effectively computer platforms but less commonly thought about in that way. Application software can be written to depend on the features of a particular platform—either the hardware, operating system, or virtual machine it runs on.
    [Show full text]
  • GNU/Linux AI & Alife HOWTO
    GNU/Linux AI & Alife HOWTO GNU/Linux AI & Alife HOWTO Table of Contents GNU/Linux AI & Alife HOWTO......................................................................................................................1 by John Eikenberry..................................................................................................................................1 1. Introduction..........................................................................................................................................1 2. Traditional Artificial Intelligence........................................................................................................1 3. Connectionism.....................................................................................................................................1 4. Evolutionary Computing......................................................................................................................1 5. Alife & Complex Systems...................................................................................................................1 6. Agents & Robotics...............................................................................................................................1 7. Programming languages.......................................................................................................................2 8. Missing & Dead...................................................................................................................................2 1. Introduction.........................................................................................................................................2
    [Show full text]
  • An Infrastructure to Support Interoperability in Reverse Engineering Nicholas Kraft Clemson University, [email protected]
    Clemson University TigerPrints All Dissertations Dissertations 5-2007 An Infrastructure to Support Interoperability in Reverse Engineering Nicholas Kraft Clemson University, [email protected] Follow this and additional works at: https://tigerprints.clemson.edu/all_dissertations Part of the Computer Sciences Commons Recommended Citation Kraft, Nicholas, "An Infrastructure to Support Interoperability in Reverse Engineering" (2007). All Dissertations. 51. https://tigerprints.clemson.edu/all_dissertations/51 This Dissertation is brought to you for free and open access by the Dissertations at TigerPrints. It has been accepted for inclusion in All Dissertations by an authorized administrator of TigerPrints. For more information, please contact [email protected]. AN INFRASTRUCTURE TO SUPPORT INTEROPERABILITY IN REVERSE ENGINEERING A Dissertation Presented to the Graduate School of Clemson University In Partial Fulfillment of the Requirements for the Degree Doctor of Philosophy Computer Science by Nicholas A. Kraft May 2007 Accepted by: Dr. Brian A. Malloy, Committee Chair Dr. Harold C. Grossman Dr. James F. Power Dr. Roy P. Pargas ABSTRACT An infrastructure that supports interoperability among reverse engineering tools and other software tools is described. The three major components of the infrastruc- ture are: (1) a hierarchy of schemas for low- and middle-level program representation graphs, (2) g4re, a tool chain for reverse engineering C++ programs, and (3) a repos- itory of reverse engineering artifacts, including the previous two components, a test suite, and tools, GXL instances, and XSLT transformations for graphs at each level of the hierarchy. The results of two case studies that investigated the space and time costs incurred by the infrastructure are provided. The results of two empirical evaluations that were performed using the api module of g4re, and were focused on computation of object-oriented metrics and three-dimensional visualization of class template diagrams, respectively, are also provided.
    [Show full text]
  • Application Programming Interface (API) Is a Specification Intended to Be Used As an Interface by Software Components to Communicate with Each Other
    Application programming interface 1 Application programming interface An application programming interface (API) is a specification intended to be used as an interface by software components to communicate with each other. An API may include specifications for routines, data structures, object classes, and variables. An API specification can take many forms, including an International Standard such as POSIX or vendor documentation such as the Microsoft Windows API, or the libraries of a programming language, e.g. Standard Template Library in C++ or Java API. An API differs from an application binary interface (ABI) in that the former is source code based while the latter is a binary interface. For instance POSIX is an API, while the Linux Standard Base is an ABI.[1] Language used An API can be: • language-dependent, meaning it is only available by using the syntax and elements of a particular language, which makes the API more convenient to use. • language-independent, written so that it can be called from several programming languages. This is a desirable feature for a service-oriented API that is not bound to a specific process or system and may be provided as remote procedure calls or web services. For example, a website that allows users to review local restaurants is able to layer their reviews over maps taken from Google Maps, because Google Maps has an API that facilitates this functionality. Google Maps' API controls what information a third-party site can use and how they can use it. The term API may be used to refer to a complete interface, a single function, or even a set of APIs provided by an organization.
    [Show full text]
  • Advanced Computer Graphics Spring 2013
    CSCI 4239/5239 Advanced Computer Graphics Spring 2013 Instructor ● Willem A (Vlakkies) Schreüder ● Email: [email protected] – Begin subject with 4830 or 7000 – Resend email not answered promptly ● Office Hours: – ECST 121 Thursday 4-5pm – Other times by appointment ● Weekday Contact Hours: 6:30am - 9:00pm Course Objectives ● Explore advanced topics in Computer Graphics – Pipeline Programming (Shaders) – Embedded System (OpenGL ES) – GPU Programming (CUDA&OpenCL) – Ray Tracing – Special topics ● Particle systems ● Assignments: Practical OpenGL – Building useful applications Course Organization and Grading ● Class participation (50% grade) – First hour: Discussion/Show and tell ● Weekly homework assignments ● Volunteers and/or round robin – Second hour: Introduction of next topic ● Semester project (50% grade) – Build a significant application in OpenGL – 10 minute presentation last class periods ● No formal tests or final Assumptions ● You need to be fluent in C/C++ – Examples are in C or simple C++ – You can do assignments in any language ● I may need help getting it to work on my system ● You need to be comfortable with OpenGL – CSCI 4229/5229 or equivalent – You need a working OpenGL environment Grading ● Satisfactory complete all assignments => A – The goal is to impress your friends ● Assignments must be submitted on time unless prior arrangements are made – Due by Thursday morning – Grace period until Thursday noon ● Assignments must be completed individually – Stealing ideas are encouraged – Code reuse with attribution is permitted
    [Show full text]
  • A Python-Based Framework for Audio and Multimedia Newbies Renato Fabbri Marília F
    gusdevpack: A Python-Based Framework for Audio and Multimedia Newbies Renato Fabbri Marília F. Chiozo NICS, IA, Unicamp IC, Unicamp Rua da Reitoria, 165 Av. Albert Einstein, 1251 Cidade Universitária Zeferino Vaz Cidade Universitária Zeferino Vaz CEP 13091-970 Campinas/SP, CEP 13084-971 Campinas/SP, Brazil, Brazil, [email protected] [email protected] Abstract such real-life applications is called figus. Doc- In this work we present a cross-platform open-source umentation is provided as part of fdp for wrap- Python-based framework for audio and multimedia. per classes and standalone methods of the li- This framework, named gusdevpack, is designed brary, describing their technical aspects such as for reducing application development time and ac- the meanings and domains of method arguments quainting new users with existing resources for mul- and data members. The tutorials, accessible timedia development. It is structured around a from the main fdp frontend along with the ex- wrapper library, example applications, tutorials and ample applications and the documentation, are documentation. meant to walk the user through the process of Keywords writing complete applications and also serves as a guide to the documentation for users who are Python, audio/multimedia development not familiar with the wrapper library. SoniPy[4] is an independently developed 1 Introduction project that is similar to ours when one com- To regular users of multimedia creation soft- pares current end products, yet it holds a fun- ware, making the transition to a fully scripted damental dierence in purpose. While fdp is environment such as Python can be a gruelling aimed primarily at the novice programmer, with task.
    [Show full text]