IWMBrowser/iwmlib
IWMBrowser/iwmlib
4
0
Fork 0
Code Issues 6 Pull Requests Releases Wiki Activity

Added minimal navigation breadcrumbs to doctests.

Browse Source
This commit is contained in:
Uwe Oestermeier 2023-05-09 13:25:39 +02:00
parent 13e0473328
commit 9501264f08
71 changed files with 5700 additions and 5332 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
css/doctest.css
View File

@ -264,3 +264,23 @@ canvas {
width: 100%;
height: 100%;
}
#ctxmenu {
position: fixed;
background: white;
color: black;
cursor: pointer;
border: 1px lightgray solid;
}
#ctxmenu > a {
display: block;
padding: 0.25rem 1rem;
font-size: 18px;
margin: 0.125rem;
}
#ctxmenu > a:hover {
background: black;
color: white;
}

55
css/index.css
View File

@ -34,7 +34,9 @@ h3 {
background-color: rgba(0, 0, 15, 0.5);
}
a { text-decoration: none; }
a {
text-decoration: none;
}
div.wrapper {
overflow: hidden;
@ -46,28 +48,48 @@ div.wrapper {
/* Color animation from https://www.tjvantoll.com/2012/02/20/css3-color-animations/ */
@-webkit-keyframes color_change {
from { background-color: rgba(0, 0, 0, 0); }
to { background-color: red; }
from {
background-color: rgba(0, 0, 0, 0);
}
to {
background-color: red;
}
}
@-moz-keyframes color_change {
from { background-color: rgba(0, 0, 0, 0); }
to { background-color: red; }
from {
background-color: rgba(0, 0, 0, 0);
}
to {
background-color: red;
}
}
@-ms-keyframes color_change {
from { background-color: rgba(0, 0, 0, 0); }
to { background-color: red; }
from {
background-color: rgba(0, 0, 0, 0);
}
to {
background-color: red;
}
}
@-o-keyframes color_change {
from { background-color: rgba(0, 0, 0, 0); }
to { background-color: red; }
from {
background-color: rgba(0, 0, 0, 0);
}
to {
background-color: red;
}
}
@keyframes color_change {
from { background-color: rgba(0, 0, 0, 0); }
to { background-color: red; }
from {
background-color: rgba(0, 0, 0, 0);
}
to {
background-color: red;
}
}
/*** CSS taken from https://medium.com/@jamesfuthey/simulating-the-creation-of-website-thumbnail-screenshots-using-iframes-7145269891db#.7v7fshos5 ***/
@ -83,7 +105,7 @@ div.wrapper {
}
.thumbnail::after {
content: "";
content: '';
display: block;
position: absolute;
top: 0;
@ -141,16 +163,17 @@ div.title {
.container {
margin: 0;
padding: 0;
margin-top: 32px;
border: 2pt #000;
min-height: 100%;
min-width: 100%;
display: -webkit-flex;
-webkit-align-items: flex-end;
align-items: flex-end;
-webkit-align-items: flex-start;
align-items: flex-start;
-webkit-flex-wrap: wrap;
flex-wrap: wrap;
-webkit-align-content: flex-end;
align-content: flex-end;
-webkit-align-content: flex-start;
align-content: flex-start;
}
/** See https://github.com/electron/electron/issues/4420 */

27
lib/_menu.js Executable file
View File

@ -0,0 +1,27 @@
const mapping = {
'lib.Application': './app.html',
'lib.Capabilities': './capabilities.html',
'lib.Card': './card/index.html',
'lib.Pixi': './pixi/index.html',
'pixi.App': './pixi/app.html'
}
function menu(event) {
let key = event.target.innerText
let html = ''
for (let k of Object.keys(mapping)) {
if (k.startsWith(key)) {
let rest = k.slice(key.length)
let url = mapping[k]
html += `<a href="${url}">${rest}</a>`
}
}
event.preventDefault()
let contextMenu = document.createElement('div')
contextMenu.id = 'ctxmenu'
contextMenu.style = `top:${event.pageY - 10}px;left:${event.pageX - 40}px`
contextMenu.onmouseleave = () => (contextMenu.outerHTML = '')
contextMenu.innerHTML = html
document.body.appendChild(contextMenu)
}

2
lib/app.html
View File

@ -13,7 +13,7 @@
<body onload="Doctest.run()">
<h1>
Application
<a href="index.html">lib.</a>Application
</h1>
<p>
IWM Browser Applications follow a common three phase pattern, shared by many programming environments as diverse as Processing, Arduino, Intern, etc.

65
lib/capabilities.html
View File

@ -1,42 +1,30 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Doctests Capabilities</title>
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../css/doctest.css">
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../css/doctest.css" />
<script src="./3rdparty/highlight/highlight.pack.js"></script>
<script type="text/javascript" src="../dist/iwmlib.js"></script>
</head>
<body onload="Doctest.run(); CapabilitiesTests.testAll()">
<main>
<h1>
Capabilities
</h1>
<p>Browsers differ in many aspects, from touch support, support of CSS and HTML5 standards, to
javascript versions. This page collects some of these differences.
<h3>
User Agent
</h3>
<p id="user_agent">
<h1><a href="index.html">lib.</a>Capabilities</h1>
<p>
Browsers differ in many aspects, from touch support, support of CSS and HTML5 standards, to javascript
versions. This page collects some of these differences.
</p>
<h3>
Device Pixel Ratio
</h3>
<p id="device_pixel_ratio">
</p>
<h3>
Multi Touch Table
</h3>
<p id="multi_touch_table">
</p>
<h3>
Supported Events
</h3>
<p id="supported_events">
</p>
<script class="doctest">
<h3>User Agent</h3>
<p id="user_agent"></p>
<h3>Device Pixel Ratio</h3>
<p id="device_pixel_ratio"></p>
<h3>Multi Touch Table</h3>
<p id="multi_touch_table"></p>
<h3>Supported Events</h3>
<p id="supported_events"></p>
<script class="doctest">
Doctest.expect(Capabilities.supportsMouseEvents(), true)
if (Capabilities.supportsTouchEvents()) {
@ -47,29 +35,22 @@ javascript versions. This page collects some of these differences.
Doctest.expect(Capabilities.supportsPointerEvents(), true)
}
</script>
<h3>
Interactive Alerts
</h3>
<h3>Interactive Alerts</h3>
<p>
Standard alerts are displayed quite differently, on Windows 10, for instance
the browser URL is encluded, and a checkbox that allows to hide the
alert dialogs.
Standard alerts are displayed quite differently, on Windows 10, for instance the browser URL is
encluded, and a checkbox that allows to hide the alert dialogs.
</p>
<button onclick="alert('Ok'); console.log('Alert')">Alert</button>
<button onclick="CapabilitiesTests.testConfirm()">Confirm</button>
<button onclick="CapabilitiesTests.testPrompt()">Prompt</button>
<p id="demo">
Result
</p>
<p id="demo">Result</p>
<hr />
<h2>
References
</h2>
<h2>References</h2>
<ul>
<li><a href="http://caniuse.com">Can I use</a></li>
<li><a href="http://webglreport.com">WebGL Report</a></li>
</ul>
</main>
</body>
</html>

2
lib/card/index.html
View File

@ -15,7 +15,7 @@
<body onload="Doctest.run();">
<h1>
Cards
<a href="../index.html">lib.</a><a href="index.html">card.</a>Cards
</h1>
<p>
Cards implement a central UI metaphor for multiuser applications. They allow users to explore information spaces

53
lib/coordinates.html
View File

@ -1,11 +1,10 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Coordinates Doctest</title>
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../css/doctest.css">
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../css/doctest.css" />
<script src="./3rdparty/highlight/highlight.pack.js"></script>
<script src="../dist/iwmlib.3rdparty.js"></script>
<script src="../dist/iwmlib.js"></script>
@ -34,34 +33,41 @@
</head>
<body onload="Doctest.run()">
<h1>
Coordinates
</h1>
<h1><a href="index.html">lib.</a>Coordinates</h1>
<p>
To position objects in defined spatial relationships presupposes a clear understanding of the involved coordinate systems.
Unfortunately, several systems with several conventions are involved:
To position objects in defined spatial relationships presupposes a clear understanding of the involved
coordinate systems. Unfortunately, several systems with several conventions are involved:
<a href="https://javascript.info/coordinates">DOM &amp; CSS</a>,
<a href="https://www.sarasoueidan.com/blog/svg-coordinate-systems/SVG">SVG</a>,
<a href="https://www.w3schools.com/graphics/canvas_coordinates.asp">Canvas</a>
</p>
<p>
We need a common reference system to switch between these coordinate systems. As the uttermost context, the browser page
coordinate system is the most natural one. A simple API was long missing but has now been established in most modern
browsers with
<a href="https://developer.mozilla.org/en-US/docs/Web/API/Window/convertPointFromNoteToPage">window.convertPointFromNoteToPage</a> and the inverse
<a href="https://developer.mozilla.org/en-US/docs/Web/API/Window/convertPointFromPageToNode">window.convertPointFromPageToNode</a>.
Although MDN Web Docs warns about their Non-standard nature the methods work in browsers targeted
by the IWM Browser project. This doctest assures that this assumption can be tested.
We need a common reference system to switch between these coordinate systems. As the uttermost context, the
browser page coordinate system is the most natural one. A simple API was long missing but has now been
established in most modern browsers with
<a href="https://developer.mozilla.org/en-US/docs/Web/API/Window/convertPointFromNoteToPage"
>window.convertPointFromNoteToPage</a
>
and the inverse
<a href="https://developer.mozilla.org/en-US/docs/Web/API/Window/convertPointFromPageToNode"
>window.convertPointFromPageToNode</a
>. Although MDN Web Docs warns about their Non-standard nature the methods work in browsers targeted by the
IWM Browser project. This doctest assures that this assumption can be tested.
</p>
<p>Let's look at a scatter object with a rotatable local coordinate system. We try to follow a point in this local coordinate
system by showing a marker outside the scatter that follows the point.
<p>
Let's look at a scatter object with a rotatable local coordinate system. We try to follow a point in this
local coordinate system by showing a marker outside the scatter that follows the point.
</p>
<div id="main" class="grayBorder interactive" style="position: relative; width: 100%; height: 280px;">
<div id="main" class="grayBorder interactive" style="position: relative; width: 100%; height: 280px">
<!-- Note that we need to set draggable to false to avoid conflicts. The DOM elements
must also be positioned absolutely. -->
<img id="women" draggable="false" style="position: absolute;" src="examples/women.jpeg" />
<img id="women" draggable="false" style="position: absolute" src="examples/women.jpeg" />
<canvas id="canvas" height="280" style="z-index: 100000; pointer-events: none; position: absolute; border: 1px solid red;">
<canvas
id="canvas"
height="280"
style="z-index: 100000; pointer-events: none; position: absolute; border: 1px solid red"
>
Canvas not supported.
</canvas>
</div>
@ -102,9 +108,8 @@
context.beginPath()
context.arc(canvasPoint.x, canvasPoint.y, 12, 0, Math.PI * 2)
context.stroke()
}
animate(followPoint)
</script>
</body>
</html>

2
lib/doctest.html
View File

@ -12,7 +12,7 @@
<body onload="Doctest.run()">
<main>
<h1>
Doctests
<a href="index.html">lib.</a>Doctests
</h1>
<p>
Doctests are explanatory descriptions of programs with executable code examples.

47
lib/electron.html
View File

@ -1,47 +1,48 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Electron Node.js Test</title>
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../css/doctest.css">
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../css/doctest.css" />
<script src="./3rdparty/highlight/highlight.pack.js"></script>
<script src="./3rdparty/all.js"></script>
<script src="../dist/iwmlib.js"></script>
</head>
<body onload="Doctest.run()">
<main>
<h1>
Electron Node.js Test
</h1>
<h1>Electron Node.js Test</h1>
<p>
This doctest is expected to work only within the IWMBrowser. IWMBrowser windows
are opened with a preload.js which is evaluated before the HTML is loaded.
According to
<a href="https://electron.atom.io/docs/faq/">"I can not use jQuery/RequireJS/Meteor/AngularJS in Electron"</a> we
have to rename the symbols in the page before other libraries are included.
In order to access node.js modules we can use `nodeRequire` instead.
This doctest is expected to work only within the IWMBrowser. IWMBrowser windows are opened with a
preload.js which is evaluated before the HTML is loaded. According to
<a href="https://electron.atom.io/docs/faq/"
>"I can not use jQuery/RequireJS/Meteor/AngularJS in Electron"</a
>
we have to rename the symbols in the page before other libraries are included. In order to access
node.js modules we can use `nodeRequire` instead.
</p>
<p>As a simple test we try to load a file from the filesystem:</p>
<script class="doctest">
if (typeof(nodeRequire) != 'undefined') {
if (typeof nodeRequire != 'undefined') {
let fs = nodeRequire('fs')
let content = fs.readFileSync('./index.html')
let lines = content.toString().split(/\n/)
console.log("First line", lines[0] )
console.log('First line', lines[0])
Doctest.expect(lines[0], '<html>')
}
</script>
<p>As simple as this test is, it shows that within the IWMBrowser one import all node.js
modules. Don't forget to test for nodeRequire to avoid runtime errors in other browsers.
<p>
As simple as this test is, it shows that within the IWMBrowser one import all node.js modules. Don't
forget to test for nodeRequire to avoid runtime errors in other browsers.
</p>
<h2>
References
</h2>
<h2>References</h2>
<ul>
<li><a href="https://electron.atom.io/docs/faq/">I can not use jQuery/RequireJS/Meteor/AngularJS in Electron</a></li>
<li>
<a href="https://electron.atom.io/docs/faq/"
>I can not use jQuery/RequireJS/Meteor/AngularJS in Electron</a
>
</li>
</ul>
</main>
</body>
</html>

66
lib/events.html
View File

@ -1,25 +1,24 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../css/doctest.css">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../css/doctest.css" />
<script src="./3rdparty/highlight/highlight.pack.js"></script>
<script src="../dist/iwmlib.3rdparty.js"></script>
<script src="../dist/iwmlib.js"></script>
</head>
<body onload="Doctest.run()">
<h1>
Events
</h1>
<h1><a href="index.html">lib.</a>Events</h1>
<p>
For functional tests it can be useful to simulate event or record and playback events.
This module provides basic support for extracting data from events and serializing
events into a JSON format that allows to save and load sequences of events.
For functional tests it can be useful to simulate event or record and playback events. This module provides
basic support for extracting data from events and serializing events into a JSON format that allows to save
and load sequences of events.
</p>
<p>
Let's look at an example of a HTML structure with click handlers. The click
handler actions log messages that can be tested.</p>
Let's look at an example of a HTML structure with click handlers. The click handler actions log messages
that can be tested.
</p>
<pre><code class="html">
&lt;div&gt;
&lt;img id="women" src="examples/women.jpeg"
@ -31,27 +30,34 @@ handler actions log messages that can be tested.</p>
&lt;/vide&gt;
&lt;/div&gt;
</code></pre>
<div id="example" class="interactive"
style="position:relative; width: 100%; border: 1px solid lightgray">
<img style="margin:8px" id="women" src="examples/women.jpeg"
onclick="record(event); Doctest.log('Lady clicked')"/>
<video id="movie" style="margin:8px" width="250" data-zoomcap="Kugellaufuhr"
<div id="example" class="interactive" style="position: relative; width: 100%; border: 1px solid lightgray">
<img
style="margin: 8px"
id="women"
src="examples/women.jpeg"
onclick="record(event); Doctest.log('Lady clicked')"
/>
<video
id="movie"
style="margin: 8px"
width="250"
data-zoomcap="Kugellaufuhr"
onclick="record(event); Doctest.log('Movie clicked')"
onmousedown="record(event)"
onmouseup="record(event)"
controls>
<source src="examples/movie.mp4" type="video/mp4">
controls
>
<source src="examples/movie.mp4" type="video/mp4" />
</video>
</div>
<button onclick="eventRecorder.stopRecording(); eventRecorder.startReplay()">Replay</button>
<script class="doctest">
var eventRecorder = new EventRecorder()
function record(event) {
let target = event.target
target.style.boxShadow = "0px 5px 10px gray"
setTimeout(() => target.style.boxShadow = "", 1000)
target.style.boxShadow = '0px 5px 10px gray'
setTimeout(() => (target.style.boxShadow = ''), 1000)
eventRecorder.record(event)
}
@ -61,16 +67,16 @@ handler actions log messages that can be tested.</p>
Events.simulateEvent('click', MouseEvent, { targetSelector: womenSel })
Events.simulateEvent('click', MouseEvent, { targetSelector: movieSel })
Doctest.expectLog('Lady clicked',
'Movie clicked')
Doctest.expectLog('Lady clicked', 'Movie clicked')
</script>
<h2>
References
</h2>
<h2>References</h2>
<ul>
<li><a href="https://gist.github.com/iahu/aafc2492d83d70e42c98">Safari Touch Emulator</a></li>
<li><a href="https://www.reddit.com/r/javascript/comments/2laqaf/how_to_trigger_a_touch_event/">How to Trigger Touch Events</a></li>
<li>
<a href="https://www.reddit.com/r/javascript/comments/2laqaf/how_to_trigger_a_touch_event/"
>How to Trigger Touch Events</a
>
</li>
</ul>
</body>
</html>

55
lib/flippable.html
View File

@ -1,23 +1,28 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Flippable Doctest</title>
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../css/doctest.css">
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../css/doctest.css" />
<script src="./3rdparty/highlight/highlight.pack.js"></script>
<script src="../dist/iwmlib.3rdparty.js"></script>
<script src="../dist/iwmlib.js"></script>
<link rel="stylesheet" href="../css/flipeffect.css">
<link rel="stylesheet" href="../css/flipeffect.css" />
<template id="flipTemplate">
<div class="flipWrapper">
<div class="flipCard">
<div class="flipFace front"></div>
<div class="flipFace back" style="visibility:hidden;"></div>
<div class="flipFace back" style="visibility: hidden"></div>
</div>
<!-- Very tricky problem to scale svgs: see https://css-tricks.com/scale-svg/ -->
<svg class="flipButton backBtn" style="visibility:hidden;" viewBox="0 0 100 100" preserveAspectRatio="xMidYMid meet">
<svg
class="flipButton backBtn"
style="visibility: hidden"
viewBox="0 0 100 100"
preserveAspectRatio="xMidYMid meet"
>
<g stroke-width="8" stroke="white">
<circle cx="50" cy="50" r="44" fill="gray" />
<line x1="30" y1="30" x2="70" y2="70" />
@ -32,19 +37,14 @@
</svg>
</div>
</template>
</head>
<body onload="Doctest.run()">
<h1>
Flippable
</h1>
<h1><a href="index.html">lib.</a>Flippable</h1>
<p>
The flip effect simulates a flip between a front and back view of an object
by means of a 3D rotation. The DOMFlippable class implements this effect for two
DOM nodes, one as the front view, the other as the back view. Both views are connected
via a HTML template that defines the placeholders for front and back views. The
style file "css/flipeffect.css" holds reasonable default styles for this kind of
templates.
The flip effect simulates a flip between a front and back view of an object by means of a 3D rotation. The
DOMFlippable class implements this effect for two DOM nodes, one as the front view, the other as the back
view. Both views are connected via a HTML template that defines the placeholders for front and back views.
The style file "css/flipeffect.css" holds reasonable default styles for this kind of templates.
</p>
<pre><code>
&lt;template id="flipTemplate"&gt;
@ -59,27 +59,24 @@ templates.
&lt;/template&gt;
</code>
</pre>
<h3>
Example
</h3>
<main id="main" style="border: 1px solid gray; position: relative; height: 256px;" >
</main>
<h3>Example</h3>
<main id="main" style="border: 1px solid gray; position: relative; height: 256px"></main>
<script class="doctest">
let scatterContainer = new DOMScatterContainer(main, { stopEvents: false })
if (Capabilities.supportsTemplate()) {
let flip = new DOMFlip(scatterContainer,
let flip = new DOMFlip(
scatterContainer,
flipTemplate,
new ImageLoader('./examples/king.jpeg'),
new ImageLoader('./examples/women.jpeg'),
{ tapDelegateFactory: CardWrapper, preloadBack: true})
{ tapDelegateFactory: CardWrapper, preloadBack: true }
)
flip.load().then((flip) => {
flip.centerAt({ x: 150, y: 120 })
})
}
else {
alert("Templates not supported, use Edge, Chrome, Safari or Firefox.")
} else {
alert('Templates not supported, use Edge, Chrome, Safari or Firefox.')
}
</script>
</body>
</html>

91
lib/frames.html
View File

@ -1,49 +1,50 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="viewport" content="width=device-width, user-scalable=no" />
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../css/doctest.css">
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../css/doctest.css" />
<script src="./3rdparty/highlight/highlight.pack.js"></script>
<script src="../dist/iwmlib.3rdparty.js"></script>
<script src="../dist/iwmlib.js"></script>
</head>
<body onload="Doctest.run()">
<h1>
Frames
</h1>
<h1><a href="index.html">lib.</a>Frames</h1>
<p>
Frames are a major way to modularize the design of complex applications. Since
pages presented in frames are independent of each other they can fail without
impact on other pages. In addition preparing content in individual HTML files
largely simplfies the workflow of content production.
Frames are a major way to modularize the design of complex applications. Since pages presented in frames are
independent of each other they can fail without impact on other pages. In addition preparing content in
individual HTML files largely simplfies the workflow of content production.
</p>
<p>This approach, however, has limitations:</p>
<script>
function appleError() {
alert("Refused to display 'http://www.apple.com/de/' in a frame because it set 'X-Frame-Options' to 'SAMEORIGIN'.")
alert(
"Refused to display 'http://www.apple.com/de/' in a frame because it set 'X-Frame-Options' to 'SAMEORIGIN'."
)
}
</script>
<ul><li>Some pages may prevent embedding them
by 'X-Frame-Options', e.g. <a href="javascript:appleError()">www.apple.com</a>
<ul>
<li>
Some pages may prevent embedding them by 'X-Frame-Options', e.g.
<a href="javascript:appleError()">www.apple.com</a>
</li>
<li>Sites with responsive design might not be able to detect the available space,
e.g. <a href="https:///de.wikipedia.org">de.wikipedia.org</a>
<li>
Sites with responsive design might not be able to detect the available space, e.g.
<a href="https:///de.wikipedia.org">de.wikipedia.org</a>
</li>
<li>Touch events are not dispatched correctly to multiple frames on platforms with
<b>TouchEvents</b>, e.g. if frame one
receives touch1, all related touch points touch2, ... touchN, are send to frame1
although they might occur over frame two.
<li>
Touch events are not dispatched correctly to multiple frames on platforms with <b>TouchEvents</b>, e.g.
if frame one receives touch1, all related touch points touch2, ... touchN, are send to frame1 although
they might occur over frame two.
</li>
</ul>
<p>To solve the last mentioned problem, we prevent frames form touch events by
assigning a <pre>pointer-events: none;</pre> style. A wrapping div is used to capture
the events instead. Captured events are collected by an InteractionMapper and
distributed as synthesized mouse or touch events to the wrapped iframes.
<p>
Let's look at an example of two HTML IFrames embedded in this Doctest.</p>
<p>To solve the last mentioned problem, we prevent frames form touch events by assigning a</p>
<pre>pointer-events: none;</pre>
style. A wrapping div is used to capture the events instead. Captured events are collected by an
InteractionMapper and distributed as synthesized mouse or touch events to the wrapped iframes.
<p>Let's look at an example of two HTML IFrames embedded in this Doctest.</p>
<pre><code class="html">
&lt;div id="frameWrapper1"&gt;
&lt;iframe style="pointer-events: none;" src="examples/multitouch.html"&gt;&lt;/iframe&gt;
@ -53,29 +54,41 @@ Let's look at an example of two HTML IFrames embedded in this Doctest.</p>
&lt;/div&gt;
</code></pre>
<div class="grayBorder" id="container" style="display: flex; justify-content: space-around;">
<div class="grayBorder" id="container" style="display: flex; justify-content: space-around">
<div id="frameWrapper1" style="padding: 4px">
<iframe style="width:400px; height:360px; border:0; pointer-events: none;" src="examples/multitouch.html" allowfullscreen></iframe>
<iframe
style="width: 400px; height: 360px; border: 0; pointer-events: none"
src="examples/multitouch.html"
allowfullscreen
></iframe>
</div>
<div id="frameWrapper2" style="padding: 4px">
<iframe style="width:400px; height:360px; border:0; pointer-events: none;" src="examples/multitouch.html" allowfullscreen></iframe>
<iframe
style="width: 400px; height: 360px; border: 0; pointer-events: none"
src="examples/multitouch.html"
allowfullscreen
></iframe>
</div>
</div>
<p>The distribution of events is handled by the enclosing container. The container
registers a InteractionMapper and provides adapter for iframes, that implement
IInteractionTarget by sending programmatically generated events. If you test
these frames on a multitouch device you will notice that the scatters within
the frames can be manipulated independently of each other:
<p>
The distribution of events is handled by the enclosing container. The container registers a
InteractionMapper and provides adapter for iframes, that implement IInteractionTarget by sending
programmatically generated events. If you test these frames on a multitouch device you will notice that the
scatters within the frames can be manipulated independently of each other:
</p>
<p />
<script class="doctest">
let frameContainer = new FrameContainer(container)
</script>
<h2>
References
</h2>
<h2>References</h2>
<ul>
<li><a href="http://stackoverflow.com/questions/8068578/how-do-i-use-multiple-iframes-in-my-html-page">Multiple iFrames</a></li>
<li>
<a href="http://stackoverflow.com/questions/8068578/how-do-i-use-multiple-iframes-in-my-html-page"
>Multiple iFrames</a
>
</li>
<li><a href="https://benmarshall.me/responsive-iframes/">Responsive iFrames</a></li>
</ul>
</body>
</html>

30
lib/imageloader.html
View File

@ -1,22 +1,20 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../css/doctest.css">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../css/doctest.css" />
<script src="./3rdparty/highlight/highlight.pack.js"></script>
<script src="./3rdparty/all.js"></script>
<script src="../dist/iwmlib.js"></script>
</head>
<body onload="Doctest.run()">
<h1>Image Loader Worker</h1>
<h1><a href="index.html">lib.</a>Image Loader Worker</h1>
<p>
The loading of multiple small images (e.g. loadimng tiles of a zoomable
map) is a time consuming task that leads to small but noticeable delays
in touch interaction if standard DOM events are used. With a worker we
The loading of multiple small images (e.g. loadimng tiles of a zoomable map) is a time consuming task that
leads to small but noticeable delays in touch interaction if standard DOM events are used. With a worker we
can try to do most of the time consuming processing in the background.
</p>
<p>Let's look at an example of a image loader worker:</p>
@ -25,7 +23,6 @@
<img id="img3" width="160" height="120" class="grayBorder interactive" src="" />
<img id="img4" width="160" height="120" class="grayBorder interactive" src="" />
<script class="doctest">
let urls = [
'http://i.imgur.com/JmvCQXd.jpg',
'http://i.imgur.com/L4ipvCE.jpg',
@ -35,18 +32,19 @@
let imgs = [img1, img2, img3, img4]
let count = 0
let worker = new Worker("imageloader.js")
let worker = new Worker('imageloader.js')
worker.onmessage = (event) => {
console.log("Loaded", event.data)
console.log('Loaded', event.data)
if (event.data.success) {
console.log("Loaded", event.data.url)
console.log('Loaded', event.data.url)
imgs[count].src = event.data.url
count += 1
}
}
worker.postMessage({command: "load", urls: urls})
worker.postMessage({command: "abort", urls: urls})
worker.postMessage({command: "load", urls: urls})
worker.postMessage({ command: 'load', urls: urls })
worker.postMessage({ command: 'abort', urls: urls })
worker.postMessage({ command: 'load', urls: urls })
</script>
</body>
</html>

15
lib/index.html
View File

@ -1,11 +1,14 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<title>Lib Doctests</title>
<meta charset="utf-8" />
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent" />
<meta name="viewport" content="width=device-width, height=device-height, initial-scale=1.0, user-scalable=0, minimum-scale=1.0, maximum-scale=1.0" />
<link rel="stylesheet" href="../css/index.css">
<meta
name="viewport"
content="width=device-width, height=device-height, initial-scale=1.0, user-scalable=0, minimum-scale=1.0, maximum-scale=1.0"
/>
<link rel="stylesheet" href="../css/index.css" />
<!-- following not necc for index.js included in iwmlib.js -->
<!-- <script src="./index.js"></script> -->
@ -17,7 +20,7 @@
<div class="preview">
<div class="thumbnail-container">
<div class="thumbnail">
<img class="icon" src="thumbnails/notfound.png">
<img class="icon" src="thumbnails/notfound.png" />
<!-- <iframe src="" frameborder="0"></iframe> -->
</div>
</div>
@ -28,7 +31,9 @@
</head>
<body>
<div id="container" class="container">
<a style="position: absolute; left: 22px; top: 12px;" target="_blank" href="http://www.iwm-tuebingen.de">IWM</a>
<a style="position: absolute; left: 22px; top: 12px" target="_blank" href="http://www.iwm-tuebingen.de"
>IWMLib Doctest</a
>
</div>
<script>
let index = new Index(itemTemplate, [

43
lib/inspect.html
View File

@ -1,36 +1,41 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../css/doctest.css">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../css/doctest.css" />
<script src="./3rdparty/highlight/highlight.pack.js"></script>
<script src="../dist/iwmlib.js"></script>
</head>
<body onload="Doctest.run(); test()">
<h1>
Code and Class Inspection
</h1>
<h1><a href="index.html">lib.</a>Code and Class Inspection</h1>
<p>
To Do: Use SystemJS to load modules and main code. This ensures that
all code can be parsed by acorn into an Abstract Syntax Tree which
in turn allows to extract class statements and related extends phrases.
To Do: Use SystemJS to load modules and main code. This ensures that all code can be parsed by acorn into an
Abstract Syntax Tree which in turn allows to extract class statements and related extends phrases.
</p>
<script class="doctest">
function test() {
let sources = Inspect.allScriptSources()
console.log(sources)
}
</script>
<h2>
References
</h2>
<h2>References</h2>
<ul>
<li><a href="https://nystudio107.com/blog/using-systemjs-as-javascript-loader">Using SystemJS as JavaScript Loader</a></li>
<li><a href="http://stackoverflow.com/questions/2051678/getting-all-variables-in-scope">Getting all Variables in Scope</a></li>
<li><a href="https://www.keithcirkel.co.uk/metaprogramming-in-es6-symbols/">Metaprogramming in JavaScript</a></li>
<li>
<a href="https://nystudio107.com/blog/using-systemjs-as-javascript-loader"
>Using SystemJS as JavaScript Loader</a
>
</li>
<li>
<a href="http://stackoverflow.com/questions/2051678/getting-all-variables-in-scope"
>Getting all Variables in Scope</a
>
</li>
<li>
<a href="https://www.keithcirkel.co.uk/metaprogramming-in-es6-symbols/"
>Metaprogramming in JavaScript</a
>
</li>
</ul>
</body>
</html>

456
lib/interaction.html
View File

@ -1,10 +1,10 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Interaction Mapper Doctest</title>
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../css/doctest.css">
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../css/doctest.css" />
<script src="./3rdparty/highlight/highlight.pack.js"></script>
<script src="../dist/iwmlib.js"></script>
<script src="../dist/iwmlib.3rdparty.js"></script>
@ -14,65 +14,60 @@
</script>
</head>
<body onload="Doctest.run()">
<h1>
Interaction Pattern
</h1>
<h1><a href="index.html">lib.</a>Interaction</h1>
<p>
Since the correct handling of the divergent browser specific multitouch
implementations is a difficult and recurring task we decided to encapsulate
all related handlers for <code>TouchEvent</code> (WebKit, Mozilla) and
<code>PointerEvent</code> (IE, Edge, Chrome) in
a single delegate pattern.
Since the correct handling of the divergent browser specific multitouch implementations is a difficult and
recurring task we decided to encapsulate all related handlers for <code>TouchEvent</code> (WebKit, Mozilla)
and <code>PointerEvent</code> (IE, Edge, Chrome) in a single delegate pattern.
</p>
<p>The main differences are that <code>PointerEvent</code> are fired for each
touch point, whereas the <code>TouchEvent</code> collects multiple
<code>TouchPoints</code> into a single event. The basic PointMap and Interaction
classes unify this behavior by collecting all contact points regardless
of their original mouse, touch, or pointer events.</p>
<h2>
Point Maps
</h2>
<p>The touch and pointer positions are collected in PointMaps which provide
access to the positions via stringified touch and pointer ids. For mouse events the
special id "mouse" is used. PointMaps can be cloned and pretty printed. In addition
they provide auxiliary methods like <code>mean</code> and <code>farthests</code>
<p>
The main differences are that <code>PointerEvent</code> are fired for each touch point, whereas the
<code>TouchEvent</code> collects multiple <code>TouchPoints</code> into a single event. The basic PointMap
and Interaction classes unify this behavior by collecting all contact points regardless of their original
mouse, touch, or pointer events.
</p>
<h2>Point Maps</h2>
<p>
The touch and pointer positions are collected in PointMaps which provide access to the positions via
stringified touch and pointer ids. For mouse events the special id "mouse" is used. PointMaps can be cloned
and pretty printed. In addition they provide auxiliary methods like <code>mean</code> and
<code>farthests</code>
which can be used to simplify the computation of gestures. In general
<code>mean</code> can be used to compute the "center of interaction", i.e. the
best guess of the anchor point for rotation and scaling operations.
<code>mean</code> can be used to compute the "center of interaction", i.e. the best guess of the anchor
point for rotation and scaling operations.
</p>
<script class="doctest">
let mouse = new PointMap({ mouse: { x: 0, y: 0 } })
let touches = new PointMap({ "touch1": {x:0, y:0}, "touch2": {x: 10, y: 10}})
let touches = new PointMap({ touch1: { x: 0, y: 0 }, touch2: { x: 10, y: 10 } })
Doctest.expect(touches,
"[PointMap touch1:{x:0, y:0}, touch2:{x:10, y:10}]")
Doctest.expect(touches.clone(),
"[PointMap touch1:{x:0, y:0}, touch2:{x:10, y:10}]")
Doctest.expect(touches.mean(), {"x":5,"y":5})
Doctest.expect(touches, '[PointMap touch1:{x:0, y:0}, touch2:{x:10, y:10}]')
Doctest.expect(touches.clone(), '[PointMap touch1:{x:0, y:0}, touch2:{x:10, y:10}]')
Doctest.expect(touches.mean(), { x: 5, y: 5 })
</script>
<p>If more than two touch points are involved it may be best to look for the
pair of points which are farthest away from each other. These points will
represent the fingers farthest away from each other, a more simple substitute
for 3, 4 or 5 touch points. Here we add a third point to our example touches
and test whether the maximal distant points are found:
<p>
If more than two touch points are involved it may be best to look for the pair of points which are farthest
away from each other. These points will represent the fingers farthest away from each other, a more simple
substitute for 3, 4 or 5 touch points. Here we add a third point to our example touches and test whether the
maximal distant points are found:
<script class="doctest">
touches.set("touch3", {x:5, y:5})
Doctest.expect(touches.farthests(), [{"x":0,"y":0},{"x":10,"y":10}])
touches.set('touch3', { x: 5, y: 5 })
Doctest.expect(touches.farthests(), [
{ x: 0, y: 0 },
{ x: 10, y: 10 }
])
</script>
<h2>
Interaction Points and Interactions
</h2>
Events and points change in time and gestures are computed from this dynamic behavior.
To collect theses changes and to simplify the computation of gestures we
collect PointMaps in a composite class InteractionPoints, which distinguishes
start, current, previous, and ended point coordinates as well as the start timestamps.
<script class="doctest">
</p>
<h2>Interaction Points and Interactions</h2>
Events and points change in time and gestures are computed from this dynamic behavior. To collect theses changes
and to simplify the computation of gestures we collect PointMaps in a composite class InteractionPoints, which
distinguishes start, current, previous, and ended point coordinates as well as the start timestamps.
<script class="doctest">
let interactionPoints = new InteractionPoints()
interactionPoints.update("touch1", {x:0, y:0})
interactionPoints.update("touch2", {x:5, y:5})
interactionPoints.update("touch3", {x:10, y:10})
interactionPoints.update('touch1', { x: 0, y: 0 })
interactionPoints.update('touch2', { x: 5, y: 5 })
interactionPoints.update('touch3', { x: 10, y: 10 })
Doctest.expect(interactionPoints.current.size, 3)
// Initially current and previous points are equal
@ -82,11 +77,13 @@ Doctest.expect(interactionPoints.current, interactionPoints.previous)
interactionPoints.updatePrevious()
// After this call current and previous can be used to compure the deltas:
interactionPoints.update("touch1", {x: -2, y: -5})
interactionPoints.update("touch2", {x: 5, y: 9})
interactionPoints.update("touch3", {x: 15, y: 20})
Doctest.expect(interactionPoints.current,
"[PointMap touch1:{x:-2, y:-5}, touch2:{x:5, y:9}, touch3:{x:15, y:20}]")
interactionPoints.update('touch1', { x: -2, y: -5 })
interactionPoints.update('touch2', { x: 5, y: 9 })
interactionPoints.update('touch3', { x: 15, y: 20 })
Doctest.expect(
interactionPoints.current,
'[PointMap touch1:{x:-2, y:-5}, touch2:{x:5, y:9}, touch3:{x:15, y:20}]'
)
// "[PointMap touch1:{x:-2, y:-5}, touch2:{x:5, y:7}, touch3:{x:15, y:20}]")
// The delta object is a convenience object to access translation, scaling,
@ -98,33 +95,30 @@ let delta = interactionPoints.delta()
// Doctest.expect(delta.zoom > 1.5, true) // Doctest ERROR! Occurs for an unspecified period of time.
// Doctest.expect(delta.rotate < 0.2, true) // Doctest ERROR! Occurs for an unspecified period of time.
// Doctest.expect(delta.about, {x: 6.5, y: 7.5}) // Doctest ERROR! Occurs for an unspecified period of time.
</script>
<p>Interaction objects extend the idea of mapping touch ids to
points to multiple target objects. Each touch id is mapped not only to the
changing points of this touch but also to the object that has been
hit by the starting touch point. This object is the target of the interaction
and remains for the whole duration of the multitouch gesture.
<p>
Interaction objects extend the idea of mapping touch ids to points to multiple target objects. Each touch id
is mapped not only to the changing points of this touch but also to the object that has been hit by the
starting touch point. This object is the target of the interaction and remains for the whole duration of the
multitouch gesture.
</p>
<h2>
Interaction Delegate
</h2>
<p>The delegator registers all needed <code>TouchEvent</code>,
<code>PointerEvent</code>, and <code>MouseEvent</code>
handlers on a provided DOM elememt for a given target object, ensures that the
events are captured by the target and boils the event handling down to simple
<h2>Interaction Delegate</h2>
<p>
The delegator registers all needed <code>TouchEvent</code>, <code>PointerEvent</code>, and
<code>MouseEvent</code>
handlers on a provided DOM elememt for a given target object, ensures that the events are captured by the
target and boils the event handling down to simple
<code>onStart</code>, <code>onMove</code>, <code>onEnd</code> events.
</p>
<p>Let's look at an example of an InteractionDelegate and a target object that
implements the <code>IInteractionTarget</code> interface. Typically you setup
the delegator in the constructor of the class that uses the interation.
<p>
Let's look at an example of an InteractionDelegate and a target object that implements the
<code>IInteractionTarget</code> interface. Typically you setup the delegator in the constructor of the class
that uses the interation.
</p>
<script class="doctest">
class InteractionTarget {
// The constructor of the target creates the InteractionDelegate
constructor(domElement) {
this.interaction = new InteractionDelegate(domElement, this)
@ -133,7 +127,9 @@ class InteractionTarget {
// The following methods are needed by the IInteractionTarget interface
// Indicates that we want all events
capture(event) { return true }
capture(event) {
return true
}
// Handle collected touch points on start
onStart(event, points) {}
@ -147,20 +143,18 @@ class InteractionTarget {
// Handle mouse wheel event
onMouseWheel(event) {}
}
</script>
<p>We can now check whether the promised interface methods are implemented by the
class:</p>
<p>We can now check whether the promised interface methods are implemented by the class:</p>
<script class="doctest">
Doctest.expect(IInteractionTarget.implementedBy(InteractionTarget), true)
</script>
<p>If we define an InteractionTarget that violates the IInteractionTarget interface
we get an error. The following example of an interaction target uses an
InteractionDelegate but does not implement the necessary methods:
<p>
If we define an InteractionTarget that violates the IInteractionTarget interface we get an error. The
following example of an interaction target uses an InteractionDelegate but does not implement the necessary
methods:
</p>
<script class="doctest">
class InvalidInteractionTarget {
constructor(domElement) {
this.interaction = new InteractionDelegate(domElement, this, { debug: true })
}
@ -169,42 +163,33 @@ InteractionDelegate but does not implement the necessary methods:
try {
new InvalidInteractionTarget(null)
} catch (error) {
Doctest.expectError(error, "Expected IInteractionTarget")
Doctest.expectError(error, 'Expected IInteractionTarget')
}
</script>
<h2>
Interaction Mapper
</h2>
<p>Often we need to assign UI elements to touch and pointer events. This is
supported by a special InteractionMapper delegate. A InteractionMapper
maps events to specific parts of a container interaction target. The
InteractionTarget must implement a findTarget method that returns an
object implementing the IInteractionTarget interface.
<h2>Interaction Mapper</h2>
<p>
Often we need to assign UI elements to touch and pointer events. This is supported by a special
InteractionMapper delegate. A InteractionMapper maps events to specific parts of a container interaction
target. The InteractionTarget must implement a findTarget method that returns an object implementing the
IInteractionTarget interface.
</p>
<p>
If the InteractionTarget also implements a <code>mapPositionToPoint</code> method this
is used to map the points to the local coordinate space of the the target.
This makes it easier to lookup elements and relate events to local
positions.
</p>
<p>Let's see an example. A graph that uses an <code>InterationMapper</code> for it´s child
objects:
If the InteractionTarget also implements a <code>mapPositionToPoint</code> method this is used to map the
points to the local coordinate space of the the target. This makes it easier to lookup elements and relate
events to local positions.
</p>
<p>Let's see an example. A graph that uses an <code>InterationMapper</code> for it´s child objects:</p>
<script class="doctest">
class Graph {
constructor(domElement) {
this.interaction = new InteractionMapper(domElement, this)
this.nodes = [
new Node('a'),
new Node('b')
]
this.nodes = [new Node('a'), new Node('b')]
}
capture(event) { return true }
capture(event) {
return true
}
findTarget() {
for (let node of this.nodes) {
@ -215,55 +200,61 @@ objects:
}
class Node {
constructor(name) {
this.name = name
}
capture(event) { return true }
capture(event) {
return true
}
onStart(event, interaction) {
Doctest.log("onStart called")
Doctest.log('onStart called')
}
onMove(event, interaction) {
Doctest.log("onMove called")
Doctest.log('onMove called')
}
onEnd(event, interaction) {
Doctest.log("onEnd called")
Doctest.log('onEnd called')
}
}
</script>
<p>Now we simulate a sequence of <code>onStart, onMove, onEnd</code> events by calling
the registered event handlers programmatically. Note that the defined
event handlers log their calls.</p>
<p>
Now we simulate a sequence of <code>onStart, onMove, onEnd</code> events by calling the registered event
handlers programmatically. Note that the defined event handlers log their calls.
</p>
<script class="doctest">
let graph = new Graph(window)
window.dispatchEvent(Doctest.event('mousedown'))
window.dispatchEvent(Doctest.event('mousemove'))
window.dispatchEvent(Doctest.event('mouseup'))
Doctest.expectLog('onStart called',
'onMove called',
'onEnd called')
Doctest.expectLog('onStart called', 'onMove called', 'onEnd called')
</script>
<h2>
Simple Dragging
</h2>
<p>Drag & Drop is a common interaction pattern. This behavior can be accomplished
by a class that implements IInteractionMapperTarget as well as IInteractionTarget.
You can grab the blue circle with touches or mouse and drag it around.</p>
<h2>Simple Dragging</h2>
<p>
Drag & Drop is a common interaction pattern. This behavior can be accomplished by a class that implements
IInteractionMapperTarget as well as IInteractionTarget. You can grab the blue circle with touches or mouse
and drag it around.
</p>
<div class="grayBorder" style="position: relative; width: 100%; height: 200px">
<div id="circle" style="position: absolute; left:50px; top: 50px; border-radius: 50%; width: 32px; height: 32px; background-color: blue;"></div>
<div
id="circle"
style="
position: absolute;
left: 50px;
top: 50px;
border-radius: 50%;
width: 32px;
height: 32px;
background-color: blue;
"
></div>
</div>
<script class="doctest">
class Dragger {
constructor(element, container) {
/* The events are captured by the container but send to this
wrapper object, if the event target is identical to the wrapped
@ -272,10 +263,12 @@ You can grab the blue circle with touches or mouse and drag it around.</p>
this.interaction = new InteractionMapper(container, this)
}
capture(event) { return true }
capture(event) {
return true
}
findTarget(event, localPoint, globalPoint) {
return (event.target == this.target) ? this : null
return event.target == this.target ? this : null
}
onStart(event, interaction) {
@ -286,8 +279,8 @@ You can grab the blue circle with touches or mouse and drag it around.</p>
let move = interaction.move()
let x = parseInt(this.target.style.left) + move.x
let y = parseInt(this.target.style.top) + move.y
this.target.style.left = x + "px"
this.target.style.top = y + "px"
this.target.style.left = x + 'px'
this.target.style.top = y + 'px'
}
onEnd(event, interaction) {
@ -305,105 +298,198 @@ You can grab the blue circle with touches or mouse and drag it around.</p>
new Dragger(circle, document.body)
</script>
<h2>
Multitouch
</h2>
<h2>Multitouch</h2>
<p>
Multitouch-Events (simultaneous events) in browsers cannot be used by default.
Even libraries like jQuery do not fix this problem. The static method "on" of the
InteractionMapper allows simultaneous events and thus multitouch. The following
events (and their specializations) can be used in addition to the default browser
events: tap, doubletap, press, pan, swipe, pinch and rotate. See http://hammerjs.github.io
for more details.
Multitouch-Events (simultaneous events) in browsers cannot be used by default. Even libraries like jQuery do
not fix this problem. The static method "on" of the InteractionMapper allows simultaneous events and thus
multitouch. The following events (and their specializations) can be used in addition to the default browser
events: tap, doubletap, press, pan, swipe, pinch and rotate. See http://hammerjs.github.io for more details.
</p>
<svg width="100%" height="300" viewBox="0 0 400 200" class="grayBorder" xmlns="http://www.w3.org/2000/svg" xmlns:bx="https://boxy-svg.com">
<svg
width="100%"
height="300"
viewBox="0 0 400 200"
class="grayBorder"
xmlns="http://www.w3.org/2000/svg"
xmlns:bx="https://boxy-svg.com"
>
<defs>
<pattern id="pattern-1" viewBox="0 0 100 100" patternUnits="userSpaceOnUse" preserveAspectRatio="none" width="100" height="100" />
<linearGradient id="gradient-1" gradientUnits="userSpaceOnUse" x1="235.294" y1="5.386" x2="235.294" y2="63.218" gradientTransform="matrix(0.479375, 0.877612, -1.161752, 0.599143, 216.009222, -193.782169)">
<pattern
id="pattern-1"
viewBox="0 0 100 100"
patternUnits="userSpaceOnUse"
preserveAspectRatio="none"
width="100"
height="100"
/>
<linearGradient
id="gradient-1"
gradientUnits="userSpaceOnUse"
x1="235.294"
y1="5.386"
x2="235.294"
y2="63.218"
gradientTransform="matrix(0.479375, 0.877612, -1.161752, 0.599143, 216.009222, -193.782169)"
>
<stop offset="0" style="stop-color: rgba(216, 216, 216, 1)" />
<stop offset="1" style="stop-color: rgb(45, 175, 182);" />
<stop offset="1" style="stop-color: rgb(45, 175, 182)" />
</linearGradient>
<linearGradient id="gradient-4" gradientUnits="userSpaceOnUse" x1="193.252" y1="126.988" x2="193.252" y2="163.836" gradientTransform="matrix(0.978752, 0, 0, 1.126983, 11.124972, -21.238213)">
<linearGradient
id="gradient-4"
gradientUnits="userSpaceOnUse"
x1="193.252"
y1="126.988"
x2="193.252"
y2="163.836"
gradientTransform="matrix(0.978752, 0, 0, 1.126983, 11.124972, -21.238213)"
>
<stop offset="0" style="stop-color: rgba(161, 110, 0, 1)" />
<stop offset="1" style="stop-color: rgba(59, 40, 0, 1)" />
</linearGradient>
</defs>
<g id="hammer-1">
<rect x="55.329" y="20.25" width="42.523" height="42.523" style="fill: rgb(236, 229, 24); stroke: rgb(0, 179, 207); stroke-width: 2; stroke-linejoin: bevel;" />
<text style="fill: rgb(51, 51, 51); font-size: 12px; white-space: pre;" x="68.736" y="45.811">tap</text>
<rect
x="55.329"
y="20.25"
width="42.523"
height="42.523"
style="fill: rgb(236, 229, 24); stroke: rgb(0, 179, 207); stroke-width: 2; stroke-linejoin: bevel"
/>
<text style="fill: rgb(51, 51, 51); font-size: 12px; white-space: pre" x="68.736" y="45.811">tap</text>
</g>
<g id="hammer-2">
<path d="M 372 149 m -25.496 0 a 25.496 26.092 0 1 0 50.992 0 a 25.496 26.092 0 1 0 -50.992 0 Z M 372 149 m -15.297 0 a 15.297 15.654 0 0 1 30.594 0 a 15.297 15.654 0 0 1 -30.594 0 Z" transform="matrix(-0.535925, 0.844266, -0.844265, -0.535925, 499.054353, -194.103207)" style="fill: rgb(194, 59, 59); stroke: rgb(141, 10, 91); stroke-width: 2;" bx:shape="ring 372 149 15.297 15.654 25.496 26.092 1@9ddd52c9" />
<text transform="matrix(1.226643, 0, 0, 1.226643, 42.737137, 26.559669)" style="fill: rgb(51, 51, 51); font-size: 9.7828px; white-space: pre;">
<path
d="M 372 149 m -25.496 0 a 25.496 26.092 0 1 0 50.992 0 a 25.496 26.092 0 1 0 -50.992 0 Z M 372 149 m -15.297 0 a 15.297 15.654 0 0 1 30.594 0 a 15.297 15.654 0 0 1 -30.594 0 Z"
transform="matrix(-0.535925, 0.844266, -0.844265, -0.535925, 499.054353, -194.103207)"
style="fill: rgb(194, 59, 59); stroke: rgb(141, 10, 91); stroke-width: 2"
bx:shape="ring 372 149 15.297 15.654 25.496 26.092 1@9ddd52c9"
/>
<text
transform="matrix(1.226643, 0, 0, 1.226643, 42.737137, 26.559669)"
style="fill: rgb(51, 51, 51); font-size: 9.7828px; white-space: pre"
>
<tspan x="94.401" y="44.224">press</tspan>
<tspan x="94.401" dy="1em">​</tspan>
</text>
</g>
<g>
<polygon id="hammer-3" style="fill: url(#gradient-1); stroke: rgb(182, 40, 92);" points="272.369 20.761 234.949 23.029 227.862 34.652 236.65 46.558 253.943 55.63 293.347 59.315 340.406 62.434 371.306 49.96 374.708 32.951 356.282 29.549 333.319 21.044 311.774 9.705 307.238 23.029 322.263 33.518 347.777 44.007 339.839 48.259 315.459 48.826 292.781 45.991 281.725 32.667 285.977 17.643 281.158 4.602 267.55 6.303 252.525 6.587 252.809 11.973 255.36 17.076 263.014 16.225 267.834 13.674 273.787 13.39 276.622 14.808" />
<text style="fill: rgb(51, 51, 51); font-size: 12px; white-space: pre;" x="296.849" y="80.823">pan</text>
<polygon
id="hammer-3"
style="fill: url(#gradient-1); stroke: rgb(182, 40, 92)"
points="272.369 20.761 234.949 23.029 227.862 34.652 236.65 46.558 253.943 55.63 293.347 59.315 340.406 62.434 371.306 49.96 374.708 32.951 356.282 29.549 333.319 21.044 311.774 9.705 307.238 23.029 322.263 33.518 347.777 44.007 339.839 48.259 315.459 48.826 292.781 45.991 281.725 32.667 285.977 17.643 281.158 4.602 267.55 6.303 252.525 6.587 252.809 11.973 255.36 17.076 263.014 16.225 267.834 13.674 273.787 13.39 276.622 14.808"
/>
<text style="fill: rgb(51, 51, 51); font-size: 12px; white-space: pre" x="296.849" y="80.823">pan</text>
</g>
<g>
<ellipse transform="matrix(-0.707107, 0.707107, -0.707107, -0.707107, 362.152622, 115.748229)" cx="221.437" cy="181.098" rx="27.616" ry="27.616" style="fill: rgb(149, 26, 133); stroke: rgb(73, 4, 62); stroke-width: 4; fill-opacity: 0.69;" />
<text style="fill: rgb(51, 51, 51); font-size: 12px; white-space: pre;" x="61.759" y="190.447">swipe</text>
<ellipse
transform="matrix(-0.707107, 0.707107, -0.707107, -0.707107, 362.152622, 115.748229)"
cx="221.437"
cy="181.098"
rx="27.616"
ry="27.616"
style="fill: rgb(149, 26, 133); stroke: rgb(73, 4, 62); stroke-width: 4; fill-opacity: 0.69"
/>
<text style="fill: rgb(51, 51, 51); font-size: 12px; white-space: pre" x="61.759" y="190.447">
swipe
</text>
</g>
<g>
<rect id="hammer-5" x="146.389" y="121.875" width="107.762" height="41.527" style="fill: url(#gradient-4); stroke-linejoin: round; stroke: rgb(0, 0, 0);" />
<text style="fill: rgb(51, 51, 51); font-size: 12px; white-space: pre;" x="187.854" y="190.447">pinch</text>
<rect
id="hammer-5"
x="146.389"
y="121.875"
width="107.762"
height="41.527"
style="fill: url(#gradient-4); stroke-linejoin: round; stroke: rgb(0, 0, 0)"
/>
<text style="fill: rgb(51, 51, 51); font-size: 12px; white-space: pre" x="187.854" y="190.447">
pinch
</text>
</g>
<g transform="matrix(1.286049, 0, 0, 1.286049, -103.444145, -48.307945)">
<path class="star" d="M 937 394.847 L 946.206 421.33 L 974.238 421.901 L 951.895 438.84 L 960.014 465.675 L 937 449.661 L 913.986 465.675 L 922.105 438.84 L 899.762 421.901 L 927.794 421.33 Z" transform="matrix(-0.809017, 0.587785, -0.587785, -0.809018, 1346.787902, -60.391979)" style="fill: rgb(83, 230, 226); stroke: rgb(24, 111, 116); stroke-width: 2; stroke-linejoin: round; stroke-dasharray: 2px;" bx:shape="star 937 434 39.154 39.153 0.4 5 1@05a6f642" />
<text style="fill: rgb(51, 51, 51); font-size: 12px; white-space: pre;" x="316.854" y="190.447">rotate</text>
<path
class="star"
d="M 937 394.847 L 946.206 421.33 L 974.238 421.901 L 951.895 438.84 L 960.014 465.675 L 937 449.661 L 913.986 465.675 L 922.105 438.84 L 899.762 421.901 L 927.794 421.33 Z"
transform="matrix(-0.809017, 0.587785, -0.587785, -0.809018, 1346.787902, -60.391979)"
style="
fill: rgb(83, 230, 226);
stroke: rgb(24, 111, 116);
stroke-width: 2;
stroke-linejoin: round;
stroke-dasharray: 2px;
"
bx:shape="star 937 434 39.154 39.153 0.4 5 1@05a6f642"
/>
<text style="fill: rgb(51, 51, 51); font-size: 12px; white-space: pre" x="316.854" y="190.447">
rotate
</text>
</g>
<g transform="matrix(1.286049, 0, 0, 1.286049, -28.431454, -48.307941)">
<path class="star" d="M 937 394.847 L 946.206 421.33 L 974.238 421.901 L 951.895 438.84 L 960.014 465.675 L 937 449.661 L 913.986 465.675 L 922.105 438.84 L 899.762 421.901 L 927.794 421.33 Z" transform="matrix(-0.809017, 0.587785, -0.587785, -0.809018, 1346.787902, -60.391979)" style="fill: rgb(83, 230, 226); stroke: rgb(24, 111, 116); stroke-width: 2; stroke-linejoin: round; stroke-dasharray: 2px;" bx:shape="star 937 434 39.154 39.153 0.4 5 1@05a6f642" />
<text style="fill: rgb(51, 51, 51); font-size: 12px; white-space: pre;" x="316.854" y="190.447">rotate</text>
<path
class="star"
d="M 937 394.847 L 946.206 421.33 L 974.238 421.901 L 951.895 438.84 L 960.014 465.675 L 937 449.661 L 913.986 465.675 L 922.105 438.84 L 899.762 421.901 L 927.794 421.33 Z"
transform="matrix(-0.809017, 0.587785, -0.587785, -0.809018, 1346.787902, -60.391979)"
style="
fill: rgb(83, 230, 226);
stroke: rgb(24, 111, 116);
stroke-width: 2;
stroke-linejoin: round;
stroke-dasharray: 2px;
"
bx:shape="star 937 434 39.154 39.153 0.4 5 1@05a6f642"
/>
<text style="fill: rgb(51, 51, 51); font-size: 12px; white-space: pre" x="316.854" y="190.447">
rotate
</text>
</g>
</svg>
<script class="doctest">
const from = { scale: 1 }
const to = { scale: 1.3, transformOrigin: 'center', repeat: 1, yoyo: true }
InteractionMapper.on('tap', document.getElementById('hammer-1'), event => {
TweenLite.fromTo(event.target, .2, from, to)
InteractionMapper.on('tap', document.getElementById('hammer-1'), (event) => {
TweenLite.fromTo(event.target, 0.2, from, to)
})
InteractionMapper.on('press', document.getElementById('hammer-2'), event => {
TweenLite.fromTo(event.target, .2, from, to)
}, {time: 1000})
InteractionMapper.on(
'press',
document.getElementById('hammer-2'),
(event) => {
TweenLite.fromTo(event.target, 0.2, from, to)
},
{ time: 1000 }
)
InteractionMapper.on('panright pandown', document.getElementById('hammer-3'), event => {
TweenLite.fromTo(event.target, .2, from, to)
InteractionMapper.on('panright pandown', document.getElementById('hammer-3'), (event) => {
TweenLite.fromTo(event.target, 0.2, from, to)
})
InteractionMapper.on(['swipeleft', 'swipedown'], document.getElementsByTagName('ellipse'), event => {
TweenLite.fromTo(event.target, .2, from, to)
InteractionMapper.on(['swipeleft', 'swipedown'], document.getElementsByTagName('ellipse'), (event) => {
TweenLite.fromTo(event.target, 0.2, from, to)
})
InteractionMapper
.on('pinch', document.getElementById('hammer-5'), event => {
TweenLite.fromTo(event.target, .2, from, to)
InteractionMapper.on('pinch', document.getElementById('hammer-5'), (event) => {
TweenLite.fromTo(event.target, 0.2, from, to)
})
InteractionMapper
.on('rotate', document.querySelectorAll('svg g > path.star'), event => {
TweenLite.fromTo(event.target, .2, from, to)
InteractionMapper.on('rotate', document.querySelectorAll('svg g > path.star'), (event) => {
TweenLite.fromTo(event.target, 0.2, from, to)
})
InteractionMapper
.on('click', document.getElementById('hammer-1'), event => {
InteractionMapper.on('click', document.getElementById('hammer-1'), (event) => {
console.log(event)
})
</script>
<h2>
References
</h2>
<h2>References</h2>
<ul>
<li><a href="https://www.amazon.de/Patterns-Elements-Reusable-Object-Oriented-Software/dp/0201633612">Design Patterns [p. 20]</a></li>
<li>
<a href="https://www.amazon.de/Patterns-Elements-Reusable-Object-Oriented-Software/dp/0201633612"
>Design Patterns [p. 20]</a
>
</li>
<li><a href="http://hammerjs.github.io">Hammer.js</a></li>
</ul>
</body>
</html>

33
lib/interface.html
View File

@ -1,50 +1,43 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../css/doctest.css">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../css/doctest.css" />
<script src="./3rdparty/highlight/highlight.pack.js"></script>
<script src="../dist/iwmlib.js"></script>
</head>
<body onload="Doctest.run()">
<h1>
Interfaces
</h1>
<h1><a href="index.html">lib.</a>Interfaces</h1>
<p>
Interfaces are objects that specify (document) the external behavior of objects
that “provide” them. An interface specifies behavior through method definitions
that specify functions and their signatures.
Interfaces are objects that specify (document) the external behavior of objects that “provide” them. An
interface specifies behavior through method definitions that specify functions and their signatures.
</p>
<p>Let's look at an example of an interface and a class implementing the interface:</p>
<script class="doctest">
class ITestable extends Interface {
reset() {}
run() {}
}
class Testable {
reset() {
print("Resetting testable object")
print('Resetting testable object')
}
run() {
print("Running testable object")
print('Running testable object')
}
}
</script>
<p>We can now check whether the promised interface methods are implemented by the
class:</p>
<p>We can now check whether the promised interface methods are implemented by the class:</p>
<script class="doctest">
Doctest.expect(ITestable.implementedBy(Testable), true)
</script>
<p>
<h2>
References
</h2>
<p></p>
<h2>References</h2>
<ul>
<li><a href="https://zopeinterface.readthedocs.io">Zope Interfaces</a></li>
</ul>
</body>
</html>

25
lib/logging.html
View File

@ -1,33 +1,30 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<title>Logging Doctest</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../css/doctest.css">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../css/doctest.css" />
<script src="./3rdparty/highlight/highlight.pack.js"></script>
<script src="../dist/iwmlib.3rdparty.js"></script>
<script src="../dist/iwmlib.js"></script>
</head>
<body id="page" onload="Doctest.run()">
<h1>
Logging
</h1>
<h1><a href="index.html">lib.</a>Logging</h1>
<p>Store informations of your app permanently or use app specific logging functions.</p>
<script class="doctest">
Logging.log('app started')
Logging.warn("shouldn't happen")
Logging.error('restart')
Logging.setup({ log: message => console.log("app specific" + message) })
Logging.log("now app related")
Logging.setup({ log: (message) => console.log('app specific' + message) })
Logging.log('now app related')
</script>
<p>You can overwrite the log, warn, and error handler by using Logging.setup with
app specific functions.</p>
<p>You can overwrite the log, warn, and error handler by using Logging.setup with app specific functions.</p>
<script class="doctest">
Logging.setup({ log: message => console.log("app specific" + message) })
Logging.log("now app related")
Logging.setup({ log: (message) => console.log('app specific' + message) })
Logging.log('now app related')
</script>
</body>
</html>

2
lib/pixi/app.html
View File

@ -15,7 +15,7 @@
<script src="../../dist/iwmlib.pixi.js"></script>
</head>
<body onload="Doctest.run()">
<h1>Application</h1>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>Application</h1>
<p>
The class PIXIApp is the main entry point to create a new PIXI Application.
It inherits from PIXI.Application, set meaningfull defaults, creates a scene and

14
lib/pixi/application.html
View File

@ -1,17 +1,20 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>PIXI.Application Doctest</title>
<link rel="stylesheet" href=".././3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../css/doctest.css" />
<script src="../../dist/iwmlib.3rdparty.js"></script>
<script src="../../dist/iwmlib.js"></script>
<script src="../../dist/iwmlib.pixi.js"></script>
</head>
<body>
<h1>Vanilla PIXI.Application</h1>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>Vanilla PIXI.Application</h1>
<script>
const app = new PIXI.Application({
@ -24,13 +27,14 @@
// ex, add display objects
const sprite = PIXI.Sprite.from('./assets/app-circle.png')
sprite.scale.set(.3, .3)
sprite.scale.set(0.3, 0.3)
app.stage.addChild(sprite)
sprite.interactive = true
sprite.buttonMode = true
sprite.on('click', e => {
sprite.on('click', (e) => {
console.log('sprite clicked')
})
</script>
</body>
</html>

30
lib/pixi/badge.html
View File

@ -5,10 +5,7 @@
<title>PIXI Badge</title>
<link
rel="stylesheet"
href="../3rdparty/highlight/styles/default.css"
/>
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../css/doctest.css" />
<script src="../3rdparty/highlight/highlight.pack.js"></script>
@ -18,16 +15,12 @@
<script src="../../dist/iwmlib.pixi.js"></script>
</head>
<body onload="Doctest.run()">
<h1>Badge</h1>
<p>
Small and adaptive tag for adding context to just about any content.
</p>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>Badge</h1>
<p>Small and adaptive tag for adding context to just about any content.</p>
<p>Let's look at some badge examples:</p>
<br />
<canvas id="canvas" class="interactive"></canvas>
<p>
What you should see: Badges, badges, badges...
</p>
<p>What you should see: Badges, badges, badges...</p>
<script class="doctest">
const app = new PIXIApp({
view: canvas,
@ -120,13 +113,11 @@
fill: 0xfe9727
})
let sprite1 = new PIXI.Sprite(
PIXI.Texture.from('./assets/badge-1.mp4')
)
let sprite1 = new PIXI.Sprite(PIXI.Texture.from('./assets/badge-1.mp4'))
sprite1.scale.set(0.05, 0.05)
let texture1 = PIXI.Texture.from('./assets/badge-1.mp4')
texture1.baseTexture.on('loaded', e => {
texture1.baseTexture.on('loaded', (e) => {
let sprite1 = new PIXI.Sprite(texture1)
sprite1.scale.set(0.05, 0.05)
sprite1.alpha = 0.5
@ -145,14 +136,7 @@
})
app.scene.addChild(circle1, circle2)
app.scene.addChild(
button1,
button2,
button3,
button4,
button5,
button6
)
app.scene.addChild(button1, button2, button3, button4, button5, button6)
app.scene.addChild(badge1, badge2, badge3)
</script>
</body>

25
lib/pixi/blurfilter.html
View File

@ -1,12 +1,12 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>PIXI BlurFilter</title>
<link rel="stylesheet" href=".././3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../../css/doctest.css">
<link rel="stylesheet" href=".././3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../css/doctest.css" />
<script src=".././3rdparty/highlight/highlight.pack.js"></script>
<script src="../../dist/iwmlib.3rdparty.js"></script>
@ -15,17 +15,15 @@
<script src="../../dist/iwmlib.pixi.js"></script>
</head>
<body onload="Doctest.run()">
<h1>BlurFilter</h1>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>BlurFilter</h1>
<p>
The BlurFilter class creates a blur filter on the renderer. In contrast to the PIXI BlurFilter, you can specify
a range (defined as a PIXI.Rectangle) on which the filter should be applied.
The BlurFilter class creates a blur filter on the renderer. In contrast to the PIXI BlurFilter, you can
specify a range (defined as a PIXI.Rectangle) on which the filter should be applied.
</p>
<h2>Example with Image</h2>
<p>Let's look at an example of creating a new blur filter near the bottom:</p>
<canvas id="canvas" class="interactive"></canvas>
<p>
What you should see: A sniffing hedgehog and three blurred areas (with different strengths of blur).
</p>
<p>What you should see: A sniffing hedgehog and three blurred areas (with different strengths of blur).</p>
<script class="doctest">
// Create the app
const app = new PIXIApp({
@ -33,10 +31,12 @@ const app = new PIXIApp({
width: 480,
height: 270,
transparent: false
}).setup().run()
})
.setup()
.run()
// Load a video and add it to the scene
const videoSprite = new PIXI.Sprite(PIXI.Texture.from("assets/blurfilter.mp4"))
const videoSprite = new PIXI.Sprite(PIXI.Texture.from('assets/blurfilter.mp4'))
videoSprite.width = app.size.width
videoSprite.height = app.size.height
app.scene.addChild(videoSprite)
@ -48,3 +48,4 @@ const blurFilter3 = new BlurFilter(new PIXI.Rectangle(380, 40, 100, 100), 20)
app.scene.filters = [blurFilter1, blurFilter2, blurFilter3]
</script>
</body>
</html>

149
lib/pixi/button.html
View File

@ -1,12 +1,12 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>PIXI Button</title>
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../../css/doctest.css">
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../css/doctest.css" />
<script src="../3rdparty/highlight/highlight.pack.js"></script>
<script src="../../dist/iwmlib.3rdparty.js"></script>
@ -15,26 +15,27 @@
<script src="../../dist/iwmlib.pixi.js"></script>
</head>
<body onload="Doctest.run()">
<h1>Button</h1>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>Button</h1>
<p>
The Button class defines a clickable/touchable button. Use custom button styles for actions in forms, dialogs,
and more with support for multiple sizes, states, and more. Buttons will appear pressed when active. Make
buttons look inactive by setting the disabled state to true. To allow changing the state between active/inactive, set
the button type to "checkbox".
The Button class defines a clickable/touchable button. Use custom button styles for actions in forms,
dialogs, and more with support for multiple sizes, states, and more. Buttons will appear pressed when
active. Make buttons look inactive by setting the disabled state to true. To allow changing the state
between active/inactive, set the button type to "checkbox".
</p>
<p><a href="../../doc/out/Button.html">JavaScript API</a></p>
<p>Let's look at some button examples:</p><br />
<p>Let's look at some button examples:</p>
<br />
<canvas id="canvas" class="interactive"></canvas>
<p>
What you should see: Many buttons with very different styling and behaviour.
</p>
<p>What you should see: Many buttons with very different styling and behaviour.</p>
<script class="doctest">
const app = new PIXIApp({
view: canvas,
width: 900,
height: 600,
transparent: false
}).setup().run()
})
.setup()
.run()
const button1 = new Button({ x: 10, y: 10 })
@ -44,7 +45,7 @@ const button2 = new Button({
y: 10,
label: 'Button',
type: 'checkbox',
action: e => {
action: (e) => {
console.info('Button clicked')
}
})
@ -54,7 +55,7 @@ const button3 = new Button({
y: 10,
label: 'Checkbox button',
type: 'checkbox',
action: e => {
action: (e) => {
console.info('Button clicked', e)
}
})
@ -64,7 +65,7 @@ const button4 = new Button({
y: 10,
label: 'Disabled button',
disabled: true,
action: e => {
action: (e) => {
console.info('Disabled button clicked')
}
})
@ -249,7 +250,7 @@ const button20 = new Button({
label: 'Link Button',
type: 'checkbox',
style: 'link',
action: event => {
action: (event) => {
console.log('Link button clicked')
}
})
@ -306,7 +307,113 @@ const button25 = new Button({
}
})
const countries = ['Tajikistan', 'Zambia', 'Dominica', 'Australia', 'Botswana', 'Mozambique', 'Lesotho', 'Thailand', 'Gabon', 'Cuba', 'Mexico', 'Central African Republic', 'Réunion', 'Montenegro', 'Romania', 'Jamaica', 'Thailand', 'Cameroon', 'French Guiana', 'Nigeria', 'Tokelau', 'Slovenia', 'Kuwait', 'Palestinian Territories', 'Estonia', 'Germany', 'Cameroon', 'Somalia', 'El Salvador', 'San Marino', 'Sierra Leone', 'Sierra Leone', 'Gibraltar', 'Benin', 'Russia', 'Iraq', 'Tunisia', 'Greenland', 'Côte d\'Ivoire', 'Tanzania', 'Zambia', 'Bermuda', 'Somalia', 'Malaysia', 'Croatia', 'Togo', 'Belgium', 'Uruguay', 'Equatorial Guinea', 'Nigeria', 'St. Martin', 'Tuvalu', 'South Africa', 'Hong Kong SAR China', 'Palau', 'Canary Islands', 'Algeria', 'Hong Kong SAR China', 'Brunei', 'Dominican Republic', 'Sierra Leone', 'Moldova', 'Indonesia', 'Central African Republic', 'Anguilla', 'Malaysia', 'Bahrain', 'Indonesia', 'Peru', 'Namibia', 'Congo - Brazzaville', 'Micronesia', 'Cambodia', 'Réunion', 'Honduras', 'Hungary', 'Brazil', 'Trinidad & Tobago', 'Hungary', 'Madagascar', 'Sierra Leone', 'Seychelles', 'St. Martin', 'New Caledonia', 'Tokelau', 'Macedonia', 'Netherlands', 'Panama', 'Venezuela', 'Nepal', 'Guernsey', 'Papua New Guinea', 'Finland', 'Malaysia', 'Hong Kong SAR China', 'Trinidad & Tobago', 'Montserrat', 'Comoros', 'Benin', 'South Korea', 'Peru', 'Botswana', 'Cambodia', 'Isle of Man', 'Mozambique']
const countries = [
'Tajikistan',
'Zambia',
'Dominica',
'Australia',
'Botswana',
'Mozambique',
'Lesotho',
'Thailand',
'Gabon',
'Cuba',
'Mexico',
'Central African Republic',
'Réunion',
'Montenegro',
'Romania',
'Jamaica',
'Thailand',
'Cameroon',
'French Guiana',
'Nigeria',
'Tokelau',
'Slovenia',
'Kuwait',
'Palestinian Territories',
'Estonia',
'Germany',
'Cameroon',
'Somalia',
'El Salvador',
'San Marino',
'Sierra Leone',
'Sierra Leone',
'Gibraltar',
'Benin',
'Russia',
'Iraq',
'Tunisia',
'Greenland',
"Côte d'Ivoire",
'Tanzania',
'Zambia',
'Bermuda',
'Somalia',
'Malaysia',
'Croatia',
'Togo',
'Belgium',
'Uruguay',
'Equatorial Guinea',
'Nigeria',
'St. Martin',
'Tuvalu',
'South Africa',
'Hong Kong SAR China',
'Palau',
'Canary Islands',
'Algeria',
'Hong Kong SAR China',
'Brunei',
'Dominican Republic',
'Sierra Leone',
'Moldova',
'Indonesia',
'Central African Republic',
'Anguilla',
'Malaysia',
'Bahrain',
'Indonesia',
'Peru',
'Namibia',
'Congo - Brazzaville',
'Micronesia',
'Cambodia',
'Réunion',
'Honduras',
'Hungary',
'Brazil',
'Trinidad & Tobago',
'Hungary',
'Madagascar',
'Sierra Leone',
'Seychelles',
'St. Martin',
'New Caledonia',
'Tokelau',
'Macedonia',
'Netherlands',
'Panama',
'Venezuela',
'Nepal',
'Guernsey',
'Papua New Guinea',
'Finland',
'Malaysia',
'Hong Kong SAR China',
'Trinidad & Tobago',
'Montserrat',
'Comoros',
'Benin',
'South Korea',
'Peru',
'Botswana',
'Cambodia',
'Isle of Man',
'Mozambique'
]
setInterval(() => {
button25.badge.content = countries[Math.floor(Math.random() * countries.length)]
button25.layout()
@ -321,8 +428,8 @@ const button26 = new Button({
textStyleActive: {
fill: 0x28a745
},
textAlpha: .2,
textActiveAlpha: .6
textAlpha: 0.2,
textActiveAlpha: 0.6
})
app.scene.addChild(button1, button2, button3, button4, button5, button6)

107
lib/pixi/buttongroup.html
View File

@ -1,12 +1,12 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-eqv="Content-Type" content="text/html; charset=utf-8">
<meta http-eqv="Content-Type" content="text/html; charset=utf-8" />
<title>PIXI ButtonGroup</title>
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../../css/doctest.css">
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../css/doctest.css" />
<script src="../3rdparty/highlight/highlight.pack.js"></script>
<script src="../../dist/iwmlib.3rdparty.js"></script>
@ -16,22 +16,21 @@
<script src="../../dist/iwmlib.pixi.js"></script>
</head>
<body onload="Doctest.run()">
<h1>ButtonGroup</h1>
<p>
Group a series of buttons together on a single line with the button group.
</p>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>ButtonGroup</h1>
<p>Group a series of buttons together on a single line with the button group.</p>
<p><a href="../../doc/out/ButtonGroup.html">JavaScript API</a></p>
<p>Let's look at some button groups:</p><br />
<p>Let's look at some button groups:</p>
<br />
<canvas id="canvas" class="interactive"></canvas>
<p>
What you should see: Many button groups with very different styling and behaviour.
</p>
<p>What you should see: Many button groups with very different styling and behaviour.</p>
<script class="doctest">
const app = new PIXIApp({
view: canvas,
width: 1000,
height: 1700
}).setup().run()
})
.setup()
.run()
const buttonGroup1 = new ButtonGroup({
x: 10,
@ -81,8 +80,21 @@ const buttonGroup4 = new ButtonGroup({
buttons: [
{ label: 'Button 1', action: (event, button) => console.log(button.id) },
{ label: 'Button 2', action: (event, button) => console.log(button.id), radius: 0 },
{label: 'Button 3', textStyle: {fill: '#fd6b6a'}, stroke: 0xd7a3f9, strokeWidth: 8, strokeAlpha: .8},
{label: 'Button 4', textStyle: {fill: '#40c3f2'}, radius: 20, icon: 'looks', iconPosition: 'right', iconColor: 0xd7ff30}
{
label: 'Button 3',
textStyle: { fill: '#fd6b6a' },
stroke: 0xd7a3f9,
strokeWidth: 8,
strokeAlpha: 0.8
},
{
label: 'Button 4',
textStyle: { fill: '#40c3f2' },
radius: 20,
icon: 'looks',
iconPosition: 'right',
iconColor: 0xd7ff30
}
],
margin: 40,
minWidth: 180,
@ -152,12 +164,7 @@ const buttonGroup8 = new ButtonGroup({
const buttonGroup9 = new ButtonGroup({
x: 10,
y: 320,
buttons: [
{icon: 'attachment'},
{icon: 'autorenew'},
{icon: 'backup'},
{icon: 'apps'}
],
buttons: [{ icon: 'attachment' }, { icon: 'autorenew' }, { icon: 'backup' }, { icon: 'apps' }],
orientation: 'vertical',
minWidth: 70
})
@ -222,7 +229,13 @@ const buttonGroup13 = new ButtonGroup({
{ icon: 'volume_off', label: 'Aus', align: 'left', iconColor: 0x99ffff, verticalAlign: 'top' },
{ icon: 'volume_mute', label: 'Lautlos', active: true, iconColorActive: 0xd7a3f9 },
{ icon: 'volume_down', label: 'Leiser', align: 'right', iconPosition: 'right' },
{icon: 'volume_up', label: 'Lauter', align: 'right', iconPosition: 'right', verticalAlign: 'bottom'}
{
icon: 'volume_up',
label: 'Lauter',
align: 'right',
iconPosition: 'right',
verticalAlign: 'bottom'
}
],
orientation: 'vertical',
margin: 0,
@ -237,14 +250,14 @@ const buttonGroup14 = new ButtonGroup({
x: 10,
y: 960,
buttons: [
{label: 'Stacked button 1', action: event => console.log('clicked 1')},
{label: 'Stacked button 2', action: event => console.log('clicked 2')},
{label: 'Stacked button 3', action: event => console.log('clicked 3')},
{label: 'Stacked button 4', action: event => console.log('clicked 4')},
{label: 'Stacked button 5', action: event => console.log('clicked 5')},
{label: 'Stacked button 6', action: event => console.log('clicked 6')},
{label: 'Stacked button 7', action: event => console.log('clicked 7')},
{label: 'Stacked button 8', action: event => console.log('clicked 8')}
{ label: 'Stacked button 1', action: (event) => console.log('clicked 1') },
{ label: 'Stacked button 2', action: (event) => console.log('clicked 2') },
{ label: 'Stacked button 3', action: (event) => console.log('clicked 3') },
{ label: 'Stacked button 4', action: (event) => console.log('clicked 4') },
{ label: 'Stacked button 5', action: (event) => console.log('clicked 5') },
{ label: 'Stacked button 6', action: (event) => console.log('clicked 6') },
{ label: 'Stacked button 7', action: (event) => console.log('clicked 7') },
{ label: 'Stacked button 8', action: (event) => console.log('clicked 8') }
],
stackPadding: 6,
maxWidth: 620,
@ -271,7 +284,12 @@ const buttonGroup15 = new ButtonGroup({
const buttons16 = []
for (let i = 1; i < 101; i++) {
buttons16.push({label: `Button ${i}`, stroke: Math.floor(Math.random() * 16777215), strokeWidth: 3, radius: 16})
buttons16.push({
label: `Button ${i}`,
stroke: Math.floor(Math.random() * 16777215),
strokeWidth: 3,
radius: 16
})
}
buttons16.splice(6, 0, { minWidth: 50, style: 'link' })
@ -295,7 +313,12 @@ const buttonGroup17 = new ButtonGroup({
{ icon: 'local_dining', type: 'checkbox', iconColorActive: 0xefc201, badge: 'Dining' },
{ icon: 'local_florist', type: 'checkbox', iconColorActive: 0xefc201, badge: 'Florist' },
{ icon: 'local_gas_station', type: 'checkbox', iconColorActive: 0xefc201, badge: 'Gas station' },
{icon: 'local_grocery_store', type: 'checkbox', iconColorActive: 0xefc201, badge: 'Grocery store'},
{
icon: 'local_grocery_store',
type: 'checkbox',
iconColorActive: 0xefc201,
badge: 'Grocery store'
},
{ icon: 'local_mall', type: 'checkbox', iconColorActive: 0xefc201, badge: 'Mall' },
{ icon: 'local_pizza', type: 'checkbox', iconColorActive: 0xefc201, badge: 'Pizza' },
{ icon: 'local_printshop', type: 'checkbox', iconColorActive: 0xefc201, badge: 'Printshop' },
@ -330,11 +353,7 @@ const buttonGroup18 = new ButtonGroup({
const buttonGroup19 = new ButtonGroup({
x: 10,
y: 1420,
buttons: [
{label: 'move'},
{label: 'explanation dried'},
{label: 'out catch'}
],
buttons: [{ label: 'move' }, { label: 'explanation dried' }, { label: 'out catch' }],
maxWidth: 500,
app
})
@ -343,13 +362,9 @@ const buttonGroup20 = new ButtonGroup({
x: 10,
y: 1520,
type: 'checkbox',
buttons: [
{label: 'one'},
{label: 'two'},
{label: 'three'}
],
textAlpha: .7,
textActiveAlpha: .2
buttons: [{ label: 'one' }, { label: 'two' }, { label: 'three' }],
textAlpha: 0.7,
textActiveAlpha: 0.2
})
const buttonGroup21 = new ButtonGroup({
@ -357,8 +372,8 @@ const buttonGroup21 = new ButtonGroup({
y: 1520,
type: 'checkbox',
buttons: [
{label: 'eins', textAlpha: 1, textActiveAlpha: .2},
{label: 'zwei', textAlpha: .2, textActiveAlpha: 1},
{ label: 'eins', textAlpha: 1, textActiveAlpha: 0.2 },
{ label: 'zwei', textAlpha: 0.2, textActiveAlpha: 1 },
{ label: 'drei' }
]
})

2
lib/pixi/coordinates.html
View File

@ -15,7 +15,7 @@
<body onload="Doctest.run()">
<h1>
Coordinates
<a href="../index.html">lib.</a><a href="index.html">pixi.</a>Coordinates
</h1>
<p>
To position objects in defined spatial relationships presupposes a clear understanding of the involved coordinate systems.

85
lib/pixi/deepzoom/deepzoom.html
View File

@ -1,13 +1,12 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>DeepZoomImage Doctests</title>
<link rel="stylesheet" href="../../3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../../../css/doctest.css">
<link rel="stylesheet" href="../../3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../../css/doctest.css" />
<script src="../../3rdparty/highlight/highlight.pack.js"></script>
@ -29,30 +28,32 @@
</head>
<body onload="Doctest.run()">
<h1>Double DeepZoomImage</h1>
<h1>
<a href="../../index.html">lib.</a><a href="../index.html">pixi.</a><a href="index.html">deepzoom.</a>
DeepZoom
</h1>
<p>
The main class of a deeply zoomable image that is represented by a hierarchy of tile layers for each zoom level. This gives
the user the impression that even huge pictures (up to gigapixel-images) can be zoomed instantaneously, since the
tiles at smaller levels are scaled immediately and overloaded by more detailed tiles at the larger level as fast
as possible.
The main class of a deeply zoomable image that is represented by a hierarchy of tile layers for each zoom
level. This gives the user the impression that even huge pictures (up to gigapixel-images) can be zoomed
instantaneously, since the tiles at smaller levels are scaled immediately and overloaded by more detailed
tiles at the larger level as fast as possible.
</p>
<br />
<div id="div1" style="float: left;"></div>
<div id="div2" style="float: right;"></div>
<div style="clear: left; margin-top: 540px;" />
<div id="div1" style="float: left"></div>
<div id="div2" style="float: right"></div>
<div style="clear: left; margin-top: 540px" />
<script class="doctest">
// deepZoom
//--------------------
const deepZoomInfo = new DeepZoomInfo({
"tileSize": 128,
"format": "jpg",
"overlap": 0,
"type": "map",
"height": 4096,
"width": 4096,
"path": "../assets/maps/test",
"urlTileTemplate": "{path}/{level}/{column}/{row}.{format}"
tileSize: 128,
format: 'jpg',
overlap: 0,
type: 'map',
height: 4096,
width: 4096,
path: '../assets/maps/test',
urlTileTemplate: '{path}/{level}/{column}/{row}.{format}'
})
// const deepZoomInfo = new DeepZoomInfo({
// compression: [
@ -83,8 +84,10 @@
window.app = new PIXIApp({
width: 400,
height: 500,
backgroundColor: 0xFFCCCCCC
}).setup().run()
backgroundColor: 0xffcccccc
})
.setup()
.run()
div1.appendChild(app.view)
@ -100,7 +103,7 @@
deepZoomImage1.scatter = new DisplayObjectScatter(deepZoomImage1, app.renderer, {
minScale: 0,
maxScale: 50,
onTransform: event => {
onTransform: (event) => {
//console.log('currentLevel', deepZoomImage1.currentLevel)
deepZoomImage1.transformed(event)
}
@ -109,14 +112,15 @@
scatterContainer1.addChild(deepZoomImage1)
}, 1000)
// app2
//--------------------
const app2 = new PIXIApp({
width: 400,
height: 500,
backgroundColor: 0xFFCCCCCC
}).setup().run()
backgroundColor: 0xffcccccc
})
.setup()
.run()
div2.appendChild(app2.view)
@ -137,27 +141,27 @@
})
scatterContainer2.addChild(deepZoomImage2)
</script>
<h1>DeepZoomImage in DeepZoomImage</h1>
<p>
The main class of a deeply zoomable image that is represented by a hierarchy of tile layers for each zoom level. This gives
the user the impression that even huge pictures (up to gigapixel-images) can be zoomed instantaneously, since the
tiles at smaller levels are scaled immediately and overloaded by more detailed tiles at the larger level as fast
as possible.
The main class of a deeply zoomable image that is represented by a hierarchy of tile layers for each zoom
level. This gives the user the impression that even huge pictures (up to gigapixel-images) can be zoomed
instantaneously, since the tiles at smaller levels are scaled immediately and overloaded by more detailed
tiles at the larger level as fast as possible.
</p>
<br />
<div id="div3"></div>
<script class="doctest">
// app3
//--------------------
const app3 = new PIXIApp({
width: 900,
height: 500,
backgroundColor: 0xFFCCCCCC
}).setup().run()
backgroundColor: 0xffcccccc
})
.setup()
.run()
window.app3 = app3
@ -165,7 +169,12 @@
// create the ScatterContainer
//--------------------
const scatterContainer3 = new ScatterContainer(app3.renderer, {app: app3, showBounds: true, claimEvent: false, stopEvents: false})
const scatterContainer3 = new ScatterContainer(app3.renderer, {
app: app3,
showBounds: true,
claimEvent: false,
stopEvents: false
})
app3.scene.addChild(scatterContainer3)
// Create the DeepZoomImage
@ -212,8 +221,6 @@
app3._deepZoomImage4 = deepZoomImage4
scatterContainer3.addChild(deepZoomImage4)
</script>
</body>
</html>

72
lib/pixi/deepzoom/image.html
View File

@ -1,13 +1,12 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>DeepZoomImage Doctests</title>
<link rel="stylesheet" href="../../3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../../../css/doctest.css">
<link rel="stylesheet" href="../../3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../../css/doctest.css" />
<script src="../../3rdparty/highlight/highlight.pack.js"></script>
<script src="../../../dist/iwmlib.3rdparty.js"></script>
@ -28,12 +27,15 @@
</head>
<body onload="Doctest.run()">
<h1>DeepZoomImage</h1>
<h1>
<a href="../../index.html">lib.</a><a href="../index.html">pixi.</a
><a href="index.html">deepzoom.</a>DeepZoomImage
</h1>
<p>
The main class of a deeply zoomable image that is represented by a hierarchy of tile layers for each zoom level. This gives
the user the impression that even huge pictures (up to gigapixel-images) can be zoomed instantaneously, since the
tiles at smaller levels are scaled immediately and overloaded by more detailed tiles at the larger level as fast
as possible.
The main class of a deeply zoomable image that is represented by a hierarchy of tile layers for each zoom
level. This gives the user the impression that even huge pictures (up to gigapixel-images) can be zoomed
instantaneously, since the tiles at smaller levels are scaled immediately and overloaded by more detailed
tiles at the larger level as fast as possible.
</p>
<br />
<div id="app">
@ -42,7 +44,6 @@
<div id="info"></div>
</div>
<script class="doctest">
// When an element is added, the ScatterApp wrapps it in it's own Scatter Container.
// Just as in the doctest: scatter.html
class ScatterApp extends PIXIApp {
@ -66,11 +67,10 @@
app.destroy(true)
}
//A new canvas has to be created
//for the new view.
var canvas = document.createElement("canvas")
canvas_container.appendChild(canvas);
var canvas = document.createElement('canvas')
canvas_container.appendChild(canvas)
app = new ScatterApp({
resolution: state + 1,
@ -80,35 +80,32 @@
autoResize: false,
width: 128,
height: 128,
backgroundColor: 0xFFCCCCCC
}).setup().run()
backgroundColor: 0xffcccccc
})
.setup()
.run()
// To create a DeepZoomImage, a DeepZoomInfo has to
// be provided. It contains all the necessary informations
// for the DeepZoomImage, to behave as intended.
// (E.g. that it displays the right level of tiles for the current view distance.)
deepZoomInfo = new DeepZoomInfo(
{
"tileSize": 128,
"format": "jpg",
"overlap": 0,
"type": "map",
"height": 4096,
"width": 4096,
"path": "../assets/maps/test",
"urlTileTemplate": "{path}/{level}/{column}/{row}.{format}"
});
deepZoomInfo = new DeepZoomInfo({
tileSize: 128,
format: 'jpg',
overlap: 0,
type: 'map',
height: 4096,
width: 4096,
path: '../assets/maps/test',
urlTileTemplate: '{path}/{level}/{column}/{row}.{format}'
})
// Create the DeepZoomImage
deepZoomImage = new DeepZoomImage(deepZoomInfo, {
highResolution: !!state,
app
});
})
deepZoomImage.scatter = new DisplayObjectScatter(deepZoomImage, app.renderer, {
// Allow more flexible scaling for debugging purposes.
@ -119,25 +116,20 @@
onTransform: (event) => {
deepZoomImage.transformed(event)
}
});
})
// Add the DeepZoomImage to the scene.
app.scene.addChild(deepZoomImage)
//Set info text.
info.innerHTML = "resolution: " + app.renderer.resolution +
"<br>high resolution: " + !!state;
info.innerHTML = 'resolution: ' + app.renderer.resolution + '<br>high resolution: ' + !!state
}
// Add functionality to the button.
change_dpr.addEventListener("click", (event) => {
change_dpr.addEventListener('click', (event) => {
state = (state + 1) % 2
changePIXI()
})
</script>
</body>
</html>

23
lib/pixi/deepzoom/index.html
View File

@ -2,8 +2,11 @@
<head>
<title>PIXI Lib Doctests</title>
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent" />
<meta name="viewport" content="width=device-width, height=device-height, initial-scale=1.0, user-scalable=0, minimum-scale=1.0, maximum-scale=1.0" />
<link rel="stylesheet" href="../../../css/index.css">
<meta
name="viewport"
content="width=device-width, height=device-height, initial-scale=1.0, user-scalable=0, minimum-scale=1.0, maximum-scale=1.0"
/>
<link rel="stylesheet" href="../../../css/index.css" />
<script src="../../../dist/iwmlib.js"></script>
@ -12,7 +15,7 @@
<div class="preview">
<div class="thumbnail-container">
<div class="thumbnail">
<img class="icon" >
<img class="icon" />
<!-- <iframe src="" frameborder="0"></iframe> -->
</div>
</div>
@ -23,15 +26,19 @@
</head>
<body>
<div id="container" class="container">
<a style="position: absolute; left: 22px; top: 12px;" target="_blank" href="http://www.iwm-tuebingen.de">IWM</a>
<a style="position: absolute; left: 22px; top: 12px" target="_blank" href="http://www.iwm-tuebingen.de"
>IWMLib PIXI DeepZoom</a
>
</div>
<script>
const index = new Index(itemTemplate, [
const index = new Index(
itemTemplate,
[
['Deepzoom', 'deepzoom.html'],
['Image', 'image.html'],
['Image', 'image.html']
],
null)
null
)
index.load()
</script>
</body>

14
lib/pixi/flipeffect.html
View File

@ -16,12 +16,12 @@
<div class="flipWrapper">
<div class="flipCard">
<img class="flipFace front" src="" />
<div class="flipFace back" style="visibility:hidden;"></div>
<div class="flipFace back" style="visibility: hidden"></div>
</div>
<!-- Very tricky problem to scale svgs: see https://css-tricks.com/scale-svg/ -->
<svg
class="flipButton backBtn"
style="visibility:hidden;"
style="visibility: hidden"
viewBox="0 0 100 100"
preserveAspectRatio="xMidYMid meet"
>
@ -41,9 +41,7 @@
</template>
</head>
<body onload="Doctest.run()">
<h1>
Flip Effect
</h1>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>Flip Effect</h1>
<p>
The flip effect, which simulates a flip between a front and back view of an object by means of a 3D
rotation, is an interaction between a PIXI scatter object and a DOM Flip effect. The PIXI scatter is used as
@ -63,10 +61,8 @@
</li>
<li>If the back card is closed, the DOM nodes are removed and the PIXI scatter is shown again.</li>
</ul>
<h3>
Example
</h3>
<main id="main" style="border: 1px solid red; position: relative;">
<h3>Example</h3>
<main id="main" style="border: 1px solid red; position: relative">
<canvas id="canvas" class="grayBorder interactive">Canvas not supported</canvas>
</main>
<script class="doctest">

74
lib/pixi/flippable.html
View File

@ -1,12 +1,12 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>PIXI Flippable</title>
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../../css/doctest.css">
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../css/doctest.css" />
<script src="../3rdparty/highlight/highlight.pack.js"></script>
<script src="../../dist/iwmlib.3rdparty.js"></script>
@ -17,27 +17,29 @@
<script src="../3rdparty/gsap/src/minified/TweenMax.min.js"></script>
</head>
<body onload="Doctest.run()">
<h1>Flippable</h1>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>Flippable</h1>
<p>
Using the Flippable class, any PIXI element (PIXI.DisplayObject) can be back-mounted
(which can include another PIXI.DisplayObject), and turning it over to the back can
be adjusted by many parameters in speed and behavior.
Using the Flippable class, any PIXI element (PIXI.DisplayObject) can be back-mounted (which can include
another PIXI.DisplayObject), and turning it over to the back can be adjusted by many parameters in speed and
behavior.
</p>
<p><a href="../../doc/out/Flippable.html">JavaScript API</a></p>
<p>Let's look at some flippable examples:</p><br />
<p>Let's look at some flippable examples:</p>
<br />
<canvas id="canvas" class="interactive"></canvas>
<p>
What you should see: Six flippable elements and one button.
</p>
<p>What you should see: Six flippable elements and one button.</p>
<script class="doctest">
const app = new PIXIApp({
view: canvas,
width: 900,
height: 420,
transparent: false
}).setup().run()
})
.setup()
.run()
app.loadTextures([
app.loadTextures(
[
'./assets/fruit-1.jpg',
'./assets/fruit-2.jpg',
'./assets/fruit-3.jpg',
@ -48,13 +50,13 @@ app.loadTextures([
'./assets/fruit-8.jpg',
'./assets/fruit-9.jpg',
'./assets/fruit-10.jpg'
], textures => {
],
(textures) => {
// Example 1
//--------------------
const sprite1 = new PIXI.Sprite(textures.get('./assets/fruit-1.jpg'))
sprite1.position.set(10, 10)
sprite1.scale.set(.2, .2)
sprite1.scale.set(0.2, 0.2)
const sprite2 = new PIXI.Sprite(textures.get('./assets/fruit-2.jpg'))
const flippable1 = new Flippable(sprite1, sprite2, app.renderer)
@ -63,25 +65,25 @@ app.loadTextures([
//--------------------
const sprite3 = new PIXI.Sprite(textures.get('./assets/fruit-3.jpg'))
sprite3.position.set(10, 120)
sprite3.scale.set(.2, .2)
sprite3.scale.set(0.2, 0.2)
const sprite4 = new PIXI.Sprite(textures.get('./assets/fruit-4.jpg'))
const flippable2 = new Flippable(sprite3, sprite4, app.renderer, {
duration: 6,
ease: Bounce.easeOut,
shadow: true,
eulerX: .8
eulerX: 0.8
})
// Example 3
//--------------------
const sprite5 = new PIXI.Sprite(textures.get('./assets/fruit-5.jpg'))
sprite5.position.set(10, 240)
sprite5.scale.set(.2, .2)
sprite5.scale.set(0.2, 0.2)
const sprite6 = new PIXI.Sprite(textures.get('./assets/fruit-6.jpg'))
sprite6.position.set(400, 180)
sprite6.scale.set(.3, .3)
sprite6.rotation = .3
sprite6.scale.set(0.3, 0.3)
sprite6.rotation = 0.3
const flippable3 = new Flippable(sprite5, sprite6, app.renderer, {
duration: 4,
@ -94,11 +96,11 @@ app.loadTextures([
//--------------------
const sprite7 = new PIXI.Sprite(textures.get('./assets/fruit-7.jpg'))
sprite7.position.set(700, 10)
sprite7.scale.set(.2, .2)
sprite7.scale.set(0.2, 0.2)
const sprite8 = new PIXI.Sprite(textures.get('./assets/fruit-8.jpg'))
sprite8.position.set(550, 180)
sprite8.scale.set(.15, .15)
sprite8.skew.set(0, .1)
sprite8.scale.set(0.15, 0.15)
sprite8.skew.set(0, 0.1)
const flippable4 = new Flippable(sprite7, sprite8, app.renderer, {
duration: 5,
@ -115,12 +117,12 @@ app.loadTextures([
//--------------------
const sprite9 = new PIXI.Sprite(textures.get('./assets/fruit-9.jpg'))
sprite9.position.set(700, 130)
sprite9.scale.set(.2, .2)
sprite9.skew.set(.2, .2)
sprite9.scale.set(0.2, 0.2)
sprite9.skew.set(0.2, 0.2)
const sprite10 = new PIXI.Sprite(textures.get('./assets/fruit-10.jpg'))
sprite10.position.set(700, 130)
sprite10.scale.set(.2, .2)
sprite10.skew.set(-.2, -.2)
sprite10.scale.set(0.2, 0.2)
sprite10.skew.set(-0.2, -0.2)
const flippable5 = new Flippable(sprite9, sprite10, app.renderer, {
duration: 2,
@ -143,13 +145,13 @@ app.loadTextures([
graphic2.beginFill(0xcedc9c, 1)
graphic2.drawRect(0, 0, 160, 100)
for (let i = 0; i < 1000; i++) {
graphic2.beginFill(Math.random() * 0xffffff << 0, 1)
graphic2.lineStyle(1, Math.random() * 0xffffff << 0, 1)
graphic2.beginFill((Math.random() * 0xffffff) << 0, 1)
graphic2.lineStyle(1, (Math.random() * 0xffffff) << 0, 1)
graphic2.drawCircle(Math.random() * 160, Math.random() * 100, 2)
}
const flippable6 = new Flippable(graphic1, graphic2, app.renderer, {
eulerX: -.3
eulerX: -0.3
})
// Button
@ -159,7 +161,7 @@ app.loadTextures([
y: 10,
label: 'Toggle',
type: 'checkbox',
action: e => {
action: (e) => {
flippable1.toggle()
flippable2.toggle()
flippable3.toggle()
@ -170,7 +172,9 @@ app.loadTextures([
})
app.scene.addChild(sprite1, sprite3, sprite5, sprite7, sprite9, graphic1, button)
}, {resolutionDependent: false})
},
{ resolutionDependent: false }
)
</script>
</body>
</html>

2
lib/pixi/flippable.test.html
View File

@ -13,7 +13,7 @@
</head>
<body onload="Doctest.run();" >
<h1>
Functional Tests
<a href="../index.html">lib.</a><a href="index.html">pixi.</a>Functional Tests
</h1>
<p>
If you want to test the UI in all functional aspects, it'is important to be able

90
lib/pixi/forcelayout.html
View File

@ -1,12 +1,12 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>PIXI ForceLayout</title>
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../../css/doctest.css">
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../css/doctest.css" />
<script src="../3rdparty/highlight/highlight.pack.js"></script>
<script src="../../dist/iwmlib.3rdparty.js"></script>
@ -18,25 +18,27 @@
<script src="./lib/graphology-layout-forceatlas2.js"></script>
</head>
<body onload="Doctest.run()">
<h1>ForceLayout</h1>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>ForceLayout</h1>
<p>
Comparison of a <a href="https://github.com/d3/d3-force/blob/master/README.md">D3 ForceLayout</a> with a <a href="https://github.com/graphology/graphology-layout-forceatlas2">ForceAtlas 2</a> forcelayout.
Comparison of a <a href="https://github.com/d3/d3-force/blob/master/README.md">D3 ForceLayout</a> with a
<a href="https://github.com/graphology/graphology-layout-forceatlas2">ForceAtlas 2</a> forcelayout.
</p>
<h2>Let's look at the D3 ForceLayout:</h2><br />
<h2>Let's look at the D3 ForceLayout:</h2>
<br />
<canvas id="canvas" class="interactive"></canvas>
<script class="doctest">
const app = new PIXIApp({
view: canvas,
width: 900,
height: 420,
transparent: false
}).setup().run()
app.loadTextures([
'./assets/circle.png'
], textures => {
})
.setup()
.run()
app.loadTextures(
['./assets/circle.png'],
(textures) => {
// add sprites
//--------------------
const sprites = []
@ -46,7 +48,7 @@ app.loadTextures([
sprite.x = randomInt(0, app.size.width)
sprite.y = randomInt(0, app.size.height)
sprite.width = sprite.height = 2
sprite.anchor.set(.5, .5)
sprite.anchor.set(0.5, 0.5)
sprite.__random = Math.random()
sprites.push(sprite)
}
@ -55,8 +57,9 @@ app.loadTextures([
// force simulation
//--------------------
const forceCollide = d3.forceCollide().radius(d => d.width / 2 + 1)
const simulation = d3.forceSimulation(sprites)
const forceCollide = d3.forceCollide().radius((d) => d.width / 2 + 1)
const simulation = d3
.forceSimulation(sprites)
.on('tick', () => {
//forceCollide.radius(d => d.radius)
})
@ -64,33 +67,41 @@ app.loadTextures([
.force('x', d3.forceX(app.center.x))
.force('y', d3.forceY(app.center.y))
.stop()
.force('radial', d3.forceRadial(d => {
return d.__random < .5 ? 60 : 160
}, app.center.x, app.center.y))
.force(
'radial',
d3.forceRadial(
(d) => {
return d.__random < 0.5 ? 60 : 160
},
app.center.x,
app.center.y
)
)
d3.timeout(() => {
simulation.restart()
}, 500)
}, {resolutionDependent: false})
},
{ resolutionDependent: false }
)
</script>
<h2>D3 ForceLayout with links:</h2><br />
<h2>D3 ForceLayout with links:</h2>
<br />
<canvas id="canvas2" class="interactive"></canvas>
<script class="doctest">
const app2 = new PIXIApp({
view: canvas2,
width: 900,
height: 420,
transparent: false
}).setup().run()
app2.loadTextures([
'./assets/circle2.png'
], textures => {
})
.setup()
.run()
app2.loadTextures(
['./assets/circle2.png'],
(textures) => {
// add sprites
//--------------------
const sprites = []
@ -101,7 +112,7 @@ app2.loadTextures([
sprite.x = randomInt(0, app2.size.width)
sprite.y = randomInt(0, app2.size.height)
sprite.width = sprite.height = 16
sprite.anchor.set(.5, .5)
sprite.anchor.set(0.5, 0.5)
sprites.push(sprite)
}
@ -112,8 +123,9 @@ app2.loadTextures([
// force simulation
//--------------------
const forceCollide = d3.forceCollide().radius(d => d.width / 2 + 4)
const forceLink = d3.forceLink([
const forceCollide = d3.forceCollide().radius((d) => d.width / 2 + 4)
const forceLink = d3
.forceLink([
{ source: 88, target: 8 },
{ source: 47, target: 55 },
{ source: 70, target: 1 },
@ -140,8 +152,11 @@ app2.loadTextures([
{ source: 84, target: 25 },
{ source: 57, target: 58 },
{ source: 87, target: 19 }
]).id(d => d.id).strength(.05)
const simulation = d3.forceSimulation(sprites)
])
.id((d) => d.id)
.strength(0.05)
const simulation = d3
.forceSimulation(sprites)
.on('tick', () => {
links.clear()
links.lineStyle(1, 0xfdc02f)
@ -157,8 +172,9 @@ app2.loadTextures([
d3.timeout(() => {
simulation.restart()
}, 1000)
}, {resolutionDependent: false})
},
{ resolutionDependent: false }
)
</script>
</body>
</html>

20
lib/pixi/index.html
View File

@ -2,8 +2,11 @@
<head>
<title>PIXI Lib Doctests</title>
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent" />
<meta name="viewport" content="width=device-width, height=device-height, initial-scale=1.0, user-scalable=0, minimum-scale=1.0, maximum-scale=1.0" />
<link rel="stylesheet" href="../../css/index.css">
<meta
name="viewport"
content="width=device-width, height=device-height, initial-scale=1.0, user-scalable=0, minimum-scale=1.0, maximum-scale=1.0"
/>
<link rel="stylesheet" href="../../css/index.css" />
<script src="../../dist/iwmlib.js"></script>
@ -12,7 +15,7 @@
<div class="preview">
<div class="thumbnail-container">
<div class="thumbnail">
<img class="icon" src="thumbnails/notfound.png">
<img class="icon" src="thumbnails/notfound.png" />
<!-- <iframe src="" frameborder="0"></iframe> -->
</div>
</div>
@ -23,10 +26,14 @@
</head>
<body>
<div id="container" class="container">
<a style="position: absolute; left: 22px; top: 12px;" target="_blank" href="http://www.iwm-tuebingen.de">IWM</a>
<a style="position: absolute; left: 22px; top: 12px" target="_blank" href="http://www.iwm-tuebingen.de"
>IWMLib PIXI Doctests</a
>
</div>
<script>
const index = new Index(itemTemplate, [
const index = new Index(
itemTemplate,
[
['PIXI.Application', 'application.html'],
['Application', 'app.html'],
['Badge', 'badge.html'],
@ -56,7 +63,8 @@ const index = new Index(itemTemplate, [
['Scrollview', 'scrollview.html'],
['Stylus', 'stylus.html']
],
null)
null
)
index.load()
</script>
</body>

44
lib/pixi/labeledgraphics.html
View File

@ -1,12 +1,12 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>PIXI LabeledGraphics</title>
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../../css/doctest.css">
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../css/doctest.css" />
<script src="../3rdparty/highlight/highlight.pack.js"></script>
<script src="../../dist/iwmlib.3rdparty.js"></script>
@ -15,24 +15,24 @@
<script src="../../dist/iwmlib.pixi.js"></script>
</head>
<body onload="Doctest.run()">
<h1>LabeledGraphics</h1>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>LabeledGraphics</h1>
<p>
A labeled graphics extends the PIXI.Graphics class with an ensureLabel method that allows
to place and reuse labels, i.e. PIXI.Text objects. The labels are cached by a given key
and only rendered anew if necessary.
A labeled graphics extends the PIXI.Graphics class with an ensureLabel method that allows to place and reuse
labels, i.e. PIXI.Text objects. The labels are cached by a given key and only rendered anew if necessary.
</p>
<p><a href="../../doc/out/LabeledGraphics.html">JavaScript API</a></p>
<p>Let's look at an example:</p><br />
<p>Let's look at an example:</p>
<br />
<canvas id="canvas1" class="interactive"></canvas>
<p>
What you should see: A box with a label.
</p>
<p>What you should see: A box with a label.</p>
<script class="doctest">
const app = new PIXIApp({
view: canvas1,
width: 900,
height: 150
}).setup().run()
})
.setup()
.run()
const labeledBox = new LabeledGraphics()
labeledBox.ensureLabel('key', 'This is a label in a box', { justify: 'top' })
@ -43,8 +43,9 @@ labeledBox.endFill()
app.scene.addChild(labeledBox)
</script>
<h2>Zoomable Labels</h2>
<p>Labeled graphics can also be used to represent zoomable text columns in more complex layouts.
Use the mousewheel to zoom the following text column:
<p>
Labeled graphics can also be used to represent zoomable text columns in more complex layouts. Use the
mousewheel to zoom the following text column:
</p>
<canvas id="canvas2" class="interactive"></canvas>
@ -53,13 +54,20 @@ const app2 = new PIXIApp({
view: canvas2,
width: 900,
height: 150
}).setup().run()
})
.setup()
.run()
const loremIpsum = `Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua.
At vero eos et accusam et justo duo dolores et ea rebum.`
const column = new LabeledGraphics()
const text = column.ensureLabel('key', loremIpsum, { maxWidth: 250, zoomFonts: true, justify: 'top', align: 'align'})
const text = column.ensureLabel('key', loremIpsum, {
maxWidth: 250,
zoomFonts: true,
justify: 'top',
align: 'align'
})
column.beginFill(0x333333)
column.drawRect(0, 0, 900, 150)
column.endFill()
@ -80,5 +88,5 @@ app2.view.addEventListener('mousewheel', (event) => {
app2.scene.addChild(column)
</script>
</body>
</html>

74
lib/pixi/list.html
View File

@ -1,12 +1,12 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>PIXI List</title>
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../../css/doctest.css">
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../css/doctest.css" />
<script src="../3rdparty/highlight/highlight.pack.js"></script>
<script src="../../dist/iwmlib.3rdparty.js"></script>
@ -16,26 +16,25 @@
<script src="../../dist/iwmlib.js"></script>
</head>
<body onload="Doctest.run()">
<h1>List</h1>
<p>
Using the List class, any PIXI elements (PIXI.DisplayObject) can be included
in a scrollable list.
</p>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>List</h1>
<p>Using the List class, any PIXI elements (PIXI.DisplayObject) can be included in a scrollable list.</p>
<p><a href="../../doc/out/List.html">JavaScript API</a></p>
<p>Let's look at some list examples:</p><br />
<p>Let's look at some list examples:</p>
<br />
<canvas id="canvas" class="interactive"></canvas>
<p>
What you should see: Three lists, one horizontal and two vertical.
</p>
<p>What you should see: Three lists, one horizontal and two vertical.</p>
<script class="doctest">
const app = new PIXIApp({
view: canvas,
width: 900,
height: 420,
transparent: false
}).setup().run()
})
.setup()
.run()
app.loadTextures([
app.loadTextures(
[
'./assets/elephant-1.jpg',
'./assets/elephant-2.jpg',
'./assets/elephant-3.jpg',
@ -46,8 +45,8 @@ app.loadTextures([
'./assets/bamboo-3.jpg',
'./assets/bamboo-4.jpg',
'./assets/bamboo-5.jpg'
], textures => {
],
(textures) => {
// Example 1
//--------------------
const elephant1 = new PIXI.Sprite(textures.get('./assets/elephant-1.jpg'))
@ -57,7 +56,7 @@ app.loadTextures([
const elephant5 = new PIXI.Sprite(textures.get('./assets/elephant-5.jpg'))
const elephants = [elephant1, elephant2, elephant3, elephant4, elephant5]
elephants.forEach(it => it.scale.set(.1, .1))
elephants.forEach((it) => it.scale.set(0.1, 0.1))
const elephantList = new List(elephants)
elephantList.x = 10
@ -72,7 +71,7 @@ app.loadTextures([
const bamboo5 = new PIXI.Sprite(textures.get('./assets/bamboo-5.jpg'))
const bamboos = [bamboo1, bamboo2, bamboo3, bamboo4, bamboo5]
bamboos.forEach(it => it.scale.set(.15, .15))
bamboos.forEach((it) => it.scale.set(0.15, 0.15))
const bambooList = new List(bamboos, {
orientation: 'horizontal',
@ -92,8 +91,8 @@ app.loadTextures([
for (let i = 0; i < 1000; i++) {
const text = new PIXI.Text(`Example Text ${i}`, style)
text.interactive = true
text.on('tap', event => console.log(`tap text ${i}`))
text.on('click', event => console.log(`click text ${i}`))
text.on('tap', (event) => console.log(`tap text ${i}`))
text.on('click', (event) => console.log(`click text ${i}`))
texts.push(text)
}
@ -109,36 +108,35 @@ app.loadTextures([
// Add to scene
//--------------------
app.scene.addChild(elephantList, bambooList, textList)
}, {resolutionDependent: false})
},
{ resolutionDependent: false }
)
</script>
<h1>List in a Scatter</h1>
<p>
A PixiJS UI List is displayed inside a ScatterObject.
</p>
<p>A PixiJS UI List is displayed inside a ScatterObject.</p>
<canvas id="canvas2" class="interactive"></canvas>
<p>
What you should see: A ScatterObject with a list in it.
</p>
<p>What you should see: A ScatterObject with a list in it.</p>
<script class="doctest">
const app2 = new PIXIApp({
view: canvas2,
width: 900,
height: 420,
transparent: false
}).setup().run()
})
.setup()
.run()
app2.loadTextures([
app2.loadTextures(
[
'./assets/jungle.jpg',
'./assets/elephant-1.jpg',
'./assets/elephant-2.jpg',
'./assets/elephant-3.jpg',
'./assets/elephant-4.jpg',
'./assets/elephant-5.jpg'
], textures => {
],
(textures) => {
// ScatterContainer
//--------------------
const scatterContainer = new ScatterContainer(app2.renderer, {
@ -174,7 +172,7 @@ app.loadTextures([
const elephant5 = new PIXI.Sprite(textures.get('./assets/elephant-5.jpg'))
const elephants = [elephant1, elephant2, elephant3, elephant4, elephant5]
elephants.forEach(it => it.scale.set(.15, .15))
elephants.forEach((it) => it.scale.set(0.15, 0.15))
const elephantList = new List(elephants, {
height: 200
@ -185,7 +183,9 @@ app.loadTextures([
// Add to scene
//--------------------
jungle.addChild(elephantList)
}, {resolutionDependent: false})
},
{ resolutionDependent: false }
)
</script>
</body>
</html>

2
lib/pixi/maps/geographics.html
View File

@ -32,7 +32,7 @@
<body onload='Doctest.run()'>
<h1>GeoGraphics</h1>
<h1><a href="../../index.html">lib.</a><a href="../index.html">pixi.</a><a href="index.html">maps.</a>GeoGraphics</h1>
<p> GeoGraphics are graphical objects, that does not store the graphics information
in screen space, but in geographical coordinates. Therefore GeoGraphics must be
placed on GeoLayers to work properly. </p>

2
lib/pixi/maps/geojson.html
View File

@ -85,7 +85,7 @@
</head>
<body onload='Doctest.run()'>
<h1>GeoJson</h1>
<h1><a href="../../index.html">lib.</a><a href="../index.html">pixi.</a><a href="index.html">maps.</a>GeoJson</h1>
<p>GeoJson is a standardized format of how to display geometry in a geographical context, using latitude/longitude
pairs
to display one (or multiple) Point, Line or Polygon.

98
lib/pixi/maps/map.html
View File

@ -1,21 +1,19 @@
<!DOCTYPE html>
<html lang="en" class="dark-mode">
<head>
<meta charset="UTF-8" />
<title>Map</title>
<script src="../../3rdparty/highlight/highlight.pack.js"></script>
<link rel="stylesheet" href="../../../fonts/material-icon-font/material-icons.css">
<link rel='stylesheet' href='../../3rdparty/highlight/styles/vs2015.css'>
<link rel='stylesheet' href='../../../css/doctest.css'>
<link rel="stylesheet" href="../../../fonts/material-icon-font/material-icons.css" />
<link rel="stylesheet" href="../../3rdparty/highlight/styles/vs2015.css" />
<link rel="stylesheet" href="../../../css/doctest.css" />
<script src="../../../dist/iwmlib.3rdparty.js"></script>
<script src="../../../dist/iwmlib.js"></script>
<script src="../../../dist/iwmlib.pixi.js"></script>
<style>
.controls {
display: flex;
@ -24,49 +22,39 @@
</head>
<body onload="Doctest.run()">
<h1>Map</h1>
<p>
The Map class shows a geographical map using a scatter element.
</p>
<h1><a href="../../index.html">lib.</a><a href="../index.html">pixi.</a><a href="index.html">maps.</a>Map</h1>
<p>The Map class shows a geographical map using a scatter element.</p>
<h2 id="DeepZoomMap">DeepZoomMap</h2>
<p>Usually a DeepZoomMap will be used to display maps. It uses a <a
href="../deepzoom/deepzoom.html">DeepZoomImage</a> to display the map in different resolutions depending on
the zoom factor.</p>
<canvas id="deepZoomCanvas">
</canvas>
<script>
</script>
<p>
Usually a DeepZoomMap will be used to display maps. It uses a
<a href="../deepzoom/deepzoom.html">DeepZoomImage</a> to display the map in different resolutions depending
on the zoom factor.
</p>
<canvas id="deepZoomCanvas"> </canvas>
<script></script>
<script class="doctest" data-collapsible data-collapsed data-title="Script">
(function () {
;(function () {
// Create the mapapp.
let app = window.DeepZoomMapApp = new MapApp({
let app = (window.DeepZoomMapApp = new MapApp({
view: deepZoomCanvas,
coordsLogging: true,
width: 512,
height: 512
})
}))
// Load or specify a tilesConfig as required by the DeepZoomImage.
const tilesConfig = {
"tileSize": 256,
"format": "png",
"overlap": 0,
"type": "map",
"height": 1024,
"width": 1024,
"path": "../assets/maps/osm",
"urlTileTemplate": "{path}/{level}/{row}/{column}.{format}"
tileSize: 256,
format: 'png',
overlap: 0,
type: 'map',
height: 1024,
width: 1024,
path: '../assets/maps/osm',
urlTileTemplate: '{path}/{level}/{row}/{column}.{format}'
}
// Create a projection.
const projection = new Projection.Mercator()
@ -77,7 +65,7 @@
const osmMap = new DeepZoomMap(osmDeepZoomMapProjection, tilesConfig)
// Add the map to the app.
app.addMap("osm", osmMap)
app.addMap('osm', osmMap)
// Run the app when at least one map is set.
app.setup().run()
@ -85,39 +73,31 @@
</script>
<h2 id="imageMap">ImageMap</h2>
<p>Single images can be also used as maps. This can be useful for examples, debugging purposes or other use-cases
when there are no different tiles required or available.</p>
<canvas id="imageMapCanvas">
</canvas>
<script>
</script>
<p>
Single images can be also used as maps. This can be useful for examples, debugging purposes or other
use-cases when there are no different tiles required or available.
</p>
<canvas id="imageMapCanvas"> </canvas>
<script></script>
<script class="doctest" data-collapsible data-collapsed data-title="Script">
(function () {
;(function () {
// Create the mapapp.
let app = window.ImageMapApp = new MapApp({
let app = (window.ImageMapApp = new MapApp({
view: imageMapCanvas,
coordsLogging: true,
width: 512,
height: 512
})
const mapTexture = "../assets/maps/wikimedia-world-robinson/2000px-BlankMap-World.png"
}))
const mapTexture = '../assets/maps/wikimedia-world-robinson/2000px-BlankMap-World.png'
// The images used by the image map need to be loaded beforehand.
// Therefore this loading step is required.
app.loadSprites([mapTexture], sprites => spritesLoaded(sprites), {
app.loadSprites([mapTexture], (sprites) => spritesLoaded(sprites), {
resolutionDependent: false
})
spritesLoaded = (sprites) => {
// Create a projection.
const projection = new Projection.Robinson(10)
@ -127,19 +107,13 @@
// Create the map
let imageMap = new ImageMap(sprites.get(mapTexture), mapProjection)
// Add the map to the app.
app.addMap("europe", imageMap)
app.addMap('europe', imageMap)
// Run the app when at least one map is set.
app.setup().run()
}
})()
</script>
</body>
</html>

86
lib/pixi/maps/mapapp.html
View File

@ -1,21 +1,19 @@
<!DOCTYPE html>
<html lang="en" class="dark-mode">
<head>
<meta charset="UTF-8" />
<title>MapApp</title>
<script src="../../3rdparty/highlight/highlight.pack.js"></script>
<link rel="stylesheet" href="../../../fonts/material-icon-font/material-icons.css">
<link rel='stylesheet' href='../../3rdparty/highlight/styles/vs2015.css'>
<link rel='stylesheet' href='../../../css/doctest.css'>
<link rel="stylesheet" href="../../../fonts/material-icon-font/material-icons.css" />
<link rel="stylesheet" href="../../3rdparty/highlight/styles/vs2015.css" />
<link rel="stylesheet" href="../../../css/doctest.css" />
<script src="../../../dist/iwmlib.3rdparty.js"></script>
<script src="../../../dist/iwmlib.js"></script>
<script src="../../../dist/iwmlib.pixi.js"></script>
<style>
.controls {
display: flex;
@ -24,11 +22,12 @@
</head>
<body onload="Doctest.run()">
<h1>MapApp</h1>
<h1>
<a href="../../index.html">lib.</a><a href="../index.html">pixi.</a><a href="index.html">maps.</a>MapApp
</h1>
<p>
This class extends the PIXIApp to simplify the process of rendering
Maps in the canvas. For that reason, it contains useful functions
for an easier handling of maps in the canvas.
This class extends the PIXIApp to simplify the process of rendering Maps in the canvas. For that reason, it
contains useful functions for an easier handling of maps in the canvas.
</p>
<canvas id="canvas"></canvas>
<div id="mapControl"></div>
@ -36,35 +35,34 @@
<p><strong>WHAT TO SEE:</strong> The map should focus Paris.</p>
<script>
let osmConfig = {
"projection": "mercator",
"type": "deepzoom",
"tiles": {
"tileSize": 256,
"format": "png",
"overlap": 0,
"type": "map",
"height": 1024,
"width": 1024,
"path": "../assets/maps/osm",
"urlTileTemplate": "{path}/{level}/{row}/{column}.{format}"
projection: 'mercator',
type: 'deepzoom',
tiles: {
tileSize: 256,
format: 'png',
overlap: 0,
type: 'map',
height: 1024,
width: 1024,
path: '../assets/maps/osm',
urlTileTemplate: '{path}/{level}/{row}/{column}.{format}'
}
}
let testConfig = {
"projection": "mercator",
"type": "deepzoom",
"tiles": {
"tileSize": 128,
"format": "jpg",
"overlap": 0,
"type": "map",
"height": 4096,
"width": 4096,
"path": "../assets/maps/test",
"urlTileTemplate": "{path}/{level}/{row}/{column}.{format}"
projection: 'mercator',
type: 'deepzoom',
tiles: {
tileSize: 128,
format: 'jpg',
overlap: 0,
type: 'map',
height: 4096,
width: 4096,
path: '../assets/maps/test',
urlTileTemplate: '{path}/{level}/{row}/{column}.{format}'
}
}
</script>
<script class="doctest">
let capitals = {
@ -94,7 +92,7 @@
let europe = '../assets/maps/pixabay/europe.jpg'
//Preload all required sprites for the image map.
app.loadSprites([europe], sprites => ready(sprites), {
app.loadSprites([europe], (sprites) => ready(sprites), {
resolutionDependent: false
})
@ -110,7 +108,6 @@
})
function ready(sprites) {
const cover = true
// When resources are loaded, the ImageMap can be instantiated.
@ -123,14 +120,18 @@
let testMapProjection = new DeepZoomMapProjection(new Projection.Mercator(), testConfig.tiles, {
app
})
let testMap = new DeepZoomMap(testMapProjection, Object.assign({}, testConfig.tiles, { app }), { cover })
app.addMap("test", testMap)
let testMap = new DeepZoomMap(testMapProjection, Object.assign({}, testConfig.tiles, { app }), {
cover
})
app.addMap('test', testMap)
let osmMapProjection = new DeepZoomMapProjection(new Projection.Mercator(), osmConfig.tiles, {
app
})
let deepZoomMap = new DeepZoomMap(osmMapProjection, Object.assign({}, osmConfig.tiles, { app }), { cover })
app.addMap("osm", deepZoomMap)
let deepZoomMap = new DeepZoomMap(osmMapProjection, Object.assign({}, osmConfig.tiles, { app }), {
cover
})
app.addMap('osm', deepZoomMap)
// Finally apply the map to the MapApp
app.setMap('europe', imageMap)
@ -140,9 +141,9 @@
app.setup().run()
for (let [key, val] of Object.entries(app.mapList.maps)) {
let mapBtn = document.createElement("button")
let mapBtn = document.createElement('button')
mapBtn.innerText = key
mapBtn.addEventListener("click", () => {
mapBtn.addEventListener('click', () => {
app.mapLayer.changeMap(val)
})
mapControl.appendChild(mapBtn)
@ -150,14 +151,13 @@
}
for (let [key, val] of Object.entries(capitals)) {
let cityBtn = document.createElement("button")
let cityBtn = document.createElement('button')
cityBtn.innerText = key
cityBtn.addEventListener("click", () => {
cityBtn.addEventListener('click', () => {
app.mapLayer.map.moveTo(val)
})
cityControl.appendChild(cityBtn)
}
</script>
</body>
</html>

2
lib/pixi/maps/mapprojection.html
View File

@ -37,7 +37,7 @@
</head>
<body onload='Doctest.run()'>
<h1>MapProjection</h1>
<h1><a href="../../index.html">lib.</a><a href="../index.html">pixi.</a><a href="index.html">maps.</a>MapProjection</h1>
<p>The map projection calculates is responsible for transforming map coordinates to pixel coordinates and backwards.</p>
<h2>Static Squared World Map</h2>

2
lib/pixi/maps/maps.html
View File

@ -30,7 +30,7 @@
</head>
<body onload='Doctest.run()'>
<h1>Maps</h1>
<h1><a href="../../index.html">lib.</a><a href="../index.html">pixi.</a><a href="index.html">maps.</a>Maps</h1>
<p>Maps represent a geographical image in a PIXI.Application. Preferably in a MapApp to have more convenient methods
to
handle the maps.</p>

87
lib/pixi/maps/mapviewport.html
View File

@ -1,21 +1,19 @@
<!DOCTYPE html>
<html lang="en" class="dark-mode">
<head>
<meta charset="UTF-8" />
<title>MapViewport</title>
<script src="../../3rdparty/highlight/highlight.pack.js"></script>
<link rel="stylesheet" href="../../../fonts/material-icon-font/material-icons.css">
<link rel='stylesheet' href='../../3rdparty/highlight/styles/vs2015.css'>
<link rel='stylesheet' href='../../../css/doctest.css'>
<link rel="stylesheet" href="../../../fonts/material-icon-font/material-icons.css" />
<link rel="stylesheet" href="../../3rdparty/highlight/styles/vs2015.css" />
<link rel="stylesheet" href="../../../css/doctest.css" />
<script src="../../../dist/iwmlib.3rdparty.js"></script>
<script src="../../../dist/iwmlib.js"></script>
<script src="../../../dist/iwmlib.pixi.js"></script>
<style>
.controls {
display: flex;
@ -24,11 +22,13 @@
</head>
<body onload="Doctest.run()">
<h1>MapViewport</h1>
<h1>
<a href="../../index.html">lib.</a><a href="../index.html">pixi.</a
><a href="index.html">maps.</a>MapViewport
</h1>
<p>
The MapViewport works under the hood of a map layer to track the informations about the current focus point and
zoom position.
This is important to maintain the same view when maps are changed.
The MapViewport works under the hood of a map layer to track the informations about the current focus point
and zoom position. This is important to maintain the same view when maps are changed.
</p>
<canvas id="canvas"></canvas>
<div id="mapControl"></div>
@ -36,35 +36,34 @@
<p><strong>WHAT TO SEE:</strong> The map should focus Paris.</p>
<script>
let osmConfig = {
"projection": "mercator",
"type": "deepzoom",
"tiles": {
"tileSize": 256,
"format": "png",
"overlap": 0,
"type": "map",
"height": 1024,
"width": 1024,
"path": "../assets/maps/osm",
"urlTileTemplate": "{path}/{level}/{row}/{column}.{format}"
projection: 'mercator',
type: 'deepzoom',
tiles: {
tileSize: 256,
format: 'png',
overlap: 0,
type: 'map',
height: 1024,
width: 1024,
path: '../assets/maps/osm',
urlTileTemplate: '{path}/{level}/{row}/{column}.{format}'
}
}
let testConfig = {
"projection": "mercator",
"type": "deepzoom",
"tiles": {
"tileSize": 128,
"format": "jpg",
"overlap": 0,
"type": "map",
"height": 4096,
"width": 4096,
"path": "../assets/maps/test",
"urlTileTemplate": "{path}/{level}/{row}/{column}.{format}"
projection: 'mercator',
type: 'deepzoom',
tiles: {
tileSize: 128,
format: 'jpg',
overlap: 0,
type: 'map',
height: 4096,
width: 4096,
path: '../assets/maps/test',
urlTileTemplate: '{path}/{level}/{row}/{column}.{format}'
}
}
</script>
<script class="doctest">
let capitals = {
@ -94,7 +93,7 @@
let europe = '../assets/maps/pixabay/europe.jpg'
//Preload all required sprites for the image map.
app.loadSprites([europe], sprites => ready(sprites), {
app.loadSprites([europe], (sprites) => ready(sprites), {
resolutionDependent: false
})
@ -110,7 +109,6 @@
})
function ready(sprites) {
const cover = true
// When resources are loaded, the ImageMap can be instantiated.
@ -123,14 +121,18 @@
let testMapProjection = new DeepZoomMapProjection(new Projection.Mercator(), testConfig.tiles, {
app
})
let testMap = new DeepZoomMap(testMapProjection, Object.assign({}, testConfig.tiles, { app }), { cover })
app.addMap("test", testMap)
let testMap = new DeepZoomMap(testMapProjection, Object.assign({}, testConfig.tiles, { app }), {
cover
})
app.addMap('test', testMap)
let osmMapProjection = new DeepZoomMapProjection(new Projection.Mercator(), osmConfig.tiles, {
app
})
let deepZoomMap = new DeepZoomMap(osmMapProjection, Object.assign({}, osmConfig.tiles, { app }), { cover })
app.addMap("osm", deepZoomMap)
let deepZoomMap = new DeepZoomMap(osmMapProjection, Object.assign({}, osmConfig.tiles, { app }), {
cover
})
app.addMap('osm', deepZoomMap)
// Finally apply the map to the MapApp
app.setMap('europe', imageMap)
@ -140,9 +142,9 @@
app.setup().run()
for (let [key, val] of Object.entries(app.mapList.maps)) {
let mapBtn = document.createElement("button")
let mapBtn = document.createElement('button')
mapBtn.innerText = key
mapBtn.addEventListener("click", () => {
mapBtn.addEventListener('click', () => {
app.mapLayer.changeMap(val)
})
mapControl.appendChild(mapBtn)
@ -150,14 +152,13 @@
}
for (let [key, val] of Object.entries(capitals)) {
let cityBtn = document.createElement("button")
let cityBtn = document.createElement('button')
cityBtn.innerText = key
cityBtn.addEventListener("click", () => {
cityBtn.addEventListener('click', () => {
app.mapLayer.map.moveTo(val)
})
cityControl.appendChild(cityBtn)
}
</script>
</body>
</html>

77
lib/pixi/maps/overlay.html
View File

@ -1,24 +1,20 @@
<!DOCTYPE html>
<html lang="en" class="dark-mode">
<head>
<meta charset="UTF-8" />
<title>Overlay</title>
<script src="../../3rdparty/highlight/highlight.pack.js"></script>
<link rel="stylesheet" href="../../../fonts/material-icon-font/material-icons.css">
<link rel='stylesheet' href='../../3rdparty/highlight/styles/vs2015.css'>
<link rel='stylesheet' href='../../../css/doctest.css'>
<link rel="stylesheet" href="../../../fonts/material-icon-font/material-icons.css" />
<link rel="stylesheet" href="../../3rdparty/highlight/styles/vs2015.css" />
<link rel="stylesheet" href="../../../css/doctest.css" />
<script src="../../../dist/iwmlib.3rdparty.js"></script>
<script src="../../../dist/iwmlib.js"></script>
<script src="../../../dist/iwmlib.pixi.js"></script>
<link rel="shortcut icon" type="image/x-icon" href="../../../assets/icons/map.png">
<link rel="shortcut icon" type="image/x-icon" href="../../../assets/icons/map.png" />
<style>
.inline-showcase {
@ -34,12 +30,11 @@
</head>
<body onload="Doctest.run()">
<h1 class="title">Overlay</h1>
<h1 class="title">
<a href="../../index.html">lib.</a><a href="../index.html">pixi.</a><a href="index.html">maps.</a>Overlay
</h1>
<!-- <a href="../../../" class="Documentation"></a> -->
<p class="description">
The overlayclass creates a convenient way to create and design
complex map overlays.
</p>
<p class="description">The overlayclass creates a convenient way to create and design complex map overlays.</p>
<canvas id="view" class="center"> </canvas>
<script>
let app = new MapApp({
@ -51,25 +46,17 @@
var osmworld = '../assets/maps/osm/0/0/0.png'
let worlOSMData = new MapProjection(new Projection.Mercator())
function setupMap(textures) {
// Create the map!
let map = new ImageMap(
new PIXI.Sprite(textures.get(osmworld)),
worlOSMData
)
let map = new ImageMap(new PIXI.Sprite(textures.get(osmworld)), worlOSMData)
// Setup the map in the mapapp.
app.setMap('osm', map)
app.setup().run()
}
</script>
<script class="doctest" data-collapsible data-collapsed data-title="Overlay Data">
/**
* To create an overlay you just need to create a JSON file.
* The styles defined in the styles are cascading, meaning that
@ -111,41 +98,39 @@
let exampleOverlayJSON = {
icon: '../../../assets/icons/place.png',
iconColor: "0x35aaea",
iconColor: '0x35aaea',
iconAnchor: { x: 0.5, y: 1 },
size: 5,
scale: 0.2,
disabledColor: 0x000000,
disabledIconColor: 0xCCCCCC,
disabledIconColor: 0xcccccc,
disabledScale: 0.5,
color: '0x3FA7EE',
items: [
{
name: 'Custom Icon',
fontWeight: "bold",
fontWeight: 'bold',
icon: '../../../assets/icons/beenhere.png',
iconColor: 0x00ff00,
iconAlpha: 0.5,
size: 0,
labelVerticalAlignment: "underneath",
labelVerticalAlignment: 'underneath',
label: 'Abidjan',
location: {
x: 5.34947,
y: -4.006472
},
information:
'Here a custom icon is used. It overrides the icon setting in the global section.'
information: 'Here a custom icon is used. It overrides the icon setting in the global section.'
},
{
name: 'Berlin',
label: "enabled",
disabledLabel: "disabled",
label: 'enabled',
disabledLabel: 'disabled',
location: {
x: 52.52543,
y: 13.385291
},
information:
'... ist die Bundeshauptstadt der Bundesrepublik Deutschland.',
information: '... ist die Bundeshauptstadt der Bundesrepublik Deutschland.',
enabled: false
},
{
@ -155,8 +140,7 @@
x: -35.282025,
y: 149.128648
},
information:
'... ist die Hauptstadt und achtgrößte Stadt Australiens.'
information: '... ist die Hauptstadt und achtgrößte Stadt Australiens.'
},
{
name: 'Kapstadt',
@ -165,8 +149,7 @@
x: -33.925448,
y: 18.416962
},
information:
`This item adjusts it's size according to the map.`
information: `This item adjusts it's size according to the map.`
},
{
name: 'Moskau',
@ -195,13 +178,12 @@
x: -22.8714,
y: -43.28049
},
information:
'... ist eine ausgedehnte brasilianische Küstenmetropole. '
information: '... ist eine ausgedehnte brasilianische Küstenmetropole. '
},
{
name: 'Tokio',
type: "factory",
label: "factory",
type: 'factory',
label: 'factory',
location: {
x: 35.696278,
y: 139.731366
@ -214,7 +196,6 @@
</script>
<script class="doctest" data-collapsible data-title="Overlay">
let overlay = new Overlay(exampleOverlayJSON)
/**
@ -225,13 +206,11 @@
let overlayTextures = overlay.findAllTextures()
let list = [osmworld].concat(overlayTextures)
app.loadTextures(list, textures => texturesLoaded(textures), {
app.loadTextures(list, (textures) => texturesLoaded(textures), {
resolutionDependent: false
})
function texturesLoaded(textures) {
/** When all textures are loaded .... */
setupMap(textures)
@ -244,12 +223,10 @@
const vanishingTime = 1000
// Factories must return a geographics object.
Overlay.createFactory("factory", (item) => {
Overlay.createFactory('factory', (item) => {
// This is applied to every item in the overlay that has
// the type factory'
let geographics = new GeoPoint(item.location)
geographics.drawHandler.add((graphics) => {
@ -260,7 +237,6 @@
let text = new PIXI.Text(item.name, { fontSize: 5 })
geographics.graphics.addChild(text)
return geographics
})
@ -282,7 +258,6 @@
// correct coordinates of the map.
app.mapLayer.addLayer(exampleOverlayGeoLayer)
// Just a helper function that clears the popups and removes
// a remaining cleaner timeout.
function clearPopup() {
@ -297,8 +272,6 @@
}
}
</script>
<script>
</script>
<script></script>
</body>
</html>

2
lib/pixi/maps/scatter.html
View File

@ -25,7 +25,7 @@
</head>
<body>
<h1>Scatter</h1>
<h1><a href="../../index.html">lib.</a><a href="../index.html">pixi.</a><a href="index.html">maps.</a>Scatter</h1>
<p>The Scatter in Tüsch specifies some classes to make them more suitable for Map applications.</p>
<h2>CoverScatter</h2>

116
lib/pixi/maps/utils.html
View File

@ -1,15 +1,14 @@
<!doctype html>
<html lang='en'>
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset='UTF-8'>
<meta charset="UTF-8" />
<title>Utils</title>
<link rel='stylesheet' href='../iwmlib/lib/3rdparty/highlight/styles/default.css'>
<link rel='stylesheet' href='../iwmlib/lib/../css/doctest.css'>
<script src='../iwmlib/lib/3rdparty/highlight/highlight.pack.js'></script>
<script src='../iwmlib/lib/3rdparty/all.js'></script>
<script src='../iwmlib/lib/all.js'></script>
<script src='../iwmlib/lib/pixi/all.js'></script>
<link rel="stylesheet" href="../../../lib/3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../../css/doctest.css" />
<script src="../../../lib/3rdparty/highlight/highlight.pack.js"></script>
<script src="../../../dist/iwmlib.3rdparty.js"></script>
<script src="../../../dist/iwmlib.js"></script>
<script src="../../../dist/iwmlib.pixi.js"></script>
<script src="all.js"></script>
<style>
@ -20,62 +19,72 @@
</head>
<body onload="Doctest.run()">
<h1>Utils</h1>
<h1><a href="../../index.html">lib.</a><a href="../index.html">pixi.</a><a href="index.html">maps.</a>Utils</h1>
<p>Some utility functionalities for the Tuesch.</p>
<h2>Event Handler</h2>
<p>
The event handler class generalizes a common design principle in javascript. When an event occurs, that is of relevance for
other objects, then this event should be sent out to all objects, that are interested in that event. Objects interested
in that event, subscribe the event handler and get notified via a callback function.
The event handler class generalizes a common design principle in javascript. When an event occurs, that is
of relevance for other objects, then this event should be sent out to all objects, that are interested in
that event. Objects interested in that event, subscribe the event handler and get notified via a callback
function.
</p>
<script class="doctest">
let result = []
function a() { result.push("a") }
function b() { result.push("b") }
function c() { result.push("c") }
function d() { result.push("d") }
function e() { result.push("e") }
function f() { result.push("f") }
function a() {
result.push('a')
}
function b() {
result.push('b')
}
function c() {
result.push('c')
}
function d() {
result.push('d')
}
function e() {
result.push('e')
}
function f() {
result.push('f')
}
//Init and call.
let eventHandler = new EventHandler("manual", { listeners: [a, b] })
let eventHandler = new EventHandler('manual', { listeners: [a, b] })
eventHandler.call()
Doctest.expect(result.join(","), ["a", "b"].join(","))
Doctest.expect(result.join(','), ['a', 'b'].join(','))
result = []
// Add single
eventHandler.add(c)
eventHandler.call()
Doctest.expect(result.join(","), ["a", "b", "c"].join(","))
Doctest.expect(result.join(','), ['a', 'b', 'c'].join(','))
result = []
// Add multiple
eventHandler.addMultiple(d, e, f)
eventHandler.call()
Doctest.expect(result.join(","), ["a", "b", "c", "d", "e", "f"].join(","))
Doctest.expect(result.join(','), ['a', 'b', 'c', 'd', 'e', 'f'].join(','))
result = []
//Remove inbetween
eventHandler.remove(c)
eventHandler.call()
Doctest.expect(result.join(","), ["a", "b", "d", "e", "f"].join(","))
Doctest.expect(result.join(','), ['a', 'b', 'd', 'e', 'f'].join(','))
result = []
// Remove first
eventHandler.remove(a)
eventHandler.call()
Doctest.expect(result.join(","), ["b", "d", "e", "f"].join(","))
Doctest.expect(result.join(','), ['b', 'd', 'e', 'f'].join(','))
result = []
// Remove all remaining elements.
eventHandler.empty()
eventHandler.call()
Doctest.expect(result.join(","), [].join(","))
Doctest.expect(result.join(','), [].join(','))
result = []
</script>
<h2>DomUtils</h2>
@ -85,15 +94,23 @@
<h3>positionOnElement(element, position)</h3>
Function that returns the global position for a normalized position.
<div id="positionOnElementBox" class="box" style="width: 512px;height:256px;border: 1px solid black; box-sizing: border-box; transform: rotate(30deg); margin:100px;"></div>
<div
id="positionOnElementBox"
class="box"
style="
width: 512px;
height: 256px;
border: 1px solid black;
box-sizing: border-box;
transform: rotate(30deg);
margin: 100px;
"
></div>
<script class="doctest">
let target = document.getElementById('positionOnElementBox')
let target = document.getElementById("positionOnElementBox")
window.addEventListener("load", () => {
window.addEventListener('load', () => {
let positions = [
[0, 0],
[0, 1],
@ -102,33 +119,28 @@
[0.2, 0.2],
[0.2, 0.8],
[0.8, 0.2],
[0.8, 0.8],
[0.8, 0.8]
]
positions.forEach(position => {
positions.forEach((position) => {
position = { x: position[0], y: position[1] }
let transformedPosition = DomUtils.positionOnElement(target, position)
let dot = document.createElement("div");
const size = 10;
let dot = document.createElement('div')
const size = 10
Object.assign(dot.style, {
width: size + "px",
height: size + "px",
top: target.offsetTop + target.offsetHeight / 2 + transformedPosition.y -size/2+ "px",
left: target.offsetLeft + target.offsetWidth / 2 + transformedPosition.x -size/2 + "px",
position: "absolute",
backgroundColor: "green",
borderRadius: "50%"
width: size + 'px',
height: size + 'px',
top: target.offsetTop + target.offsetHeight / 2 + transformedPosition.y - size / 2 + 'px',
left: target.offsetLeft + target.offsetWidth / 2 + transformedPosition.x - size / 2 + 'px',
position: 'absolute',
backgroundColor: 'green',
borderRadius: '50%'
})
document.body.appendChild(dot)
})
})
</script>
</body>
</html>

31
lib/pixi/message.html
View File

@ -1,12 +1,12 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>PIXI Message</title>
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../../css/doctest.css">
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../css/doctest.css" />
<script src="../3rdparty/highlight/highlight.pack.js"></script>
<script src="../../dist/iwmlib.3rdparty.js"></script>
@ -15,27 +15,29 @@
<script src="../../dist/iwmlib.pixi.js"></script>
</head>
<body onload="Doctest.run()">
<h1>Message</h1>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>Message</h1>
<p>
A message box is a timed popup window. By default, the message window appears in the upper right corner and disappears after 5 seconds.
A message box is a timed popup window. By default, the message window appears in the upper right corner and
disappears after 5 seconds.
</p>
<p><a href="../../doc/out/Message.html">JavaScript API</a></p>
<p>Let's look at some message examples:</p><br />
<p>Let's look at some message examples:</p>
<br />
<canvas id="canvas" class="interactive"></canvas>
<p>
What you should see: Two buttons which start message windows.
</p>
<p>What you should see: Two buttons which start message windows.</p>
<script class="doctest">
const app = new PIXIApp({
view: canvas,
width: 900,
height: 250
}).setup().run()
})
.setup()
.run()
let button1 = new Button({
x: 0,
label: 'Default message',
action: e => {
action: (e) => {
const message = new Message({
app: app,
header: 'Dies ist die Überschrift',
@ -48,7 +50,7 @@ let button1 = new Button({
let button2 = new Button({
x: 170,
label: 'Bottom-centered message',
action: e => {
action: (e) => {
const message = new Message({
app: app,
content: 'Diese Nachricht hat nur einen Text.',
@ -65,7 +67,7 @@ let button3 = new Button({
x: 0,
y: 60,
label: 'Message from PixiApp',
action: e => {
action: (e) => {
let message = app.message({
content: 'Diese Nachricht verschwindet gleich wieder.'
})
@ -76,3 +78,4 @@ app.scene.addChild(button1, button2)
app.scene.addChild(button3)
</script>
</body>
</html>

62
lib/pixi/modal.html
View File

@ -1,12 +1,12 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>PIXI Modal</title>
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../../css/doctest.css">
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../css/doctest.css" />
<script src="../3rdparty/highlight/highlight.pack.js"></script>
<script src="../../dist/iwmlib.3rdparty.js"></script>
@ -14,15 +14,18 @@
<script src="../../dist/iwmlib.pixi.js"></script>
</head>
<body onload="Doctest.run()">
<h1>Modal</h1>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>Modal</h1>
<p>
In user interface design for computer applications, a modal window is a graphical control element subordinate to an application's main window. It creates a mode that disables the main window, but keeps it visible with the modal window as a child window in front of it. Users must interact with the modal window before they can return to the parent application. This avoids interrupting the workflow on the main window. Modal windows are sometimes called heavy windows or modal dialogs because they often display a dialog box.
In user interface design for computer applications, a modal window is a graphical control element
subordinate to an application's main window. It creates a mode that disables the main window, but keeps it
visible with the modal window as a child window in front of it. Users must interact with the modal window
before they can return to the parent application. This avoids interrupting the workflow on the main window.
Modal windows are sometimes called heavy windows or modal dialogs because they often display a dialog box.
</p>
<p>Let's look at some modal examples:</p><br />
<p>Let's look at some modal examples:</p>
<br />
<canvas id="canvas" class="interactive"></canvas>
<p>
What you should see: Some buttons whichs starts different modal dialogs.
</p>
<p>What you should see: Some buttons whichs starts different modal dialogs.</p>
<script class="doctest">
const app = new PIXIApp({
view: canvas,
@ -31,13 +34,15 @@ const app = new PIXIApp({
transparent: false,
backgroundColor: 0xaa2211,
theme: 'light'
}).setup().run()
})
.setup()
.run()
let button1 = new Button({
x: 10,
y: 10,
label: 'Modal',
action: e => {
action: (e) => {
const modal = new Modal({ app: app })
app.scene.addChild(modal)
}
@ -47,11 +52,11 @@ let button2 = new Button({
x: 100,
y: 10,
label: 'Modal mit Inhalt',
action: e => {
action: (e) => {
const modal = new Modal({
app: app,
closeOnBackground: false,
backgroundFillAlpha: .3,
backgroundFillAlpha: 0.3,
header: 'Dies ist die Überschrift',
content: 'Und dies ist der Fließtext.'
})
@ -63,12 +68,13 @@ let button3 = new Button({
x: 270,
y: 10,
label: 'Modal mit Fließtext',
action: e => {
action: (e) => {
const modal = new Modal({
app: app,
maxWidth: 400,
header: 'Modal mit langem Fließtext',
content: 'Die Relativitätstheorie befasst sich mit der Struktur von Raum und Zeit sowie mit dem Wesen der Gravitation. Sie besteht aus zwei maßgeblich von Albert Einstein geschaffenen physikalischen Theorien, der 1905 veröffentlichten speziellen Relativitätstheorie und der 1916 abgeschlossenen allgemeinen Relativitätstheorie. Die spezielle Relativitätstheorie beschreibt das Verhalten von Raum und Zeit aus der Sicht von Beobachtern, die sich relativ zueinander bewegen, und die damit verbundenen Phänomene.'
content:
'Die Relativitätstheorie befasst sich mit der Struktur von Raum und Zeit sowie mit dem Wesen der Gravitation. Sie besteht aus zwei maßgeblich von Albert Einstein geschaffenen physikalischen Theorien, der 1905 veröffentlichten speziellen Relativitätstheorie und der 1916 abgeschlossenen allgemeinen Relativitätstheorie. Die spezielle Relativitätstheorie beschreibt das Verhalten von Raum und Zeit aus der Sicht von Beobachtern, die sich relativ zueinander bewegen, und die damit verbundenen Phänomene.'
})
app.scene.addChild(modal)
}
@ -78,11 +84,12 @@ let button4 = new Button({
x: 470,
y: 10,
label: 'Modal nur Fließtext',
action: e => {
action: (e) => {
const modal = new Modal({
app: app,
maxWidth: 600,
content: 'Die Relativitätstheorie befasst sich mit der Struktur von Raum und Zeit sowie mit dem Wesen der Gravitation. Sie besteht aus zwei maßgeblich von Albert Einstein geschaffenen physikalischen Theorien, der 1905 veröffentlichten speziellen Relativitätstheorie und der 1916 abgeschlossenen allgemeinen Relativitätstheorie. Die spezielle Relativitätstheorie beschreibt das Verhalten von Raum und Zeit aus der Sicht von Beobachtern, die sich relativ zueinander bewegen, und die damit verbundenen Phänomene.'
content:
'Die Relativitätstheorie befasst sich mit der Struktur von Raum und Zeit sowie mit dem Wesen der Gravitation. Sie besteht aus zwei maßgeblich von Albert Einstein geschaffenen physikalischen Theorien, der 1905 veröffentlichten speziellen Relativitätstheorie und der 1916 abgeschlossenen allgemeinen Relativitätstheorie. Die spezielle Relativitätstheorie beschreibt das Verhalten von Raum und Zeit aus der Sicht von Beobachtern, die sich relativ zueinander bewegen, und die damit verbundenen Phänomene.'
})
app.scene.addChild(modal)
}
@ -92,7 +99,7 @@ let button5 = new Button({
x: 10,
y: 70,
label: 'Modal mit Button',
action: e => {
action: (e) => {
const modal = new Modal({
app: app,
header: 'Modal mit Button',
@ -110,16 +117,14 @@ let button6 = new Button({
x: 190,
y: 70,
label: 'Modal mit ButtonGroup',
action: e => {
action: (e) => {
const modal = new Modal({
app: app,
header: 'Modal mit ButtonGroup',
content: 'Seit die Mathematiker über die Relativitätstheorie hergefallen sind, verstehe ich sie selbst nicht mehr.',
content:
'Seit die Mathematiker über die Relativitätstheorie hergefallen sind, verstehe ich sie selbst nicht mehr.',
buttonGroup: {
buttons: [
{label: 'Abbrechen', action: e => modal.hide()},
{label: 'Anwenden'}
]
buttons: [{ label: 'Abbrechen', action: (e) => modal.hide() }, { label: 'Anwenden' }]
},
minWidth: 450,
maxWidth: 450,
@ -130,13 +135,13 @@ let button6 = new Button({
})
let img = PIXI.Sprite.from('./assets/modal-1.jpg')
img.scale.set(.2, .2)
img.scale.set(0.2, 0.2)
let button7 = new Button({
x: 420,
y: 70,
label: 'Modal mit Foto',
action: e => {
action: (e) => {
const modal = new Modal({
app: app,
minWidth: 0,
@ -153,7 +158,7 @@ let button8 = new Button({
x: 10,
y: 130,
label: 'App Modal',
action: e => {
action: (e) => {
let modal = app.modal({
header: 'Modal aus App gestartet',
content: 'Die größte Erfindung des menschlichen Geistes? - Die Zinseszinsen!',
@ -167,3 +172,4 @@ app.scene.addChild(button5, button6, button7)
app.scene.addChild(button8)
</script>
</body>
</html>

60
lib/pixi/popover.html
View File

@ -1,9 +1,9 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link rel="stylesheet" href=".././3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../../css/doctest.css">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link rel="stylesheet" href=".././3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../css/doctest.css" />
<script src=".././3rdparty/highlight/highlight.pack.js"></script>
<script src="../../dist/iwmlib.3rdparty.js"></script>
@ -11,29 +11,42 @@
<script src="../../dist/iwmlib.pixi.js"></script>
</head>
<body onload="Doctest.run()">
<h1>Popover</h1>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>Popover</h1>
<p>
Add small overlay content, like those found in iOS, to any element for housing secondary information.
The Popover plugin is similar to tooltips; it is a pop-up box that appears when the user clicks or
touches an element. The difference is that the popover can contain much more content.
Add small overlay content, like those found in iOS, to any element for housing secondary information. The
Popover plugin is similar to tooltips; it is a pop-up box that appears when the user clicks or touches an
element. The difference is that the popover can contain much more content.
</p>
<p>Let's look at an example of a popover:</p>
<canvas id="canvas" class="grayBorder interactive">Canvas not supported</canvas>
<script class="doctest">
const app = new PIXIApp({
view: canvas,
autoResize: false,
width: 850, height: 450
}).setup().run()
width: 850,
height: 450
})
.setup()
.run()
let popover1 = new Popover({title: "Popover title", text: "This is the popover text.", x: 150, y: 130})
let popover1 = new Popover({ title: 'Popover title', text: 'This is the popover text.', x: 150, y: 130 })
app.scene.addChild(popover1)
let popover2 = new Popover({text: "This is another popover text. It has more words than the first one, some line breaks, \n\nbut no title :-(", x: 50, y: 230, placement: "right", width: 180})
let popover2 = new Popover({
text: 'This is another popover text. It has more words than the first one, some line breaks, \n\nbut no title :-(',
x: 50,
y: 230,
placement: 'right',
width: 180
})
app.scene.addChild(popover2)
let popover3 = new Popover({title: "Popover title 3. This title has many words but the Popover has no text...", x: 650, y: 70, placement: "left"})
let popover3 = new Popover({
title: 'Popover title 3. This title has many words but the Popover has no text...',
x: 650,
y: 70,
placement: 'left'
})
app.scene.addChild(popover3)
const text4 = `
@ -49,7 +62,14 @@ und überblickte mit einem gewissermaßen bewundernden Blick den ihm doch
wohlbekannten Apparat.
`
let popover4 = new Popover({title: "Popover title 4", text: text4, x: 650, y: 120, width: 380, placement: "bottom", titleStyle: {
let popover4 = new Popover({
title: 'Popover title 4',
text: text4,
x: 650,
y: 120,
width: 380,
placement: 'bottom',
titleStyle: {
fontFamily: 'Arial',
fontSize: 40,
fontStyle: 'italic',
@ -64,14 +84,16 @@ let popover4 = new Popover({title: "Popover title 4", text: text4, x: 650, y: 12
dropShadowDistance: 3,
wordWrap: true,
wordWrapWidth: 440
}, textStyle: {
},
textStyle: {
fontFamily: 'Arial',
fontSize: 10,
fill: "#76a9c9",
fill: '#76a9c9',
strokeThickness: 5,
wordWrap: true
}})
}
})
app.scene.addChild(popover4)
</script>
</body>
</html>

34
lib/pixi/popup.html
View File

@ -1,12 +1,12 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>PIXI Popup</title>
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../../css/doctest.css">
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../css/doctest.css" />
<script src="../3rdparty/highlight/highlight.pack.js"></script>
<script src="../../dist/iwmlib.3rdparty.js"></script>
@ -15,15 +15,15 @@
<script src="../../dist/iwmlib.pixi.js"></script>
</head>
<body onload="Doctest.run()">
<h1>Popup</h1>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>Popup</h1>
<p>
This class represents a popup window that can be used to display an arbitrary view. The popup window is a floating container that appears on top of the current activity.
This class represents a popup window that can be used to display an arbitrary view. The popup window is a
floating container that appears on top of the current activity.
</p>
<p>Let's look at some popup examples:</p><br />
<p>Let's look at some popup examples:</p>
<br />
<canvas id="canvas" class="interactive"></canvas>
<p>
What you should see: Three popups and a button which opens a popup.
</p>
<p>What you should see: Three popups and a button which opens a popup.</p>
<script class="doctest">
const app = new PIXIApp({
view: canvas,
@ -31,7 +31,9 @@ const app = new PIXIApp({
height: 250,
transparent: false,
backgroundColor: 0xcccccc
}).setup().run()
})
.setup()
.run()
let popup1 = new Popup({
x: 20,
@ -52,7 +54,8 @@ let popup2 = new Popup({
let popup3 = new Popup({
x: 330,
y: 20,
content: 'Man sollte alle Tage wenigstens ein kleines Lied hören, ein gutes Gedicht lesen,\nein treffliches Gemälde sehen und, wenn es möglich zu machen wäre,\neinige vernünftige Worte sprechen.'
content:
'Man sollte alle Tage wenigstens ein kleines Lied hören, ein gutes Gedicht lesen,\nein treffliches Gemälde sehen und, wenn es möglich zu machen wäre,\neinige vernünftige Worte sprechen.'
})
let button1 = new Button({
@ -60,14 +63,16 @@ let button1 = new Button({
y: 160,
icon: 'speaker_notes',
action: () => {
app.scene.addChild(new Popup({
app.scene.addChild(
new Popup({
x: 100,
y: 100,
closeButton: true,
header: 'Die Kunst ist eine Vermittlerin des Unaussprechlichen.',
stroke: 0x336699,
strokeWidth: 3
}))
})
)
}
})
@ -75,3 +80,4 @@ app.scene.addChild(popup1, popup2, popup3)
app.scene.addChild(button1)
</script>
</body>
</html>

69
lib/pixi/popupmenu.html
View File

@ -1,12 +1,12 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>PIXI PopupMenu</title>
<link rel="stylesheet" href=".././3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../../css/doctest.css">
<link rel="stylesheet" href=".././3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../css/doctest.css" />
<script src="../3rdparty/highlight/highlight.pack.js"></script>
<script src="../../dist/iwmlib.3rdparty.js"></script>
@ -15,33 +15,40 @@
<script src="../../dist/iwmlib.pixi.js"></script>
</head>
<body onload="Doctest.run()">
<h1>PopupMenu</h1>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>PopupMenu</h1>
<p>
A popup menu is a menu in a graphical user interface (GUI) that appears upon user interaction, such as a click or touch operation. A context menu offers a limited set of choices that are available in the current state, or context, of the application to which the menu belongs. Usually the available choices are actions related to the selected object.
A popup menu is a menu in a graphical user interface (GUI) that appears upon user interaction, such as a
click or touch operation. A context menu offers a limited set of choices that are available in the current
state, or context, of the application to which the menu belongs. Usually the available choices are actions
related to the selected object.
</p>
<p>Let's look at some popup menu examples:</p><br />
<p>Let's look at some popup menu examples:</p>
<br />
<canvas id="canvas" class="interactive"></canvas>
<p>
What you should see: Some buttons whichs open popup menues.
</p>
<p>What you should see: Some buttons whichs open popup menues.</p>
<script class="doctest">
const app = new PIXIApp({
view: canvas,
width: 900,
height: 250
}).setup().run()
})
.setup()
.run()
app.loadSprites([
app.loadSprites(
[
'./assets/popupmenu-1.jpg',
'./assets/popupmenu-2.jpg',
'./assets/popupmenu-3.jpg',
'./assets/popupmenu-4.jpg',
'./assets/popupmenu-5.jpg'
], sprites => {
],
(sprites) => {
const buttonGroup1 = new ButtonGroup({
buttons: [
{icon: 'looks_1', action: () => {
{
icon: 'looks_1',
action: () => {
const popupmenu = new PopupMenu({
items: [
{ label: 'Speichern', action: () => alert('Gespeichert') },
@ -50,8 +57,11 @@ app.loadSprites([
]
})
app.scene.addChild(popupmenu)
}},
{icon: 'looks_2', action: () => {
}
},
{
icon: 'looks_2',
action: () => {
const popupmenu = new PopupMenu({
closeButton: true,
closeOnPopup: false,
@ -67,8 +77,11 @@ app.loadSprites([
})
popupmenu.x = 400
app.scene.addChild(popupmenu)
}},
{icon: 'looks_3', action: () => {
}
},
{
icon: 'looks_3',
action: () => {
const popupmenu = new PopupMenu({
items: [
{ label: 'Option 01', textStyle: { fill: 0x637a38, fontSize: 14 } },
@ -88,10 +101,12 @@ app.loadSprites([
margin: 2
})
app.scene.addChild(popupmenu)
}},
{icon: 'looks_4', action: () => {
sprites.forEach(sprite => sprite.scale.set(.33, .33))
}
},
{
icon: 'looks_4',
action: () => {
sprites.forEach((sprite) => sprite.scale.set(0.33, 0.33))
const popupmenu = new PopupMenu({
items: [
@ -106,11 +121,15 @@ app.loadSprites([
padding: 2
})
app.scene.addChild(popupmenu)
}}
}
}
]
})
app.scene.addChild(buttonGroup1)
}, {resolutionDependent: false})
},
{ resolutionDependent: false }
)
</script>
</body>
</html>

36
lib/pixi/progress.html
View File

@ -1,12 +1,12 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>PIXI Progress</title>
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../../css/doctest.css">
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../css/doctest.css" />
<script src="../3rdparty/highlight/highlight.pack.js"></script>
<script src="../../dist/iwmlib.3rdparty.js"></script>
@ -15,13 +15,12 @@
<script src="../../dist/iwmlib.pixi.js"></script>
</head>
<body onload="Doctest.run()">
<h1>Progress</h1>
<p>
A progress bar can be used to show a user how far along he/she is in a process.
</p>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>Progress</h1>
<p>A progress bar can be used to show a user how far along he/she is in a process.</p>
<h2>Example 1</h2>
<p>Let's look at the progress bar example:</p><br />
<p>Let's look at the progress bar example:</p>
<br />
<canvas id="canvas" class="interactive"></canvas>
<p>
What you should see: When the page finished loading, a progress bar should overlay the PixiJS application.
@ -32,7 +31,9 @@ const app = new PIXIApp({
width: 900,
height: 250,
transparent: false
}).setup().run()
})
.setup()
.run()
let progress1 = new Progress({
app: app
@ -40,11 +41,11 @@ let progress1 = new Progress({
app.scene.addChild(progress1)
setTimeout(() => progress1.progress = 10, 500)
setTimeout(() => progress1.progress = 20, 800)
setTimeout(() => progress1.progress = 50, 900)
setTimeout(() => progress1.progress = 80, 1500)
setTimeout(() => progress1.progress = 100, 1700)
setTimeout(() => (progress1.progress = 10), 500)
setTimeout(() => (progress1.progress = 20), 800)
setTimeout(() => (progress1.progress = 50), 900)
setTimeout(() => (progress1.progress = 80), 1500)
setTimeout(() => (progress1.progress = 100), 1700)
</script>
<h2>Example 2</h2>
@ -63,7 +64,9 @@ const app2 = new PIXIApp({
fillActive: 0xe7bc51,
margin: 200
}
}).setup().run()
})
.setup()
.run()
setTimeout(() => app2.progress(10), 1000)
setTimeout(() => app2.progress(30), 2000)
@ -74,3 +77,4 @@ setTimeout(() => app2.progress(90), 4500)
setTimeout(() => app2.progress(100), 5000)
</script>
</body>
</html>

5
lib/pixi/resolution.html
View File

@ -4,7 +4,8 @@
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>PIXI Resolution Doctest</title>
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../css/doctest.css" />
<script src="../../dist/iwmlib.3rdparty.js"></script>
<script src="../../dist/iwmlib.js"></script>
<script src="../../dist/iwmlib.pixi.js"></script>
@ -21,6 +22,7 @@
</style>
</head>
<body>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>Resolution</h1>
<canvas id="canvas"></canvas>
<script class="doctest">
@ -36,7 +38,6 @@
const textProps = { fontSize: 72, fill: 0xffffff }
Mousetrap.bind(['1', '2', '3', '4', '5'], (event, key) => {
app.stage.removeChildren()
let sprite = null

15
lib/pixi/scatter-resolution-2.html
View File

@ -4,13 +4,15 @@
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>PIXI Scatter Resolution Doctest</title>
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../css/doctest.css" />
<script src="../../dist/iwmlib.3rdparty.js"></script>
<script src="../../dist/iwmlib.js"></script>
<script src="../../dist/iwmlib.pixi.js"></script>
</head>
<body>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>Scatter Resolution</h1>
<canvas id="canvas" />
<script>
const app = new PIXIApp({
@ -29,7 +31,7 @@
'../examples/front__1_dpi600.png',
'../examples/front__1_dpi1200.png'
],
sprites => {
(sprites) => {
app.scatterContainerFront = new ScatterContainer(app.renderer, { app })
app.scatterContainerBack = new ScatterContainer(app.renderer, { app })
@ -105,12 +107,15 @@
// renderTexture
//--------------------
sprites.forEach(value => {
sprites.forEach((value) => {
const matrix = new PIXI.Matrix()
matrix.translate(-value.x, -value.y)
const texture = PIXI.RenderTexture.create({ width: value.width, height: value.height, resolution: 2 })
const texture = PIXI.RenderTexture.create({
width: value.width,
height: value.height,
resolution: 2
})
app.renderer.render(value, texture, true, matrix)
const sprite = new PIXI.Sprite(texture)

4
lib/pixi/scatter-resolution.html
View File

@ -4,13 +4,15 @@
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>PIXI Scatter Resolution Doctest</title>
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../css/doctest.css" />
<script src="../../dist/iwmlib.3rdparty.js"></script>
<script src="../../dist/iwmlib.js"></script>
<script src="../../dist/iwmlib.pixi.js"></script>
</head>
<body>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>Scatter Resolution 2</h1>
<canvas id="canvas2" class="interactive">Canvas not supported</canvas>
<script>
class ScatterApp extends PIXIApp {

99
lib/pixi/scatter.html
View File

@ -1,11 +1,10 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>PIXI Scatter Doctest</title>
<link rel="stylesheet" href=".././3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../../css/doctest.css">
<link rel="stylesheet" href=".././3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../css/doctest.css" />
<script src=".././3rdparty/highlight/highlight.pack.js"></script>
<script src="../../dist/iwmlib.3rdparty.js"></script>
@ -14,26 +13,26 @@
</head>
<body onload="Doctest.run()">
<h1>
Scatter
</h1>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>Scatter</h1>
<p>
Scatter objects are UI elements that can be rotated, scaled or moved around which typically leads to "scattered" layouts.
The PIXI scatter defined here is a specialization of the
Scatter objects are UI elements that can be rotated, scaled or moved around which typically leads to
"scattered" layouts. The PIXI scatter defined here is a specialization of the
<a href="../scatter.html">abstract scatter pattern</a>.
</p>
<p>PIXI scatter are organized in
<code>ScatterContainer</code> parent nodes and
<p>
PIXI scatter are organized in <code>ScatterContainer</code> parent nodes and
<code>DisplayObjectScatter</code> child nodes.
<p>Let's look at an example of a PIXI scatter. Since scatter objects are mainly used as main views it is a common use
case that the scene itself is used as the
<code>ScatterContainer</code>. The
<code>DisplayObjectScatter</code> is simply used as a wrapper that makes any interative DisplayObject zoomable, rotatable and translatable.</p>
</p>
<p>
Let's look at an example of a PIXI scatter. Since scatter objects are mainly used as main views it is a
common use case that the scene itself is used as the <code>ScatterContainer</code>. The
<code>DisplayObjectScatter</code> is simply used as a wrapper that makes any interative DisplayObject
zoomable, rotatable and translatable.
</p>
<canvas id="canvas" class="grayBorder interactive">Canvas not supported</canvas>
<script class="doctest">
class ScatterApp extends PIXIApp {
sceneFactory() {
return new ScatterContainer(this.renderer, { showBounds: true, showPolygon: true, app: this })
}
@ -45,9 +44,9 @@
for (let key of ['women', 'king']) {
let sprite = PIXI.Sprite.from('../examples/' + key + '.jpeg')
sprite.interactive = true
let scatter = new DisplayObjectScatter(sprite, this.renderer,
{
x: x, y: y,
let scatter = new DisplayObjectScatter(sprite, this.renderer, {
x: x,
y: y,
startScale: 0.25,
minScale: 0.2,
maxScale: 1
@ -69,21 +68,16 @@
})
.setup()
.run()
</script>
<h1>
Two ScatterContainers in one canvas-element
</h1>
<h1>Two ScatterContainers in one canvas-element</h1>
<p>
You see two ScatterContainers within the same HTML-canvas-element. The Queen is included in the first, the King in the second
ScatterContainer. You should interact the two images independently of each other.
You see two ScatterContainers within the same HTML-canvas-element. The Queen is included in the first, the
King in the second ScatterContainer. You should interact the two images independently of each other.
</p>
<canvas id="canvas2" class="grayBorder interactive">Canvas not supported</canvas>
<script class="doctest">
class DoubleScatterApp extends PIXIApp {
setup() {
super.setup()
// Obey order in which ScatterContainer are created because the
@ -103,7 +97,7 @@
let scatter1 = new DisplayObjectScatter(sprite1, this.renderer, {
x: 20,
y: 40,
startScale: .5
startScale: 0.5
})
this.scatterContainerBack.addChild(sprite1)
@ -113,7 +107,7 @@
let scatter2 = new DisplayObjectScatter(sprite2, this.renderer, {
x: 280,
y: 40,
startScale: .5
startScale: 0.5
})
this.scatterContainerFront.addChild(sprite2)
return this
@ -125,31 +119,31 @@
autoResize: false,
width: 450,
height: 250
}).setup().run()
})
.setup()
.run()
</script>
<h1>
Nested Scatter
</h1>
<h1>Nested Scatter</h1>
<p>
Sometimes it can be required, that multiple scatters are nested in one another. E.g. when a map is displayed as scatter and
another scatter is displayed on the map.
Sometimes it can be required, that multiple scatters are nested in one another. E.g. when a map is displayed
as scatter and another scatter is displayed on the map.
</p>
<canvas id="canvas3" class="grayBorder interactive">Canvas not supported</canvas>
<script class="doctest">
class NestedScatterApp extends PIXIApp {
sceneFactory() {
return new ScatterContainer(this.renderer, { application: this, showBounds: true, showPolygon: true, app: this })
return new ScatterContainer(this.renderer, {
application: this,
showBounds: true,
showPolygon: true,
app: this
})
}
setup() {
super.setup()
// Add the queen to ScatterContainer one
let woman = PIXI.Sprite.from('../examples/women.jpeg')
woman.interactive = true
@ -164,25 +158,30 @@
let nestedKing = PIXI.Sprite.from('../examples/king.jpeg')
nestedKing.interactive = true
new DisplayObjectScatter(nestedKing, this.renderer, {
x: 20, y: 20, startScale: 0.3
x: 20,
y: 20,
startScale: 0.3
})
woman.addChild(nestedKing)
let nestedQueen = PIXI.Sprite.from('../examples/women.jpeg')
nestedQueen.interactive = true
new DisplayObjectScatter(nestedQueen, this.renderer, {
x: 40, y: 40, startScale: 0.3
x: 40,
y: 40,
startScale: 0.3
})
woman.addChild(nestedQueen)
let king = PIXI.Sprite.from('../examples/king.jpeg')
king.interactive = true
new DisplayObjectScatter(king, this.renderer, {
x: 200, y: 20, startScale: 1
x: 200,
y: 20,
startScale: 1
})
this.scene.addChild(king)
return this
}
}
@ -192,7 +191,9 @@
autoResize: false,
width: 450,
height: 250
}).setup().run()
})
.setup()
.run()
</script>
</body>
</html>

2
lib/pixi/scrollview.html
View File

@ -15,7 +15,7 @@
<script src="../../dist/iwmlib.pixi.js"></script>
</head>
<body onload="Doctest.run()">
<h1>Scrollview</h1>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>Scrollview</h1>
<p>A configurable scrollbox designed for pixi.js.</p>
<p><strong>Features:</strong></p>
<p>

28
lib/pixi/slider.html
View File

@ -1,12 +1,12 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>PIXI Slider</title>
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../../css/doctest.css">
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../css/doctest.css" />
<script src="../3rdparty/highlight/highlight.pack.js"></script>
<script src="../../dist/iwmlib.3rdparty.js"></script>
@ -15,22 +15,25 @@
<script src="../../dist/iwmlib.pixi.js"></script>
</head>
<body onload="Doctest.run()">
<h1>Slider</h1>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>Slider</h1>
<p>A slider is used whenever a numeric value within a certain range is to be obtained.</p>
<p>The <strong>advantage</strong> of a slider over text input is that it becomes impossible
for the user to enter a bad value. Any value that they can pick with the slider is valid.</p>
<p>Let's look at some slider examples:</p><br />
<canvas id="canvas" class="interactive"></canvas>
<p>
What you should see: Many sliders with very different styling and behaviour.
The <strong>advantage</strong> of a slider over text input is that it becomes impossible for the user to
enter a bad value. Any value that they can pick with the slider is valid.
</p>
<p>Let's look at some slider examples:</p>
<br />
<canvas id="canvas" class="interactive"></canvas>
<p>What you should see: Many sliders with very different styling and behaviour.</p>
<script class="doctest">
const app = new PIXIApp({
view: canvas,
width: 900,
height: 450,
transparent: false
}).setup().run()
})
.setup()
.run()
let slider1 = new Slider({
x: 10,
@ -84,7 +87,7 @@ let button1 = new Button({
label: 'Toggle-slider-button',
type: 'checkbox',
active: true,
action: e => {
action: (e) => {
slider5.visible = !slider5.visible
}
})
@ -98,3 +101,4 @@ app.scene.addChild(slider1, slider2, slider3, slider4)
app.scene.addChild(button1, slider5)
</script>
</body>
</html>

54
lib/pixi/stylus.html
View File

@ -1,13 +1,12 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>PIXI Stylus</title>
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../../css/doctest.css">
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../css/doctest.css" />
<script src="../3rdparty/highlight/highlight.pack.js"></script>
@ -17,17 +16,15 @@
</head>
<body onload="Doctest.run()">
<h1>Stylus</h1>
<p>The Stylus class extends the PIXI.Graphics class and allows to draw into
a graphics object. Select the pen tool in the following example app and draw into the canvas.
</p>
<canvas id="canvas" style="border: 1px solid gray; width: 640px; height: 480px;" class="interactive"></canvas>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>Stylus</h1>
<p>
What you should see: A blank sytlus canvas.
The Stylus class extends the PIXI.Graphics class and allows to draw into a graphics object. Select the pen
tool in the following example app and draw into the canvas.
</p>
<canvas id="canvas" style="border: 1px solid gray; width: 640px; height: 480px" class="interactive"></canvas>
<p>What you should see: A blank sytlus canvas.</p>
<script class="doctest">
class StylusApp extends PIXIApp {
sceneFactory() {
return new Stylus(this.renderer)
}
@ -42,9 +39,10 @@
x: 16,
y: 16,
fill: buttonColor,
buttons: [{
buttons: [
{
icon: 'edit',
iconColorActive: 0xFFFF00,
iconColorActive: 0xffff00,
action: (event, button) => this.toggleEditMode()
},
{
@ -73,7 +71,7 @@
}
this.palette = new ButtonGroup({
type: "radio",
type: 'radio',
x: 200,
y: 16,
margin: 0,
@ -85,16 +83,16 @@
iconColorActive: 0x111111
}), // tooltip: "Black",
Object.assign({}, defaults, {
iconColor: 0xFFFF00,
iconColorActive: 0xFFFF00
iconColor: 0xffff00,
iconColorActive: 0xffff00
}), // tooltip: "Yellow",
Object.assign({}, defaults, {
iconColor: 0x00FF00,
iconColorActive: 0x00FF00
iconColor: 0x00ff00,
iconColorActive: 0x00ff00
}), // tooltip: "Green",
Object.assign({}, defaults, {
iconColor: 0xFF00FF,
iconColorActive: 0xFF00FF
iconColor: 0xff00ff,
iconColorActive: 0xff00ff
}) // tooltip: "Violet",
]
})
@ -105,7 +103,7 @@
toggleEditMode() {
this.scene.interactive = !this.scene.interactive
console.log("this.scene.interactive")
console.log('this.scene.interactive')
}
selectColor(button) {
@ -144,13 +142,15 @@
app.setup()
app.run()
</script>
<h2>
References
</h2>
<h2>References</h2>
<ul>
<li><a href="https://mattdesl.svbtle.com/drawing-lines-is-hard">Drawing Lines is Hard</a></li>
<li><a href="http://perfectionkills.com/exploring-canvas-drawing-techniques/">Exploring Canvas Drawing
Techniques</a></li>
<li>
<a href="http://perfectionkills.com/exploring-canvas-drawing-techniques/"
>Exploring Canvas Drawing Techniques</a
>
</li>
<li><a href="https://github.com/mattdesl/polyline-normals">Polyline Normals</a></li>
</ul>
</body>
</html>

54
lib/pixi/switch.html
View File

@ -1,12 +1,12 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>PIXI Switch</title>
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../../css/doctest.css">
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../css/doctest.css" />
<script src="../3rdparty/highlight/highlight.pack.js"></script>
@ -15,24 +15,41 @@
<script src="../../dist/iwmlib.pixi.js"></script>
</head>
<body onload="Doctest.run()">
<h1>Switch</h1>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>Switch</h1>
<p>A switch is a visual toggle between two mutually exclusive states—on and off.</p>
<p><strong>Consider adjusting a switch’s appearance to match the style of your app.</strong> If it works well in your app, change the colors of a switch in its on and off states or use custom imagery to represent the switch.</p>
<p><strong>Use switches in table rows only.</strong> Switches are intended for use in tables, such as in a list of settings that can be toggled on and off. If you need similar functionality in a toolbar or navigation bar, use a button instead, and provide two distinct icons that communicate the states.</p>
<p><strong>Avoid adding labels to describe the values of a switch.</strong> Switches are either on or off. Providing labels that describe these states is redundant and clutters the interface.</p>
<p><strong>Consider using switches to manage the availability of related interface elements.</strong> Switches often affect other content onscreen. Enabling the Airplane Mode switch in Settings, for example, disables certain other settings, such as Cellular and Personal Hotspot. Disabling the Wi-Fi switch in Settings > Wi-Fi causes available networks and other options to disappear.</p>
<p>Let's look at some switch examples:</p><br />
<canvas id="canvas" class="interactive"></canvas>
<p>
What you should see: Many switches with very different styling and behaviour.
<strong>Consider adjusting a switch’s appearance to match the style of your app.</strong> If it works well
in your app, change the colors of a switch in its on and off states or use custom imagery to represent the
switch.
</p>
<p>
<strong>Use switches in table rows only.</strong> Switches are intended for use in tables, such as in a list
of settings that can be toggled on and off. If you need similar functionality in a toolbar or navigation
bar, use a button instead, and provide two distinct icons that communicate the states.
</p>
<p>
<strong>Avoid adding labels to describe the values of a switch.</strong> Switches are either on or off.
Providing labels that describe these states is redundant and clutters the interface.
</p>
<p>
<strong>Consider using switches to manage the availability of related interface elements.</strong> Switches
often affect other content onscreen. Enabling the Airplane Mode switch in Settings, for example, disables
certain other settings, such as Cellular and Personal Hotspot. Disabling the Wi-Fi switch in Settings >
Wi-Fi causes available networks and other options to disappear.
</p>
<p>Let's look at some switch examples:</p>
<br />
<canvas id="canvas" class="interactive"></canvas>
<p>What you should see: Many switches with very different styling and behaviour.</p>
<script class="doctest">
const app = new PIXIApp({
view: canvas,
width: 900,
height: 250,
transparent: false
}).setup().run()
})
.setup()
.run()
let switch1 = new Switch({
x: 10,
@ -49,7 +66,7 @@ let switch2 = new Switch({
strokeActiveWidth: 4,
controlStrokeActive: 0x50d968,
controlStrokeActiveWidth: 12,
controlStrokeActiveAlpha: .8,
controlStrokeActiveAlpha: 0.8,
tooltip: 'Dies ist ein Switch'
})
@ -59,7 +76,7 @@ let switch3 = new Switch({
width: 100,
height: 40,
fill: 0xfe9727,
fillAlpha: .5,
fillAlpha: 0.5,
fillActive: 0x5954d3,
stroke: 0x5ec7f8,
strokeWidth: 12,
@ -71,7 +88,7 @@ let switch3 = new Switch({
controlStrokeWidth: 8,
controlStrokeActive: 0x50d968,
controlStrokeActiveWidth: 16,
controlStrokeActiveAlpha: .8,
controlStrokeActiveAlpha: 0.8,
controlRadiusActive: 12,
duration: 3,
durationActive: 1
@ -103,8 +120,8 @@ let switch7 = new Switch({
height: 10,
fill: 0xffffff,
fillActive: 0xffffff,
duration: .2,
durationActive: .1,
duration: 0.2,
durationActive: 0.1,
controlFill: 0x00ff00,
controlFillActive: 0xff0000,
controlRadius: 15,
@ -123,3 +140,4 @@ app.scene.addChild(switch1, switch2, switch3)
app.scene.addChild(switch4, switch5, switch6, switch7)
</script>
</body>
</html>

56
lib/pixi/text-transform.html
View File

@ -1,12 +1,12 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>PIXI Text</title>
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../../css/doctest.css">
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../css/doctest.css" />
<script src="../3rdparty/highlight/highlight.pack.js"></script>
<script src="../../dist/iwmlib.3rdparty.js"></script>
@ -17,15 +17,18 @@
<script src="../3rdparty/d3.min.js"></script>
</head>
<body onload="Doctest.run()">
<h1>Text</h1>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>Text</h1>
<p>
The tooltip or infotip or a hint is a common graphical user interface element. It is used in conjunction with a cursor, usually a pointer. The user hovers the pointer over an item, without clicking it, and a tooltip may appear—a small "hover box" with information about the item being hovered over.[1][2] Tooltips do not usually appear on mobile operating systems, because there is no cursor (though tooltips may be displayed when using a mouse).
The tooltip or infotip or a hint is a common graphical user interface element. It is used in conjunction
with a cursor, usually a pointer. The user hovers the pointer over an item, without clicking it, and a
tooltip may appear—a small "hover box" with information about the item being hovered over.[1][2] Tooltips do
not usually appear on mobile operating systems, because there is no cursor (though tooltips may be displayed
when using a mouse).
</p>
<p>Let's look at some tooltip examples:</p><br />
<p>Let's look at some tooltip examples:</p>
<br />
<canvas id="canvas" class="interactive"></canvas>
<p>
What you should see: Ten colored circles with different tooltips.
</p>
<p>What you should see: Ten colored circles with different tooltips.</p>
<script class="doctest">
const app = new PIXIApp({
view: canvas,
@ -33,7 +36,9 @@ const app = new PIXIApp({
height: 500,
transparent: false,
backgroundColor: 0x2c2d2b
}).setup().run()
})
.setup()
.run()
const container = new PIXI.Graphics()
container.beginFill(0x58595b, 1)
@ -45,11 +50,9 @@ app.scene.addChild(container)
const sixthWidth = container.width / 6
const halfHeight = container.height / 2
app.loadSprites([
'./assets/stuttgart-library.jpg',
'./assets/Arial.fnt'
], sprites => {
app.loadSprites(
['./assets/stuttgart-library.jpg', './assets/Arial.fnt'],
(sprites) => {
// PIXI.Text
//--------------------
const text = new PIXI.Text('Bibliothek\nStuttgart', { fontSize: 50 })
@ -72,17 +75,17 @@ app.loadSprites([
// PIXI.Sprite
//--------------------
const sprite = sprites.get('./assets/stuttgart-library.jpg')
sprite.scale.set(.05, .05)
sprite.scale.set(0.05, 0.05)
sprite.x = sixthWidth * 5
sprite.y = halfHeight
sprite.anchor.set(.5, .5)
sprite.anchor.set(0.5, 0.5)
container.addChild(sprite)
// Scale
//--------------------
const scaleContainer = d3.scaleLinear().domain([0, 50, 100]).range([.05, 1, 50])
const scaleTexts = d3.scaleLinear().domain([0, 50, 100]).range([.1, 1, 10])
const scaleSprite = d3.scaleLinear().domain([0, 50, 100]).range([.005, .05, .5])
const scaleContainer = d3.scaleLinear().domain([0, 50, 100]).range([0.05, 1, 50])
const scaleTexts = d3.scaleLinear().domain([0, 50, 100]).range([0.1, 1, 10])
const scaleSprite = d3.scaleLinear().domain([0, 50, 100]).range([0.005, 0.05, 0.5])
// Sliders
//--------------------
@ -139,7 +142,7 @@ app.loadSprites([
bitmapText.scale.set(value, value)
}
})
sliderBitmapText.x = app.size.width / 6 * 3 - sliderBitmapText.width / 2
sliderBitmapText.x = (app.size.width / 6) * 3 - sliderBitmapText.width / 2
sliderBitmapText.y = app.size.height - 10 - sliderBitmapText.height
app.scene.addChild(sliderBitmapText)
@ -152,11 +155,12 @@ app.loadSprites([
sprite.scale.set(value, value)
}
})
sliderSprite.x = app.size.width / 6 * 5 - sliderSprite.width / 2
sliderSprite.x = (app.size.width / 6) * 5 - sliderSprite.width / 2
sliderSprite.y = app.size.height - 10 - sliderSprite.height
app.scene.addChild(sliderSprite)
}, {resolutionDependent: false})
},
{ resolutionDependent: false }
)
</script>
</body>
</html>

29
lib/pixi/text.html
View File

@ -1,12 +1,12 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>PIXI Text</title>
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../../css/doctest.css">
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../css/doctest.css" />
<script src="../3rdparty/highlight/highlight.pack.js"></script>
<script src="../../dist/iwmlib.3rdparty.js"></script>
@ -15,26 +15,27 @@
<script src="../../dist/iwmlib.pixi.js"></script>
</head>
<body onload="Doctest.run()">
<h1>Text</h1>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>Text</h1>
<p>
The Button class defines a clickable/touchable button. Use custom button styles for actions in forms, dialogs,
and more with support for multiple sizes, states, and more. Buttons will appear pressed when active. Make
buttons look inactive by setting the disabled state to true. To allow changing the state between active/inactive, set
the button type to "checkbox".
The Button class defines a clickable/touchable button. Use custom button styles for actions in forms,
dialogs, and more with support for multiple sizes, states, and more. Buttons will appear pressed when
active. Make buttons look inactive by setting the disabled state to true. To allow changing the state
between active/inactive, set the button type to "checkbox".
</p>
<p><a href="../../doc/out/Text.html">JavaScript API</a></p>
<p>Let's look at some text examples:</p><br />
<p>Let's look at some text examples:</p>
<br />
<canvas id="canvas" class="interactive"></canvas>
<p>
What you should see: Many texts with very different styling and behaviour.
</p>
<p>What you should see: Many texts with very different styling and behaviour.</p>
<script class="doctest">
const app = new PIXIApp({
view: canvas,
width: 900,
height: 600,
transparent: false
}).setup().run()
})
.setup()
.run()
const text1 = new Text({ x: 10, y: 10 })

41
lib/pixi/theme.html
View File

@ -1,12 +1,12 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>PIXI Theme</title>
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../../css/doctest.css">
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../css/doctest.css" />
<script src="../3rdparty/highlight/highlight.pack.js"></script>
<script src="../../dist/iwmlib.3rdparty.js"></script>
@ -15,25 +15,26 @@
<script src="../../dist/iwmlib.pixi.js"></script>
</head>
<body onload="Doctest.run()">
<h1>Theme</h1>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>Theme</h1>
<p>
The Button class defines a clickable/touchable button. Use custom button styles for actions in forms, dialogs,
and more with support for multiple sizes, states, and more. Buttons will appear pressed when active. Make
buttons look inactive by setting the disabled state to true. To allow changing the state between active/inactive, set
the button type to "checkbox".
The Button class defines a clickable/touchable button. Use custom button styles for actions in forms,
dialogs, and more with support for multiple sizes, states, and more. Buttons will appear pressed when
active. Make buttons look inactive by setting the disabled state to true. To allow changing the state
between active/inactive, set the button type to "checkbox".
</p>
<p>Let's look at some button examples:</p><br />
<p>Let's look at some button examples:</p>
<br />
<canvas id="canvas" class="interactive"></canvas>
<p>
What you should see: Many buttons with very different styling and behaviour.
</p>
<p>What you should see: Many buttons with very different styling and behaviour.</p>
<script class="doctest">
const app = new PIXIApp({
view: canvas,
width: 900,
height: 250,
transparent: false
}).setup().run()
})
.setup()
.run()
let buttonDark = new Button({
x: 10,
@ -46,10 +47,7 @@ let buttonGroupLight = new ButtonGroup({
x: 230,
y: 10,
theme: 'light',
buttons: [
{label: 'Button with', active: true},
{label: 'theme light'}
],
buttons: [{ label: 'Button with', active: true }, { label: 'theme light' }],
type: 'checkbox'
})
@ -58,10 +56,7 @@ let buttonGroupRed = new ButtonGroup({
y: 10,
theme: 'red',
margin: 0,
buttons: [
{label: 'Button with', active: true},
{label: 'theme red'}
],
buttons: [{ label: 'Button with', active: true }, { label: 'theme red' }],
type: 'radio'
})
@ -104,7 +99,7 @@ let buttonYellow = new Button({
theme: yellowTheme,
label: 'Button with theme yellow',
type: 'checkbox',
action: event => {
action: (event) => {
const modal = new Modal({
app: app,
theme: yellowTheme,

67
lib/pixi/tooltip.html
View File

@ -1,12 +1,12 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>PIXI Tooltip</title>
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../../css/doctest.css">
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../css/doctest.css" />
<script src="../3rdparty/highlight/highlight.pack.js"></script>
<script src="../../dist/iwmlib.3rdparty.js"></script>
@ -15,21 +15,26 @@
<script src="../../dist/iwmlib.pixi.js"></script>
</head>
<body onload="Doctest.run()">
<h1>Tooltip</h1>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>Tooltip</h1>
<p>
The tooltip or infotip or a hint is a common graphical user interface element. It is used in conjunction with a cursor, usually a pointer. The user hovers the pointer over an item, without clicking it, and a tooltip may appear—a small "hover box" with information about the item being hovered over.[1][2] Tooltips do not usually appear on mobile operating systems, because there is no cursor (though tooltips may be displayed when using a mouse).
The tooltip or infotip or a hint is a common graphical user interface element. It is used in conjunction
with a cursor, usually a pointer. The user hovers the pointer over an item, without clicking it, and a
tooltip may appear—a small "hover box" with information about the item being hovered over.[1][2] Tooltips do
not usually appear on mobile operating systems, because there is no cursor (though tooltips may be displayed
when using a mouse).
</p>
<p>Let's look at some tooltip examples:</p><br />
<p>Let's look at some tooltip examples:</p>
<br />
<canvas id="canvas" class="interactive"></canvas>
<p>
What you should see: Ten colored circles with different tooltips.
</p>
<p>What you should see: Ten colored circles with different tooltips.</p>
<script class="doctest">
const app = new PIXIApp({
view: canvas,
width: 900,
height: 250
}).setup().run()
})
.setup()
.run()
const circle1 = new PIXI.Graphics()
circle1.beginFill(0x5251a3)
@ -86,7 +91,8 @@ let tooltip3 = new Tooltip({
object: circle3,
container: app.scene,
padding: 20,
content: 'Es reden und träumen die Menschen viel\nVon bessern künftigen Tagen,\nNach einem glücklichen goldenen Ziel\nSieht man sie rennen und jagen.'
content:
'Es reden und träumen die Menschen viel\nVon bessern künftigen Tagen,\nNach einem glücklichen goldenen Ziel\nSieht man sie rennen und jagen.'
})
let tooltip4 = new Tooltip({
@ -95,7 +101,7 @@ let tooltip4 = new Tooltip({
content: 'Stets ist die Sprache kecker als die Tat.',
textStyle: { fill: 0x5251a3, fontSize: 20 },
fill: 0xa64f94,
fillAlpha: .8
fillAlpha: 0.8
})
let tooltip5 = new Tooltip({
@ -110,12 +116,11 @@ let tooltip5 = new Tooltip({
textStyle: { fill: 0x5251a3, fontSize: 20, stroke: 0xeeeeee, strokeThickness: 2 }
})
app.loadSprites([
'./assets/tooltip-1.jpg',
'./assets/tooltip-2.jpg'
], sprites => {
app.loadSprites(
['./assets/tooltip-1.jpg', './assets/tooltip-2.jpg'],
(sprites) => {
let sprite1 = sprites.get('./assets/tooltip-1.jpg')
sprite1.scale.set(.33, .33)
sprite1.scale.set(0.33, 0.33)
let tooltip6 = new Tooltip({
object: circle6,
container: app.scene,
@ -123,7 +128,7 @@ app.loadSprites([
})
let sprite2 = sprites.get('./assets/tooltip-2.jpg')
sprite2.scale.set(.33, .33)
sprite2.scale.set(0.33, 0.33)
let tooltip7 = new Tooltip({
object: circle7,
container: app.scene,
@ -138,17 +143,22 @@ app.loadSprites([
container: app.scene,
padding: 8,
fill: 0xe7bc51,
fillAlpha: .7,
content: 'Es reden und träumen die Menschen viel\nVon bessern künftigen Tagen,\nNach einem glücklichen goldenen Ziel\nSieht man sie rennen und jagen.',
textStyle: {lineHeight: 22, fontSize: 18, fill: ['#843d39','#ae4a4a', '#d7626c'], fontStyle: 'italic'}
fillAlpha: 0.7,
content:
'Es reden und träumen die Menschen viel\nVon bessern künftigen Tagen,\nNach einem glücklichen goldenen Ziel\nSieht man sie rennen und jagen.',
textStyle: {
lineHeight: 22,
fontSize: 18,
fill: ['#843d39', '#ae4a4a', '#d7626c'],
fontStyle: 'italic'
}
})
let texture1 = PIXI.Texture.from('./assets/tooltip-3.mp4')
texture1.baseTexture.on('loaded', e => {
texture1.baseTexture.on('loaded', (e) => {
let sprite3 = new PIXI.Sprite(texture1)
sprite3.scale.set(.15, .15)
sprite3.scale.set(0.15, 0.15)
let tooltip9 = new Tooltip({
object: circle9,
container: app.scene,
@ -158,7 +168,7 @@ app.loadSprites([
})
let sprite4 = new PIXI.Sprite(texture1)
sprite4.scale.set(.1, .1)
sprite4.scale.set(0.1, 0.1)
let tooltip10 = new Tooltip({
object: circle10,
container: app.scene,
@ -168,9 +178,12 @@ app.loadSprites([
padding: 1
})
})
}, {resolutionDependent: false})
},
{ resolutionDependent: false }
)
app.scene.addChild(circle1, circle2, circle3, circle4, circle5)
app.scene.addChild(circle6, circle7, circle8, circle9, circle10)
</script>
</body>
</html>

34
lib/pixi/volatile.html
View File

@ -1,12 +1,12 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>PIXI Volatile</title>
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../../css/doctest.css">
<link rel="stylesheet" href="../3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../../css/doctest.css" />
<script src="../3rdparty/highlight/highlight.pack.js"></script>
<script src="../../dist/iwmlib.3rdparty.js"></script>
@ -15,21 +15,23 @@
<script src="../../dist/iwmlib.pixi.js"></script>
</head>
<body onload="Doctest.run()">
<h1>Volatile</h1>
<h1><a href="../index.html">lib.</a><a href="index.html">pixi.</a>Volatile</h1>
<p>
The Volatile class facilitates the "disappear" of any PixiJS DisplayObjects. Elements are "dimmed" in a predetermined direction.
The Volatile class facilitates the "disappear" of any PixiJS DisplayObjects. Elements are "dimmed" in a
predetermined direction.
</p>
<p>Let's look at some volatile examples:</p><br />
<p>Let's look at some volatile examples:</p>
<br />
<canvas id="canvas" class="interactive"></canvas>
<p>
What you should see: Buttons which starts an volatile animation.
</p>
<p>What you should see: Buttons which starts an volatile animation.</p>
<script class="doctest">
const app = new PIXIApp({
view: canvas,
width: 900,
height: 250
}).setup().run()
})
.setup()
.run()
let button1 = new Button({
label: 'Volatile me!',
@ -45,10 +47,13 @@ let button1 = new Button({
let button2 = new Button({
y: 60,
label: 'Volatile Text',
action: e => {
let text = new PIXI.Text('Gespeichert', Object.assign({}, button2.theme.textStyleLarge, {fill: button2.theme.primaryColor}))
action: (e) => {
let text = new PIXI.Text(
'Gespeichert',
Object.assign({}, button2.theme.textStyleLarge, { fill: button2.theme.primaryColor })
)
text.x = button2.width / 2
text.y = button2.y + (button2.height / 2) - (text.height / 2)
text.y = button2.y + button2.height / 2 - text.height / 2
app.scene.addChild(text)
new Volatile({
object: text,
@ -62,3 +67,4 @@ let button2 = new Button({
app.scene.addChild(button1, button2)
</script>
</body>
</html>

35
lib/poppable.html
View File

@ -1,49 +1,42 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<title>Poppable Doctest</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../css/doctest.css">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../css/doctest.css" />
<script src="./3rdparty/highlight/highlight.pack.js"></script>
<script src="./3rdparty/all.js"></script>
<script src="../dist/iwmlib.js"></script>
</head>
<body id="page" onload="Doctest.run()">
<h1>
Poppables
</h1>
<h1><a href="index.html">lib.</a>Poppables</h1>
<p>
Poppables present information on demand in a given context. This
is an abstract base class for Popup menus and other contextual information
like image highlights. It's main purpose is to ensure that only
one poppable at a time can be shown in a given context. Note
that in an application multiple poppables can be shown in different context
at the same time.
Poppables present information on demand in a given context. This is an abstract base class for Popup menus
and other contextual information like image highlights. It's main purpose is to ensure that only one
poppable at a time can be shown in a given context. Note that in an application multiple poppables can be
shown in different context at the same time.
</p>
<p>Let's look at an example of a popup class. In this class the register
method is called by the constructor. The class also implements a close
method which is called if the second poppable is registered.
<p>
Let's look at an example of a popup class. In this class the register method is called by the constructor.
The class also implements a close method which is called if the second poppable is registered.
<script class="doctest">
class ConcretePoppable extends Poppable {
constructor(context) {
super()
this.register(context)
}
close() {
alert("closed")
alert('closed')
}
}
let context = window
let a = new ConcretePoppable(context)
let b = new ConcretePoppable(context)
</script>
</p>
</body>
</html>

2
lib/popup.html
View File

@ -13,7 +13,7 @@
<body id="page" onload="Doctest.run()">
<h1>
Popups
<a href="index.html">lib.</a>Popup
</h1>
<p>
Popups present context information on demand at a specific place.

2
lib/popupmenu.html
View File

@ -12,7 +12,7 @@
<body onload="Doctest.run()">
<h1>
Popup Menus
<a href="index.html">lib.</a>Popup Menus
</h1>
<p>
Popup menus are a simple but effective solution to the problem that context dependent commands like "Delete", "Show", "Open"

84
lib/scatter.html
View File

@ -1,10 +1,10 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Scatter Doctest</title>
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../css/doctest.css">
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../css/doctest.css" />
<script src="./3rdparty/highlight/highlight.pack.js"></script>
<script src="../dist/iwmlib.3rdparty.js"></script>
<script src="../dist/iwmlib.js"></script>
@ -14,7 +14,7 @@
let context = debugCanvas.getContext('2d')
context.clearRect(0, 0, debugCanvas.width, debugCanvas.height)
let stage = scatterContainer.polygon
stage.draw(context, { stroke: "#0000FF"})
stage.draw(context, { stroke: '#0000FF' })
for (let scatter of scatterContainer.scatter.values()) {
let polygon = scatter.polygon
polygon.draw(context, { stroke: '#0000FF' })
@ -25,30 +25,30 @@
requestAnimationFrame((dt) => {
drawPolygons()
animatePolygons()
})
}
</script>
</head>
<body onload="Doctest.run()">
<h1>
Scatter
</h1>
<h1><a href="index.html">lib.</a>Scatter</h1>
<p>
Scatter objects are UI elements that can be rotated, scaled or moved around,
which typically leads to "scattered" layouts. Scatters come in two flavours:
DOM Scatters are working with arbitrary DOM elements, wheras PIXI Scatter
work with PIXI Containers and DisplayObjects within the PIXI scene graph. Here
we describe the more basic DOM scatter.
Scatter objects are UI elements that can be rotated, scaled or moved around, which typically leads to
"scattered" layouts. Scatters come in two flavours: DOM Scatters are working with arbitrary DOM elements,
wheras PIXI Scatter work with PIXI Containers and DisplayObjects within the PIXI scene graph. Here we
describe the more basic DOM scatter.
</p>
<p>Let's look at an example.</p>
<div id="main" class="grayBorder interactive" style="position: relative; width: 100%; height: 280px;">
<div id="main" class="grayBorder interactive" style="position: relative; width: 100%; height: 280px">
<!-- Note that we need to set draggable to false to avoid conflicts. The DOM elements
must also be positioned absolutely. -->
<img id="women" draggable="false" style="position: absolute;" src="examples/women.jpeg" />
<img id="king" draggable="false" style="position: absolute;" src="examples/king.jpeg" />
<img id="women" draggable="false" style="position: absolute" src="examples/women.jpeg" />
<img id="king" draggable="false" style="position: absolute" src="examples/king.jpeg" />
<canvas id="debugCanvas" height="280" style="z-index: 100000; pointer-events: none; position: absolute; border: 1px solid blue;">
<canvas
id="debugCanvas"
height="280"
style="z-index: 100000; pointer-events: none; position: absolute; border: 1px solid blue"
>
Canvas not supported.
</canvas>
</div>
@ -72,7 +72,8 @@ for(let key of ['women', 'king']) {
rotationDegrees: angle,
throwVisibility: 88,
minScale: 0.5,
maxScale: 1.5})
maxScale: 1.5
})
dx += 300
angle = -angle
}
@ -80,27 +81,31 @@ for(let key of ['women', 'king']) {
app.run()
animatePolygons()
</script>
<h1>
Interactive Content
</h1>
<h1>Interactive Content</h1>
<p>
Scatter objects may contain interactive HTML structures. There is one major flag that allows
to simulate click events by using taps. If the scatter detects a tap it looks for clickable
elements under or nearby the event position and calls the click handler. Thus gestures
can be disambiguated as moves, zooms. or taps.
Note that on touch devices you can tap beside the object if you use an object that implements the ITapDelegate interface.
An ITapDelegate allowes a distance that can be configured by allowClickDistance. The default value is 44px but here we
use 88px.
Scatter objects may contain interactive HTML structures. There is one major flag that allows to simulate
click events by using taps. If the scatter detects a tap it looks for clickable elements under or nearby the
event position and calls the click handler. Thus gestures can be disambiguated as moves, zooms. or taps.
Note that on touch devices you can tap beside the object if you use an object that implements the
ITapDelegate interface. An ITapDelegate allowes a distance that can be configured by allowClickDistance. The
default value is 44px but here we use 88px.
</p>
<div id="contentExample" class="grayBorder interactive" style="position: relative; width: 100%; height: 280px;">
<div id="contentExample" class="grayBorder interactive" style="position: relative; width: 100%; height: 280px">
<div id="interactiveContent">
<img draggable="false" style="position: absolute;" src="examples/women.jpeg" />
<a style="position:absolute; top: 10px; right: 10px; color:white;" href="javascript:alert('test link')">A Link</a>
<div onclick="alert('div clicked')" style="position:absolute; top: 30px; right: 10px; color:white;">A Div with click handler</div>
<svg onclick="alert('svg clicked')" style="position: absolute; right: 0px; bottom: 0px; width: 32px; height: 32px;" viewBox="0 0 100 100" preserveAspectRatio="xMidYMid meet">
<img draggable="false" style="position: absolute" src="examples/women.jpeg" />
<a style="position: absolute; top: 10px; right: 10px; color: white" href="javascript:alert('test link')"
>A Link</a
>
<div onclick="alert('div clicked')" style="position: absolute; top: 30px; right: 10px; color: white">
A Div with click handler
</div>
<svg
onclick="alert('svg clicked')"
style="position: absolute; right: 0px; bottom: 0px; width: 32px; height: 32px"
viewBox="0 0 100 100"
preserveAspectRatio="xMidYMid meet"
>
<circle cx="50" cy="50" r="44" stroke="white" stroke-width="8" fill="gray" />
<circle cx="50" cy="32" r="7" fill="white" />
<line x1="50" y1="46" x2="50" y2="78" stroke="white" stroke-width="12" />
@ -109,7 +114,6 @@ use 88px.
</div>
<script class="doctest">
let contentContainer = new DOMScatterContainer(contentExample)
let tapDelegate = new CardWrapper(interactiveContent, { allowClickDistance: 88 })
@ -121,8 +125,8 @@ use 88px.
tapDelegate,
throwVisibility: 88,
minScale: 0.5,
maxScale: 1.5})
maxScale: 1.5
})
</script>
</body>
</html>

2
lib/test.html
View File

@ -13,7 +13,7 @@
</head>
<body onload="Doctest.run(); loaded()" >
<h1>
Functional Tests
<a href="index.html">lib.</a>Functional Tests
</h1>
<p>
If you want to test the UI in all functional aspects, it'is important to be able

43
lib/uitest.html
View File

@ -1,38 +1,43 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>UITest Doctest</title>
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../css/doctest.css">
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../css/doctest.css" />
<script src="./3rdparty/highlight/highlight.pack.js"></script>
<script src="../dist/iwmlib.3rdparty.js"></script>
<script src="../dist/iwmlib.js"></script>
</head>
<body onload="Doctest.run()">
<h1>
UITest
</h1>
<h1><a href="index.html">lib.</a>UITest</h1>
<p>
Testing the user interface (UI) of an application is a critical part of the software development lifecycle. Most end users focus on the usability and aesthetics of the applications they interact with and are blind to the underlying source code and other technical aspects that make those apps functional. A poorly designed UI will undoubtedly lead to unhappy customers, so it’s important to test early and often to prevent as many bugs as possible from reaching the UI level.
<br><br>
Graphical user interface (GUI) testing is the process of testing an application’s visual elements to ensure the images and other features that are visible to the customer behave and look as expected. This article describes what GUI testing is, its importance, and what features your GUI testing tools should have to help you ensure proper test coverage.
Testing the user interface (UI) of an application is a critical part of the software development lifecycle.
Most end users focus on the usability and aesthetics of the applications they interact with and are blind to
the underlying source code and other technical aspects that make those apps functional. A poorly designed UI
will undoubtedly lead to unhappy customers, so it’s important to test early and often to prevent as many
bugs as possible from reaching the UI level.
<br /><br />
Graphical user interface (GUI) testing is the process of testing an application’s visual elements to ensure
the images and other features that are visible to the customer behave and look as expected. This article
describes what GUI testing is, its importance, and what features your GUI testing tools should have to help
you ensure proper test coverage.
</p>
<p>Let's look at an example.</p>
<div id="main" class="grayBorder interactive" style="position: relative; width: 100%; height: 380px;">
<div id="main" class="grayBorder interactive" style="position: relative; width: 100%; height: 380px">
<button id="button1" type="button" onclick="add1();">Click to add 1</button>
<input id="input1" type="text" value="0">
<hr>
<input id="input1" type="text" value="0" />
<hr />
<button id="button2" type="button" onclick="add2();">Click to add 1</button>
<input id="input2" type="text" value="0">
<hr>
<input id="input2" type="text" value="0" />
<hr />
<button id="button3" type="button" onclick="add3();">Click to add 1</button>
<input id="input3" type="text" value="0">
<hr>
<input id="input3" type="text" value="0" />
<hr />
<svg width="200" height="70">
<circle id="circle1" cx="40" cy="40" r="30" fill="orange" onclick="changeColor(this);" />
</svg>
<hr>
<hr />
<svg width="200" height="70">
<circle id="circle2" cx="40" cy="40" r="30" fill="blue" onclick="changeColor(this);" />
</svg>
@ -87,5 +92,5 @@ for (let i = 1; i < 6; i++) {
}
test5.start()
</script>
</body>
</html>

140
lib/utils.html
View File

@ -1,44 +1,35 @@
<!doctype html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Doctests</title>
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css">
<link rel="stylesheet" href="../css/doctest.css">
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css" />
<link rel="stylesheet" href="../css/doctest.css" />
<script src="./3rdparty/highlight/highlight.pack.js"></script>
<script src="../dist/iwmlib.js"></script>
</head>
<body onload="Doctest.run()">
<main>
<h1>
Utils
</h1>
<h1><a href="index.html">lib.</a>Utils</h1>
<p>
Utility functions can be used across modules. To avoid name conflicts most
of them are defined as static class functions (i.e. the class mainly serves
as a namespace). Typically this class name is in the plural, e.g. "Points", "Dates" to ensure that
existing class names like "Point", "Date" are not in conflict with the namespace.
Utility functions can be used across modules. To avoid name conflicts most of them are defined as static
class functions (i.e. the class mainly serves as a namespace). Typically this class name is in the
plural, e.g. "Points", "Dates" to ensure that existing class names like "Point", "Date" are not in
conflict with the namespace.
</p>
<h2>
Cycle
</h2>
<h2>Cycle</h2>
<p>Cycles simplify to switch between values in a cyclic way.</p>
<script class="doctest">
let cycle = new Cycle(1, 2, 3)
Doctest.expect(cycle.next(), 1)
Doctest.expect(cycle.next(), 2)
Doctest.expect(cycle.next(), 3)
Doctest.expect(cycle.next(), 1)
</script>
<h2>
Dates
</h2>
<h2>Dates</h2>
<script class="doctest">
let feb1900 = new Date(1900, 1, 1)
Doctest.expect(Dates.daysInMonth(feb1900), 28)
// 1900 was no leap year
@ -51,42 +42,32 @@ existing class names like "Point", "Date" are not in conflict with the namespace
</script>
<p>
A tricky problem is to iterate over years, months, and days to label timelines
and calendars in a consistent way. This can lead to problems with standard
(CET) and summer time (CEST).
To illustrate the problem look at the following example. Although march has 31 days
the formatted UTC string shows "30.3". Also note that the standard
new Date() constructor uses a zero-based month:
A tricky problem is to iterate over years, months, and days to label timelines and calendars in a
consistent way. This can lead to problems with standard (CET) and summer time (CEST). To illustrate the
problem look at the following example. Although march has 31 days the formatted UTC string shows "30.3".
Also note that the standard new Date() constructor uses a zero-based month:
</p>
<script class="doctest">
let format = { timeZone: 'UTC' }
let lastMar1913 = new Date(1913, 2, 31)
Doctest.expect(lastMar1913.toLocaleDateString("de", format), "30.3.1913")
Doctest.expect(lastMar1913.toLocaleDateString('de', format), '30.3.1913')
</script>
<p>
The following iterators guarantee that correct labels are generated:</p>
<p>The following iterators guarantee that correct labels are generated:</p>
<script class="doctest">
let lastDay = null
for (let day of Dates.iterDays(mar1913)) {
lastDay = day
}
Doctest.expect(lastDay.toLocaleDateString("de", format), "31.3.1913")
Doctest.expect(lastDay.toLocaleDateString('de', format), '31.3.1913')
</script>
<h2>
Sets
</h2>
<h2>Sets</h2>
<p>
Unfortunately the common set operations of other languages are missing in JavaScript. Therefore we use
a Sets helper class with static methods:
Unfortunately the common set operations of other languages are missing in JavaScript. Therefore we use a
Sets helper class with static methods:
</p>
<script class="doctest">
let set1 = new Set([1, 2, 3])
let set2 = new Set([2, 3, 4, 5])
let set3 = new Set([2, 3, 6])
@ -94,30 +75,38 @@ The following iterators guarantee that correct labels are generated:</p>
Doctest.expect(Array.from(Sets.intersect(set1, set2, set3)), [2, 3])
Doctest.expect(Array.from(Sets.union(set1, set2, set3)), [1, 2, 3, 4, 5, 6])
Doctest.expect(Array.from(Sets.difference(set2, set1, set3)), [4, 5])
</script>
<h2>
Polygon
</h2>
<p>An intersection of polygons is needed to compute the overlap of rotated rectangles.
We are using the library <a href="https://gist.github.com/cwleonard/e124d63238bda7a3cbfa">jspolygon.js</a> but provide a more convenient API that
is compatible with arrays of absolute points.
<h2>Polygon</h2>
<p>
An intersection of polygons is needed to compute the overlap of rotated rectangles. We are using the
library <a href="https://gist.github.com/cwleonard/e124d63238bda7a3cbfa">jspolygon.js</a> but provide a
more convenient API that is compatible with arrays of absolute points.
</p>
<p>To detect intersection with another Polygon object, the instance
method uses the Separating Axis Theorem. It returns false
if there is no intersection, or an object if there is. The object
contains 2 fields, overlap and axis. Moving the other polygon by overlap
on axis will get the polygons out of intersection.
<p>
To detect intersection with another Polygon object, the instance method uses the Separating Axis
Theorem. It returns false if there is no intersection, or an object if there is. The object contains 2
fields, overlap and axis. Moving the other polygon by overlap on axis will get the polygons out of
intersection.
</p>
<p>The following triangles show an overlap. Moving the triangle along the red line would remove the overlap.
<p>
The following triangles show an overlap. Moving the triangle along the red line would remove the
overlap.
</p>
<canvas id="canvas" class="grayBorder interactive">Canvas not supported</canvas>
<script class="doctest">
let context = canvas.getContext("2d")
let context = canvas.getContext('2d')
// The jspolygon syntax
let a = Polygon.fromPoints([{ x: 20, y: 20}, { x: 100, y: 100}, { x: 150, y: 50}])
let a = Polygon.fromPoints([
{ x: 20, y: 20 },
{ x: 100, y: 100 },
{ x: 150, y: 50 }
])
a.draw(context)
let b = Polygon.fromPoints([{x: 70, y: 50}, {x: 150, y: 10}, {x: 200, y: 70}])
let b = Polygon.fromPoints([
{ x: 70, y: 50 },
{ x: 150, y: 10 },
{ x: 200, y: 70 }
])
b.draw(context)
context.strokeStyle = '#ff0000'
@ -130,18 +119,18 @@ is compatible with arrays of absolute points.
context.lineTo(target.x, target.y)
}
context.stroke()
</script>
<h2>
Low Pass Filter
</h2>
<h2>Low Pass Filter</h2>
<p>
Low Pass Filter muffles fast (high-frequency) changes to the signal.
For more information visit the <a href="http://en.wikipedia.org/wiki/Low-pass_filter">wikipedia article</a>.
Low Pass Filter muffles fast (high-frequency) changes to the signal. For more information visit the
<a href="http://en.wikipedia.org/wiki/Low-pass_filter">wikipedia article</a>.
</p>
<script class="doctest">
let lpf = new LowPassFilter(0.5)
Doctest.expect(lpf.smoothArray([10,8,9,10,12,8,50,10,12,8]), [10,9,9,10,11,9,30,20,16,12])
Doctest.expect(
lpf.smoothArray([10, 8, 9, 10, 12, 8, 50, 10, 12, 8]),
[10, 9, 9, 10, 11, 9, 30, 20, 16, 12]
)
Doctest.expect(lpf.next(20), 10.0)
Doctest.expect(lpf.next(20), 12.5)
@ -153,21 +142,22 @@ is compatible with arrays of absolute points.
Doctest.expect(lpf.next(20), 12.0)
Doctest.expect(lpf.next(10), 10.32)
</script>
<h2>
References
</h2>
<h2>References</h2>
<ul>
<li><a href="https://en.wikipedia.org/wiki/Circular_buffer">
Circular buffer
</a></li>
<li><a href="http://stackoverflow.com/questions/20867562/create-a-date-object-with-cet-timezone">
<li><a href="https://en.wikipedia.org/wiki/Circular_buffer"> Circular buffer </a></li>
<li>
<a href="http://stackoverflow.com/questions/20867562/create-a-date-object-with-cet-timezone">
Create a Date object with CET timezone
</a></li>
<li> <a href="http://stackoverflow.com/questions/315760/what-is-the-best-way-to-determine-the-number-of-days-in-a-month-with-javascript">
</a>
</li>
<li>
<a
href="http://stackoverflow.com/questions/315760/what-is-the-best-way-to-determine-the-number-of-days-in-a-month-with-javascript"
>
What is the best way to determine the number of days in a month with javascript?
</a></li>
</a>
</li>
</ul>
</main>
</body>
</html>