Spelling suggestions: "subject:"javascript"" "subject:"avascript""
31 |
Dependency Analysis in the HTML5, JavaScript and CSS3 StackJanuary 2014 (has links)
abstract: The Internet is transforming its look, in a short span of time we have come very far from black and white web forms with plain buttons to responsive, colorful and appealing user interface elements. With the sudden rise in demand of web applications, developers are making full use of the power of HTML5, JavaScript and CSS3 to cater to their users on various platforms. There was never a need of classifying the ways in which these languages can be interconnected to each other as the size of the front end code base was relatively small and did not involve critical business logic. This thesis focuses on listing and defining all dependencies between HTML5, JavaScript and CSS3 that will help developers better understand the interconnections within these languages. We also explore the present techniques available to a developer to make his code free of dependency related defects. We build a prototype tool, HJCDepend, based on our model, which aims at helping developers discover and remove defects early in the development cycle. / Dissertation/Thesis / M.C.St. Computing Studies 2014
|
32 |
Analýza možností a omezení BI nástroje Report Studio / Analysis of possibilities and limitations of BI tool Report StudioČapková, Lenka January 2013 (has links)
This master thesis focuses on the opinions and barriers from the BI tool in Report Studio as the part of IBM Cognos BI for the creation of reports. The aim of this thesis is to analyze all the functions of this tool and simplify that experience for other users. The theoretical section of this thesis introduces Business Intelligence as well as the product IBM Cognos BI itself divided into individual components. The final part of thesis introduces and compares similar products available on the market from the competitors. The practical part consists of analysis of Report Studio tool functions followed by applied criteria. In this part, the strengths and weaknesses of Report Studio are mentioned along with proposals of procedures regarding work efficiency using this tool. This section also lists nonstandard examples collected from the client's experience followed by the exact procedures using solution default functions of Report Studio and script language JavaScript.
|
33 |
JavaScript DOM Manipulation Performance : Comparing Vanilla JavaScript and Leading JavaScript Front-end FrameworksPersson, Morgan January 2020 (has links)
Background. Websites of 2020 are often feature rich and highly interactive applications. JavaScript is a popular programming language for the web, with many frameworks available. A common denominator for highly interactive web applications 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 application 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. In Vanilla JavaScript DOM manipulation is handled by direct interaction with the DOM interface. When using the selected frameworks the actual interaction with the DOM interface is abstracted away from the developer and handled by the framework. While React and Vue.js both have implemented a Virtual DOM to optimize DOM interactions, Angular has implemented Incremental DOM. Vanilla JavaScript had the best DOM performance in all tests and the smallest application size. Amongst the frameworks React had the best DOM performance, Angular performed close to React in nearly all test, and Vue.js was slightly slower in most tests. In nearly all tests the applications performed better in Google Chrome. Conclusions. Vanilla JavaScript and the selected frameworks, and thereby their DOM manipulation methodologies, are all feasible alternatives for creating interactive web applications with high DOM performance. Tests indicate that Vanilla JavaScript and the selected frameworks achieves better DOM performance in Google Chrome compared to Firefox.
|
34 |
Combining Result Size Calculation and Query Execution for the GraphQL Query LanguageLundquist, Andreas January 2020 (has links)
GraphQL is an open source framework for creating adaptable API layers and was developed and released by Facebook in 2015. GraphQL includes both a query language and an execution engine and has quickly gained popularity among developers. However, GraphQL suffers from a problem, certain types of queries can generate huge response objects that grow exponentially in size. A recent research paper proposed a solution to this problem in the form of an algorithm that calculates the result size of a query without executing the query itself. The algorithm enables the possibility to decide if a query should be executed based on the query response size. In an implementation and evaluation of this algorithm, it was found that for simple queries, running the algorithm takes approximately the same time as executing the query, which means that the total query processing time is doubled. This thesis proposes a way to solve that problem by introducing an extended algorithm that combines the result size calculation with query execution. An implementation of the extended algorithm was evaluated and shows that it is a viable option that only has a minor impact on the total query processing time for most queries.
|
35 |
Řízení autonomního agenta pomocí neuroevoluceHnátek, Martin January 2018 (has links)
Thesis describe theory behind neuroevolution. Then it describes both design and creation of simulated environment for autonomous agent and its training with library Neataptic in environments with various difficulty. Thesis also describes pro- cess of designing frontend for visualization of results and backend for faster training of agents. At the end it describes resulting agents and proposes enhancements to existing solution.
|
36 |
SayHi – En webbshop : Ett projekt skapat med ASP.NET Core MVC, JavaScript och SASSRanemo, Charlotte January 2021 (has links)
The purpose of this website was to create a platform for the company SayHi to sell their selfmade greeting cards. By creating an administrator part of the website it will be enabled for administrators to log in and add new cards for sale, as well as categories and new users. The webshop will be fully functioning and have invoice as the option for payment, and the customer will recieve an order confirmation by email after a purchase has been done, and these purchases will be kept on record and will be displayable for the administrators. The website will be made using ASP.NET Core MVC, SASS, HTML5 and JavaScript and will be coded in Visual Studio 2019. By the end of this project, we will have a functioning webshop with a user-tested design that speaks to the customers and enables them to buy greeting cards online. The result of this project is a functioning e-commerce store that enables the selling of self made greeting cards in a user friendly manner. / Syftet med detta arbete var att ta fram en webbshop som möjliggjorde för mig som ägare av SayHi att sälja egengjorda gratulationskort. Genom att skapa en administratörsdel skulle det gå för registrerade administratörer att lägga till, redigera och ta bort gratulationskort som är till salu, samt att göra detsamma med de kategorier av kort som ligger uppe på siten. Själva webbshoppen skulle ha ett fungerande flöde, från försäljning och visning av kort till genomförd beställning och e-postbekräftelse till den e-post som kunden angivit. Denna webbplats och alla dess funktioner skapas med ASP.NET Core MVC som backend, samt SASS, HTML5 och JavaScript som frontend. SayHi är namnet som applikationen tilldelades, och ska ligga tillgänglig på en domän med samma namn. Målet med applikationen är att skapa en webbshop som fungerar fullt ut, men med faktura som enda tillgängliga betalmedel. Webbplatsen ska se attraktiv ut för besökare, och den ska validera och genomgå användartester innan den anses vara färdig. Resultatet av detta arbete är en fungerande webbshop som möjliggör försäljningen av gratulationskort på ett användarvänligt sätt.
|
37 |
A closer look at WebAssemblyEleskovic, Denis January 2020 (has links)
WebAssembly is a new emerging technology for the web which offers a low-level bytecode format for other languages to compile to. The aim of the technology is to effectively speed up the performance of the web, as well as to offer a way for developers to port existing libraries and code that were written in static languages such as C/C++ or Rust. The technology is currently supported in all the major browsers of today.This study takes a closer look at how the technology works and how it is compiled and executed across two of the major browsers as compared to JavaScript. Furthermore, a smaller experiment was conducted where AssemblyScript was used to compile to WebAssembly, with AssemblyScript being a typescript-to-WebAssembly compiler. The two technologies were then tested in terms of runtime performance and consistency across two browsers, operating systems as well as with different optimizations.The study showed that the technology goes through ahead-of-time-compilation and optimization through a compiler toolchain that depends on the language used as opposed to JavaScript which makes use of just-in-time-compilation. Furthermore, the fundamental structure for WebAssembly proved to be limited in order to be able to better link directly to machine code and through this offer performance benefits. The experiment conducted showed that WebAssembly performed better when it came to pure calculations but fell behind JavaScript when performing operations on an array. The reason is most likely due to the overhead of passing data structures between the two technologies. The experiment further showed that WebAssembly was able to offer a more consistent and predictable performance than JavaScript.
|
38 |
Performance study of JavaScript WebSocket frameworks / Prestandajämförelse av JavaScript WebSocket ramverkHansson, Jakob January 2020 (has links)
The requirements on software and applications are getting harder. If they are perceived as slow or power hungry, the customers will be looking for other solutions instead. The development of open source frameworks is rapid. Frameworks are being built and updated continuously, with different performance, functionality and complexity. This bachelor’s thesis studies and compares WebSocket frameworks in JavaScript, with focus on performance and scalability. A pre-study was made to find out which parameters are of interest when testing and measuring the performance of web servers. A test bench was then built and plain WebSocket, Socket.IO and SockJS were benchmarked. The study shows that there exist significant differences in performance and trends that indicate that some frameworks are superior to others in high concurrency applications. Plain WebSocket can be up to 3.7 times as fast to receive a message from the server compared to Socket.IO and 1.7 times as fast compared to SockJS. Plain WebSocket scales well in terms of response time and memory requirement with higher concurrency levels. Socket.IO requires a lot of memory which is a potential problem. SockJS does not scale well at all and does not manage the same level of concurrency as the other two.
|
39 |
ScriptSpaces: An Isolation Abstraction for Web BrowsersDeka, Amarjyoti 02 September 2010 (has links)
Current web browsers are ill-prepared to manage execution of scripts embedded in web pages, because they treat all JavaScript code executing in a page as one unit. All code shares the same namespace, same security domain, and shares uncontrolled access to the same heap; some browsers even use the same thread for multiple tabs or windows. This lack of isolation frequently causes problems that range from loss of functionality to security compromises.
ScriptSpace is an abstraction that provides separate, isolated execution environments for parts or all of a web page. Within each ScriptSpace, we maintain the traditional, single-threaded JavaScript environment to provide compatibility with existing code written under this assumption. Multiple ScriptSpaces within a page are isolated with respect to namespace, CPU, and memory consumption. The user has the ability to safely terminate failing scripts without affecting the functionality of still-functional components of the page, or of other pages.
We implemented a prototype of ScriptSpace based on the Firefox 3.0 browser. Rather than mapping ScriptSpaces to OS-level threads, we exploit a migrating-thread model in which threads enter and leave the ScriptSpaces associated with the respective sections of the document tree during the event dispatching process. A proportional share scheduler ensures that the number of bytecode instructions executed within each ScriptSpace is controlled. Our prototype can isolate resource-hogging gadgets within an iGoogle Mashup page as well as across multiple pages loaded in the browser and still retain interactive response. / Master of Science
|
40 |
Rich Cloud-based Web Applications with Cloudbrowser 2.0Pan, Xiaozhong 21 June 2015 (has links)
When developing web applications using traditional methods, developers need to partition the application logic between client side and server side, then implement these two parts separately (often using two different programming languages) and write the communication code to synchronize the application's state between the two parts. CloudBrowser is a server- centric web framework that eliminates this need for partitioning applications entirely. In CloudBrowser, the application code is executed in server side virtual browsers which preserve the application's presentation state. The client web browsers act like rendering devices, fetching and rendering the presentation state from the virtual browsers. The client-server communication and user interface rendering is implemented by the framework under the hood. CloudBrowser applications are developed in a way similar to regular web pages, using no more than HTML, CSS and JavaScript. Since the user interface state is preserved, the framework also provides a continuous experience for users who can disconnect from the application at any time and reconnect to pick up at where they left off.
The original implementation of CloudBrowser was single-threaded and supported deployment on only one process. We implemented CloudBrowser 2.0, a multi-process implementation of CloudBrowser. CloudBrowser 2.0 can be deployed on a cluster of servers as well as a single multi-core server. It distributes the virtual browsers to multiple processes and dispatches client requests to the associated virtual browsers. CloudBrowser 2.0 also refines the CloudBrowser application deployment model to make the framework a PaaS platform. The developers can develop and deploy different types of applications and the platform will automatically scale them to multiple servers. / Master of Science
|
Page generated in 0.0382 seconds