DOCSLIB.ORG

Understanding Javascript Behaviors in Web Pages by Visually Exploring the Browser

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Understanding Javascript Behaviors in Web Pages by Visually Exploring the Browser FireInsight: Understanding JavaScript Behaviors in Web Pages by Visually Exploring the Browser by Steven Xinyue Gao B.Sc., Dalhousie University, 2004 A THESIS SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF Master of Science in THE FACULTY OF GRADUATE STUDIES (Computer Science) THE UNIVERSITY OF BRITISH COLUMBIA (Vancouver) December 2009 c Steven Xinyue Gao, 2009 Abstract JavaScript is one of the most important and prevalent programming languages today. It is the language of the web browser and it has seen a surge in active devel- opment since the rise of the Ajax approach for developing highly interactive web ap- plications. Often misunderstood as a simple scripting language, JavaScript is in fact powerful and expressive. As web applications have grown in sophistication, so have their user interfaces, which are predominately implemented as client-side JavaScript. This growth in complexity has resulted in a vast array of JavaScript frameworks, best practices and design patterns. Since JavaScript applications involve creating user interfaces, adopting a visual development approach would seem a natural choice to help manage complexity and improve program understanding. One possible ap- proach is to allow the developer to visually relate semantically meaningful elements on a web page to the actual JavaScript source code that implements its behavior. This can be accomplished by leveraging context information during JavaScript ex- ecution. Additionally, control-flow graphs are dynamically generated to help the developer understand how a series of function calls might be related based on events triggered in the user interface. Inspired by work from Li and Wohlstadter, we im- plement the above approach by creating a program called FireInsight. It integrates with the Mozilla Firefox web browser and the Firebug development tool. We use an HTTP proxy to instrument JavaScript source code with our own analysis code. We analyze this approach and evaluate its effectiveness by applying FireInsight to an open-source web application called Java Pet Store 2.0. ii Contents Abstract ...................................... ii Contents ...................................... iii List of Figures .................................. v Acknowledgments ................................ vii Chapter 1 Introduction ............................ 1 1.1 ProblemandMotivation......................... 2 1.2 Contributions............................... 5 1.3 ThesisOutline .............................. 6 Chapter 2 Background ............................ 7 2.1 Evolving the Web: Ajax, JavaScript and User Interaction ...... 10 2.1.1 Iteration 1: Classic Web Application Model . 10 2.1.2 Iteration 2: Ajax Web Application Model . 13 2.2 The Client-Side: JavaScript, HTML, CSS and the DOM . 17 2.2.1 HTML............................... 17 2.2.2 CSS ................................ 19 2.2.3 JavaScriptandtheDOM . 23 2.3 TheFront-endDeveloper . 29 2.4 Program Understanding and Software Maintenance . 32 iii 2.5 RelatedWork............................... 34 2.5.1 JavaScript Frameworks and Programming Tools . 35 2.5.2 Visual Programming Tools . 38 2.5.3 JavaScript Instrumentation . 45 2.5.4 ScriptInsight........................... 48 Chapter 3 Methodology ........................... 51 3.1 Understanding the UI-JavaScript Mapping Problem . 52 3.2 Motivating Example: Java Pet Store 2.0 . 55 3.3 Extending Script Insight to Improve Program Understanding . 63 Chapter 4 Design and Implementation .................. 70 4.1 FireInsightArchitectureOverview . 71 4.2 Implementation Assumptions . 74 4.3 Firefox,FirebugandFireInsight . 75 4.3.1 DOM Mutation Graph and MxGraph . 78 4.4 JavaScript Instrumentation using an HTTP Proxy . 79 4.5 KnownLimitations............................ 83 Chapter 5 Results and Evaluation ..................... 87 5.1 FireInsightEvaluation . 88 5.1.1 Case Study: RSS News Feed . 88 5.1.2 Case Study: Catalog Browser Info Pane . 96 5.1.3 Case Study: Pet Info Overlay Pop-up . 108 5.2 ChallengesandDrawbacks. 114 5.2.1 JavaScriptFrameworks . 114 5.2.2 JavaScript Instrumentation . 117 Chapter 6 Conclusions and Future Work ................ 119 Bibliography ................................... 121 iv List of Figures 2.1 Iteration 1: A Classic Web Application Architecture . ...... 11 2.2 Client-Server Communication for the Classic Web Application Model 12 2.3 Iteration 2: An Interactive Application Architecture. ......... 15 2.4 ASimpleHTMLDocument . 18 2.5 Screenshot of the HTML Document . 19 2.6 AnHTMLDocumentwithCSScode . 21 2.7 Screenshot of the HTML Document with CSS . 23 2.8 An HTML Document with CSS code and JavaScript code . 24 2.9 HTMLandtheDOM .......................... 25 2.10 Screenshot of the HTML Document with CSS and JavaScript . 28 2.11 Mapping Behavior and Presentation of Web Page, from Browser to Implementation.............................. 30 2.12 AscreenshotofAdobeDreamweaver . 39 2.13 AscreenshotofFirebug . 42 3.1 Mapping Behavior of Web Page, from Browser to Implementation . 53 3.2 JavaPetStore2.0-RSSNewFeedFeature . 57 3.3 RSSNewsFeedDOMElement . 59 3.4 RSSNewsFeedJavaScriptBehavior . 60 3.5 FirebugHTMLInspectionMode . 61 3.6 GraphicalModelofExecutionContext . 62 v 3.7 ExecutionStack ............................. 64 3.8 JavaScript Instrumentation through Proxy . 67 4.1 FireInsightArchitecture . 72 4.2 FireInsightPlug-in ............................ 76 4.3 FireInsightHTTPProxy. 79 5.1 FireInsight Attribute View: RSS News Feed . 90 5.2 FireInsight Source Code View: RSS News Feed . 91 5.3 FireInsight Event Handler View and DMG View: RSS News Feed . 93 5.4 Browser View and FireInsight DMG View: RSS News Feed . 95 5.5 FireInsight Attribute View: RSS News Feed Part 2 . 97 5.6 FireInsightDMGView: RSSNewsFeedPart2 . 98 5.7 Case Study: Catalog Browser Info Pane . 99 5.8 FireInsight Attribute View: Catalog Browser Info Pane . 101 5.9 FireInsight Event Handler and DMG Views Part 1: Catalog Browser InfoPane ................................. 103 5.10 FireInsight Event Handler and DMG Views Part 2: Catalog Browser InfoPane ................................. 104 5.11 Case Study Final Result: Catalog Browser Info Pane . 107 5.12 Case Study: Pet Info Overlay Pop-up . 108 5.13 JavaScript Bug: Pet Info Overlay Pop-up . 110 5.14 Inspection Mode: Pet Info Overlay Pop-up . 111 5.15 Event Handlers: Pet Info Overlay Pop-up . 113 5.16 DMGView: PetInfoOverlayPop-up . 115 5.17 Handling JavaScript Frameworks . 116 vi Acknowledgments Thanks to my supervisor Eric Wohlstadter for the thoughtful advice and diligence in guiding me towards the completion of this thesis. Thanks to Loyal Chow for the many interesting discussions regarding JavaScript and web development in general. Thank you Kris De Volder for taking the time to be on my examining committee. Thanks to my parents for their love and support, without which I would never have reached this point in my academic career. Finally, thanks to my lovely Chenoa, for supporting me through all the ups and downs in finishing my Masters degree. vii Chapter 1 Introduction Web applications have evolved dramatically over the past decade. One component of the web application which has seen significant technical advancements is the user interface (UI). The widespread adoption of web programming specifications such as JavaScript and the W3C Document Object Model (DOM), gave developers the ability to create increasingly sophisticated UIs. As a result, web applications can now provide seamless and highly interactive user experiences, similar to desktop applications. Naturally, this additional interactivity has led to a corresponding rise in the UI’s complexity. Building and maintaining rich web UIs now require a greater development effort. Because JavaScript is the language of the web browser, most of the development effort is spent on JavaScript programming. As the language matured, the development community has produced numer- ous frameworks, programming tools, best practices, and design patterns to help make JavaScript applications easier to build. Frameworks, such as Prototype and Dojo [24], provide reusable JavaScript libraries as well as a system for architect- ing the JavaScript code. Best practices, such as decoupling JavaScript code from presentation code (CSS), creating build and deployment procedures for JavaScript, and compressing JavaScript code for production environments, provide a means to manage complexity and improve the performance of the UI [33]. Software, such as 1 JSLint [4] and Aptana [2], provide invaluable assistance to help developers avoid the weaknesses of the language. Other tools such as Firebug [14] and Dreamweaver [1], enable developers to program the UI using visual and interactive techniques. 1.1 Problem and Motivation However, there is currently very little research or progress in the area of JavaScript program understanding. Program understanding represents the knowledge of how the source code implements an application’s behavior. Within the domain of UI programming, this knowledge corresponds to an abstract mapping that connects the source code to the actual UI behavior that occurs in the browser. Program understanding is crucial for software maintenance. Many of to- day’s most popular interactive web applications, such as Google Maps, Facebook, Twitter, and Gmail, have constantly evolving UI components. Because these in- terfaces are implemented in JavaScript, fixing and augmenting existing JavaScript code are common activities within web development. Many software projects face constantly
Load more

Recommended publications
  • Mozilla Firefox Lower Version Free Download Firefox Release Notes
    mozilla firefox lower version free download Firefox Release Notes. Release Notes tell you what’s new in Firefox. As always, we welcome your feedback. You can also file a bug in Bugzilla or see the system requirements of this release. Download Firefox — English (US) Your system may not meet the requirements for Firefox, but you can try one of these versions: Download Firefox — English (US) Download Firefox Download Firefox Download Firefox Download Firefox Download Firefox Download Firefox Download Firefox Download Firefox Firefox for Android Firefox for iOS. December 1, 2014. We'd also like to extend a special thank you to all of the new Mozillians who contributed to this release of Firefox! Default search engine changed to Yandex for Belarusian, Kazakh, and Russian locales. Improved search bar (en-US only) Firefox Hello real-time communication client. Easily switch themes/personas directly in the Customizing mode. Wikipedia search now uses HTTPS for secure searching (en-US only) Recover from a locked Firefox process in the "Firefox is already running" dialog on Windows. Fixed. CSS transitions start correctly when started at the same time as changes to display, position, overflow, and similar properties. Fullscreen video on Mac disables display sleep, and dimming, during playback. Various Yosemite visual fixes (see bug 1040250) Changed. Proprietary window.crypto properties/functions re-enabled (to be removed in Firefox 35) Firefox signed by Apple OS X version 2 signature. Developer. WebIDE: Create, edit, and test a new Web application from your browser. Highlight all nodes that match a given selector in the Style Editor and the Inspector's Rules panel.
    [Show full text]
  • Brief Intro to Firebug Firebug at a Glance
    Brief Intro to Firebug Firebug at a glance • One of the most popular web debugging tool with a collec6on of powerful tools to edit, debug and monitor HTML, CSS and JavaScript, etc. • Many rich features: • Inspect, Log, Profile • Debug, Analyze, Layout How to install • Get firebug: • Open Firefox, and go to hp://geirebug.com/ • Click Install Firebug, and follow the instruc6ons • Ways to launch Firebug • F12, or Firebug Buon • Right click an element on the page and inspect it with Firebug Firebug Panels • Console: An interac6ve JavaScript Console • HTML: HTML View • CSS: CSS View • Script: JavaScript Debugger • DOM: A list of DOM proper6es (defaults to window object) • Net: HTTP traffic monitoring • Cookies: Cookie View Tasks for HTML Panel • Open twiLer.com and log in with your account. Ac6vate Firebug. • Tasks with HTML Panel • 1. Which <div> tag corresponds to the navigaon bar at the top of the page? • 2. Change the text “Messages” in the navigaon bar to “Tweets” • 3. Find out which <div> tag corresponds to the dashboard which is the le` column of the page. Can you change the width of the dashboard to 200px? • 4. Try to figure out the URL of your profile picture at the top le` corner of the home page, and use this URL to open this picture in a new tab. • 5. Change your name next to your profile picture to something else, and change the text colour to blue. Inspect HTTP Traffic • Open twiLer.com and log in with your account. Ac6vate Firebug. • Tasks with Net Panel • 1. Which request takes the longest 6me to load? • 2.
    [Show full text]
  • Empirical Studies of Javascript-‐ Based Web Applicaxon
    Empirical Studies of JavaScript- based Web Applica8on Reliability Karthik Pa@abiraman1 Frolin Ocariza1 Kar.k Bajaj1 Ali Mesbah1 Benjamin Zorn2 1 University of Bri.sh Columbia (UBC), 2MicrosoE Research (MSR) Web 2.0 Applicaons Copyright: Karthik Paabiraman, 2014 Web 2.0 Applicaon: Amazon.com Menu Amazon’s Third party Search bar Web 2.0 applicaons allow rich UI funconality within a single web page own ad gadget ad Func8on Copyright: Karthik Paabiraman, 2014 Modern Web Applicaons: JavaScript • JavaScript: Implementaon of ECMAScript standard – Client-Side JavaScript: used to develop web apps • Executes in client’s browser – send AJAX messages • Responsible for web applicaon’s core func.onality • Not easy to write code in – has many “evil” features 4 Copyright: Karthik Paabiraman, 2014 JavaScript: History Brief History of JavaScript (Source: TomBarker.com) JavaScript (JS) had to “look like Java” only less so, be Java’s dumb kid brother or boy-hostage sidekick. Plus, I had to be done in ten days or something worse than JS would have happened – Brendan Eich (Inventor of JavaScript) Copyright: Karthik Paabiraman, 2014 • • 10000 20000 30000 40000 50000 60000 70000 80000 90000 Thousands of lines of code, oEen > 10,000 97 of the 0 Google YouTube Yahoo Baidu QQ MSN Amazon JavaScript: Prevalence Sina WordPress Alexa Ebay LinkedIn Bing MicrosoE Yandex 163 top 100 websites use JavaScript Copyright: Karthik Paabiraman, 2014 mail.ru PayPal FC2 Flickr IMDb Lines of code Apple Livedoor BBC Sohu go.com Soso Youku AOL CNN MediaFire ESPN MySpace MegaUpload Mozilla 4shared Adobe About LiveJournal Tumblr goDaddy CNET YieldManager Sogou Zedo Ifeng Pirate Bay ImageShack Weather NY Times Nelix JavaScript: “good” or “Evil” ? Vs Eval Calls (Source: Richards et al.
    [Show full text]
  • Development Production Line the Short Story
    Development Production Line The Short Story Jene Jasper Copyright © 2007-2018 freedumbytes.dev.net (Free Dumb Bytes) Published 3 July 2018 4.0-beta Edition While every precaution has been taken in the preparation of this installation manual, the publisher and author assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein. This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License. To get an idea of the Development Production Line take a look at the following Application Integration overview and Maven vs SonarQube Quality Assurance reports comparison. 1. Operating System ......................................................................................................... 1 1.1. Windows ........................................................................................................... 1 1.1.1. Resources ................................................................................................ 1 1.1.2. Desktop .................................................................................................. 1 1.1.3. Explorer .................................................................................................. 1 1.1.4. Windows 7 Start Menu ................................................................................ 2 1.1.5. Task Manager replacement ........................................................................... 3 1.1.6. Resource Monitor .....................................................................................
    [Show full text]
  • Installation and Maintenance Guide
    Contract Management Installation and Maintenance Guide Software Version 6.9.1 May 2016 Title: Gimmal Contract Management Installation and Maintenance Guide V6.9.1 © 2016 Gimmal LLC Gimmal® is a registered trademark of Gimmal Group. Microsoft® and SharePoint® are registered trademarks of Microsoft. Gimmal LLC believes the information in this publication is accurate as of its publication date. The information in this publication is provided as is and is subject to change without notice. Gimmal LLC makes no representations or warranties of any kind with respect to the information contained in this publication, and specifically disclaims any implied warranties of merchantability or fitness for a par- ticular purpose. Use, copying, and distribution of any Gimmal software described in this publication requires an appli- cable software license. For the most up-to-date listing of Gimmal product names and information, visit www.gimmal.com. All other trademarks used herein are the property of their respective owners. Software Revision History Publication Date Description October 2015 Updated to Gimmal branding. December 2015 Updated for version 6.8.6 release. March 2016 Updated for version 6.9 release. May 2016 Updated for version 6.9.1 release. If you have questions or comments about this publication, you can email TechnicalPublica- [email protected]. Be sure to identify the guide, version number, section, and page number to which you are referring. Your comments are welcomed and appreciated. Contents About this Guide vii Examples and Conventions . viii Chapter 1 Environment and System Requirements 1 Overview of Requirements . 2 Gimmal Contract Management Physical Environment. 2 Gimmal Contract Management and Documentum Content Management System .
    [Show full text]
  • Here.Is.Only.Xul
    Who am I? Alex Olszewski Elucidar Software Co-founder Lead Developer What this presentation is about? I was personally assigned to see how XUL and the Mozilla way measured up to RIA application development standards. This presentation will share my journey and ideas and hopefully open your minds to using these concepts for application development. RIA and what it means Different to many “Web Applications” that have features and functions of “Desktop” applications Easy install (generally requires only application install) or one-time extra(plug in) Updates automatically through network connections Keeps UI state on desktop and application state on server Runs in a browser or known “Sandbox” environment but has ability to access native OS calls to mimic desktop applications Designers can use asynchronous communication to make applications more responsive RIA and what it means(continued) Success of RIA application will ultimately be measured by how will it can match user’s needs, their way of thinking, and their behaviour. To review RIA applications take advantage of the “best” of both web and desktop apps. Sources: http://www.keynote.com/docs/whitepapers/RichInternet_5.pdf http://en.wikipedia.org/wiki/Rich_Internet_application My First Steps • Find working examples Known Mozilla Applications Firefox Thunderbird Standalone Applications Songbird Joost Komodo FindthatFont Prism (formerly webrunner) http://labs.mozilla.com/featured- projects/#prism XulMine-demo app http://benjamin.smedbergs.us/XULRunner/ Mozilla
    [Show full text]
  • 12 Understanding Javascript Event-Based Interactions With
    Understanding JavaScript Event-Based Interactions with Clematis SABA ALIMADADI, SHELDON SEQUEIRA, ALI MESBAH, 12 and KARTHIK PATTABIRAMAN, University of British Columbia Web applications have become one of the fastest-growing types of software systems today. Despite their pop- ularity, understanding the behavior of modern web applications is still a challenging endeavor for developers during development and maintenance tasks. The challenges mainly stem from the dynamic, event-driven, and asynchronous nature of the JavaScript language. We propose a generic technique for capturing low-level event-based interactions in a web application and mapping those to a higher-level behavioral model. This model is then transformed into an interactive visualization, representing episodes of triggered causal and temporal events, related JavaScript code executions, and their impact on the dynamic DOM state. Our ap- proach, implemented in a tool called CLEMATIS, allows developers to easily understand the complex dynamic behavior of their application at three different semantic levels of granularity. Furthermore, CLEMATIS helps developers bridge the gap between test cases and program code by localizing the fault related to a test assertion. The results of our industrial controlled experiment show that CLEMATIS is capable of improving the comprehension task accuracy by 157% while reducing the task completion time by 47%. A follow-up experiment reveals that CLEMATIS improves the fault localization accuracy of developers by a factor of two. Categories and Subject Descriptors: D.2.5 [Software Engineering]: Testing and Debugging; D.2.7 [Software Engineering]: Distribution, Maintenance, and Enhancement General Terms: Design, Algorithms, Experimentation Additional Key Words and Phrases: Program comprehension, event-based interactions, JavaScript, web applications, fault localization ACM Reference Format: Saba Alimadadi, Sheldon Sequeira, Ali Mesbah, and Karthik Pattabiraman.
    [Show full text]
  • Flare-On 3: Challenge 10 Solution - FLAVA
    Flare-On 3: Challenge 10 Solution - FLAVA Challenge Authors: FireEye Labs Advanced Vulnerability Analysis Team (FLAVA) Intro The first part of FLAVA challenge is a JavaScript puzzle based on the notorious Angler Exploit Kit (EK) attacks in 2015 and early 2016. All classic techniques leveraged by Angler, along with some other intriguing tricks utilized by certain APT threat actors, are bundled into this challenge. While Angler EK’s activities have quieted down since the takedown of a Russian group “Lurk” in mid 2016, its advanced anti-analysis and anti-detection techniques are still nuggets of wisdom that we think are worth sharing with the community for future reference. Walkthrough Compromising or malvertising on legitimate websites are the most common ways that exploit kits redirect victims to their landing pages. Exploit kits can redirect traffic multiple times before serving the victim the landing page. Once on the landing page, the exploit kit profiles the victim’s environment, and may choose to serve an exploit that affects it. In the case of this challenge, the landing page is only one redirect away from the compromised site (hxxp://10.11.106.81: 18089/flareon_found_in_milpitas.html). Often, Angler’s (and many other EKs’) landing page request has a peculiar, and thus fishy, URL after some seemingly legit HTTP transactions. Layer-0 Walkthrough The landing page may initially seem daunting, and that’s exactly the purpose of obfuscation. But it’s still code, regardless of the forms it may take. After all, it’s supposed to carry out the attack without any user interaction. It’s strongly advised to rewrite the code with meaningful names during analysis, just as one would in IDA when analyzing binaries.
    [Show full text]
  • Javascript for PHP Developers
    www.it-ebooks.info www.it-ebooks.info JavaScript for PHP Developers Stoyan Stefanov www.it-ebooks.info JavaScript for PHP Developers by Stoyan Stefanov Copyright © 2013 Stoyan Stefanov. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://my.safaribooksonline.com). For more information, contact our corporate/ institutional sales department: 800-998-9938 or [email protected]. Editor: Mary Treseler Indexer: Meghan Jones, WordCo Indexing Production Editor: Kara Ebrahim Cover Designer: Randy Comer Copyeditor: Amanda Kersey Interior Designer: David Futato Proofreader: Jasmine Kwityn Illustrator: Rebecca Demarest April 2013: First Edition Revision History for the First Edition: 2013-04-24: First release See http://oreilly.com/catalog/errata.csp?isbn=9781449320195 for release details. Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of O’Reilly Media, Inc. JavaScript for PHP Developers, the image of an eastern gray squirrel, and related trade dress are trademarks of O’Reilly Media, Inc. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and O’Reilly Media, Inc., was aware of a trade‐ mark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this book, the publisher and author assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.
    [Show full text]
  • Designing for Extensibility and Planning for Conflict
    Designing for Extensibility and Planning for Conflict: Experiments in Web-Browser Design Benjamin S. Lerner A dissertation submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy University of Washington 2011 Program Authorized to Offer Degree: UW Computer Science & Engineering University of Washington Graduate School This is to certify that I have examined this copy of a doctoral dissertation by Benjamin S. Lerner and have found that it is complete and satisfactory in all respects, and that any and all revisions required by the final examining committee have been made. Chair of the Supervisory Committee: Daniel Grossman Reading Committee: Daniel Grossman Steven Gribble John Zahorjan Date: In presenting this dissertation in partial fulfillment of the requirements for the doctoral degree at the University of Washington, I agree that the Library shall make its copies freely available for inspection. I further agree that extensive copying of this dissertation is allowable only for scholarly purposes, consistent with “fair use” as prescribed in the U.S. Copyright Law. Requests for copying or reproduction of this dissertation may be referred to Proquest Information and Learning, 300 North Zeeb Road, Ann Arbor, MI 48106-1346, 1-800-521-0600, to whom the author has granted “the right to reproduce and sell (a) copies of the manuscript in microform and/or (b) printed copies of the manuscript made from microform.” Signature Date University of Washington Abstract Designing for Extensibility and Planning for Conflict: Experiments in Web-Browser Design Benjamin S. Lerner Chair of the Supervisory Committee: Associate Professor Daniel Grossman UW Computer Science & Engineering The past few years have seen a growing trend in application development toward “web ap- plications”, a fuzzy category of programs that currently (but not necessarily) run within web browsers, that rely heavily on network servers for data storage, and that are developed and de- ployed differently from traditional desktop applications.
    [Show full text]
  • Javascript: the Used Parts
    JavaScript: The Used Parts by Sharath Chowdary Gude A thesis submitted to the Graduate Faculty of Auburn University in partial fulfillment of the requirements for the Degree of Master of Science Auburn, Alabama Feb May 22,2, 2014 2014 Keywords: JavaScript, Empirical Study, Programming languages Copyright 2014 by Sharath Chowdary Gude Approved by Dr. Munawar Hafiz, Computer Science and Software Engineering Dr. Levent Yilmaz, Computer Science and Software Engineering Dr. Jeff Overbey,Computer Science and Software Engineering Abstract JavaScript is designed as a scripting language which gained mainstream adoption even without creation of proper formal standard. The success of JavaScript could be attributed to the explosion of the internet and simplicity of its usage. Even though web is still its strongest domain, JavaScript is a language constantly evolving. The language is now used in OS free Desktop application development, databases etc. The standards committee wants to revamp the standard with addition of new features and provide solutions to controversial features of language[1]. This needs a large scale empirical studies spanning all diverse paradigms of JavaScript. The interpreted nature of language needs a proper mechanism to perform both static and dynamic analysis. These analyses should be analyzed and interpreted to understand the general usage of language by the programming community and formulate the best ways to evolve the language. The inherent misconceptions among the programming community about the language are to be studied, usage patterns are to be analyzed to generate data on usage of features and thus justifying an argument for need to refine the feature. The thesis explores the features in the language deemed problematic by experts, the way these features are used by the programming community and the need for refining these features backed up with an empirical study.
    [Show full text]
  • Use Firefox's Firebug Addon to Debug EBI 3 Webservices
    Sean Hoppe Consulting Group Use Firefox’s Firebug Addon to Debug EBI 3 Webservices In our previous tech memo, we looked at Creating REST Webservices Provider in less than 15 Minutes. The instructions below, are a continuation of the previous post and shows users how to use Firefox's Firebug add-on to test the REST Webservice Provider we just created. In our scenario, the EBI 3 REST Webservice will be returning the EBI ProcessID as a property in the Response Headers. With help from Firebug, we will be able to see the ProcessID property. Note: Users will need to download the Firefox browser to be able to use the instructions below. 1 DOWNLOAD FIREFOX’S FIREBUG ADDON The first step the EBI user needs to take is download Firefox's Firebug. It can be downloaded here: https://addons.mozilla.org/en-US/firefox/addon/firebug/ 114294-1 - EBIThree - Use Firefox’s Firebug Addon to Debug EBI 3 Webservices Page 1 2 START WEBSERVICE PROVIDER We will want to start the EBI 3 Webservice Provider, if it has not started. Users can refer to Starting Local Server in the previous tech memo: . 114293-1 - Create REST Webservices Provider in less than 15 Minutes 3 ACTIVATE FIREFOX’S FIREBUG Open up the Firefox Browser and activate Firebug Initially, the Firebug icon might be greyed out (below) If the Firebug icon is greyed out, click on it, to activate Firebug (below) Once Firebug is activated, we should see a lower control panel for Firebug. 114294-1 - EBIThree - Use Firefox’s Firebug Addon to Debug EBI 3 Webservices Page 2 4 TEST EBI 3 WEBSERVICE Once the EXTOL Webservice Monitor is started and Firebug is active, we can input the Webservice URL into the browser.
    [Show full text]