DOCSLIB.ORG

Plan.Js: a Motion Planning Library for Javascript Clinton Freeman

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Plan.Js: a Motion Planning Library for Javascript Clinton Freeman 1 plan.js: A Motion Planning Library for Javascript Clinton Freeman Abstract—In the past decade, there has been a large move- by the browser ahead of time into machine code in order ment in industry toward web browser based applications and to gain a significant boost in performance. Mozilla claims away from native desktop programs. My semester project was that using Emscripten and asm.js can result in performance an attempt to build a JavaScript library, plan.js, for motion planning in web applications. This document recounts attempts at that is only twice as slow as native applications. Major game converting two native motion planning libraries into JavaScript engines including Unity3D and UnrealEngine are providing by using Mozilla’s Emscripten. The primary contribution of this asm.js ports of their software that can run at interactive speeds. project is an evaluation of the work required to convert each Portable Native Client (PNaCL) is Google’s alternative to library, preliminary headway on converting both projects, and a Emscripten [4]. It follows a similar scheme of converting functional demo of the PQP collision detection library converted to JavaScript. C++ source code to a LLVM-esque bytecode, but stops short of converting this into JavaScript, instead choosing to add a bytecode interpreter into the browser. This approach gives I. INTRODUCTION PNaCL a significant advantage over Emscripten in terms of N the past decade, there has been a large movement in speed, since the compiled code is able to run at native speeds. I industry toward web browser based applications and away from native desktop programs. This is due in large part because C. Examples of Converting Large Native Projects of the inherent cross-platform nature of in-browser applica- As mentioned in the introduction, ammo.js is a javascript tions. As a part of this movement, numerous open source library for performing collision detection. This library is libraries have been developed that provide functionality that created by compiling the popular Bullet collision detection has been available in other languages such as C/C++ for quite library with Emscripten. This is one route that one can take some time. While several libraries have covered important when attempting to port a library over to JavaScript. areas such as 3D graphics (three.js) and collision detection Google has converted many popular C++ projects to run (ammo.js), there is not a widely used motion planning library under PNaCL in order to demonstrate its capability to handle to the best of my knowledge. a broad range of inputs. In particular, they provide a fully Plan.js is a JavaScript library that aims to address this gap working version of the Boost libraries including boost thread. in available software. It should contain many commonly used This is important to note since the dependency on Boost and motion planning algorithms such as RRT, RRT*, PRM, and threads is the primary roadblock to a full conversion of OMPL exact geometric methods for 2D motion planning. It should with Emscripten. be open source with the source code available to others on GitHub, and users should be able to view visualizations of the III. PROBLEM DEFINITION algorithms live in the browser. Native code is composed of machine instructions specific to a particular computer architecture (e.g. x86). This is in contrast II. RELATED WORK to interpreted code, which is composed of instructions that are A. Native Planning Libraries translated into actual machine instructions by a virtual machine The Open Motion Planning Library (OMPL) is a standard at run time. Native code has historically run significantly faster resource for motion planning algorithms for desktop C++ than interpreted code, although over time the gap has become applications [1]. It contains implementations of a wide variety much smaller. While native code (generated by languages such of algorithms, including RRT*, PRM, and others. Many years as C++) has an edge when it comes to runtime performance, of work have gone into the implementations available in this interpreted code (generated by languages such as Java) is library. generally able to run across a larger number of platforms The motion strategy library (MSL) is a C++ library built without modification. by Steve Lavalle’s group at the University of Iowa and A web worker is a JavaScript utility that is essentially a subsequently at the University of Illinois [2]. It also contains thread that has no shared state and may only communicate via some popular algorithms, but has not been updated in many message passing. This is a problem for converting native pro- years. grams to JavaScript because there is no isomorphism between normal threads and web workers. Thus, any program that uses multithreading of any sort must be modified to account for B. Native to JavaScript Conversion Tools this problem. Emscripten is a compiler developed by Mozilla that com- Emscripten is a compiler from low level virtual machine piles native C/C++ code into a subset of Javascript known (LLVM) bytecode to JavaScript. Clang is a compiler that as asm.js [3]. asm.js javascript files are able to be compiled converts C++ source code into LLVM bytecode. gcc is a 2 compiler that converts C++ source code directly into machine code. emcc is Emscripten’s replacement for gcc that uses Clang behind the scenes to compile to bytecode. Most large projects use Makefiles to automate the build process. A make file specifies how output files are generated from input files by specifying a set of rules. In order to build a project, a user will typically change directory to the root of the project and invoke the command make ¡target¿. Emscripten allows users to instead run emmake make ¡target¿ to compile javascript outputs instead of normal exectuables, archives, and shared objects. IV. METHODS My goal with this project was to build a motion planning library that is actually useful to web programmers. There are (broadly) two ways to reach this goal. The first is to hand-write JavaScript implementations of the desired algorithms. While this method is an attractive way to cement my understanding of each algorithm I successfully implement, it is very work intensive and will take a great deal of time and effort to produce something that may be considered useful to other programmers. Fig. 1. PQP’s “spinning” demo converted to WebGL with Emscripten. The The second is to convert an existing native library using an red line denotes the shortest distance between the blue bunny and green torus. automated tool such as Emscripten or PNaCL. This method is attractive from a productivity point of view: if successful, reasons: it does not use threads at all, it comes with a Makefile I can reuse a great deal of work in order to benefit other tailored to using gcc in a Linux environment, and its only programmers. A downside is that the problem becomes not dependence is on PQP. implementing motion planning algorithms (i.e. learning the The proximity query package (PQP) is a C++ collision subject matter of the course), but instead is an engineering detection library written by the GAMMA group at UNC- challenge of converting code from one language to another. Chapel Hill [5], [6]. The implementation and source code I chose the second method because I wanted the project is extremely simple in comparison to monolithic packages to have a real product that could be used by others at the such as Bullet. It operates on pairs of triangle meshes and end. I chose to use Emscripten over PNaCL to convert an places no restriction on mesh topology. It comes with several existing library because the results would be immediate and demo applications that show various objects and the computed the general consensus on the web is that PNaCL will not enjoy results from PQP (intersection set, shortest distance, etc). wide adoption beyond Google Chrome. I initially chose to Converting PQP with Emscripten was very straightforward. convert OMPL instead of MSL because OMPL is significantly The primary challenge was removing outdated OpenGL calls more active and contains newer algorithms. that are not supported by Emscripten/WebGL. V. RESULTS REFERENCES A. Converting OMPL [1] I. A. S¸ucan, M. Moll, and L. E. Kavraki, “The Open Motion Planning OMPL depends on the Boost C++ libraries for much of Library,” IEEE Robotics & Automation Magazine, vol. 19, no. 4, pp. 72–82, December 2012, http://ompl.kavrakilab.org. its functionality. In particular, the planner classes all inherit [2] “Motion strategy library,” http://msl.cs.uiuc.edu/msl/, accessed: 2014-05- from a base class that inherits from boost thread. Removing 01. this dependence is rather problematic since it occurs at such [3] A. Zakai, “Emscripten: an llvm-to-javascript compiler,” in Proceedings of the ACM international conference companion on Object oriented an abstract level of OMPL and affects virtually all motion programming systems languages and applications companion. ACM, planning algorithms. It is possible that a programmer more 2011, pp. 301–312. intimately familiar with the inner workings of OMPL would [4] B. Yee, D. Sehr, G. Dardyk, J. B. Chen, R. Muth, T. Ormandy, S. Okasaka, N. Narula, and N. Fullagar, “Native client: A sandbox for portable, be able to remove boost thread without too much trouble, but untrusted x86 native code,” in Security and Privacy, 2009 30th IEEE it was not feasible for me to do so within the time frame of Symposium on. IEEE, 2009, pp. 79–93. this class. [5] S. Gottschalk, M. C. Lin, and D. Manocha, “Obbtree: A hierarchical structure for rapid interference detection,” in Proceedings of the 23rd annual conference on Computer graphics and interactive techniques.
Load more

Recommended publications
  • Machine Learning in the Browser
    Machine Learning in the Browser The Harvard community has made this article openly available. Please share how this access benefits you. Your story matters Citable link http://nrs.harvard.edu/urn-3:HUL.InstRepos:38811507 Terms of Use This article was downloaded from Harvard University’s DASH repository, and is made available under the terms and conditions applicable to Other Posted Material, as set forth at http:// nrs.harvard.edu/urn-3:HUL.InstRepos:dash.current.terms-of- use#LAA Machine Learning in the Browser a thesis presented by Tomas Reimers to The Department of Computer Science in partial fulfillment of the requirements for the degree of Bachelor of Arts in the subject of Computer Science Harvard University Cambridge, Massachusetts March 2017 Contents 1 Introduction 3 1.1 Background . .3 1.2 Motivation . .4 1.2.1 Privacy . .4 1.2.2 Unavailable Server . .4 1.2.3 Simple, Self-Contained Demos . .5 1.3 Challenges . .5 1.3.1 Performance . .5 1.3.2 Poor Generality . .7 1.3.3 Manual Implementation in JavaScript . .7 2 The TensorFlow Architecture 7 2.1 TensorFlow's API . .7 2.2 TensorFlow's Implementation . .9 2.3 Portability . .9 3 Compiling TensorFlow into JavaScript 10 3.1 Motivation to Compile . 10 3.2 Background on Emscripten . 10 3.2.1 Build Process . 12 3.2.2 Dependencies . 12 3.2.3 Bitness Assumptions . 13 3.2.4 Concurrency Model . 13 3.3 Experiences . 14 4 Results 15 4.1 Benchmarks . 15 4.2 Library Size . 16 4.3 WebAssembly . 17 5 Developer Experience 17 5.1 Universal Graph Runner .
    [Show full text]
  • Create Mobile Apps with HTML5, Javascript and Visual Studio
    Create mobile apps with HTML5, JavaScript and Visual Studio DevExtreme Mobile is a single page application (SPA) framework for your next Windows Phone, iOS and Android application, ready for online publication or packaged as a store-ready native app using Apache Cordova (PhoneGap). With DevExtreme, you can target today’s most popular mobile devices with a single codebase and create interactive solutions that will amaze. Get started today… ・ Leverage your existing Visual Studio expertise. ・ Build a real app, not just a web page. ・ Deliver a native UI and experience on all supported devices. ・ Use over 30 built-in touch optimized widgets. Learn more and download your free trial devexpress.com/mobile All trademarks or registered trademarks are property of their respective owners. Untitled-4 1 10/2/13 11:58 AM APPLICATIONS & DEVELOPMENT SPECIAL GOVERNMENT ISSUE INSIDE Choose a Cloud Network for Government-Compliant magazine Applications Geo-Visualization of SPECIAL GOVERNMENT ISSUE & DEVELOPMENT SPECIAL GOVERNMENT ISSUE APPLICATIONS Government Data Sources Harness Open Data with CKAN, OData and Windows Azure Engage Communities with Open311 THE DIGITAL GOVERNMENT ISSUE Inside the tools, technologies and APIs that are changing the way government interacts with citizens. PLUS SPECIAL GOVERNMENT ISSUE APPLICATIONS & DEVELOPMENT SPECIAL GOVERNMENT ISSUE & DEVELOPMENT SPECIAL GOVERNMENT ISSUE APPLICATIONS Enhance Services with Windows Phone 8 Wallet and NFC Leverage Web Assets as Data Sources for Apps APPLICATIONS & DEVELOPMENT SPECIAL GOVERNMENT ISSUE ISSUE GOVERNMENT SPECIAL DEVELOPMENT & APPLICATIONS Untitled-1 1 10/4/13 11:40 AM CONTENTS OCTOBER 2013/SPECIAL GOVERNMENT ISSUE OCTOBER 2013/SPECIAL GOVERNMENT ISSUE magazine FEATURES MOHAMMAD AL-SABT Editorial Director/[email protected] Geo-Visualization of Government KENT SHARKEY Site Manager Data Sources MICHAEL DESMOND Editor in Chief/[email protected] Malcolm Hyson ..........................................
    [Show full text]
  • Extracting Taint Specifications for Javascript Libraries
    Extracting Taint Specifications for JavaScript Libraries Cristian-Alexandru Staicu Martin Toldam Torp Max Schäfer TU Darmstadt Aarhus University GitHub [email protected] [email protected] [email protected] Anders Møller Michael Pradel Aarhus University University of Stuttgart [email protected] [email protected] ABSTRACT ACM Reference Format: Modern JavaScript applications extensively depend on third-party Cristian-Alexandru Staicu, Martin Toldam Torp, Max Schäfer, Anders Møller, and Michael Pradel. 2020. Extracting Taint Specifications for JavaScript libraries. Especially for the Node.js platform, vulnerabilities can Libraries. In 42nd International Conference on Software Engineering (ICSE have severe consequences to the security of applications, resulting ’20), May 23–29, 2020, Seoul, Republic of Korea. ACM, New York, NY, USA, in, e.g., cross-site scripting and command injection attacks. Existing 12 pages. https://doi.org/10.1145/3377811.3380390 static analysis tools that have been developed to automatically detect such issues are either too coarse-grained, looking only at 1 INTRODUCTION package dependency structure while ignoring dataflow, or rely on JavaScript is powering a wide variety of web applications, both manually written taint specifications for the most popular libraries client-side and server-side. Many of these applications are security- to ensure analysis scalability. critical, such as PayPal, Netflix, or Uber, which handle massive In this work, we propose a technique for automatically extract- amounts of privacy-sensitive user data and other assets. An impor- ing taint specifications for JavaScript libraries, based on a dynamic tant characteristic of modern JavaScript-based applications is the analysis that leverages the existing test suites of the libraries and extensive use of third-party libraries.
    [Show full text]
  • Microsoft AJAX Library Essentials Client-Side ASP.NET AJAX 1.0 Explained
    Microsoft AJAX Library Essentials Client-side ASP.NET AJAX 1.0 Explained A practical tutorial to using Microsoft AJAX Library to enhance the user experience of your ASP.NET Web Applications Bogdan Brinzarea Cristian Darie BIRMINGHAM - MUMBAI Microsoft AJAX Library Essentials Client-side ASP.NET AJAX 1.0 Explained Copyright © 2007 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the authors, Packt Publishing, nor its dealers or distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. First published: July 2007 Production Reference: 1230707 Published by Packt Publishing Ltd. 32 Lincoln Road Olton Birmingham, B27 6PA, UK. ISBN 978-1-847190-98-7 www.packtpub.com Cover Image by www.visionwt.com Table of Contents Preface 1 Chapter 1: AJAX and ASP.NET 7 The Big Picture 8 AJAX and Web 2.0 10 Building
    [Show full text]
  • Learning Javascript Design Patterns
    Learning JavaScript Design Patterns Addy Osmani Beijing • Cambridge • Farnham • Köln • Sebastopol • Tokyo Learning JavaScript Design Patterns by Addy Osmani Copyright © 2012 Addy Osmani. All rights reserved. Revision History for the : 2012-05-01 Early release revision 1 See http://oreilly.com/catalog/errata.csp?isbn=9781449331818 for release details. ISBN: 978-1-449-33181-8 1335906805 Table of Contents Preface ..................................................................... ix 1. Introduction ........................................................... 1 2. What is a Pattern? ...................................................... 3 We already use patterns everyday 4 3. 'Pattern'-ity Testing, Proto-Patterns & The Rule Of Three ...................... 7 4. The Structure Of A Design Pattern ......................................... 9 5. Writing Design Patterns ................................................. 11 6. Anti-Patterns ......................................................... 13 7. Categories Of Design Pattern ............................................ 15 Creational Design Patterns 15 Structural Design Patterns 16 Behavioral Design Patterns 16 8. Design Pattern Categorization ........................................... 17 A brief note on classes 17 9. JavaScript Design Patterns .............................................. 21 The Creational Pattern 22 The Constructor Pattern 23 Basic Constructors 23 Constructors With Prototypes 24 The Singleton Pattern 24 The Module Pattern 27 iii Modules 27 Object Literals 27 The Module Pattern
    [Show full text]
  • Analysing the Use of Outdated Javascript Libraries on the Web
    Updated in September 2017: Require valid versions for library detection throughout the paper. The vulnerability analysis already did so and remains identical. Modifications in Tables I, III and IV; Figures 4 and 7; Sections III-B, IV-B, IV-C, IV-F and IV-H. Additionally, highlight Ember’s security practices in Section V. Thou Shalt Not Depend on Me: Analysing the Use of Outdated JavaScript Libraries on the Web Tobias Lauinger, Abdelberi Chaabane, Sajjad Arshad, William Robertson, Christo Wilson and Engin Kirda Northeastern University {toby, 3abdou, arshad, wkr, cbw, ek}@ccs.neu.edu Abstract—Web developers routinely rely on third-party Java- scripts or HTML into vulnerable websites via a crafted tag. As Script libraries such as jQuery to enhance the functionality of a result, it is of the utmost importance for websites to manage their sites. However, if not properly maintained, such dependen- library dependencies and, in particular, to update vulnerable cies can create attack vectors allowing a site to be compromised. libraries in a timely fashion. In this paper, we conduct the first comprehensive study of To date, security research has addressed a wide range of client-side JavaScript library usage and the resulting security client-side security issues in websites, including validation [30] implications across the Web. Using data from over 133 k websites, we show that 37 % of them include at least one library with a and XSS ([17], [36]), cross-site request forgery [4], and session known vulnerability; the time lag behind the newest release of fixation [34]. However, the use of vulnerable JavaScript libraries a library is measured in the order of years.
    [Show full text]
  • 6. Client-Side Processing
    6. Client-Side Processing 1. Client-side processing 2. JavaScript 3. Client-side scripting 4. Document Object Model (DOM) 5. Document methods and properties 6. Events 7. Calling a function 8. Table of squares function 9. Comments on previous script 10. Defining a function 11. Event handlers 12. Event handlers example 13. Event listeners 14. Functions and form fields 15. Defining the function myTranslate 16. Navigating the DOM tree 17. Finding elements by name 18. Finding elements by name (function body) 19. Using CSS selectors 20. Adding elements 21. Deleting elements 22. Using jQuery 23. Using jQuery to add elements 24. Finding elements by name (jQuery) 25. DOM and XML 26. jQuery method to load an XML file 27. Retrieving RSS item titles 28. Retrieving JSON data 29. JSON country data 30. Code for JSON retrieval (1) 31. Code for JSON retrieval (2) 32. Exercises 33. Links to more information 6.1. Client-side processing client program (e.g. web browser) can be used to customise interaction with the user validate user input (although HTML5 now provides this) generate (part of) document dynamically send requests to a server in the background make interaction with a web page similar to that of a desktop application this is typically done using JavaScript, since a Javascript interpreter is built into browsers 6.2. JavaScript interpreted, scripting language for the web loosely typed variables do not have to be declared the same variable can store values of different types at different times HTML <script> element specifies script to be executed type attribute has value text/javascript src attribute specifies URI of external script usually <script> appears in the <head> and just declares functions to be called later ECMAScript, 10th edition (June 2019) is the latest standard 6.3.
    [Show full text]
  • Javascript DOM Manipulation Performance Comparing Vanilla Javascript and Leading Javascript Front-End Frameworks
    JavaScript DOM Manipulation Performance Comparing Vanilla JavaScript and Leading JavaScript Front-end Frameworks Morgan Persson 28/05/2020 Faculty of Computing, Blekinge Institute of Technology, 371 79 Karlskrona, Sweden This thesis is submitted to the Faculty of Computing at Blekinge Institute of Technology in partial fulfillment of the requirements for the bachelor’s degree in software engineering. The thesis is equivalent to 10 weeks of full-time studies. Contact Information: Author(s): Morgan Persson E-mail: [email protected] University advisor: Emil Folino Department of Computer Science Faculty of Computing Internet : www.bth.se Blekinge Institute of Technology Phone : +46 455 38 50 00 SE–371 79 Karlskrona, Sweden Fax : +46 455 38 50 57 Abstract Background. Websites of 2020 are often feature rich and highly interactive ap- plications. JavaScript is a popular programming language for the web, with many frameworks available. A common denominator for highly interactive web applica- tions is the need for efficient methods of manipulating the Document Object Model to enable a solid user experience. Objectives. This study compares Vanilla JavaScript and the JavaScript frameworks Angular, React and Vue.js in regards to DOM performance, DOM manipulation methodology and application size. Methods. A literature study was conducted to compare the DOM manipulation methodologies of Vanilla JavaScript and the selected frameworks. An experiment was conducted where test applications was created using Vanilla JavaScript and the selected frameworks. These applications were used as base for comparing applica- tion size and for comparison tests of DOM performance related metrics using Google Chrome and Firefox. Results. In regards to DOM manipulation methodology, there is a distinct difference between Vanilla JavaScript and the selected frameworks.
    [Show full text]
  • Load Time Optimization of Javascript Web Applications
    URI: urn:nbn:se:bth-17931 Bachelor of Science in Software Engineering May 2019 Load time optimization of JavaScript web applications Simon Huang Faculty of Computing, Blekinge Institute of Technology, 371 79 Karlskrona, Sweden This thesis is submitted to the Faculty of Computing at Blekinge Institute of Technology in partial fulfilment of the requirements for the degree of Bachelor of Science in Software Engineering. The thesis is equivalent to 10 weeks of full time studies. The authors declare that they are the sole authors of this thesis and that they have not used any sources other than those listed in the bibliography and identified as references. They further declare that they have not submitted this thesis at any other institution to obtain a degree. Contact Information: Author: Simon Huang E-mail: [email protected] University advisor: Emil Folino Department of Computer Science Faculty of Computing Internet : www.bth.se Blekinge Institute of Technology Phone : +46 455 38 50 00 SE–371 79 Karlskrona, Sweden Fax : +46 455 38 50 57 Abstract Background. Websites are getting larger in size each year, the median size increased from 1479.6 kilobytes to 1699.0 kilobytes on the desktop and 1334.3 kilobytes to 1524.1 kilobytes on the mobile. There are several methods that can be used to decrease the size. In my experiment I use the methods tree shaking, code splitting, gzip, bundling, and minification. Objectives. I will investigate how using the methods separately affect the loading time and con- duct a survey targeted at participants that works as JavaScript developers in the field.
    [Show full text]
  • Comparing Javascript Libraries
    www.XenCraft.com Comparing JavaScript Libraries Craig Cummings, Tex Texin October 27, 2015 Abstract Which JavaScript library is best for international deployment? This session presents the results of several years of investigation of features of JavaScript libraries and their suitability for international markets. We will show how the libraries were evaluated and compare the results for ECMA, Dojo, jQuery Globalize, Closure, iLib, ibm-js and intl.js. The results may surprise you and will be useful to anyone designing new international or multilingual JavaScript applications or supporting existing ones. 2 Agenda • Background • Evaluation Criteria • Libraries • Results • Q&A 3 Origins • Project to extend globalization - Complex e-Commerce Software - Multiple subsystems - Different development teams - Different libraries already in use • Should we standardize? Which one? - Reduce maintenance - Increase competence 4 Evaluation Criteria • Support for target and future markets • Number of internationalization features • Quality of internationalization features • Maintained? • Widely used? • Ease of migration from existing libraries • Browser compatibility 5 Internationalization Feature Requirements • Encoding Support • Text Support -Unicode -Case, Accent Mapping -Supplementary Chars -Boundary detection -Bidi algorithm, shaping -Character Properties -Transliteration -Charset detection • Message Formatting -Conversion -IDN/IRI -Resource/properties files -Normalization -Collation -Plurals, Gender, et al 6 Internationalization Feature Requirements
    [Show full text]
  • Opencv.Js: Computer Vision Processing for the Web
    24 OpenCV.js: Computer Vision Processing for the Web Sajjad Taheri, Alexander Veidenbaum, Mohammad R. Haghighat Alexandru Nicolau Intel Corp Computer Science Department, Univerity of [email protected] California, Irvine sajjadt,alexv,[email protected] ABSTRACT the web based application development, the general paradigm The Web is the most ubiquitous computing platform. There is used to be deploying computationally complex logic on the are already billions of devices connected to the web that server. However, with recent client side technologies, such have access to a plethora of visual information. Understand- as Just in time compilation, web clients are able to handle ing images is a complex and demanding task which requires more demanding tasks. sophisticated algorithms and implementations. OpenCV is There are recent efforts to provide computer vision for the defacto library for general computer vision application web based platforms. For instance [4] and [5] have pro- development, with hundreds of algorithms and efficient im- vided lightweight JavaScript libraries that offer selected vi- plementation in C++. However, there is no comparable sion functions. There is also a JavaScript binding for Node.js, computer vision library for the Web offering an equal level that provides JavaScript programs with access to OpenCV of functionality and performance. This is in large part due libraries. There are requirements for a computer vision li- to the fact that most web applications used to adopt a client- brary on the web that are not entirely addressed by the server approach in which the computational part is handled above mentioned libraries that this work seeks to meet: by the server.
    [Show full text]
  • Javalikescript User Guide
    JavaLikeScript User Guide spyl <[email protected]> Table of Contents 1. Installation ..................................................................................................................... 1 1.1. Installed Directory Tree ......................................................................................... 1 1.2. Update the PATH variable ..................................................................................... 2 1.3. Linux 64-bit ........................................................................................................ 2 2. Usage ........................................................................................................................... 2 2.1. Command line arguments ...................................................................................... 2 2.2. Garbage collection ................................................................................................ 3 2.3. Self executable ..................................................................................................... 3 2.4. Web browser ....................................................................................................... 3 3. Concepts ....................................................................................................................... 4 3.1. Bootstrap ............................................................................................................ 4 3.2. Classes ..............................................................................................................
    [Show full text]