DOCSLIB.ORG

HYCU for Azure Open Source Licenses

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

OPEN SOURCE LICENSES HYCU Data Protection as a Service for Azure Service update date: November 2020 Document release date: November 2020 Legal notices Copyright notice © 2020 HYCU. All rights reserved. This document contains proprietary information, which is protected by copyright. No part of this document may be photocopied, reproduced, distributed, transmitted, stored in a retrieval system, modified or translated to another language in any form by any means, without the prior written consent of HYCU. Trademarks HYCU logos, names, trademarks and/or service marks and combinations thereof are the property of HYCU or its affiliates. Other product names are the property of their respective trademark or service mark holders and are hereby acknowledged. Azure®, Internet Explorer®, Microsoft®, Microsoft Edge™, and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Google Chrome™ is a trademark of Google LLC. Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries. Mozilla and Firefox are trademarks of the Mozilla Foundation in the U.S. and other countries. Disclaimer The details and descriptions contained in this document are believed to have been accurate and up to date at the time the document was written. The information contained in this document is subject to change without notice. HYCU provides this material "as is" and makes no warranty of any kind, expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. HYCU shall not be liable for errors and omissions contained herein. In no event shall HYCU be liable for any direct, indirect, consequential, punitive, special or incidental damages, including, without limitation, damages for loss and profits, loss of anticipated savings, business interruption, or loss of information arising out of the use or inability to use this document, or any action taken based on the information contained herein, even if it has been advised of the possibility of such damages, whether based on warranty, contract, or any other legal theory. 2 The only warranties for HYCU products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Notice This document is provided in connection with HYCU products. HYCU may have copyright, patents, patent applications, trademark, or other intellectual property rights covering the subject matter of this document. Except as expressly provided in any written license agreement from HYCU, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property on HYCU products. Use of underlying HYCU product(s) is governed by their respective Software License and Support Terms. Important: Please read Software License and Support Terms before using the accompanying software product(s). HYCU www.hycu.com 3 Contents Apache License 2.0 7 Open Sans 7 BSD 3-Clause License 10 ace-builds 1.4.12 11 d3 3.5.17 11 ISC License 12 glob 7.1.1 12 MIT License 13 angular 1.6.1 13 angular-animate 1.6.1 13 angular-busy2 5.2.0 14 angular-cookies 1.6.0 15 angular-gridster 0.13.14 15 angular-ivh-treeview 2.0.0-alpha.2 16 angular-mocks 1.5.8 16 angular-modal-service 0.10.1 17 angular-sanitize 1.5.9 17 angular-ui-router 0.4.2 18 angularjs-toaster 2.1.0 18 animate.css 3.5.2 19 babel-core 6.18.2 19 babel-loader 6.2.7 20 babel-plugin-transform-runtime 6.23.0 21 babel-preset-es2015 6.18.0 21 babel-preset-es2016 6.24.1 22 babel-preset-es2017 6.24.1 22 bean 1.0.15 23 4 bootstrap 3.3.7 23 bootstrap-progressbar 0.9.0 24 chalk 1.1.3 25 css-loader 0.25.0 25 dateformat 1.0.12 26 del 2.2.2 26 eonasdan-bootstrap-datetimepicker-npm 4.17.42 27 event-source-polyfill 0.0.7 27 extract-text-webpack-plugin 1.0.1 28 file-loader 0.9.0 28 file-saver 1.3.3 29 Fontello 29 gulp 3.9.1 30 gulp-util 3.0.7 30 imports-loader 0.7.1 31 jasmine-core 2.5.2 31 jquery 2.2.4 32 jquery-mousewheel 3.1.13 32 json-schema-faker 0.4.0 33 json-server 0.9.5 34 karma 1.3.0 34 karma-chrome-launcher 2.0.0 35 karma-jasmine 1.0.2 35 karma-webpack 1.8.0 36 lodash 4.17.2 36 malihu-custom-scrollbar-plugin 3.1.5 37 moment 2.17.1 38 moment-timezone 0.5.27 39 ngstorage 0.3.11 39 node-sass 3.11.2 40 raw-loader 0.5.1 40 5 sass-loader 4.0.2 41 url-loader 0.5.7 41 vinyl-named 1.1.0 42 webpack 1.13.3 42 webpack-dev-server 1.16.2 43 webpack-stream 3.2.0 43 SIL Open Font License 1.1 44 Font Awesome 44 Inconsolata 46 Muli 48 Source Code Pro 50 6 Apache License 2.0 Apache License 2.0 HYCU acknowledges the use of the following open source component that is provided under this license. Open Sans https://github.com/googlefonts/opensans License source: https://github.com/googlefonts/opensans/blob/master/LICENSE.txt Copyright 2010-2018 Google LLC Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. 7 Apache License 2.0 "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty- free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty- free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted.
Recommended publications
  • Differential Fuzzing the Webassembly

    Differential Fuzzing the Webassembly

    Master’s Programme in Security and Cloud Computing Differential Fuzzing the WebAssembly Master’s Thesis Gilang Mentari Hamidy MASTER’S THESIS Aalto University - EURECOM MASTER’STHESIS 2020 Differential Fuzzing the WebAssembly Fuzzing Différentiel le WebAssembly Gilang Mentari Hamidy This thesis is a public document and does not contain any confidential information. Cette thèse est un document public et ne contient aucun information confidentielle. Thesis submitted in partial fulfillment of the requirements for the degree of Master of Science in Technology. Antibes, 27 July 2020 Supervisor: Prof. Davide Balzarotti, EURECOM Co-Supervisor: Prof. Jan-Erik Ekberg, Aalto University Copyright © 2020 Gilang Mentari Hamidy Aalto University - School of Science EURECOM Master’s Programme in Security and Cloud Computing Abstract Author Gilang Mentari Hamidy Title Differential Fuzzing the WebAssembly School School of Science Degree programme Master of Science Major Security and Cloud Computing (SECCLO) Code SCI3084 Supervisor Prof. Davide Balzarotti, EURECOM Prof. Jan-Erik Ekberg, Aalto University Level Master’s thesis Date 27 July 2020 Pages 133 Language English Abstract WebAssembly, colloquially known as Wasm, is a specification for an intermediate representation that is suitable for the web environment, particularly in the client-side. It provides a machine abstraction and hardware-agnostic instruction sets, where a high-level programming language can target the compilation to the Wasm instead of specific hardware architecture. The JavaScript engine implements the Wasm specification and recompiles the Wasm instruction to the target machine instruction where the program is executed. Technically, Wasm is similar to a popular virtual machine bytecode, such as Java Virtual Machine (JVM) or Microsoft Intermediate Language (MSIL).
  • Deadline-Driven Serverless for the Edge

    Deadline-Driven Serverless for the Edge

    SledgeEDF: Deadline-driven Serverless for the Edge by Sean Patrick McBride B.S. in German, May 2007, United States Military Academy M.A.S. in Information Technology and Management, May 2013, Illinois Institute of Technology A Thesis submitted to The Faculty of The School of Engineering and Applied Science of The George Washington University in partial satisfaction of the requirements for the degree of Master of Science January 8, 2021 Thesis directed by Gabriel Parmer Associate Professor of Computer Science c Copyright 2021 by Sean Patrick McBride All rights reserved ii Dedication This thesis is dedicated to the many educators, mentors, and battle buddies that have helped me grow as a technologist, software engineer, and computer scientist. Sankaran Iyer, Susan Schwartz, Chris Okasaki, Christa Chewar, Ray Trygstad, Jeremy Hajek, Jeffrey Kimont, Robert Hendry, Carol Davids, Bill Slater, Bonnie Goins, David Gaertner, Andy Quintana, Patricia Schatz, Wayne Bucek, Pat Medo, Lih Wang, Tony Liu, Bill Seubert, Marty Horan, Fred Bader, Mitch Green, Bob Kaas, Richard Lewis, Gwen Dente, Ray Mullins, Frank DeGilio, Paul Novak, Bruce Hayden, Art Breslau, Chris Ganim, Mark Woehrer, Will Dory, Steve Payne, Walt Melo, Mark Davis, Omri Bernstein, Eliot Szwajkowski, Dani Young-Smith, Conrad Holloman, David Tillery, Garth Hershfield, Daniel Cox, Doug Fort, Jeff Hemminger, Josh Rutherford, Hiromi Suenaga, Kait Moreno, Howie Huang, Ben Bowman, Yuede Ji, Pradeep Kumar, Nahid Ghalaty, Roozbeh Haghnazar, Morris Lancaster, Gabe Parmer, Phani Kishoreg, and the unnamed others I’ve forgotten. I am mostly an ambulatory accumulation of the investments others have made in me over the years. I hope that you consider me a worthy investment, and I pledge to pay this forward! iii Abstract SledgeEDF: Deadline-driven Serverless for the Edge Serverless Computing has gained mass popularity by offering lower cost, improved elasticity, and improved ease of use.
  • Domando Al Escritor, Edición 2018 En Formato

    Domando Al Escritor, Edición 2018 En Formato

    Domando al Escritor LibreOffice™ Writer para escritores Edición 2018 Ricardo Gabriel "erla##o ¡No puedes pasar! https://elpinguinotolkiano.wordpress.com/ LibreOffice™ Writer o$rece% tanto al a&cionado como al pro$esional de las letras% una serie de (erramientas )ers*tiles + potentes que $acilitan el trabajo del escritor% automatizando las tareas m*s /di$íciles1 + dejando al a'tor con la única res3 ponsabilidad de escribir4 Di$erentes estilos de p*5ina% re$erencias cruzadas + biblio3 5r*&cas% opciones tipo5r*&cas a)anzadas% complejos diseños de te7to% tablas% $8rmulas matem*ticas% 5r*&cas9 todo esto + m*s puede ser realizado en LibreOffice™ Writer4 :o todo es per$ecto% tendremos problemas ,'e resol)er% por lo que en este libro tambi;n )er*s las limitaciones del pro5rama + c8mo superarlas4 El te7to (a sido or5anizado en la $orma de un /curso1 que% partiendo de lo m*s b*sico lle5a pro5resi)amente a mos3 trar todo lo ,'e este pro5rama tiene para o$recernos4 La presente edici8n se centra en la )ersi8n <4=% e7plicando sus numerosas no)edades e indicando ,'; nos traer* <4>4 ?arios capítulos ser*n dedicados a o$recer 'na introduc3 ci8n a otras componentes como Dra@% Aat( + B(art4 Domando al Escritor LibreOffice™ Writer para escritores Edición 2018 Ricardo Gabrie! " rla#so Cor,'e el pincel de $ormato no puede pasar D >E=F Ricardo Gabriel Berlasso Esta obra se distrib'+e ba-o licencia Breati)e Bommons Gtribuci8n3BompartirHgual I4E Hnternacional JBB "K3LG I4EM Jhttp://creativecommons.org/licenses/by-sa/4.0/M Atribución: Osted debe darle crédito
  • Full Stack Web Development

    Full Stack Web Development

    Full Stack Web Development Partial report in partial fulfilment of the requirement of the Degree of Bachelor of Technology In Computer Science and Engineering By Charchit Kapoor (161207) Under the supervision of Umesh Sharma Product Manager (magicPin Samast Technologies Pvt. Ltd) To Department of Computer Science Engineering and Information Technology Jaypee University of Information Technology,Waknaghat,Solan-173234 Himachal Pradesh I CERTIFICATE Candidate Declaration I”declare that the work presented in this report ‘Full Stack Web Development’ in partial fulfilment of”the requirements for the award of the degree of bachelor of Technology in Computer Science and Engineering submitted in the department of Computer Science and Engineering/ Information Technology,”Jaypee University of Information Technology Waknaghat, is an authentic record of my work carried out over a period of Feb,2020 to”May,2020 under the Supervision of Umesh Sharma (Product Manager, magicPin). The matter embodied in the report”has not been submitted for the award of any other degree or diploma. It contains sufficient”information to describe the various tasks performed by me during the internship. Charchit Kapoor, 161207 This is to certify that”the above statement made by the candidate is true to the best of my knowledge. The report has been reviewed by the company officials, and has been audited according to the company guidelines. Umesh Sharma Product Manager magicPin (Samast Technologies Private Ltd.) Dated: May 29th, 2020 II ACKNOWLEDGEMET We have taken efforts in”this project. However, it would not have been possible without the kind support and help of many”individuals and organisations. I would like to extend our sincere thanks to all of them.
  • International Journal of Progressive Research in Science and Engineering, Vol.2, No.8, August 2021

    International Journal of Progressive Research in Science and Engineering, Vol.2, No.8, August 2021

    INTERNATIONAL JOURNAL OF PROGRESSIVE RESEARCH IN SCIENCE AND ENGINEERING, VOL.2, NO.8, AUGUST 2021. Web Application to Search and Rank Online Learning Resources from Various Sites Keshav J1, Venkat Kumar B M1, Ananth N1 1Student, Department of Computer Engineering, Velammal Engineering College, Anna University, Chennai, Tamil Nadu, India. Corresponding Author: [email protected] Abstract: - E-Learning is becoming one of the most reliable and fast methods for learning in the present days and this trend will only continue to grow in the coming years. However, the process of finding the correct course in the desired topic is becoming harder and harder day by day due to the sheer number of resource material being uploaded to the internet. Currently, whenever there’s a need to acquire a new skill or learn something new, people go on different platforms to search for resources to learn them - YouTube for videos, Google for blogs, Coursera/Udemy/Edx for courses. This leads to taking too much time in finding the right resource to start learning. They have to try out multiple resources before finding the right one. We plan to eliminate this with our website, where a single search query will fetch the top videos, blogs, and courses for that query. Users will be able to rate the results, and the upcoming search results will be ordered primarily based on the user ratings. This will allow the most useful blogs, courses, and videos to rank up. Additionally, the resources will have comments and tags, so that the user can read a review before opening a tutorial.
  • AMP's Governance Model

    AMP's Governance Model

    Governance Update & Next Steps AMP Contributor Summit - October 10, 2019 Tobie Langel (@tobie) bit.ly/ampgov-blog AMP’s Governance Model ● The Technical Steering Committee (TSC) ● The Advisory Committee (AC) ● Working Groups (WGs) Technical Steering Committee (TSC) Sets AMP's technical & product direction based on the project guidelines. TSC Members ● Chris Papazian, Pinterest - @cpapazian* ● David Strauss, Pantheon - @davidstrauss* ● Dima Voytenko, Google - @dvoytenko* ● Malte Ubl, Google - @cramforce* ● Paul Armstrong, Twitter - @paularmstrong ● Rudy Galfi, Google - @rudygalfi* ● Saulo Santos, Microsoft - @ssantosms* * Present at the AMP Contributor Summit 2019 So… what has the TSC been up to? ● Set up the initial set of Working Groups. ● Clarified the contribution process (OWNERS/Reviewers/Collaborators). ● Formalized how cherry picks are handled. ● Asked for more formal regular updates from the Working Groups. Working Groups (WGs) Segments of the community with knowledge/interest in specific areas of AMP. Working groups ● Access control and subscriptions WG - user ● AMP4Email WG - AMP4Email project. specific controlled access to AMP content. ● Ads WG - ads features and integrations in AMP ● Validation & caching WG - AMP validator and ● Analytics WG - analytics features and integrations features related to AMP caches. in AMP. ● Viewers WG - ensures support for AMP viewers ● Stories WG - implements and improves AMP's and for the amp-viewer project. story format. ● Approvers WG - approves changes that have a ● Performance WG - monitors and improves AMP's significant impact on AMP's behavior or significant load and runtime perf. new features. ● Runtime WG - AMP's core runtime ● Infrastructure WG - AMP's infrastructure, (layout/rendering and data binding). including building, testing and release. ● UX & Accessibility WG - AMP's visual ● Code of Conduct WG - enforces AMP's CoC.
  • FONT GUIDE Workbook to Help You Find the Right One for Your Brand

    FONT GUIDE Workbook to Help You Find the Right One for Your Brand

    FONT GUIDE Workbook to help you find the right one for your brand. www.ottocreative.com.au Choosing the right font for your brand YOUR BRAND VALUES: How different font styles can be used to make up your brand: Logo Typeface: Is usually a bit more special and packed with your brands personality. This font should be used sparingly and kept for special occasions. Headings font: Logo Font This font will reflect the same brand values as your logo font - eg in this example both fonts are feminine and elegant. Headings Unlike your logo typeface, this font should be easier to read and look good a number of different sizes and thicknesses. Body copy Body font: The main rule here is that this font MUST be easy to read, both digitally and for print. If there is already alot going on in your logo and heading font, keep this style simple. Typefaces, common associations & popular font styles San Serif: Clean, Modern, Neutral Try these: Roboto, Open Sans, Lato, Montserrat, Raleway Serif: Classic, Traditional, reliable Try these: Playfair Display, Lora, Source Serif Pro, Prata, Gentium Basic Slab Serif: Youthful, modern, approachable Try these: Roboto Slab, Merriweather, Slabo 27px, Bitter, Arvo Script: Feminine, Romantic, Elegant Try these: Dancing Script, Pacifico, Satisfy, Courgette, Great Vibes Monotype:Simple, Technical, Futuristic Try these: Source Code Pro, Nanum Gothic Coding, Fira Mono, Cutive Mono Handwritten: Authentic, casual, creative Try these: Indie Flower, Shadows into light, Amatic SC, Caveat, Kalam Display: Playful, fun, personality galore Try these: Lobster, Abril Fatface, Luckiest Guy, Bangers, Monoton NOTE: Be careful when using handwritten and display fonts, as they can be hard to read.
  • Recent Enhancements of Node-RED for Rapid Development of Large Scale and Robust Iot Applications

    Recent Enhancements of Node-RED for Rapid Development of Large Scale and Robust Iot Applications

    Recent Enhancements of Node-RED for Rapid Development of Large Scale and Robust IoT Applications . .2.2 0.,21010 Agenda 1. Introduction to Node-RED 2. Flow-based Programming in Node-RED 3. Recent Features of Node-RED © Hitachi, Ltd. 2019. All rights reserved. 2 Agenda 1. Introduction to Node-RED 2. Flow-based Programming in Node-RED 3. Recent Features of Node-RED © Hitachi, Ltd. 2019. All rights reserved. 3 What is Node-RED? OSS Visual Programing Tool for IoT Applications Development p Originally developed by IBM. Currently project under OpenJS Foundation p Works on broad range of computers: Small IoT devices to Cloud Env. p Rapid development of Applications by connecting set of predefined nodes d9RLRM)*02UURP[N[NNM 4 Growing Use of Node-RED Node-RED users are growing continuously since its introduction: p Over 60K downloads/month in 2019 p 1.8M accumulated downloads in 2019 (K downloads) Accumulated(Left) Monthly(Right) (K downloads) 2,000 80 70 1,500 60 50 1,000 40 30 Number of Number Number of Number 500 20 10 Downloads/Month Accumulated Downloads Downloads Accumulated 0 0 Jan '15 Jan '16 Jan '17 Jan '18 Jan '19 NPM download Statistics of Node-RED d9RLRM)*02UURP[N[NNM 5 Production Use of Node-RED Major IT companies adopting Node-RED for their products/services For Edge Environment: In HITACHI: p Use Node-RED in "DevOps for IoT" application :WNU BRNVNW[ 8 ":XC8Na ":C)) "NMR development env. of Lumada Solution Hub* BV[]WP CX[RK 4 "2AC: "B:G "4G:E Cloud Environment: :3 2CC 4:B4 ":34UX]M "2CCUX5N[RPWN "NTR BRNVNW[ ]SR[] 9:C249: "RWMBNN "4:2 "]VM *: [1((RLRLXV(N(LWN[(VXW()*0(),(*0),*/VU d9RLRM)*02UURP[N[NNM 6 HITACHI's Contribution to Node-RED p HITACHI started OSS activities on Node-RED in 2017 p Added features to Node-RED and contributed them to community (over 51,000 lines of code) Lines of codes in Node-RED repository 50,000 40,000 Other 30,000 HITACHI started IBM 20,000 contribution HITACHI 10,000 0 Jan-16 Jan-17 Jan-18 Jan-19 Contributor's Ranking of GitHub: 5 from HITACHI in top 10 Contributions from HITACHI d9RLRM)*02UURP[N[NNM 7 Agenda 1.
  • 264 Tugboat, Volume 37 (2016), No. 3 Typographers' Inn Peter Flynn

    264 Tugboat, Volume 37 (2016), No. 3 Typographers' Inn Peter Flynn

    264 TUGboat, Volume 37 (2016), No. 3 A Typographers’ Inn X LE TEX Peter Flynn Back at the ranch, we have been experimenting with X LE ATEX in our workflow, spurred on by two recent Dashing it off requests to use a specific set of OpenType fonts for A I recently put up a new version of Formatting Infor- some GNU/Linux documentation. X LE TEX offers A mation (http://latex.silmaril.ie), and in the two major improvements on pdfLTEX: the use of section on punctuation I described the difference be- OpenType and TrueType fonts, and the handling of tween hyphens, en rules, em rules, and minus signs. UTF-8 multibyte characters. In particular I explained how to type a spaced Font packages. You can’t easily use the font pack- dash — like that, using ‘dash~---Ђlike’ to put a A ages you use with pdfLTEX because the default font tie before the dash and a normal space afterwards, encoding is EU1 in the fontspec package which is key so that if the dash occurred near a line-break, it to using OTF/TTF fonts, rather than the T1 or OT1 would never end up at the start of a line, only at A conventionally used in pdfLTEX. But late last year the end. I somehow managed to imply that a spaced Herbert Voß kindly posted a list of the OTF/TTF dash was preferable to an unspaced one (probably fonts distributed with TEX Live which have packages because it’s my personal preference, but certainly A of their own for use with X LE TEX [6].
  • Investigating Reason As a Substitute for Javascript

    Investigating Reason As a Substitute for Javascript

    DEGREE PROJECT IN COMPUTER ENGINEERING, FIRST CYCLE, 15 CREDITS STOCKHOLM, SWEDEN 2020 Investigating Reason as a substitute for JavaScript AXEL PETTERSSON KTH ROYAL INSTITUTE OF TECHNOLOGY SCHOOL OF ELECTRICAL ENGINEERING AND COMPUTER SCIENCE Investigation of Reason as a substitute for JavaScript AXEL PETTERSSON Degree Programme in Information and Communication Technology Date: June 4, 2020 Supervisor: Thomas Sjöland Examiner: Johan Montelius School of Electrical Engineering and Computer Science Host company: Slagkryssaren AB Swedish title: Undersökning av Reason som ett substitut till JavaScript Investigation of Reason as a substitute for JavaScript / Undersökning av Reason som ett substitut till JavaScript c 2020 Axel Pettersson Abstract | i Abstract JavaScript has in recent years become one of the most utilized programming languages for developing different kinds of applications. However, even though it has received a lot of praise for its simplicity, versatility and highly active community, it lacks some functionalities and features that a lot of programmers highly value, like static and strict typing, compile-time debugging, and to not be required to make use of third-party libraries to integrate crucial functionality. However, several new languages built on top of JavaScript have been developed to address and resolve these issues developers find with JavaScript without losing the benefits that come with it. One of these super- set languages is Reason, the new syntax and toolchain powered by the OCaml compiler. This thesis aims to address whether there are scenarios where Reason could act as a reasonable substitute of JavaScript by investigating how the languages compare in regards to different criteria. The criteria examined are writability, data structures and typing, reliability and testing, community support, market demand, portability, and performance.
  • Beaulivre Write YOUR BOOKS in a COLORFUL WAY

    Beaulivre Write YOUR BOOKS in a COLORFUL WAY

    ProȷΣLib beaulivre WRiTE YOUR BOOKS iN A COLORFUL WAY Corresponding to: beaulivre 2021/08/11 JINWEN XU August 2021, Beijing This page is intentionally left blank PREFACE beaulivre is a member of the colorist class series. Its name is taken from French words “beau” (for “beautiful”) and “livre” (for “book”). The entire collection includes colorart and lebhart for typesetting articles and colorbook and beaulivre for typesetting books. My original intention in designing this series was to write drafts and notes that look colorful yet not dazzling. beaulivre has multi‑language support, including Chinese (simplified and traditional), English, French, German, Italian, Japanese, Portuguese (European and Brazilian), Russian and Spanish. These languages can be switched seamlessly in a single document. Due to the usage of custom fonts, lebhart requires X LE ATEX or LuaLATEX to compile. This documentation is typeset using beaulivre (with the option allowbf). You can think of it as a short introduction and demonstration. TiP Multi‑language support, theorem‑like environments, draft marks and some other features are pro‑ vided by the ProȷΣLib toolkit. Here we only briefly discuss how to use it with this document class. For more detailed information, you can refer to the documentation of ProȷΣLib. iii This page is intentionally left blank CONTENTS PREFACE. iii I INSTRUCTION BEFORE YOU START . 3 1 Usage and examples . 5 1.1 How to load it . 5 1.2 Example ‑ A complete document . 5 1.2.1 Initialization . 6 1.2.2 Set the language . 6 1.2.3 Draft marks . 6 1.2.4 Theorem‑like environments . 6 2 On the default fonts .
  • Project Evaluation Report

    Project Evaluation Report

    Project Evaluation Report Project Title: SMART-bridge-to-WEB School/Department: Design, Creative and Digital Industries/Computer Science and Engineering Project Team: Wesam Makadicy, Tomasz Wasowski, Marius Ignat, Nasro ABdi Hassan Sharif, Adam Ahmed-Keyte, Alexander Bolotov, GaBriele Pierantoni, David Chan You Fee Abstract An analysis of the SMARTEST website [1] node view was conducted to gather what features should be transferred over to SMART-bridge-to-WEB (SB2W). Then, several prototypes were created from the requirements identified during analysis until a final master prototype was developed. This prototype was used as a reference for the project’s implementation, which can be viewed at [2]. The report is concluded by reflecting on our teamworK, how the project went, and on what we will do next with the project. Introduction This project aims at developing a web-based application which will target an additional functionality to the already developed Knowledge and learning platform SMARTEST [1]. The platform, as it currently stands, enables interactions between students and academics, represents learning content graphically in forms of module structures and learning processes. It has attracted more than 300 registered student users both from University of Westminster (UoW) and various groups of students at our partner university in TashKent – Westminster International University in TashKent (WIUT). This is due to it offering a more interactive interface of building learning content in the form of graphs and learning paths [3], which other existing learning platforms such as BlacKboard [4] does not. However, for many student users and academics, specifically for those not from STEM disciplines, the representation of learning content in the form of graphs may not be ideal as it requires an understanding of the additional graph structure/concept.