background preloader

J Home

J Home
Related:  LanguagesJ

about:jisp Accessing the System Clipboard with JavaScript – A Holy Grail? « Novak in Academia I am developing an API written in JavaScript for a project which requires the ability to copy data to, and retrieve data from, a clipboard within a web browser. A simple/common problem definition – but due to tight browser security, finding a solution is a bit of a nightmare. This article outlines and discusses a number of approaches for implementing a clipboard feature into your JavaScript applications. The Ideal JavaScript Clipboard Interface The concept of the “clipboard” is simple; it is essentially a place for storing and retrieving a single unit/piece of cloned data. The code snippet below describes this clipboard concept in terms of a JavaScript interface. A simple concept, a self explanatory interface. Multiple Clipboards Unfortunately there can be more than one clipboard present. The Web’s Sandbox Environment Web applications run in a sandbox environment to prevent malicious scripts from infecting a visitor’s computer. Internet Explorer’s clipboardData Object Using Java Applets

J History[edit] Use in English[edit] In English, 'j' most commonly represents the affricate /dʒ/. In Old English the phoneme /dʒ/ was represented orthographically as 'cg' or 'cȝ'.[5] Under the influence of Old French, which had a similar phoneme deriving from Latin /j/, English scribes began to use 'i' (later 'j') to represent word-initial /dʒ/ of Old English (for example, 'iest' later 'jest'), while using 'dg' elsewhere (for example, 'hedge').[5] Later many other uses of 'i' (later 'j') were added in loanwords from French and other languages (e.g. 'adjoin', 'junta'). The first English-language book to make a clear distinction between 'i' and 'j' was published in 1633.[6] In loan words such as raj, "J" may be pronounced /ʒ/ by some speakers. In English, 'J' is the fourth-least-frequently used letter in words, being more frequent only than 'Z', 'Q', and 'X'. Use in other languages[edit] The letter J is generally not used in the modern Celtic languages and in Galician, except in loanwords.

Converge This document is intended to give programmers familiar with other programming languages a quick introduction to Converge, essentially pointing out those things that may be different from other languages; it is not intended to be a complete, thorough reference manual. After reading this document you will probably want to read the modules reference manual which documents the standard library, or the guide to compile-time meta-programming which documents Converge's macro-like facilities. Concrete syntax Since the direct interaction with Converge is through its concrete syntax in the form of source code in a text editor, let us establish the general rules for representing Converge code. Converge is syntactically similar to Python. This means it relies on indentation to show code blocks rather than using curly brackets { ... } or begin ... end keywords. Hello world! Let's start with the traditional Hello world! import Sys func main(): Sys::println("Hello world!") Running programs Lexical scoping

Geolocation API Specification Abstract This specification defines an API that provides scripted access to geographical location information associated with the hosting device. Status of This Document This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at This document was published by the Geolocation Working Group as a Last Call Working Draft on @@ May 2014. it merged errata into the Geolocation API v1 Recommendation, which was published on October 24, 2013.This document is intended to become a W3C Recommendation. Publication as a Last Call Working Draft does not imply endorsement by the W3C Membership. Comments on the document should be sent to the Working Group's public mailing list public-geolocation@w3.org (subscribe, archives). Table of Contents 1 Conformance requirements 2 Introduction The

Learning Contents >> << Usr Pri JfC LJ Phr Dic Rel Voc !: Help Learning J J software and documentation are available at the J Software Home Page This book is also available in various formats from here Please send comments and criticisms to the J Forum Copyright © Roger Stokes 2013. This book is meant to help the reader to learn the computer-programming language J. My hope is that the book will be useful to a wide readership. The scope of this book is the core J language defined in the J Dictionary. Hence the book does not cover topics such as graphics, plotting, GUI, and database covered in the J User Guide, nor does it cover the J Application Library . The book is organized as follows. All the examples have been executed with J701. Acknowledgments I am grateful to readers of earlier drafts for encouragement and for valuable criticisms and suggestions.

Laurence Tratt: Parsing: The Solved Problem That Isn't Updated (2014-10-24): If you find this article interesting, you may be interested in the follow-up article on an editor for composed programs. Parsing is the act of taking a stream of characters and deducing if and how they conform to an underlying grammar. For example the sentence Bill hits Ben conforms to the part of the English grammar noun verb noun. Parsing concerns itself with uncovering structure; although this gives a partial indication of the meaning of a sentence, the full meaning is only uncovered by later stages of processing. Parseable, but obviously nonsensical, sentences like Bill evaporates Ben highlight this (the sentence is still noun verb noun, but finding two people who agree on what it means will be a struggle). As humans we naturally parse text all the time, without even thinking about it; indeed, we even have a fairly good ability to parse constructs that we've never seen before. The general consensus, therefore, is that parsing is a solved problem. Tokenization

Cross-Origin Resource Sharing Abstract This document defines a mechanism to enable client-side cross-origin requests. Specifications that enable an API to make cross-origin requests to resources can use the algorithms defined by this specification. If such an API is used on resources, a resource on can opt in using the mechanism described by this specification (e.g., specifying Access-Control-Allow-Origin: as response header), which would allow that resource to be fetched cross-origin from Status of this Document This section describes the status of this document at the time of its publication. This document has been reviewed by W3C Members, by software developers, and by other W3C groups and interested parties, and is endorsed by the Director as a W3C Recommendation. If you wish to make comments regarding this document, please send them to public-webappsec@w3.org (subscribe, archives). Table of Contents 1 Introduction 2 Conformance The

Whatever Happened to APL? Late, great Ken Iverson Whatever Happened to APL?by John C. Dvorak (originally appeared circa 1998) The first language I learned to code should have been FORTRAN. APL, was invented by Ken Iverson from 1957-1960 and means, simply, A Programming Language, although it was originally dubbed Iverson Notation when Iverson developed it at Harvard. APL has a number of interest characteristics in its original form. One other noteworthy feature is the power of computation that can be compressed into a single line of code. Some of the drawbacks to APL were corrected by the newer version of the language simply called “J.” — also developed by Iverson with Roger Hui. Doing a Whatever Happened to APL (or J) is somewhat ludicrous because nothing ever happened to the language. APL was a small player during this change over and pretty much got shoved aside completely, which is probably good for the language. This may change with the introduction of two products. Enter J. [note: Ken Iverson died in 2004]

Paul Chiusano: The problematic culture of "Worse is Better" [ culture tech ] Our industry has been infected by a dangerous meme, and it’s one that hasn’t been given its proper scrutiny. Like many memes that explode in popularity, “Worse is Better” gave a name to an underlying fragment of culture or philosophy that had been incubating for some time. I point to C++ as one of the first instances of what would later become “Worse is Better” culture. There’s nothing inherently wrong with making tradeoffs like C++ did. The signs that “Worse is Better” would become a cultural phenomenon—rather than a properly justified philosophy—were everywhere. Thus when Richard P. Nowadays, the “Worse is Better” meme gets brought up in just about every tech discussion in which criticisms are leveled against any technology in widespread use or suggestions are made of a better way (among other places, on this blog see CSS is unnecessary). As a rule, we should confine ourselves to incremental, evolutionary change. Closing remarks

Traverse the Document Object Model with JavaScript Introduction The Document Object Model (DOM) has been defined in different groups of specifications (DOM Level 1, DOM Level 2, and DOM Level 3) by the World Wide Web Consortium (W3C). The DOM represents an HTML or XML document as a tree composed of a hierarchy of nodes with properties and methods. Using client-side languages such as JavaScript, you can add, modify, delete, and attach events to nodes inside the tree, making it possible to generate interactive, dynamic web pages. Modifying the DOM with client-side scripting (JavaScript) is called DOM scripting. DOM scripting is used in lieu of the generic term Dynamic HTML (DHTML), which has been used in web development to indicate the construction of interactive web pages through HTML, CSS, and JavaScript. In this article, explore the most commonly used methods and attributes in the DOM API. You can download the source code used in this article. Back to top DOM scripting In DOM terminology, a document is represented as the root of the tree.

J Forums The J forum mailing lists give life to the J community. They are the best way to get help, help others, report bugs, and share your interest in J. Newbies ask questions and get helpful, polite answers. Gurus present insights, sample code, problems, and solutions. The programming, beta, source and general forums are core forums. The chat forum is an open discussion group, covering computer languages as long as there is some connection to J: array programming, aspects of other computer languages, historical tidbits, random questions about J, wish lists, etc. The core forums are moderated and posters of inappropriate messages will be directed to chat. Jsoftware will remove any member that, in Jsoftware's sole opinion, sends messages that are abusive or inappropriate to the purpose of the forum. Many people will see your message. In answering questions, remember that teaching fishing is better than giving a fish. Please note that the forum email addresses are the name @ jsoftware.com.

red/red · GitHub JSmooth - Java Executable Wrapper

Related: