https://aplwiki.com/api.php?action=feedcontributions&user=RLevine&feedformat=atomAPL Wiki - User contributions [en-gb]2024-03-29T11:23:59ZUser contributionsMediaWiki 1.38.2https://aplwiki.com/index.php?title=Fonts&diff=9993Fonts2022-12-10T00:13:44Z<p>RLevine: /* Rendering APL on websites */</p>
<hr />
<div>With the prevalence of [[Unicode]], many systems render APL legibly out-of-the-box. However, for a uniform appearance, the font should be designed with APL in mind.<ref>Phil Chastney: ''[https://web.archive.org/web/20161005120746/http://www.chastney.com/~philip/SImPL/APL_fonts_are_different.pdf APL fonts are different]''<br />
</ref> This article lists some fonts that are suited for APL, and shows how to use them.<br />
== Monospace ==<br />
{|class=wikitable<br />
!Name<br>(website) !! Source<br>(download) !! Description !! Sample<br />
|-<br />
| [https://www.ibm.com/us-en/marketplace/apl2 APL2 Unicode] || [https://www.ibm.com/account/reg/us-en/signup?formid=urx-32206 IBM] || Straight from IBM typewriter terminals with oblique letters. ||<br />
[[File:APL2 Unicode.png|none]]<br />
|-<br />
|[https://abrudz.github.io/APL2741/ APL2741 Unicode]||[https://github.com/abrudz/APL2741/raw/main/APL2741%20Unicode.ttf GitHub]||Unicode version of APL2741 with more characters.||<br />
[[File:APL2741.png|none]]<br />
|-<br />
|[http://apl385.com/fonts/index.htm APL385 Unicode]||[http://apl385.com/fonts/apl385.zip Adrian Smith]||Inspired by Comic Sans Serif.||<br />
[[File:APL385 Unicode.png|none]]<br />
|-<br />
|[https://abrudz.github.io/APL386/ APL386 Unicode]||[https://github.com/abrudz/APL386/raw/master/APL386.ttf GitHub]||APL385 Unicode with fewer issues and more accented characters.||<br />
[[File:APL386 Unicode.png|none]]<br />
|-<br />
|[https://github.com/dzaima/BQN386 BQN386 Unicode]||[https://github.com/dzaima/BQN386/blob/master/BQN386.ttf?raw=true GitHub]||Re-hinted APL386 Unicode with harmonised glyphs and support for [[BQN]].||<br />
[[File:APL386 Unicode.png|none]]<br />
|-<br />
| [http://www.microapl.com/apl/learn_apl.html APLX Upright] || [http://www.microapl.co.uk/download/aplx_unicode.ttf MicroAPL] || A monospaced grotesque font, reminiscent of Akzidenz-Grotesk.||<br />
[[File:APLX Upright.png|none]]<br />
|-<br />
| [https://www.ibm.com/us-en/marketplace/apl2 Courier APL2 Unicode] || [https://www.ibm.com/account/reg/us-en/signup?formid=urx-32206 IBM] || The classic Courier typewriter font, extended with APL symbols.||<br />
[[File:Courier APL2 Unicode.png|none]]<br />
|-<br />
|[https://mlochbaum.github.io/BQN/fonts.html DejaVu BQN Sans Mono]||[https://github.com/mlochbaum/BQN/blob/master/docs/DejaVuBQNSansMono.ttf?raw=true GitHub]||DejaVu Sans Mono with support for [[BQN]].||<br />
[[File:DejaVu Sans Mono.png|none]]<br />
|-<br />
|[https://dejavu-fonts.github.io/ DejaVu Sans Mono]||[https://github.com/senotrusov/dejavu-fonts-ttf/raw/master/ttf/DejaVuSansMono.ttf GitHub]||Wide range of characters with original look and feel of Vera.||<br />
[[File:DejaVu Sans Mono.png|none]]<br />
|-<br />
|[https://github.com/chrismwendt/bront DejaVu Sans Mono Bront]||[https://github.com/chrismwendt/bront/raw/master/DejaVuSansMono-Bront.ttf GitHub]|| DejaVu Sans Mono tweaked to be better geared for programming.||<br />
[[File:DejaVu Sans Mono Bront.png|none]]<br />
|-<br />
|[https://www.nerdfonts.com/ DejaVu Sans Mono Nerd]||[https://raw.githubusercontent.com/ryanoasis/nerd-fonts/v2.0.0/patched-fonts/DejaVuSansMono/Regular/complete/DejaVu%20Sans%20Mono%20Nerd%20Font%20Complete%20Mono.ttf AUR]|| DejaVu Sans Mono patched with a high number of extra glyphs.||[[File:DejaVu Sans Mono.png|none]]<br />
|-<br />
| [https://www.evertype.com/emono/ Everson Mono] || [https://www.evertype.com/emono/evermono-beta.zip Evertype] (shareware) || A simple font, quite legible at sizes as small as 4 points. || [[File:Everson Mono.png|none]]<br />
|-<br />
| [https://www.kreativekorp.com/software/fonts/fairfax.shtml Fairfax] || rowspan=2|[https://www.kreativekorp.com/swdownload/fonts/relaybm/fairfax.zip KreativeKorp] || Regular/Bold/Italic 6×12 bitmap font supporting many characters. || [[File:Fairfax.png|none]]<br />
|-<br />
| [https://www.kreativekorp.com/software/fonts/fairfax.shtml Fairfax Serif] || Serif 6×12 bitmap font supporting many characters. || [[File:Fairfax_Serif.png|none]]<br />
|-<br />
| [https://www.kreativekorp.com/software/fonts/fairfaxhd.shtml Fairfax HD] || [https://www.kreativekorp.com/swdownload/fonts/core/fairfaxhd.zip KreativeKorp] || Plotter-like font supporting many characters. || [[File:Fairfax HD.png|none]]<br />
|-<br />
| [https://github.com/Tortus-exe/FiraCode Fira Code APL] || [https://github.com/Tortus-exe/FiraCode/raw/master/FiraCodeAPL-Regular.otf Github] || A special version of the free monospaced font with programming ligatures which supports APL and BQN glyphs. ||<br />
[[File:Fira_Code_APL_Unbolded.png|none|500px]]<br />
|-<br />
| [https://github.com/rbanffy/3270font IBM 3270] || [https://github.com/rbanffy/3270font/releases/download/v2.2.1/3270_fonts_70de9c7.zip GitHub] || Modern version of a classic [[IBM]] terminal font. || [[File:IBM 3270.png|none|500px]]<br />
|-<br />
| [https://typeof.net/Iosevka/ Iosevka] Anonymous Pro Style || [https://github.com/be5invis/Iosevka/releases/download/v10.1.1/ttf-iosevka-fixed-ss02-10.1.1.zip GitHub]||rowspan=7|A slender, highly customisable monospace sans-serif and slab-serif typeface inspired by Pragmata Pro, M+ and PF DIN Mono. This list includes seven ready-made versions, but it is easy to build one's own version too. When compiling, it is possible to configure character variants with <code>apl-form = 'enable'</code> to prioritise harmonising APL glyphs. ||[[File:Iosevka Anonymous Pro.png|none]]<br />
|-<br />
| [https://typeof.net/Iosevka/ Iosevka] Fira Mono Style || [https://github.com/be5invis/Iosevka/releases/download/v10.1.1/ttf-iosevka-fixed-ss05-10.1.1.zip GitHub] || [[File:Iosevka Fira Mono.png|none]]<br />
|-<br />
| [https://typeof.net/Iosevka/ Iosevka] Pragmata Pro Style || [https://github.com/be5invis/Iosevka/releases/download/v10.1.1/ttf-iosevka-fixed-ss08-10.1.1.zip GitHub] || [[File:Iosevka Pragmata Pro.png|none]]<br />
|-<br />
| [https://typeof.net/Iosevka/ Iosevka] Source Code Pro Style || [https://github.com/be5invis/Iosevka/releases/download/v10.1.1/ttf-iosevka-fixed-ss09-10.1.1.zip GitHub] || [[File:Iosevka Source Code Pro.png|none]]<br />
|-<br />
| [https://typeof.net/Iosevka/ Iosevka] JetBrains Mono Style || [https://github.com/be5invis/Iosevka/releases/download/v10.1.1/ttf-iosevka-fixed-ss14-10.1.1.zip GitHub] || [[File:Iosevka JetBrains Mono.png|none]]<br />
|-<br />
| [https://typeof.net/Iosevka/ Iosevka] IBM Plex Mono Style || [https://github.com/be5invis/Iosevka/releases/download/v10.1.1/ttf-iosevka-fixed-ss15-10.1.1.zip GitHub] || [[File:Iosevka IBM Plex Mono.png|none]]<br />
|-<br />
| [https://typeof.net/Iosevka/ Iosevka] Recursive Mono Style || [https://github.com/be5invis/Iosevka/releases/download/v10.1.1/ttf-iosevka-fixed-ss17-10.1.1.zip GitHub] || [[File:Iosevka Recursive Mono.png|none]]<br />
|-<br />
| [https://codeberg.org/Wezl/fonts poultreMono] || [https://codeberg.org/attachments/042040b4-ca97-4ffe-8401-540d4921e534 Codeberg] || A 5×9 pixel font. || [[File:PoultreMono.png|none]]<br />
|-<br />
| [https://www.fsd.it/shop/fonts/pragmatapro/ PragmataPro] || (commercial) || A condensed font optimized for coding, mathematics and engineering.||<br />
[[File:PragmataPro.png|none]]<br />
|-<br />
| [https://abrudz.github.io/SAX2/ SAX2] || [https://github.com/abrudz/SAX2/raw/master/SAX2.ttf GitHub]||Curly font with italic letters, based on Sharp APL for Unix.||<br />
[[File:SAX2.png|none]]<br />
|-<br />
|[http://archive.vector.org.uk/art10002160 SImPL] ||[http://archive.vector.org.uk/resource/simpl02.zip Vector]||Courier-based, but thicker.||<br />
[[File:SImPL.png|none]]<br />
|-<br />
|[https://unifoundry.com/unifont/index.html Unifont] || [https://unifoundry.com/pub/unifont/unifont-13.0.06/font-builds/unifont-13.0.06.ttf Unifoundry] || Low-resolution bitmap fall-back font || [[File:Unifont.png|none]]<br />
|}<br />
<br />
== Proportional ==<br />
{|class=wikitable<br />
!Name<br>(website) !! Source<br>(download) !! Description !! Sample<br />
|-<br />
|[http://apl385.com/fonts/index.htm APL333]|| [http://apl385.com/fonts/apl333.zip Adrian Smith] || Proportionally spaced version of APL385 Unicode||<br />
[[File:APL333.png|none]]<br />
|-<br />
| [https://en.wikipedia.org/wiki/Code2000 Code2000] || [https://www.fontspace.com/code2000-font-f13284 FontSpace] || Wedge-serif pan-Unicode font. || <br />
[[File:Code2000.png|none]]<br />
|-<br />
| [https://typeof.net/Iosevka/ Iosevka Aile] || [https://github.com/be5invis/Iosevka/releases/download/v5.0.4/ttf-iosevka-aile-5.0.4.zip GitHub]|| Proportionally spaced version of Iosevka. ||<br />
[[File:Iosevka Aile.png|none]]<br />
|-<br />
| [https://typeof.net/Iosevka/ Iosevka Etoile] || [https://github.com/be5invis/Iosevka/releases/download/v5.0.4/ttf-iosevka-fixed-ss02-5.0.4.zip GitHub]|| Proportionally spaced slab-serif version of Iosevka. ||<br />
[[File:Iosevka Etoile.png|none]]<br />
|-<br />
| [http://www.quivira-font.com/ Quivira] || [http://www.quivira-font.com/files/Quivira.otf Website] || Serif font supporting many symbols, similar to Garamond. || <br />
[[File:Quivira.png|none]]<br />
|-<br />
| [https://www.fonts.com/font/microsoft-corporation/segoe-ui-symbol Segoe UI Symbol] || (commercial) || Microsoft's humanist interface and corporate font. || [[File:Segoe UI Symbol.png|none]]<br />
|-<br />
|[https://www.stixfonts.org/ Stix Two Math]||[https://github.com/stipub/stixfonts/archive/v2.0.2.zip GitHub]|| Serif font, broadly compatible with Times New Roman.||<br />
[[File:Stix Two Math.png|none]]<br />
|-<br />
|[https://dn-works.com/ufas/ Symbola] || [https://dn-works.com/wp-content/uploads/2020/UFAS-Fonts/Symbola.zip UFAS] (free for personal non-commercial use only) || Supporting many scripts and symbols, similar to Computer Modern. || [[File:Screenshot 2021-03-19 Screenshot.png|none]]<br />
|}<br />
<br />
[[File:APLTypeBall.jpg|thumb|right|The APL typeball]]<br />
<br />
== Historical anecdote ==<br />
Using [[IBM]]'s [[APL\360]] required the use of the [[wikipedia:IBM_2741#APL\360|IBM 2741]] or [[wikipedia:IBM 1050|IBM 1050]] printing terminal with an APL [[wikipedia:type ball|type ball]]. The APL2741 font is based directly on this type ball.<br />
<br />
== Rendering APL on websites ==<br />
For APL code to be rendered well on a website, three conditions must be fulfilled:<br />
# The page has to use a proper encoding<br />
# The APL code has to be formatted with an appropriate APL font<br />
# The APL font has to be made available for those users that do not have it installed<br />
All these things can be achieved by inserting the following into the <syntaxhighlight lang=html inline><head></syntaxhighlight> element of the page.<br />
Replace font name and file name with values corresponding to the desired font:<br />
<syntaxhighlight lang=html><br />
<meta charset="UTF-8"><br />
<style><br />
@font-face {<br />
font-family: APL; <br />
src: local("APL385 Unicode"), url(Apl385.ttf)<br />
}<br />
pre, code {<br />
font-family: APL<br />
}<br />
</style><br />
</syntaxhighlight><br />
The <syntaxhighlight lang=shell inline>Apl385.ttf</syntaxhighlight> font file must be placed in the same directory as the HTML file, and all APL code must be wrapped in <syntaxhighlight lang=html inline><pre></syntaxhighlight> or <syntaxhighlight lang=html inline><code></syntaxhighlight> elements.<br />
<br />
== Changing font in Dyalog RIDE ==<br />
[[Dyalog Ltd]]'s cross-platform RIDE interface, which is the default GUI interface on all non-Windows platforms, does not expose a font setting. However, it is trivial to change font:<br />
* Open ride-base.css[[#loc|*]]<br />
* Find the line that says <syntaxhighlight lang=css inline>src: url('./fonts/Apl385.woff') format('woff'), url('./fonts/Apl385.ttf') format('truetype');</syntaxhighlight><br />
* Insert <syntaxhighlight lang=css inline>local('font name'),</syntaxhighlight> immediately after <syntaxhighlight lang=css inline>src:</syntaxhighlight>, for example <syntaxhighlight lang=css inline>src: local('SAX2'), url('./fonts/Apl385.woff') format('woff'), url('./fonts/Apl385.ttf') format('truetype');</syntaxhighlight><br />
* Restart RIDE<br />
<br />
<span id=loc>[[#Changing font in Dyalog RIDE|*]]</span> The full path to ride-base.css varies (examples for RIDE 4.4 and Dyalog 18.2):<br />
:* Stand-alone installation:<br />
:** Windows: %LOCALAPPDATA%\Programs\Dyalog\Ride-4.4\resources\app\style\ride-base.css<br />
:** Linux: /opt/ride-4.4/resources/app/style/ride-base.css<br />
:** macOS: /Applications/Ride-4.4.app/resources/app/style/ride-base.css<br />
:* Zero-footprint RIDE (served by the interpreter and normally accessed through a browser):<br />
:** Linux or AIX: /opt/mdyalog/18.2/64/unicode/Contents/Resources/Dyalog/RIDEapp/resources/app/style/ride-base.css<br />
:** macOS: /Applications/Dyalog-18.2.app/Contents/Resources/Dyalog/RIDEapp/resources/app/style/ride-base.css<br />
<br />
== References ==<br />
<references/><br />
{{APL development}}[[Category:APL character set]][[Category:Lists]]</div>RLevinehttps://aplwiki.com/index.php?title=Fonts&diff=9951Fonts2022-11-30T18:39:18Z<p>RLevine: </p>
<hr />
<div>With the prevalence of [[Unicode]], many systems render APL legibly out-of-the-box. However, for a uniform appearance, the font should be designed with APL in mind.<ref>Phil Chastney: ''[https://web.archive.org/web/20161005120746/http://www.chastney.com/~philip/SImPL/APL_fonts_are_different.pdf APL fonts are different]''<br />
</ref> This article lists some fonts that are suited for APL, and shows how to use them.<br />
== Monospace ==<br />
{|class=wikitable<br />
!Name<br>(website) !! Source<br>(download) !! Description !! Sample<br />
|-<br />
| [https://www.ibm.com/us-en/marketplace/apl2 APL2 Unicode] || [https://www.ibm.com/account/reg/us-en/signup?formid=urx-32206 IBM] || Straight from IBM typewriter terminals with oblique letters. ||<br />
[[File:APL2 Unicode.png|none]]<br />
|-<br />
|[https://abrudz.github.io/APL2741/ APL2741 Unicode]||[https://github.com/abrudz/APL2741/raw/main/APL2741%20Unicode.ttf GitHub]||Unicode version of APL2741 with more characters.||<br />
[[File:APL2741.png|none]]<br />
|-<br />
|[http://apl385.com/fonts/index.htm APL385 Unicode]||[http://apl385.com/fonts/apl385.zip Adrian Smith]||Inspired by Comic Sans Serif.||<br />
[[File:APL385 Unicode.png|none]]<br />
|-<br />
|[https://abrudz.github.io/APL386/ APL386 Unicode]||[https://github.com/abrudz/APL386/raw/master/APL386.ttf GitHub]||APL385 Unicode with fewer issues and more accented characters.||<br />
[[File:APL386 Unicode.png|none]]<br />
|-<br />
|[https://github.com/dzaima/BQN386 BQN386 Unicode]||[https://github.com/dzaima/BQN386/blob/master/BQN386.ttf?raw=true GitHub]||Re-hinted APL386 Unicode with harmonised glyphs and support for [[BQN]].||<br />
[[File:APL386 Unicode.png|none]]<br />
|-<br />
| [http://www.microapl.com/apl/learn_apl.html APLX Upright] || [http://www.microapl.co.uk/download/aplx_unicode.ttf MicroAPL] || A monospaced grotesque font, reminiscent of Akzidenz-Grotesk.||<br />
[[File:APLX Upright.png|none]]<br />
|-<br />
| [https://www.ibm.com/us-en/marketplace/apl2 Courier APL2 Unicode] || [https://www.ibm.com/account/reg/us-en/signup?formid=urx-32206 IBM] || The classic Courier typewriter font, extended with APL symbols.||<br />
[[File:Courier APL2 Unicode.png|none]]<br />
|-<br />
|[https://mlochbaum.github.io/BQN/fonts.html DejaVu BQN Sans Mono]||[https://github.com/mlochbaum/BQN/blob/master/docs/DejaVuBQNSansMono.ttf?raw=true GitHub]||DejaVu Sans Mono with support for [[BQN]].||<br />
[[File:DejaVu Sans Mono.png|none]]<br />
|-<br />
|[https://dejavu-fonts.github.io/ DejaVu Sans Mono]||[https://github.com/senotrusov/dejavu-fonts-ttf/raw/master/ttf/DejaVuSansMono.ttf GitHub]||Wide range of characters with original look and feel of Vera.||<br />
[[File:DejaVu Sans Mono.png|none]]<br />
|-<br />
|[https://github.com/chrismwendt/bront DejaVu Sans Mono Bront]||[https://github.com/chrismwendt/bront/raw/master/DejaVuSansMono-Bront.ttf GitHub]|| DejaVu Sans Mono tweaked to be better geared for programming.||<br />
[[File:DejaVu Sans Mono Bront.png|none]]<br />
|-<br />
|[https://www.nerdfonts.com/ DejaVu Sans Mono Nerd]||[https://raw.githubusercontent.com/ryanoasis/nerd-fonts/v2.0.0/patched-fonts/DejaVuSansMono/Regular/complete/DejaVu%20Sans%20Mono%20Nerd%20Font%20Complete%20Mono.ttf AUR]|| DejaVu Sans Mono patched with a high number of extra glyphs.||[[File:DejaVu Sans Mono.png|none]]<br />
|-<br />
| [https://www.evertype.com/emono/ Everson Mono] || [https://www.evertype.com/emono/evermono-beta.zip Evertype] (shareware) || A simple font, quite legible at sizes as small as 4 points. || [[File:Everson Mono.png|none]]<br />
|-<br />
| [https://www.kreativekorp.com/software/fonts/fairfax.shtml Fairfax] || rowspan=2|[https://www.kreativekorp.com/swdownload/fonts/relaybm/fairfax.zip KreativeKorp] || Regular/Bold/Italic 6×12 bitmap font supporting many characters. || [[File:Fairfax.png|none]]<br />
|-<br />
| [https://www.kreativekorp.com/software/fonts/fairfax.shtml Fairfax Serif] || Serif 6×12 bitmap font supporting many characters. || [[File:Fairfax_Serif.png|none]]<br />
|-<br />
| [https://www.kreativekorp.com/software/fonts/fairfaxhd.shtml Fairfax HD] || [https://www.kreativekorp.com/swdownload/fonts/core/fairfaxhd.zip KreativeKorp] || Plotter-like font supporting many characters. || [[File:Fairfax HD.png|none]]<br />
|-<br />
| [https://github.com/Tortus-exe/FiraCode Fira Code APL] || [https://github.com/Tortus-exe/FiraCode/raw/master/FiraCodeAPL-Regular.otf Github] || A special version of the free monospaced font with programming ligatures which supports APL and BQN glyphs. ||<br />
[[File:Fira_Code_APL_Unbolded.png|none|500px]]<br />
|-<br />
| [https://github.com/rbanffy/3270font IBM 3270] || [https://github.com/rbanffy/3270font/releases/download/v2.2.1/3270_fonts_70de9c7.zip GitHub] || Modern version of a classic [[IBM]] terminal font. || [[File:IBM 3270.png|none|500px]]<br />
|-<br />
| [https://typeof.net/Iosevka/ Iosevka] Anonymous Pro Style || [https://github.com/be5invis/Iosevka/releases/download/v10.1.1/ttf-iosevka-fixed-ss02-10.1.1.zip GitHub]||rowspan=7|A slender, highly customisable monospace sans-serif and slab-serif typeface inspired by Pragmata Pro, M+ and PF DIN Mono. This list includes seven ready-made versions, but it is easy to build one's own version too. When compiling, it is possible to configure character variants with <code>apl-form = 'enable'</code> to prioritise harmonising APL glyphs. ||[[File:Iosevka Anonymous Pro.png|none]]<br />
|-<br />
| [https://typeof.net/Iosevka/ Iosevka] Fira Mono Style || [https://github.com/be5invis/Iosevka/releases/download/v10.1.1/ttf-iosevka-fixed-ss05-10.1.1.zip GitHub] || [[File:Iosevka Fira Mono.png|none]]<br />
|-<br />
| [https://typeof.net/Iosevka/ Iosevka] Pragmata Pro Style || [https://github.com/be5invis/Iosevka/releases/download/v10.1.1/ttf-iosevka-fixed-ss08-10.1.1.zip GitHub] || [[File:Iosevka Pragmata Pro.png|none]]<br />
|-<br />
| [https://typeof.net/Iosevka/ Iosevka] Source Code Pro Style || [https://github.com/be5invis/Iosevka/releases/download/v10.1.1/ttf-iosevka-fixed-ss09-10.1.1.zip GitHub] || [[File:Iosevka Source Code Pro.png|none]]<br />
|-<br />
| [https://typeof.net/Iosevka/ Iosevka] JetBrains Mono Style || [https://github.com/be5invis/Iosevka/releases/download/v10.1.1/ttf-iosevka-fixed-ss14-10.1.1.zip GitHub] || [[File:Iosevka JetBrains Mono.png|none]]<br />
|-<br />
| [https://typeof.net/Iosevka/ Iosevka] IBM Plex Mono Style || [https://github.com/be5invis/Iosevka/releases/download/v10.1.1/ttf-iosevka-fixed-ss15-10.1.1.zip GitHub] || [[File:Iosevka IBM Plex Mono.png|none]]<br />
|-<br />
| [https://typeof.net/Iosevka/ Iosevka] Recursive Mono Style || [https://github.com/be5invis/Iosevka/releases/download/v10.1.1/ttf-iosevka-fixed-ss17-10.1.1.zip GitHub] || [[File:Iosevka Recursive Mono.png|none]]<br />
|-<br />
| [https://codeberg.org/Wezl/fonts poultreMono] || [https://codeberg.org/attachments/042040b4-ca97-4ffe-8401-540d4921e534 Codeberg] || A 5×9 pixel font. || [[File:PoultreMono.png|none]]<br />
|-<br />
| [https://www.fsd.it/shop/fonts/pragmatapro/ PragmataPro] || (commercial) || A condensed font optimized for coding, mathematics and engineering.||<br />
[[File:PragmataPro.png|none]]<br />
|-<br />
| [https://abrudz.github.io/SAX2/ SAX2] || [https://github.com/abrudz/SAX2/raw/master/SAX2.ttf GitHub]||Curly font with italic letters, based on Sharp APL for Unix.||<br />
[[File:SAX2.png|none]]<br />
|-<br />
|[http://archive.vector.org.uk/art10002160 SImPL] ||[http://archive.vector.org.uk/resource/simpl02.zip Vector]||Courier-based, but thicker.||<br />
[[File:SImPL.png|none]]<br />
|-<br />
|[https://unifoundry.com/unifont/index.html Unifont] || [https://unifoundry.com/pub/unifont/unifont-13.0.06/font-builds/unifont-13.0.06.ttf Unifoundry] || Low-resolution bitmap fall-back font || [[File:Unifont.png|none]]<br />
|}<br />
<br />
== Proportional ==<br />
{|class=wikitable<br />
!Name<br>(website) !! Source<br>(download) !! Description !! Sample<br />
|-<br />
|[http://apl385.com/fonts/index.htm APL333]|| [http://apl385.com/fonts/apl333.zip Adrian Smith] || Proportionally spaced version of APL385 Unicode||<br />
[[File:APL333.png|none]]<br />
|-<br />
| [https://en.wikipedia.org/wiki/Code2000 Code2000] || [https://www.fontspace.com/code2000-font-f13284 FontSpace] || Wedge-serif pan-Unicode font. || <br />
[[File:Code2000.png|none]]<br />
|-<br />
| [https://typeof.net/Iosevka/ Iosevka Aile] || [https://github.com/be5invis/Iosevka/releases/download/v5.0.4/ttf-iosevka-aile-5.0.4.zip GitHub]|| Proportionally spaced version of Iosevka. ||<br />
[[File:Iosevka Aile.png|none]]<br />
|-<br />
| [https://typeof.net/Iosevka/ Iosevka Etoile] || [https://github.com/be5invis/Iosevka/releases/download/v5.0.4/ttf-iosevka-fixed-ss02-5.0.4.zip GitHub]|| Proportionally spaced slab-serif version of Iosevka. ||<br />
[[File:Iosevka Etoile.png|none]]<br />
|-<br />
| [http://www.quivira-font.com/ Quivira] || [http://www.quivira-font.com/files/Quivira.otf Website] || Serif font supporting many symbols, similar to Garamond. || <br />
[[File:Quivira.png|none]]<br />
|-<br />
| [https://www.fonts.com/font/microsoft-corporation/segoe-ui-symbol Segoe UI Symbol] || (commercial) || Microsoft's humanist interface and corporate font. || [[File:Segoe UI Symbol.png|none]]<br />
|-<br />
|[https://www.stixfonts.org/ Stix Two Math]||[https://github.com/stipub/stixfonts/archive/v2.0.2.zip GitHub]|| Serif font, broadly compatible with Times New Roman.||<br />
[[File:Stix Two Math.png|none]]<br />
|-<br />
|[https://dn-works.com/ufas/ Symbola] || [https://dn-works.com/wp-content/uploads/2020/UFAS-Fonts/Symbola.zip UFAS] (free for personal non-commercial use only) || Supporting many scripts and symbols, similar to Computer Modern. || [[File:Screenshot 2021-03-19 Screenshot.png|none]]<br />
|}<br />
<br />
[[File:APLTypeBall.jpg|thumb|right|The APL typeball]]<br />
<br />
== Historical anecdote ==<br />
Using [[IBM]]'s [[APL\360]] required the use of the [[wikipedia:IBM_2741#APL\360|IBM 2741]] or [[wikipedia:IBM 1050|IBM 1050]] printing terminal with an APL [[wikipedia:type ball|type ball]]. The APL2741 font is based directly on this type ball.<br />
<br />
== Rendering APL on websites ==<br />
For APL code to be rendered well on a website, three conditions must be fulfilled:<br />
# The page has to use a proper encoding<br />
# The APL code has to be formatted with an appropriate APL font<br />
# The APL font has to be made available for those users that do not have it installed<br />
All these things can be achieved by inserting the following into the <syntaxhighlight lang=html inline><head></syntaxhighlight> element of the page (replace font name and file name with desired font):<br />
<syntaxhighlight lang=html><br />
<meta charset="UTF-8"><br />
<style><br />
@font-face{<br />
font-family: APL; src: local("APL385 Unicode"), url(Apl385.ttf)<br />
}<br />
pre, code {<br />
font-family: APL<br />
}<br />
</style><br />
</syntaxhighlight><br />
The <syntaxhighlight lang=shell inline>Apl385.ttf</syntaxhighlight> file must then be placed in the same directory as the HTML file, and all APL code must be wrapped in <syntaxhighlight lang=html inline><pre></syntaxhighlight> or <syntaxhighlight lang=html inline><code></syntaxhighlight> elements.<br />
<br />
== Changing font in Dyalog RIDE ==<br />
[[Dyalog Ltd]]'s cross-platform RIDE interface, which is the default GUI interface on all non-Windows platforms, does not expose a font setting. However, it is trivial to change font:<br />
* Open ride-base.css[[#loc|*]]<br />
* Find the line that says <syntaxhighlight lang=css inline>src: url('./fonts/Apl385.woff') format('woff'), url('./fonts/Apl385.ttf') format('truetype');</syntaxhighlight><br />
* Insert <syntaxhighlight lang=css inline>local('font name'),</syntaxhighlight> immediately after <syntaxhighlight lang=css inline>src:</syntaxhighlight>, for example <syntaxhighlight lang=css inline>src: local('SAX2'), url('./fonts/Apl385.woff') format('woff'), url('./fonts/Apl385.ttf') format('truetype');</syntaxhighlight><br />
* Restart RIDE<br />
<br />
<span id=loc>[[#Changing font in Dyalog RIDE|*]]</span> The full path to ride-base.css varies (examples for RIDE 4.4 and Dyalog 18.2):<br />
:* Stand-alone installation:<br />
:** Windows: %LOCALAPPDATA%\Programs\Dyalog\Ride-4.4\resources\app\style\ride-base.css<br />
:** Linux: /opt/ride-4.4/resources/app/style/ride-base.css<br />
:** macOS: /Applications/Ride-4.4.app/resources/app/style/ride-base.css<br />
:* Zero-footprint RIDE (served by the interpreter and normally accessed through a browser):<br />
:** Linux or AIX: /opt/mdyalog/18.2/64/unicode/Contents/Resources/Dyalog/RIDEapp/resources/app/style/ride-base.css<br />
:** macOS: /Applications/Dyalog-18.2.app/Contents/Resources/Dyalog/RIDEapp/resources/app/style/ride-base.css<br />
<br />
== References ==<br />
<references/><br />
{{APL development}}[[Category:APL character set]][[Category:Lists]]</div>RLevinehttps://aplwiki.com/index.php?title=Talk:APL_logo&diff=8158Talk:APL logo2022-02-10T16:02:34Z<p>RLevine: /* Parallel lines comment by RLevine (talk) */</p>
<hr />
<div>On this page, you can leave feedback or submit ideas, but note that '''voting is currently happening'''.<br />
<br />
* [{{fullurl:{{TALKPAGENAME}}|action=edit&section=new&preloadtitle=%5Blogo%20name%5D%20comment%20by%20~~<noinclude></noinclude>~}} Click here to comment on an existing proposal.]<br />
<br />
* [{{fullurl:{{TALKPAGENAME}}|action=edit&section=new&preloadtitle=General%20comment%20by%20~~<noinclude></noinclude>~}} Click here to leave a general comment.]<br />
<br />
== Nested bitmaps comment by LdBeth ==<br />
<br />
I love the bitmap style font used in this logo, and this one comes with many variations.<br />
Might be great if combined with the dot halftone style logo used for APL Wiki.<br />
<br />
== Parallel lines comment by RGS ==<br />
<br />
The “parallel lines” logo is very hard to read and it's hard to understand that there's an “APL” written in there.<br />
In general, I would go for things that are easy to read.<br />
<br />
== Display matrix comment by [[User:PaulMansour|PaulMansour]] ([[User talk:PaulMansour|talk]]) ==<br />
<br />
This is an excellent starting point, but rather than the exact output of the DISPLAY function, a good graphic designer could stylize it a bit, perhaps removing some white space, a little kerning on the letters, some color, etc.<br />
<br />
== Cube apple comment by [[User:Ros|Ros]] ([[User talk:Ros|talk]]) ==<br />
<br />
Stylistically, I like this logo the best - but it is my least preferred option: for me, it is too reminiscent of the [[Dyalog APL|Dyalog]] application logo to be a general and independent APL logo. [[User:Ros|Ros]] ([[User talk:Ros|talk]]) 09:17, 8 October 2021 (UTC)<br />
<br />
== Script apple comment by Fiona ==<br />
<br />
Although I rather like the "hollow" version of this, Dyalog Ltd have already adopted a slight variation of this for use as the APL Seeds logo (user meetings, events and information specifically for new APLers) – [https://www.dyalog.com/apl-seeds-user-meetings/aplseeds21.htm see here for an example] and the detail makes it harder to shrink. The filled version is slightly more reminiscent of a bell pepper than an apple to me – I prefer the shape of the (otherwise similar) 50 Years one further down the page.<br />
<br />
== Cube apple comment by [[User:Fiona|Fiona]] ([[User talk:Fiona|talk]]) ==<br />
<br />
I like the cube representation and its array implications but it's maybe a tad too similar to the [https://aplwiki.com/wiki/Dyalog_APL| Dyalog product logo]. I really dislike the text – on first impression it looked odd, and when realising that it's APL glyphs instead of letters it just seemed a bit of an inside joke that might alienate those who are not in the know (the same comment applies to the "Lamp Rho Downstile" and "APL matrix" logos).<br />
<br />
== Parallel lines comment by [[User:Fiona|Fiona]] ([[User talk:Fiona|talk]]) ==<br />
<br />
This might appeal to those who have fond memories of the rather brilliant book, but it looks very dated, is hard to read unless you already know what it said, wouldn't render well when small, and wouldn't work in black-and-white.<br />
<br />
== General comment by MichaelBaas ==<br />
<br />
It would be useful if the icons were shown in the same size(s), perhaps 32x32 as a miniature version (favicon etc.) and 192 x 192, and maybe each on a black and on a white background - so 4 versions per icon.<br />
<br />
== Plain Ellipse comment by [[User:PaulMansour|PaulMansour]] ([[User talk:PaulMansour|talk]]) ==<br />
<br />
Very nice. Simple, clean, should be good at all sizes. Gets my vote!<br />
<br />
== Display matrix comment by [[User:DanHirschi|DanHirschi]] ([[User talk:DanHirschi|talk]]) ==<br />
<br />
I actually like this one. If placed in the matrix of other logos above, it would stand out a bit because of its simplicity (I think the white space actually helps). <br />
Possible changes (that might improve it):<br />
- make the letters and box a bit thicker<br />
- use the older font where the characters are more italicized<br />
- use the old underscored font<br />
- as mentioned, adjust the spacing between the letters<br />
<br />
== Plain Ellipse comment by [[User:Fiona|Fiona]] ([[User talk:Fiona|talk]]) ==<br />
<br />
I agree with Paul's comment on the clarity and simplicity of this design but would suggest that it is not taken forward in this colour due to its similarity to an existing logo: APL Media's logo is a lower case "apl" in a red circle – https://twitter.com/apl_media – but perhaps a different single colour (green?) would introduce more differentiation.<br />
<br />
== APL Rotated Array comment by [[Adám Brudzewsky]] ==<br />
<br />
I quite like this one. It is simple and timeless.<br />
<br />
However, I will dispute that the [[APL Wiki logo]] is "the most established APL logo to date". It was in fact recently changed from its previous logo, as seen on [https://old.aplwiki.com old.aplwiki.com], which was shared with [https://aplteam.github.io/ APL Team].<br />
<br />
Furthermore, APL isn't a well-recognised language, and so I think it is important that the logo spells out "APL" such that people can at least go search for it.<br />
<br />
== APL Wiki comment by [[User:KSK|KSK]] ([[User talk:KSK|talk]]) ==<br />
<br />
The APL Wiki would be my preference, followed by the Display matrix (which would be nicer if it were boxed up without breaks and maybe slightly slanted), then the Cube Apple.<br />
<br />
== General comment by [[Adám Brudzewsky]] ==<br />
<br />
I think we should avoid a logo based on an apple, to avoid any legal issues with Apple Inc. See justification [https://retrocomputing.stackexchange.com/questions/22375/when-was-an-image-of-an-apple-first-used-to-promote-the-apl-language?noredirect=1#comment73769_22375 here].<br />
<br />
== Display matrix comment by [[User:Razetime|Razetime]] ([[User talk:Razetime|talk]]) ==<br />
<br />
I'd say this is the best one and then simplest by far.<br />
<br />
== General comment by [[Adám Brudzewsky]] ==<br />
<br />
I think the letters "APL" should be clearly legible, and their order be obvious. Some logos are ambiguous if the name is APL or ALP etc. Stylising them as <code>⍝⍴⌊</code> might be fine, but APL isn't well-known, so the logo must give away the name such that people can go search for it.<br />
<br />
== General comment by Dr. Jürgen Sauermann (GNU APL author and maintainer) ==<br />
<br />
All apple based logos: not really vendor-agnostic (too much similarity with Apple Inc.)<br />
<br />
My preferred one: Lamp Rho Downstile. Not sure where the logos are being used but<br />
if I think of e.g. favicon.ico and similar usage (i.e. icons) then the logo should have a<br />
simple structure without tiny details that looks good even as a 32×32 pixel image.<br />
<br />
== General comment by [[User:Peter Cyriax|Peter Cyriax]] ([[User talk:Peter Cyriax|talk]]) ==<br />
<br />
I like almost all of these Logos; but I think we really need to focus on what we are trying to achieve here and then choose a Logo that satisfies those objectives.<br />
<br />
As I understand it, we want a Logo that is used to 'Promote the Use of APL'. If so, the Target Market is people who commision, design or implement IT sytems that could (or should?) be written in APL. Within this group and their influencers, those we most want to reach are the ones who have not even heard of APL, far less know anything about it. We need to sell them the benefits - robust, well functioning sytems with rapid development timelines, flexability and low maintenance. These benefits are what matter the them: their job is to get things done, so they typically have little interest per. se. in the beautiful technology that we care so much about and which gives rise to these benefits.<br><br />
<br><br />
As far as I can make out we propose that the APL Logo will be used to "brand" demonstrations, presentations and systems plus associated documentation; and the core purpose of the Logo is to proclaim to the Target Market: "This is APL in Action", i.e. to promote the APL brand. Also, as far as I can make out, we anticipate that the APL Logo will typically display at a size of around 120 x 120 pixels - not a lot of space for such a big message. Because, what we have to fit into that space is:<br />
1. This is written in APL - Brand Recognition<br><br />
2. APL is (and stands for) "A Programming Language" - the Target Market will not know this; plus we have to distinguish our "APL" from other uses of 'APL'<br><br />
3. APL is a sophisticated IT Tool: it delivers huge benefits... - the Core Message.<br><br />
<br />
<br />
Peter<br />
<br />
== Nested bitmaps comment by [[User:Dnm|Dnm]] ([[User talk:Dnm|talk]]) ==<br />
<br />
+1 for this logo, as my first choice (FWIW).<br />
<br />
== Display matrix comment by [[User:Dnm|Dnm]] ([[User talk:Dnm|talk]]) ==<br />
<br />
Maybe my second choice preference for a logo (again, FWIW).<br />
<br />
== Lamp Box comment by [[User:Soveran|Soveran]] ([[User talk:Soveran|talk]]) ==<br />
<br />
This logo is simple, direct, recognizable, and beautiful. I would love to use it.<br />
<br />
== Lamp Box and Lamp Rho Downstile Box comment by [[Adám Brudzewsky]] ==<br />
<br />
These two could be used in combination, with Lamp Rho Downstile Box being the official logo and Lamp Box being used at small sizes like for favicons.<br />
<br />
== General comment by Richard ==<br />
<br />
Personally I think the logo should be as simple and straightforward as possible. The logo also represents how we see ourselves in the community. It's difficult to express myself with these kind of subtleness in English, but I'll give it a try.<br />
<br />
We should see APL as a major language.There are several YouTube Video's about esoteric languages. And APL is always mentioned in these videos... That is not where it belongs. APL is not a synthetic or artificial language just for fun.<br />
<br />
This must also be reflected in the logo. No cryptic or nerdy design which reflects on the niche people think APL belongs to. No offence meant to other designs!!! Don't put yourself in a place you don't belong or want to be.<br />
<br />
If you google APL, the first hit (in my case)is a ocean transport company. And it's logo is the three APL letters. Same goes for some shoe company (third hit), also the three letters. The APL programming language is not representing some kind of company but a serious programming language with its own applications and territory where it is sublime!<br />
<br />
I am not a programmer and do nothing with software development for my job. I learned myself programming in C during my study (many years ago) to solve problems I encountered. However, what I experienced in C (and the same goes perhaps for a lot of other languages) is that you can start programming right away, and on the way start thinking about the solution. I started with APL three week ago. And this is completely different. First you have to think about the solution and then you start programming. (maybe it even shouldn't be called programming!). And again, I might be very wrong about this because of my lack of programming experience.<br />
<br />
For me, APL is:<br><br />
<br />
''Back to basic. Think first, act (program) later. A direct approach to the solution of your problem.''<br><br />
<br />
And the language reflects this way of thinking. Even the (for a novice) cryptic symbols forces (helps!) you to pick up this mind set. So should the logo.<br />
<br />
== Letters From the Cube comment by [[User:Mlliarm|Mlliarm]] ([[User talk:Mlliarm|talk]]) ==<br />
<br />
This could be read as `APL` but also as `ALP`, so it might confuse those that are not aware of the language name or people outside of the community.<br />
<br />
== APL Wiki comment by [[User:Mlliarm|Mlliarm]] ([[User talk:Mlliarm|talk]]) ==<br />
<br />
I like this one actually.<br />
<br />
- it is very modern as per design.<br />
- it's been used already in the APLwiki page (even though maybe the version with the traditional name in the middle is better) so some of us already feel used to it.<br />
<br />
- It could be decided to use the traditional name APL with the nice curvy font, which will keep a connection with the past of the language this way.<br />
<br />
- If the name was used I'd prefer the Lamp Rho Floor symbols or the curvy font mentioned earlier.<br />
<br />
- If the name was used I don't think if like it to be anywhere else than in the middle. That's only where it's possible to enclose the letters with a bubble.<br />
<br />
- The symbolism might be visible only to those that can recognize a matrix when they see it, but for me it has a deep and important symbolism: everything in APL is an array, be it 0-dimensioned (scalar), 1-dimensioned (vector or array), 2-dimensioned (matrix), n-dimensioned where n greater than 2 (tensor).<br />
<br />
== Quad APL comment by [[User:Mlliarm|Mlliarm]] ([[User talk:Mlliarm|talk]]) ==<br />
<br />
This imho is too cryptic.<br />
<br />
It carries the message that APL code can look like arcane ancient voodoo spells or incantations to [[wiki:Cthulhu|Cthulhu]] and Yog Sothoth. <br />
<br />
So I don't think it'd be a good idea to use this one, no matter how original is the idea of the creator.<br />
<br />
It'd probably scare a beginner off. But I think the general feelings one should get when they lay their eyes on the logo are:<br />
<br />
- aesthetic pleasing: it must have symmetry, be curvy and avoid many angles<br />
<br />
- it has to make them curious or lure them to look into the language.<br />
<br />
Not sure how the APL community can solve the issue that the glyphs bring math traumas to the surface (this is my naive "theory") and so, only those that can see the beauty of it all beyond the weird symbols will stay. <br />
<br />
But I guess this is a problem (or a non problem) that the logo cannot solve, no matter how good and pleasant to the eye it is: for some people the glyphs will scare them away (possible math trauma in the past) and for others (the few mathematically inclined, or those that can handle any math anxiety that a total alien looking language can create to a new user -- like a westerner that tries to learn Japanese) it is this that will attract them to the language.<br />
<br />
I suppose one needs to have a fair amount of weirdness in their mind/psyche to appreciate APL and decide to learn it, and keep pushing through the math anxiety it creates, like learning Japanese.<br />
<br />
== 50 years apple comment by [[User:Mlliarm|Mlliarm]] ([[User talk:Mlliarm|talk]]) ==<br />
<br />
Classic, but not very modern. Also keeps the APL/apple pun around. Not sure how good this is.<br />
<br />
== Display matrix comment by [[User:Mlliarm|Mlliarm]] ([[User talk:Mlliarm|talk]]) ==<br />
<br />
Even though the design is a bit dated, I like a lot the fact that it can be created using the APL REPL and a few chars from the APL character set.<br />
<br />
Maybe with some vidual artistic polishing it could be a strong contestant.<br />
<br />
== Modern comment by [[User:Mlliarm|Mlliarm]] ([[User talk:Mlliarm|talk]]) ==<br />
<br />
I'd avoid the star in the logo...<br />
<br />
In my eyes it makes look like it's an extremist left revolutionary group...<br />
<br />
== Cube apple comment by [[User:Mlliarm|Mlliarm]] ([[User talk:Mlliarm|talk]]) ==<br />
<br />
I like this very much:<br />
<br />
- it has the apple looking design, so here's the connection with the past<br />
<br />
- the apple looks like a design from a cubist painter, and very modern, so here's the connection to the present and the future. Also being a cube, it has a strong reference to the basic data structure of the language (array) and suggests that APL works with n-dimensional data too<br />
<br />
- finally, it has the curvy APL name in the center that looks good to the eyes, makes it very clear of how the language is called plus it introduces the newcomers to their first three glyphs: Lamp Rho Floor.<br />
<br />
Very strong contestant too imho.<br />
<br />
== Letters From the Cube comment by [[User:John niss hansen|John niss hansen]] ([[User talk:John niss hansen|talk]]) ==<br />
<br />
I like this logo based on a plyomino and coded in APL<br />
<br />
== Letters From the Cube comment by [[User:AplProgrammer148|AplProgrammer148]] ([[User talk:AplProgrammer148|talk]]) ==<br />
<br />
I like this because it showcases APL's array-oriented programming.<br />
<br />
== 50 years apple comment by [[User:Bill Early|Bill Early]] ([[User talk:Bill Early|talk]]) ==<br />
<br />
If I may make a suggestion...<br />
- Use the same general shape of this logo<br />
- Red apple, not green<br />
- Maybe a little green leaf or two<br />
- No worm<br />
- "APL" in the thicker 2741-like font, like in a nearby logo<br />
<br />
== Parallel lines comment by [[User:RLevine|RLevine]] ([[User talk:RLevine|talk]]) ==<br />
<br />
The basic design is strong. A font designer could simplify the letters inside the black parallel lines, perhps while keeping the parallel lines motif in the letters.</div>RLevinehttps://aplwiki.com/index.php?title=Talk:APL_logo&diff=8157Talk:APL logo2022-02-10T16:01:16Z<p>RLevine: /* Parallel lines comment by ~~~ */ new section</p>
<hr />
<div>On this page, you can leave feedback or submit ideas, but note that '''voting is currently happening'''.<br />
<br />
* [{{fullurl:{{TALKPAGENAME}}|action=edit&section=new&preloadtitle=%5Blogo%20name%5D%20comment%20by%20~~<noinclude></noinclude>~}} Click here to comment on an existing proposal.]<br />
<br />
* [{{fullurl:{{TALKPAGENAME}}|action=edit&section=new&preloadtitle=General%20comment%20by%20~~<noinclude></noinclude>~}} Click here to leave a general comment.]<br />
<br />
== Nested bitmaps comment by LdBeth ==<br />
<br />
I love the bitmap style font used in this logo, and this one comes with many variations.<br />
Might be great if combined with the dot halftone style logo used for APL Wiki.<br />
<br />
== Parallel lines comment by RGS ==<br />
<br />
The “parallel lines” logo is very hard to read and it's hard to understand that there's an “APL” written in there.<br />
In general, I would go for things that are easy to read.<br />
<br />
== Display matrix comment by [[User:PaulMansour|PaulMansour]] ([[User talk:PaulMansour|talk]]) ==<br />
<br />
This is an excellent starting point, but rather than the exact output of the DISPLAY function, a good graphic designer could stylize it a bit, perhaps removing some white space, a little kerning on the letters, some color, etc.<br />
<br />
== Cube apple comment by [[User:Ros|Ros]] ([[User talk:Ros|talk]]) ==<br />
<br />
Stylistically, I like this logo the best - but it is my least preferred option: for me, it is too reminiscent of the [[Dyalog APL|Dyalog]] application logo to be a general and independent APL logo. [[User:Ros|Ros]] ([[User talk:Ros|talk]]) 09:17, 8 October 2021 (UTC)<br />
<br />
== Script apple comment by Fiona ==<br />
<br />
Although I rather like the "hollow" version of this, Dyalog Ltd have already adopted a slight variation of this for use as the APL Seeds logo (user meetings, events and information specifically for new APLers) – [https://www.dyalog.com/apl-seeds-user-meetings/aplseeds21.htm see here for an example] and the detail makes it harder to shrink. The filled version is slightly more reminiscent of a bell pepper than an apple to me – I prefer the shape of the (otherwise similar) 50 Years one further down the page.<br />
<br />
== Cube apple comment by [[User:Fiona|Fiona]] ([[User talk:Fiona|talk]]) ==<br />
<br />
I like the cube representation and its array implications but it's maybe a tad too similar to the [https://aplwiki.com/wiki/Dyalog_APL| Dyalog product logo]. I really dislike the text – on first impression it looked odd, and when realising that it's APL glyphs instead of letters it just seemed a bit of an inside joke that might alienate those who are not in the know (the same comment applies to the "Lamp Rho Downstile" and "APL matrix" logos).<br />
<br />
== Parallel lines comment by [[User:Fiona|Fiona]] ([[User talk:Fiona|talk]]) ==<br />
<br />
This might appeal to those who have fond memories of the rather brilliant book, but it looks very dated, is hard to read unless you already know what it said, wouldn't render well when small, and wouldn't work in black-and-white.<br />
<br />
== General comment by MichaelBaas ==<br />
<br />
It would be useful if the icons were shown in the same size(s), perhaps 32x32 as a miniature version (favicon etc.) and 192 x 192, and maybe each on a black and on a white background - so 4 versions per icon.<br />
<br />
== Plain Ellipse comment by [[User:PaulMansour|PaulMansour]] ([[User talk:PaulMansour|talk]]) ==<br />
<br />
Very nice. Simple, clean, should be good at all sizes. Gets my vote!<br />
<br />
== Display matrix comment by [[User:DanHirschi|DanHirschi]] ([[User talk:DanHirschi|talk]]) ==<br />
<br />
I actually like this one. If placed in the matrix of other logos above, it would stand out a bit because of its simplicity (I think the white space actually helps). <br />
Possible changes (that might improve it):<br />
- make the letters and box a bit thicker<br />
- use the older font where the characters are more italicized<br />
- use the old underscored font<br />
- as mentioned, adjust the spacing between the letters<br />
<br />
== Plain Ellipse comment by [[User:Fiona|Fiona]] ([[User talk:Fiona|talk]]) ==<br />
<br />
I agree with Paul's comment on the clarity and simplicity of this design but would suggest that it is not taken forward in this colour due to its similarity to an existing logo: APL Media's logo is a lower case "apl" in a red circle – https://twitter.com/apl_media – but perhaps a different single colour (green?) would introduce more differentiation.<br />
<br />
== APL Rotated Array comment by [[Adám Brudzewsky]] ==<br />
<br />
I quite like this one. It is simple and timeless.<br />
<br />
However, I will dispute that the [[APL Wiki logo]] is "the most established APL logo to date". It was in fact recently changed from its previous logo, as seen on [https://old.aplwiki.com old.aplwiki.com], which was shared with [https://aplteam.github.io/ APL Team].<br />
<br />
Furthermore, APL isn't a well-recognised language, and so I think it is important that the logo spells out "APL" such that people can at least go search for it.<br />
<br />
== APL Wiki comment by [[User:KSK|KSK]] ([[User talk:KSK|talk]]) ==<br />
<br />
The APL Wiki would be my preference, followed by the Display matrix (which would be nicer if it were boxed up without breaks and maybe slightly slanted), then the Cube Apple.<br />
<br />
== General comment by [[Adám Brudzewsky]] ==<br />
<br />
I think we should avoid a logo based on an apple, to avoid any legal issues with Apple Inc. See justification [https://retrocomputing.stackexchange.com/questions/22375/when-was-an-image-of-an-apple-first-used-to-promote-the-apl-language?noredirect=1#comment73769_22375 here].<br />
<br />
== Display matrix comment by [[User:Razetime|Razetime]] ([[User talk:Razetime|talk]]) ==<br />
<br />
I'd say this is the best one and then simplest by far.<br />
<br />
== General comment by [[Adám Brudzewsky]] ==<br />
<br />
I think the letters "APL" should be clearly legible, and their order be obvious. Some logos are ambiguous if the name is APL or ALP etc. Stylising them as <code>⍝⍴⌊</code> might be fine, but APL isn't well-known, so the logo must give away the name such that people can go search for it.<br />
<br />
== General comment by Dr. Jürgen Sauermann (GNU APL author and maintainer) ==<br />
<br />
All apple based logos: not really vendor-agnostic (too much similarity with Apple Inc.)<br />
<br />
My preferred one: Lamp Rho Downstile. Not sure where the logos are being used but<br />
if I think of e.g. favicon.ico and similar usage (i.e. icons) then the logo should have a<br />
simple structure without tiny details that looks good even as a 32×32 pixel image.<br />
<br />
== General comment by [[User:Peter Cyriax|Peter Cyriax]] ([[User talk:Peter Cyriax|talk]]) ==<br />
<br />
I like almost all of these Logos; but I think we really need to focus on what we are trying to achieve here and then choose a Logo that satisfies those objectives.<br />
<br />
As I understand it, we want a Logo that is used to 'Promote the Use of APL'. If so, the Target Market is people who commision, design or implement IT sytems that could (or should?) be written in APL. Within this group and their influencers, those we most want to reach are the ones who have not even heard of APL, far less know anything about it. We need to sell them the benefits - robust, well functioning sytems with rapid development timelines, flexability and low maintenance. These benefits are what matter the them: their job is to get things done, so they typically have little interest per. se. in the beautiful technology that we care so much about and which gives rise to these benefits.<br><br />
<br><br />
As far as I can make out we propose that the APL Logo will be used to "brand" demonstrations, presentations and systems plus associated documentation; and the core purpose of the Logo is to proclaim to the Target Market: "This is APL in Action", i.e. to promote the APL brand. Also, as far as I can make out, we anticipate that the APL Logo will typically display at a size of around 120 x 120 pixels - not a lot of space for such a big message. Because, what we have to fit into that space is:<br />
1. This is written in APL - Brand Recognition<br><br />
2. APL is (and stands for) "A Programming Language" - the Target Market will not know this; plus we have to distinguish our "APL" from other uses of 'APL'<br><br />
3. APL is a sophisticated IT Tool: it delivers huge benefits... - the Core Message.<br><br />
<br />
<br />
Peter<br />
<br />
== Nested bitmaps comment by [[User:Dnm|Dnm]] ([[User talk:Dnm|talk]]) ==<br />
<br />
+1 for this logo, as my first choice (FWIW).<br />
<br />
== Display matrix comment by [[User:Dnm|Dnm]] ([[User talk:Dnm|talk]]) ==<br />
<br />
Maybe my second choice preference for a logo (again, FWIW).<br />
<br />
== Lamp Box comment by [[User:Soveran|Soveran]] ([[User talk:Soveran|talk]]) ==<br />
<br />
This logo is simple, direct, recognizable, and beautiful. I would love to use it.<br />
<br />
== Lamp Box and Lamp Rho Downstile Box comment by [[Adám Brudzewsky]] ==<br />
<br />
These two could be used in combination, with Lamp Rho Downstile Box being the official logo and Lamp Box being used at small sizes like for favicons.<br />
<br />
== General comment by Richard ==<br />
<br />
Personally I think the logo should be as simple and straightforward as possible. The logo also represents how we see ourselves in the community. It's difficult to express myself with these kind of subtleness in English, but I'll give it a try.<br />
<br />
We should see APL as a major language.There are several YouTube Video's about esoteric languages. And APL is always mentioned in these videos... That is not where it belongs. APL is not a synthetic or artificial language just for fun.<br />
<br />
This must also be reflected in the logo. No cryptic or nerdy design which reflects on the niche people think APL belongs to. No offence meant to other designs!!! Don't put yourself in a place you don't belong or want to be.<br />
<br />
If you google APL, the first hit (in my case)is a ocean transport company. And it's logo is the three APL letters. Same goes for some shoe company (third hit), also the three letters. The APL programming language is not representing some kind of company but a serious programming language with its own applications and territory where it is sublime!<br />
<br />
I am not a programmer and do nothing with software development for my job. I learned myself programming in C during my study (many years ago) to solve problems I encountered. However, what I experienced in C (and the same goes perhaps for a lot of other languages) is that you can start programming right away, and on the way start thinking about the solution. I started with APL three week ago. And this is completely different. First you have to think about the solution and then you start programming. (maybe it even shouldn't be called programming!). And again, I might be very wrong about this because of my lack of programming experience.<br />
<br />
For me, APL is:<br><br />
<br />
''Back to basic. Think first, act (program) later. A direct approach to the solution of your problem.''<br><br />
<br />
And the language reflects this way of thinking. Even the (for a novice) cryptic symbols forces (helps!) you to pick up this mind set. So should the logo.<br />
<br />
== Letters From the Cube comment by [[User:Mlliarm|Mlliarm]] ([[User talk:Mlliarm|talk]]) ==<br />
<br />
This could be read as `APL` but also as `ALP`, so it might confuse those that are not aware of the language name or people outside of the community.<br />
<br />
== APL Wiki comment by [[User:Mlliarm|Mlliarm]] ([[User talk:Mlliarm|talk]]) ==<br />
<br />
I like this one actually.<br />
<br />
- it is very modern as per design.<br />
- it's been used already in the APLwiki page (even though maybe the version with the traditional name in the middle is better) so some of us already feel used to it.<br />
<br />
- It could be decided to use the traditional name APL with the nice curvy font, which will keep a connection with the past of the language this way.<br />
<br />
- If the name was used I'd prefer the Lamp Rho Floor symbols or the curvy font mentioned earlier.<br />
<br />
- If the name was used I don't think if like it to be anywhere else than in the middle. That's only where it's possible to enclose the letters with a bubble.<br />
<br />
- The symbolism might be visible only to those that can recognize a matrix when they see it, but for me it has a deep and important symbolism: everything in APL is an array, be it 0-dimensioned (scalar), 1-dimensioned (vector or array), 2-dimensioned (matrix), n-dimensioned where n greater than 2 (tensor).<br />
<br />
== Quad APL comment by [[User:Mlliarm|Mlliarm]] ([[User talk:Mlliarm|talk]]) ==<br />
<br />
This imho is too cryptic.<br />
<br />
It carries the message that APL code can look like arcane ancient voodoo spells or incantations to [[wiki:Cthulhu|Cthulhu]] and Yog Sothoth. <br />
<br />
So I don't think it'd be a good idea to use this one, no matter how original is the idea of the creator.<br />
<br />
It'd probably scare a beginner off. But I think the general feelings one should get when they lay their eyes on the logo are:<br />
<br />
- aesthetic pleasing: it must have symmetry, be curvy and avoid many angles<br />
<br />
- it has to make them curious or lure them to look into the language.<br />
<br />
Not sure how the APL community can solve the issue that the glyphs bring math traumas to the surface (this is my naive "theory") and so, only those that can see the beauty of it all beyond the weird symbols will stay. <br />
<br />
But I guess this is a problem (or a non problem) that the logo cannot solve, no matter how good and pleasant to the eye it is: for some people the glyphs will scare them away (possible math trauma in the past) and for others (the few mathematically inclined, or those that can handle any math anxiety that a total alien looking language can create to a new user -- like a westerner that tries to learn Japanese) it is this that will attract them to the language.<br />
<br />
I suppose one needs to have a fair amount of weirdness in their mind/psyche to appreciate APL and decide to learn it, and keep pushing through the math anxiety it creates, like learning Japanese.<br />
<br />
== 50 years apple comment by [[User:Mlliarm|Mlliarm]] ([[User talk:Mlliarm|talk]]) ==<br />
<br />
Classic, but not very modern. Also keeps the APL/apple pun around. Not sure how good this is.<br />
<br />
== Display matrix comment by [[User:Mlliarm|Mlliarm]] ([[User talk:Mlliarm|talk]]) ==<br />
<br />
Even though the design is a bit dated, I like a lot the fact that it can be created using the APL REPL and a few chars from the APL character set.<br />
<br />
Maybe with some vidual artistic polishing it could be a strong contestant.<br />
<br />
== Modern comment by [[User:Mlliarm|Mlliarm]] ([[User talk:Mlliarm|talk]]) ==<br />
<br />
I'd avoid the star in the logo...<br />
<br />
In my eyes it makes look like it's an extremist left revolutionary group...<br />
<br />
== Cube apple comment by [[User:Mlliarm|Mlliarm]] ([[User talk:Mlliarm|talk]]) ==<br />
<br />
I like this very much:<br />
<br />
- it has the apple looking design, so here's the connection with the past<br />
<br />
- the apple looks like a design from a cubist painter, and very modern, so here's the connection to the present and the future. Also being a cube, it has a strong reference to the basic data structure of the language (array) and suggests that APL works with n-dimensional data too<br />
<br />
- finally, it has the curvy APL name in the center that looks good to the eyes, makes it very clear of how the language is called plus it introduces the newcomers to their first three glyphs: Lamp Rho Floor.<br />
<br />
Very strong contestant too imho.<br />
<br />
== Letters From the Cube comment by [[User:John niss hansen|John niss hansen]] ([[User talk:John niss hansen|talk]]) ==<br />
<br />
I like this logo based on a plyomino and coded in APL<br />
<br />
== Letters From the Cube comment by [[User:AplProgrammer148|AplProgrammer148]] ([[User talk:AplProgrammer148|talk]]) ==<br />
<br />
I like this because it showcases APL's array-oriented programming.<br />
<br />
== 50 years apple comment by [[User:Bill Early|Bill Early]] ([[User talk:Bill Early|talk]]) ==<br />
<br />
If I may make a suggestion...<br />
- Use the same general shape of this logo<br />
- Red apple, not green<br />
- Maybe a little green leaf or two<br />
- No worm<br />
- "APL" in the thicker 2741-like font, like in a nearby logo<br />
<br />
== Parallel lines comment by [[User:RLevine|RLevine]] ([[User talk:RLevine|talk]]) ==<br />
<br />
The basic design is strong. A font designer could simplify the letters inside the black parallel lines, perhps while keeping the parallel lines motifin the letters.</div>RLevinehttps://aplwiki.com/index.php?title=Talk:Bob_Smith&diff=5983Talk:Bob Smith2020-11-26T04:57:09Z<p>RLevine: </p>
<hr />
<div>I added "Sudley Place Software" to clarify that this link goes to a section of the main Sudley Place Software website, in the absence of any other indication. I didn't think it was obvious that "APL Projects" also goes to Sudley Place Software for those unfamiliar with the website. Throughout the APL Wiki it would be nice to accompany external links with some brief indication of the significance of the link and where the link ends up. But that's a personal preference. Is there some guideline about this? There was clearly a rationale for specifically noting "APL Projects" with its own link, and it would be interesting and useful to indicate this in the Wiki.</div>RLevinehttps://aplwiki.com/index.php?title=Talk:Running_APL&diff=5982Talk:Running APL2020-11-26T04:52:05Z<p>RLevine: </p>
<hr />
<div>APL2 (from IBM) is a dialect that can be obtained today. Same question for APL2000 which I understand is commercially available. One way to include them on this page would be - add a table containing these two below the first table. Is cost a factor on inclusion in this page? I can't think of any other APLs that are available, either at commercial prices or free. (I understand APLX is free and works, but I think there are various reasons not to recommend it for new users.) Overall I think APL2 and APL2000 should be in some list of viable alternatives in order to follow APL Wiki principles of being "APL-neutral". In summary - Do APL2 and APL2000 belong in a list on this page? If not on this page, then in which list? --[[User:RLevine|RLevine]] ([[User talk:RLevine|talk]]) 04:51, 26 November 2020 (UTC)</div>RLevinehttps://aplwiki.com/index.php?title=Talk:Running_APL&diff=5981Talk:Running APL2020-11-26T04:51:04Z<p>RLevine: Created page with "APL2 (from IBM) is a dialect that can be obtained today. Same question for APL2000 which I understand is commercially available. One way to do this on this page would be to ad..."</p>
<hr />
<div>APL2 (from IBM) is a dialect that can be obtained today. Same question for APL2000 which I understand is commercially available. One way to do this on this page would be to add a table containing these two below the first table. Is cost a factor on inclusion in this page? I can't think of any other APLs that are available, either at commercial prices or free. (I understand APLX is free and works, but I think there are various reasons not to recommend it for new users.) Overall I think APL2 and APL2000 should be in some list of viable alternatives in order to follow APL Wiki principles of being "APL-neutral". In summary - Do APL2 and APL2000 belong in a list on this page? If not on this page, then in which list? --[[User:RLevine|RLevine]] ([[User talk:RLevine|talk]]) 04:51, 26 November 2020 (UTC)</div>RLevinehttps://aplwiki.com/index.php?title=Talk:Bob_Smith&diff=5980Talk:Bob Smith2020-11-26T04:19:48Z<p>RLevine: Created page with "I added "Sudley Place Software" to clarify that this link goes to a section of the main Sudley Place Software website, in the absence of any other indication. I don't think th..."</p>
<hr />
<div>I added "Sudley Place Software" to clarify that this link goes to a section of the main Sudley Place Software website, in the absence of any other indication. I don't think this is immediately obvious for those unfamiliar with the website. It would be more logical to put this second, but I think that goes against a guideline to put links in alphabetical order. Throughout the APL Wiki it would be nice to accompany external links with some brief indication of the significance of the link and where the link ends up. Is there some guideline about this?</div>RLevinehttps://aplwiki.com/index.php?title=Bob_Smith&diff=5979Bob Smith2020-11-26T04:09:27Z<p>RLevine: /* External links */</p>
<hr />
<div>[[File:BobSmith.jpg|thumb|right|Bob Smith at [[Dyalog '16]]]]<br />
'''Robert "Boolean Bob" Asa Smith''' of Laurel, Maryland first encountered APL in 1969 while working for [[wikipedia:NSA|NSA]]. Devoted to studying and contributing to the language, he left for [[STSC]] two years later. At STSC, he was involved in the creation of [[NARS]], and currently develops and maintains its successor, [[NARS2000]], though his company, Sudley Place Software. He was the editor of the problem section in the [[APL Quote Quad]], and regularly publishes and updates papers on various subjects of cutting edge APL.<br />
<br />
Smith also developed lots of system-level software, including the [[wikipedia:386MAX|386<sup>MAX</sup>]] memory manager.<br />
<br />
== Publications ==<br />
<br />
* [https://doi.org/10.1145/800136.804488 "A programming technique for non-rectangular data"] ([http://www.sudleyplace.com/APL/boolean.pdf pdf]) at [[APL79]].<br />
* [https://doi.org/10.1145/800142.805376 "Nested arrays, operators, and functions"] at [[APL81]].<br />
* [https://doi.org/10.1145/17701.255358 "Writing interpreters (panel)"] at [[APL85]]. With [[Bob Bernecky|Robert Bernecky]], Geno Coschi, James Ryan, [[Philip Van Cleave|Philip A. Van Cleave]], and James Wheeler.<br />
<br />
== External links ==<br />
<br />
* [http://www.sudleyplace.com/APL/projects.html APL Projects] at Sudley Place Software<br />
* [http://www.sudleyplace.com/ Sudley Place Software]<br />
{{APL community}}{{DEFAULTSORT:Smith}}[[Category:People]][[Category:Designers]][[Category:Implementers]]</div>RLevinehttps://aplwiki.com/index.php?title=Talk:APL2000&diff=5978Talk:APL20002020-11-26T04:04:43Z<p>RLevine: /* Page title */</p>
<hr />
<div>== Page title ==<br />
<br />
I have changed the page title from the registered company name APLNow to the service mark and commonly-used name APL2000, following the policies at [[wikipedia:Wikipedia:Official names|Wikipedia:Official names]]. The registered name is very obscure as it is not even used by the company itself in most publications. It is also confusing to use it because, from the user's perspective, APL2000 has remained the same entity despite the change in ownership (it seems to be the same in practice as the takeover of Dyalog by Insight but with a different legal arrangement). --[[User:Marshall|Marshall]] ([[User talk:Marshall|talk]]) 16:49, 27 May 2020 (UTC)<br />
<br />
[[User:RLevine|RLevine]] ([[User talk:RLevine|talk]]) 00:47, 25 November 2020 (UTC) I agree. APL2000 has been around for a long time and deserves a clear description. I added a bit about the APLDN to support the reference to APLDN on the VisualAPL page. I put in a small but positive editorial opinion about the forum which I trust is OK but am ready to submit to the "merciless editing" principle if not. It is an interesting forum though (:>)<br />
<br />
:As I understand it, Wikipedia doctrine is that a valuable source should be (or will naturally be) highlighted by using it for citations. Until someone has the time to go through APLDN and put the information in articles, I don't see a problem with the editorial. As for non-archive APLDN, it's hard to dispute that it's "well-organized" and I think that would be fine in an article regardless of the state of the wiki. --[[User:Marshall|Marshall]] ([[User talk:Marshall|talk]]) 17:46, 25 November 2020 (UTC)<br />
<br />
::Thinking about your comments, I removed the point about "well-organized". The key idea was the suggestion to take a few moments to check out the APLDN forum even though it's stated focus is APL2000. I see your point - if it turns out to valuable as a general resource, this will be noted in time as you describe. One thing that would be nice to include at some point is a summary description of where APL2000 sits in the APL world, in terms of following any APL standard and any noteworthy extensions. This is all part of working on some entries for STSC and APL/PLUS --[[User:RLevine|RLevine]] ([[User talk:RLevine|talk]]) 03:34, 26 November 2020 (UTC)</div>RLevinehttps://aplwiki.com/index.php?title=List_of_language_developers&diff=5977List of language developers2020-11-26T03:53:50Z<p>RLevine: </p>
<hr />
<div>:''This page lists notable language developers only. For all APL dialects including those without notable developers, see [[Timeline of APL dialects]]. To choose a dialect for use today, consider [[Running APL]].''<br />
<br />
A language developer is an organization or individual that develops and distributes a programming language. This includes vendors, which are companies that sell APL implementations, as well as developers of free implementations. In the [[wikipedia:Mainframe computer|mainframe]] era it was common for hardware vendors to create APL implementations in machine code for their particular architecture. Developers active today use portable languages in order to support multiple architectures.<br />
<br />
== Past developers ==<br />
<br />
=== Hardware vendors with APL implementations ===<br />
<br />
* [[wikipedia:Analogic Corporation|Analogic Corporation]]: The APL Machine<br />
* [[wikipedia:Burroughs Corporation|Burroughs Corporation]]: APL-B5500, [[APL/700]]<br />
* [[wikipedia:Commodore International|Commodore International]]: Waterloo APL<br />
* [[wikipedia:Control Data Corporation|Control Data Corporation]] (CDC): APL/VE<br />
* [[wikipedia:Data General|Data General]]: AOS/VS APL<br />
* [[wikipedia:Digital Equipment Corporation|Digital Equipment Corporation]] (DEC): APL-10, VAX-11 APL<br />
* Harris Computer Systems: Harris APL<br />
* [[wikipedia:Honeywell|Honeywell]]: GCOS7 APL7<br />
* [[wikipedia:Hewlett-Packard|Hewlett-Packard]] (HP): [[APL\3000]]<br />
* Micro Computer Machines: [[wikipedia:MCM/70|MCM/70]] firmware<br />
* [[wikipedia:Siemens|Siemens AG]]<br />
* [[wikipedia:Xerox|Xerox]]<br />
<br />
=== Portable array language developers ===<br />
<br />
* [[wikipedia:DECUS|DECUS]]: APL-11 for DEC [[wikipedia:PDP-11|PDP-11]]<br />
* [[I.P. Sharp Associates]]<br />
* Leptonics Systems Company: MacAPL<br />
* MicroAPL: [[APL.68000]], [[APLX]]<br />
* [[STSC]]<br />
<br />
== Active developers ==<br />
<br />
=== Organizations ===<br />
<br />
* [[APL2000]]: [[APL+Win]], [[APL64]]<br />
* [[Dyalog Ltd.]]: [[Dyalog APL]]<br />
* [[IBM]]: [[APL2]] and its predecessors<br />
* [[Jsoftware]]: [[J]]<br />
* [[wikipedia:Kx Systems|Kx Systems]]: [[K|K4]] and [[Q]]<br />
<br />
=== Individual developers ===<br />
<br />
* [[Adám Brudzewsky]]: [[Extended Dyalog APL]]<br />
* [[Bob Smith]] (as Sudley Place Software): [[NARS2000]]<br />
* dzaima: [[dzaima/APL]], [[dzaima/BQN]]<br />
* [[Marshall Lochbaum]]: [[I]], [[BQN]]<br />
* [[Nick Nickolov]]: [[ngn/apl]] and [[ngn/k]]<br />
* [[wikipedia:Rob Pike|Rob Pike]]: [[Ivy]]<br />
<br />
{{APL development}}[[Category:Vendors]][[Category:Lists]]</div>RLevinehttps://aplwiki.com/index.php?title=List_of_language_developers&diff=5976List of language developers2020-11-26T03:53:12Z<p>RLevine: </p>
<hr />
<div>:''This page lists notable language developers only. For all APL dialects including those without notable developers, see [[timeline of APL dialects]]. To choose a dialect for use today, consider [[Running APL]].''<br />
<br />
A language developer is an organization or individual that develops and distributes a programming language. This includes vendors, which are companies that sell APL implementations, as well as developers of free implementations. In the [[wikipedia:Mainframe computer|mainframe]] era it was common for hardware vendors to create APL implementations in machine code for their particular architecture. Developers active today use portable languages in order to support multiple architectures.<br />
<br />
== Past developers ==<br />
<br />
=== Hardware vendors with APL implementations ===<br />
<br />
* [[wikipedia:Analogic Corporation|Analogic Corporation]]: The APL Machine<br />
* [[wikipedia:Burroughs Corporation|Burroughs Corporation]]: APL-B5500, [[APL/700]]<br />
* [[wikipedia:Commodore International|Commodore International]]: Waterloo APL<br />
* [[wikipedia:Control Data Corporation|Control Data Corporation]] (CDC): APL/VE<br />
* [[wikipedia:Data General|Data General]]: AOS/VS APL<br />
* [[wikipedia:Digital Equipment Corporation|Digital Equipment Corporation]] (DEC): APL-10, VAX-11 APL<br />
* Harris Computer Systems: Harris APL<br />
* [[wikipedia:Honeywell|Honeywell]]: GCOS7 APL7<br />
* [[wikipedia:Hewlett-Packard|Hewlett-Packard]] (HP): [[APL\3000]]<br />
* Micro Computer Machines: [[wikipedia:MCM/70|MCM/70]] firmware<br />
* [[wikipedia:Siemens|Siemens AG]]<br />
* [[wikipedia:Xerox|Xerox]]<br />
<br />
=== Portable array language developers ===<br />
<br />
* [[wikipedia:DECUS|DECUS]]: APL-11 for DEC [[wikipedia:PDP-11|PDP-11]]<br />
* [[I.P. Sharp Associates]]<br />
* Leptonics Systems Company: MacAPL<br />
* MicroAPL: [[APL.68000]], [[APLX]]<br />
* [[STSC]]<br />
<br />
== Active developers ==<br />
<br />
=== Organizations ===<br />
<br />
* [[APL2000]]: [[APL+Win]], [[APL64]]<br />
* [[Dyalog Ltd.]]: [[Dyalog APL]]<br />
* [[IBM]]: [[APL2]] and its predecessors<br />
* [[Jsoftware]]: [[J]]<br />
* [[wikipedia:Kx Systems|Kx Systems]]: [[K|K4]] and [[Q]]<br />
<br />
=== Individual developers ===<br />
<br />
* [[Adám Brudzewsky]]: [[Extended Dyalog APL]]<br />
* [[Bob Smith]] (as Sudley Place Software): [[NARS2000]]<br />
* dzaima: [[dzaima/APL]], [[dzaima/BQN]]<br />
* [[Marshall Lochbaum]]: [[I]], [[BQN]]<br />
* [[Nick Nickolov]]: [[ngn/apl]] and [[ngn/k]]<br />
* [[wikipedia:Rob Pike|Rob Pike]]: [[Ivy]]<br />
<br />
{{APL development}}[[Category:Vendors]][[Category:Lists]]</div>RLevinehttps://aplwiki.com/index.php?title=Talk:APL2000&diff=5975Talk:APL20002020-11-26T03:39:04Z<p>RLevine: /* Page title */</p>
<hr />
<div>== Page title ==<br />
<br />
I have changed the page title from the registered company name APLNow to the service mark and commonly-used name APL2000, following the policies at [[wikipedia:Wikipedia:Official names|Wikipedia:Official names]]. The registered name is very obscure as it is not even used by the company itself in most publications. It is also confusing to use it because, from the user's perspective, APL2000 has remained the same entity despite the change in ownership (it seems to be the same in practice as the takeover of Dyalog by Insight but with a different legal arrangement). --[[User:Marshall|Marshall]] ([[User talk:Marshall|talk]]) 16:49, 27 May 2020 (UTC)<br />
<br />
[[User:RLevine|RLevine]] ([[User talk:RLevine|talk]]) 00:47, 25 November 2020 (UTC) I agree. APL2000 has been around for a long time and deserves a clear description. I added a bit about the APLDN to support the reference to APLDN on the VisualAPL page. I put in a small but positive editorial opinion about the forum which I trust is OK but am ready to submit to the "merciless editing" principle if not. It is an interesting forum though (:>)<br />
<br />
:As I understand it, Wikipedia doctrine is that a valuable source should be (or will naturally be) highlighted by using it for citations. Until someone has the time to go through APLDN and put the information in articles, I don't see a problem with the editorial. As for non-archive APLDN, it's hard to dispute that it's "well-organized" and I think that would be fine in an article regardless of the state of the wiki. --[[User:Marshall|Marshall]] ([[User talk:Marshall|talk]]) 17:46, 25 November 2020 (UTC)<br />
<br />
::Thinking about your comments, I removed the point about "well-organized". The key idea was the suggestion to take a few moments to check out the APLDN forum even though it's stated focus is APL2000. I see your point - if it turns out to valuable as a general resource, this will be noted in time as you describe. One thing that would be nice to include at some point is a summary description of where APL2000 sits in the APL world, in terms of following any APL standard and any noteworthy extensions. --[[User:RLevine|RLevine]] ([[User talk:RLevine|talk]]) 03:34, 26 November 2020 (UTC)</div>RLevinehttps://aplwiki.com/index.php?title=Talk:APL2000&diff=5974Talk:APL20002020-11-26T03:34:03Z<p>RLevine: /* Page title */</p>
<hr />
<div>== Page title ==<br />
<br />
I have changed the page title from the registered company name APLNow to the service mark and commonly-used name APL2000, following the policies at [[wikipedia:Wikipedia:Official names|Wikipedia:Official names]]. The registered name is very obscure as it is not even used by the company itself in most publications. It is also confusing to use it because, from the user's perspective, APL2000 has remained the same entity despite the change in ownership (it seems to be the same in practice as the takeover of Dyalog by Insight but with a different legal arrangement). --[[User:Marshall|Marshall]] ([[User talk:Marshall|talk]]) 16:49, 27 May 2020 (UTC)<br />
<br />
[[User:RLevine|RLevine]] ([[User talk:RLevine|talk]]) 00:47, 25 November 2020 (UTC) I agree. APL2000 has been around for a long time and deserves a clear description. I added a bit about the APLDN to support the reference to APLDN on the VisualAPL page. I put in a small but positive editorial opinion about the forum which I trust is OK but am ready to submit to the "merciless editing" principle if not. It is an interesting forum though (:>)<br />
<br />
:As I understand it, Wikipedia doctrine is that a valuable source should be (or will naturally be) highlighted by using it for citations. Until someone has the time to go through APLDN and put the information in articles, I don't see a problem with the editorial. As for non-archive APLDN, it's hard to dispute that it's "well-organized" and I think that would be fine in an article regardless of the state of the wiki. --[[User:Marshall|Marshall]] ([[User talk:Marshall|talk]]) 17:46, 25 November 2020 (UTC)<br />
<br />
::Thinking about your comments, I removed the point about "well-organized". The key idea was the suggestion to take a few moments to check out the APLDN forum even though it's stated focus is APL2000. I see your point - if it turns out to valuable as a general resource, this will be noted in time as you describe. --[[User:RLevine|RLevine]] ([[User talk:RLevine|talk]]) 03:34, 26 November 2020 (UTC)</div>RLevinehttps://aplwiki.com/index.php?title=APL2000&diff=5973APL20002020-11-26T03:22:40Z<p>RLevine: /* APL Developer Network (APLDN) */ Remove the "well-organized" comment (could apply to most anything)</p>
<hr />
<div>:''This page is about the APL vendor. For the 2000 [[APL conference]], see [[APL00]].''<br />
<br />
'''APLNow LLC''' (formerly known as '''APL2000''', which is retained as a service mark for its products) is the vendor of [[APL+Win]]. In addition to APL+Win, APLNow developed the discontinued [[VisualAPL]] and is now working on [[APL64]], a 64-bit successor to APL+Win. After Financial Reporting Software (soon to be LEX2000, after its main product) bought the rights to APL products including [[APL*PLUS/WIN]] from Manugistics (formerly [[STSC]]) in 1995,<ref>PRNewswire press release ([http://apl2000.com/press1.php reprint]). 1995-10-23.</ref> it was formed as a subsidiary to sell these products. LEX2000 was purchased by [[wikipedia:Cognos|Cognos]] in 1999,<ref>Business Wire press release ([http://apl2000.com/press4.php reprint]). 1999-01-25.</ref> and in 2005 APL2000's assets were purchased by the employee-owned business APLNow LLC, which adopted the name APL2000.<ref>Press release ([http://apl2000.com/press5.php reprint]). 2005-06-29.</ref><br />
<br />
APL2000, and later APLNow, held the [[APL2000 user conferences]] from 1996 to 2014.<br />
<br />
== APL Developer Network (APLDN) ==<br />
The APL Developer Network (APLDN) is an online community organized by the company for the exchange of ideas, programming tips and discussion of product issues among the customers and staff of APL2000. Their online forum, although directed to APL2000 users, has topics of general interest for APL users. The APLDN Archive is an older static version of the forum that is worth poking around in for historical nuggets.<br />
<br />
== References ==<br />
<references /><br />
<br />
== External links ==<br />
* [http://apl2000.com/ APL2000 website]<br />
* [http://forum.apl2000.com/ APLDN] forum<br />
* [http://apldn.apl2000.com/apldn.apl2000.com/default.htm APLDN archive]<br />
<br />
{{APL development}}[[Category:Vendors]]</div>RLevinehttps://aplwiki.com/index.php?title=Talk:APL2000&diff=5945Talk:APL20002020-11-25T00:51:03Z<p>RLevine: /* Page title */</p>
<hr />
<div>== Page title ==<br />
<br />
I have changed the page title from the registered company name APLNow to the service mark and commonly-used name APL2000, following the policies at [[wikipedia:Wikipedia:Official names|Wikipedia:Official names]]. The registered name is very obscure as it is not even used by the company itself in most publications. It is also confusing to use it because, from the user's perspective, APL2000 has remained the same entity despite the change in ownership (it seems to be the same in practice as the takeover of Dyalog by Insight but with a different legal arrangement). --[[User:Marshall|Marshall]] ([[User talk:Marshall|talk]]) 16:49, 27 May 2020 (UTC)<br />
<br />
[[User:RLevine|RLevine]] ([[User talk:RLevine|talk]]) 00:47, 25 November 2020 (UTC) I agree. APL2000 has been around for a long time and deserves a clear description. I added a bit about the APLDN to support the reference to APLDN on the VisualAPL page. I put in a small but positive editorial opinion about the forum which I trust is OK but am ready to submit to the "merciless editing" principle if not. It is an interesting forum though (:>)</div>RLevinehttps://aplwiki.com/index.php?title=Talk:APL2000&diff=5944Talk:APL20002020-11-25T00:49:00Z<p>RLevine: /* Page title */</p>
<hr />
<div>== Page title ==<br />
<br />
I have changed the page title from the registered company name APLNow to the service mark and commonly-used name APL2000, following the policies at [[wikipedia:Wikipedia:Official names|Wikipedia:Official names]]. The registered name is very obscure as it is not even used by the company itself in most publications. It is also confusing to use it because, from the user's perspective, APL2000 has remained the same entity despite the change in ownership (it seems to be the same in practice as the takeover of Dyalog by Insight but with a different legal arrangement). --[[User:Marshall|Marshall]] ([[User talk:Marshall|talk]]) 16:49, 27 May 2020 (UTC)<br />
<br />
[[User:RLevine|RLevine]] ([[User talk:RLevine|talk]]) 00:47, 25 November 2020 (UTC) I agree. APL2000 has been around for a long time and deserves a clear description. I added a bit about the APLDN to support the reference to APLDN on the VisualAPL page.</div>RLevinehttps://aplwiki.com/index.php?title=Talk:APL2000&diff=5943Talk:APL20002020-11-25T00:48:36Z<p>RLevine: /* Page title */</p>
<hr />
<div>== Page title ==<br />
<br />
I have changed the page title from the registered company name APLNow to the service mark and commonly-used name APL2000, following the policies at [[wikipedia:Wikipedia:Official names|Wikipedia:Official names]]. The registered name is very obscure as it is not even used by the company itself in most publications. It is also confusing to use it because, from the user's perspective, APL2000 has remained the same entity despite the change in ownership (it seems to be the same in practice as the takeover of Dyalog by Insight but with a different legal arrangement). --[[User:Marshall|Marshall]] ([[User talk:Marshall|talk]]) 16:49, 27 May 2020 (UTC)<br />
<br />
[[User:RLevine|RLevine]] ([[User talk:RLevine|talk]]) 00:47, 25 November 2020 (UTC) I agree. APL2000 has been around for a long time and deserves a clear description. I added a bit about the APLDN to support the reference to APLDN on the VisualAPL page which is interesting.</div>RLevinehttps://aplwiki.com/index.php?title=Talk:APL2000&diff=5942Talk:APL20002020-11-25T00:48:10Z<p>RLevine: /* Page title */</p>
<hr />
<div>== Page title ==<br />
<br />
I have changed the page title from the registered company name APLNow to the service mark and commonly-used name APL2000, following the policies at [[wikipedia:Wikipedia:Official names|Wikipedia:Official names]]. The registered name is very obscure as it is not even used by the company itself in most publications. It is also confusing to use it because, from the user's perspective, APL2000 has remained the same entity despite the change in ownership (it seems to be the same in practice as the takeover of Dyalog by Insight but with a different legal arrangement). --[[User:Marshall|Marshall]] ([[User talk:Marshall|talk]]) 16:49, 27 May 2020 (UTC)<br />
<br />
[[User:RLevine|RLevine]] ([[User talk:RLevine|talk]]) 00:47, 25 November 2020 (UTC) I agree. APL2000 has been around for a while and deserves a clear description. I added a bit about the APLDN to support the reference to APLDN on the VisualAPL page which is interesting.</div>RLevinehttps://aplwiki.com/index.php?title=Talk:APL2000&diff=5941Talk:APL20002020-11-25T00:47:46Z<p>RLevine: /* Page title */</p>
<hr />
<div>== Page title ==<br />
<br />
I have changed the page title from the registered company name APLNow to the service mark and commonly-used name APL2000, following the policies at [[wikipedia:Wikipedia:Official names|Wikipedia:Official names]]. The registered name is very obscure as it is not even used by the company itself in most publications. It is also confusing to use it because, from the user's perspective, APL2000 has remained the same entity despite the change in ownership (it seems to be the same in practice as the takeover of Dyalog by Insight but with a different legal arrangement). --[[User:Marshall|Marshall]] ([[User talk:Marshall|talk]]) 16:49, 27 May 2020 (UTC)<br />
<br />
[[User:RLevine|RLevine]] ([[User talk:RLevine|talk]]) 00:47, 25 November 2020 (UTC)I agree. APL2000 has been around for a while and deserves a clear description. I added a bit about the APLDN to support the reference to APLDN on the VisualAPL page which is interesting.</div>RLevinehttps://aplwiki.com/index.php?title=Talk:APL2000&diff=5940Talk:APL20002020-11-25T00:47:27Z<p>RLevine: /* Page title */</p>
<hr />
<div>== Page title ==<br />
<br />
I have changed the page title from the registered company name APLNow to the service mark and commonly-used name APL2000, following the policies at [[wikipedia:Wikipedia:Official names|Wikipedia:Official names]]. The registered name is very obscure as it is not even used by the company itself in most publications. It is also confusing to use it because, from the user's perspective, APL2000 has remained the same entity despite the change in ownership (it seems to be the same in practice as the takeover of Dyalog by Insight but with a different legal arrangement). --[[User:Marshall|Marshall]] ([[User talk:Marshall|talk]]) 16:49, 27 May 2020 (UTC)<br />
[[User:RLevine|RLevine]] ([[User talk:RLevine|talk]]) 00:47, 25 November 2020 (UTC)I agree. APL2000 has been around for a while and deserves a clear description. I added a bit about the APLDN to support the reference to APLDN on the VisualAPL page which is interesting.</div>RLevinehttps://aplwiki.com/index.php?title=APL2000&diff=5939APL20002020-11-25T00:42:47Z<p>RLevine: /* APL Developer Network (APLDN) */</p>
<hr />
<div>:''This page is about the APL vendor. For the 2000 [[APL conference]], see [[APL00]].''<br />
<br />
'''APLNow LLC''' (formerly known as '''APL2000''', which is retained as a service mark for its products) is the vendor of [[APL+Win]]. In addition to APL+Win, APLNow developed the discontinued [[VisualAPL]] and is now working on [[APL64]], a 64-bit successor to APL+Win. After Financial Reporting Software (soon to be LEX2000, after its main product) bought the rights to APL products including [[APL*PLUS/WIN]] from Manugistics (formerly [[STSC]]) in 1995,<ref>PRNewswire press release ([http://apl2000.com/press1.php reprint]). 1995-10-23.</ref> it was formed as a subsidiary to sell these products. LEX2000 was purchased by [[wikipedia:Cognos|Cognos]] in 1999,<ref>Business Wire press release ([http://apl2000.com/press4.php reprint]). 1999-01-25.</ref> and in 2005 APL2000's assets were purchased by the employee-owned business APLNow LLC, which adopted the name APL2000.<ref>Press release ([http://apl2000.com/press5.php reprint]). 2005-06-29.</ref><br />
<br />
APL2000, and later APLNow, held the [[APL2000 user conferences]] from 1996 to 2014.<br />
<br />
== APL Developer Network (APLDN) ==<br />
The APL Developer Network (APLDN) is an online community organized by the company for the exchange of ideas, programming tips and discussion of product issues among the customers and staff of APL2000. Their online forum is well-organized and, although directed to APL2000 users, it has topics of general interest for APL users. The APLDN Archive is an older static version of the forum that is worth poking around in for historical nuggets.<br />
<br />
== References ==<br />
<references /><br />
<br />
== External links ==<br />
* [http://apl2000.com/ APL2000 Website]<br />
* [http://forum.apl2000.com/ APLDN] forum<br />
<br />
{{APL development}}[[Category:Vendors]]</div>RLevinehttps://aplwiki.com/index.php?title=APL2000&diff=5938APL20002020-11-25T00:42:33Z<p>RLevine: /* APL Developer Network (APLDN) */</p>
<hr />
<div>:''This page is about the APL vendor. For the 2000 [[APL conference]], see [[APL00]].''<br />
<br />
'''APLNow LLC''' (formerly known as '''APL2000''', which is retained as a service mark for its products) is the vendor of [[APL+Win]]. In addition to APL+Win, APLNow developed the discontinued [[VisualAPL]] and is now working on [[APL64]], a 64-bit successor to APL+Win. After Financial Reporting Software (soon to be LEX2000, after its main product) bought the rights to APL products including [[APL*PLUS/WIN]] from Manugistics (formerly [[STSC]]) in 1995,<ref>PRNewswire press release ([http://apl2000.com/press1.php reprint]). 1995-10-23.</ref> it was formed as a subsidiary to sell these products. LEX2000 was purchased by [[wikipedia:Cognos|Cognos]] in 1999,<ref>Business Wire press release ([http://apl2000.com/press4.php reprint]). 1999-01-25.</ref> and in 2005 APL2000's assets were purchased by the employee-owned business APLNow LLC, which adopted the name APL2000.<ref>Press release ([http://apl2000.com/press5.php reprint]). 2005-06-29.</ref><br />
<br />
APL2000, and later APLNow, held the [[APL2000 user conferences]] from 1996 to 2014.<br />
<br />
== APL Developer Network (APLDN) ==<br />
The APL Developer Network (APLDN) is an online community organized by the company for the exchange of ideas, programming tips and discussion of product issues among the customers and staff of APL2000. Their online forum is well-organized and, although directed to APL2000 users, it has topics of general interest for APL users. The APLDN Archive is an older statis version of the forum that is worth poking around in for historical nuggets.<br />
<br />
== References ==<br />
<references /><br />
<br />
== External links ==<br />
* [http://apl2000.com/ APL2000 Website]<br />
* [http://forum.apl2000.com/ APLDN] forum<br />
<br />
{{APL development}}[[Category:Vendors]]</div>RLevinehttps://aplwiki.com/index.php?title=APL2000&diff=5937APL20002020-11-25T00:41:55Z<p>RLevine: /* APL Developer Network and Forum */</p>
<hr />
<div>:''This page is about the APL vendor. For the 2000 [[APL conference]], see [[APL00]].''<br />
<br />
'''APLNow LLC''' (formerly known as '''APL2000''', which is retained as a service mark for its products) is the vendor of [[APL+Win]]. In addition to APL+Win, APLNow developed the discontinued [[VisualAPL]] and is now working on [[APL64]], a 64-bit successor to APL+Win. After Financial Reporting Software (soon to be LEX2000, after its main product) bought the rights to APL products including [[APL*PLUS/WIN]] from Manugistics (formerly [[STSC]]) in 1995,<ref>PRNewswire press release ([http://apl2000.com/press1.php reprint]). 1995-10-23.</ref> it was formed as a subsidiary to sell these products. LEX2000 was purchased by [[wikipedia:Cognos|Cognos]] in 1999,<ref>Business Wire press release ([http://apl2000.com/press4.php reprint]). 1999-01-25.</ref> and in 2005 APL2000's assets were purchased by the employee-owned business APLNow LLC, which adopted the name APL2000.<ref>Press release ([http://apl2000.com/press5.php reprint]). 2005-06-29.</ref><br />
<br />
APL2000, and later APLNow, held the [[APL2000 user conferences]] from 1996 to 2014.<br />
<br />
== APL Developer Network (APLDN) ==<br />
The APL Developer Network (APLDN) is an online community organized by the company for the exchange of ideas, programming tips and discussion of product issues among the customers and staff of APL2000. Their online forum is well-organized and, although directed to APL2000 users, it has topics of general interest for APL users. The APLDN Archive is an older version of the forum that is worth poking around in for historical nuggets.<br />
<br />
== References ==<br />
<references /><br />
<br />
== External links ==<br />
* [http://apl2000.com/ APL2000 Website]<br />
* [http://forum.apl2000.com/ APLDN] forum<br />
<br />
{{APL development}}[[Category:Vendors]]</div>RLevinehttps://aplwiki.com/index.php?title=VisualAPL&diff=5936VisualAPL2020-11-25T00:41:29Z<p>RLevine: </p>
<hr />
<div>{{Infobox array language<br />
| array model = [[nested array model|nested]]<br />
| index origin = 0 (default) or 1<br />
| function styles = [[Defined function|defined]], .NET signature method<br />
| numeric types = Any .NET type<br />
| unicode support = full<br />
| released = 2009<br />
| withdrawn = 2011<br />
| developer = [[APL2000]]<br />
| platform = [[wikipedia:Common_Language_Infrastructure|CLI]]<br />
| operating system = Windows<br />
| license = Unavailable / Proprietary software<br />
| website = [http://forum.apl2000.com/viewforum.php?f=4 APLDN]<br />
| documentation = [http://forum.apl2000.com/viewtopic.php?f=4&t=626&p=2383&hilit=documentation#p2383 APLDN]<br />
| forum = [http://forum.apl2000.com/ APLDN]<br />
| influenced by = [[APL+Win]], [[wikipedia:C_Sharp_(programming_language)|C#]]<br />
}}<br />
'''Visual APL''', also known as APLNext, was an attempt by [[APL2000]] at creating an implementation of APL based on the Microsoft [[.NET#.NET_Framework|.NET framework]],<br />
designed to make APL available to mainstream programmers by being fully integrated into Visual Studio, the (then) foremost IDE for .NET based development on Windows. This meant a lot of changes to traditional aspects of APL programming, like having a workspace, and avoiding all reserved words. VisualAPL supported the intermingling of C# and APL code.<br />
<br />
Much like [[Dyalog Ltd.]]'s similar project, [[APL-sharp|APL#]], it quickly fizzled. It was released in 2009 and the last news about it were published in 2011.<br />
<br />
== External links ==<br />
<br />
[http://forum.apl2000.com/viewforum.php?f=4 VisualAPL topics] on the [[APL2000|APLDN]]<br />
<br />
{{APL dialects}}[[Category:APL dialects]][[Category:Nested array languages]][[Category:.NET]]</div>RLevinehttps://aplwiki.com/index.php?title=APL2000&diff=5935APL20002020-11-25T00:29:55Z<p>RLevine: /* External links */</p>
<hr />
<div>:''This page is about the APL vendor. For the 2000 [[APL conference]], see [[APL00]].''<br />
<br />
'''APLNow LLC''' (formerly known as '''APL2000''', which is retained as a service mark for its products) is the vendor of [[APL+Win]]. In addition to APL+Win, APLNow developed the discontinued [[VisualAPL]] and is now working on [[APL64]], a 64-bit successor to APL+Win. After Financial Reporting Software (soon to be LEX2000, after its main product) bought the rights to APL products including [[APL*PLUS/WIN]] from Manugistics (formerly [[STSC]]) in 1995,<ref>PRNewswire press release ([http://apl2000.com/press1.php reprint]). 1995-10-23.</ref> it was formed as a subsidiary to sell these products. LEX2000 was purchased by [[wikipedia:Cognos|Cognos]] in 1999,<ref>Business Wire press release ([http://apl2000.com/press4.php reprint]). 1999-01-25.</ref> and in 2005 APL2000's assets were purchased by the employee-owned business APLNow LLC, which adopted the name APL2000.<ref>Press release ([http://apl2000.com/press5.php reprint]). 2005-06-29.</ref><br />
<br />
APL2000, and later APLNow, held the [[APL2000 user conferences]] from 1996 to 2014.<br />
<br />
== APL Developer Network and Forum ==<br />
The APL Developer Network (APLDN) is an online community organized by the company for the exchange of ideas, programming tips and discussion of product issues among the customers and staff of APL2000. Their online forum is well-organized and, although directed to APL2000 users, it has topics of general interest for APL users. The APLDN Archive is an older version of the forum that is worth poking around in for historical nuggets. <br />
<br />
== References ==<br />
<references /><br />
<br />
== External links ==<br />
* [http://apl2000.com/ APL2000 Website]<br />
* [http://forum.apl2000.com/ APLDN] forum<br />
<br />
{{APL development}}[[Category:Vendors]]</div>RLevinehttps://aplwiki.com/index.php?title=APL2000&diff=5934APL20002020-11-25T00:29:20Z<p>RLevine: </p>
<hr />
<div>:''This page is about the APL vendor. For the 2000 [[APL conference]], see [[APL00]].''<br />
<br />
'''APLNow LLC''' (formerly known as '''APL2000''', which is retained as a service mark for its products) is the vendor of [[APL+Win]]. In addition to APL+Win, APLNow developed the discontinued [[VisualAPL]] and is now working on [[APL64]], a 64-bit successor to APL+Win. After Financial Reporting Software (soon to be LEX2000, after its main product) bought the rights to APL products including [[APL*PLUS/WIN]] from Manugistics (formerly [[STSC]]) in 1995,<ref>PRNewswire press release ([http://apl2000.com/press1.php reprint]). 1995-10-23.</ref> it was formed as a subsidiary to sell these products. LEX2000 was purchased by [[wikipedia:Cognos|Cognos]] in 1999,<ref>Business Wire press release ([http://apl2000.com/press4.php reprint]). 1999-01-25.</ref> and in 2005 APL2000's assets were purchased by the employee-owned business APLNow LLC, which adopted the name APL2000.<ref>Press release ([http://apl2000.com/press5.php reprint]). 2005-06-29.</ref><br />
<br />
APL2000, and later APLNow, held the [[APL2000 user conferences]] from 1996 to 2014.<br />
<br />
== APL Developer Network and Forum ==<br />
The APL Developer Network (APLDN) is an online community organized by the company for the exchange of ideas, programming tips and discussion of product issues among the customers and staff of APL2000. Their online forum is well-organized and, although directed to APL2000 users, it has topics of general interest for APL users. The APLDN Archive is an older version of the forum that is worth poking around in for historical nuggets. <br />
<br />
== References ==<br />
<references /><br />
<br />
== External links ==<br />
* [http://apl2000.com/ Website]<br />
* [http://forum.apl2000.com/ APLDN] forum<br />
<br />
{{APL development}}[[Category:Vendors]]</div>RLevinehttps://aplwiki.com/index.php?title=VisualAPL&diff=5933VisualAPL2020-11-24T23:45:27Z<p>RLevine: </p>
<hr />
<div>{{Infobox array language<br />
| array model = [[nested array model|nested]]<br />
| index origin = 0 (default) or 1<br />
| function styles = [[Defined function|defined]], .NET signature method<br />
| numeric types = Any .NET type<br />
| unicode support = full<br />
| released = 2009<br />
| withdrawn = 2011<br />
| developer = [[APL2000]]<br />
| platform = [[wikipedia:Common_Language_Infrastructure|CLI]]<br />
| operating system = Windows<br />
| license = Unavailable / Proprietary software<br />
| website = [http://forum.apl2000.com/viewforum.php?f=4 APLDN]<br />
| documentation = [http://forum.apl2000.com/viewtopic.php?f=4&t=626&p=2383&hilit=documentation#p2383 APLDN]<br />
| forum = [http://forum.apl2000.com/ APLDN]<br />
| influenced by = [[APL+Win]], [[wikipedia:C_Sharp_(programming_language)|C#]]<br />
}}<br />
'''Visual APL''', also known as APLNext, was an attempt by [[APL2000]] at creating an implementation of APL based on the Microsoft [[.NET#.NET_Framework|.NET framework]],<br />
designed to make APL available to mainstream programmers by being fully integrated into Visual Studio, the (then) foremost IDE for .NET based development on Windows. This meant a lot of changes to traditional aspects of APL programming, like having a workspace, and avoiding all reserved words. VisualAPL supported the intermingling of C# and APL code.<br />
<br />
Much like [[Dyalog Ltd.]]'s similar project, [[APL-sharp|APL#]], it quickly fizzled. It was released in 2009 and the last news about it were published in 2011.<br />
<br />
== External links ==<br />
<br />
[http://forum.apl2000.com/viewforum.php?f=4 VisualAPL topics] on [[APLDN]]<br />
<br />
{{APL dialects}}[[Category:APL dialects]][[Category:Nested array languages]][[Category:.NET]]</div>RLevinehttps://aplwiki.com/index.php?title=Template:APL_development&diff=5902Template:APL development2020-11-24T03:58:11Z<p>RLevine: Adjusted link to GNU APL leaving out community in the link (the community is not the "vendor")</p>
<hr />
<div><noinclude>__NOTITLE__</noinclude><br />
{| class="wikitable <includeonly>{{{1|mw-collapsible mw-collapsed}}}</includeonly>" style="width:100%"<br />
! colspan="2" | '''<big>APL development</big>''' [[{{fullurl:Template:APL_development|action=edit}} edit]]<br />
|-<br />
! style="width:8em" | Interface<br />
| [[Session]] ∙ [[Typing glyphs]] ([[Typing glyphs on Linux|on Linux]]) ∙ [[Fonts]] ∙ [[Text editors]]<br />
|-<br />
! Publications<br />
| [[Introductions]] ∙ [[Learning resources]] ∙ [[Simple examples]] ∙ [[Advanced examples]] ∙ [[Mnemonics]] ∙ [[Standards]] ∙ [[A Dictionary of APL]] ∙ [[Case studies]] ∙ [[Documentation suites]] ∙ [[Books]] ∙ [[Papers]] ∙ [[Videos]] ∙ [[Periodicals]] ∙ [[German terminology]]<br />
|-<br />
! style="width:8em;" | [[Sharing code]]<br />
| [[Backwards compatibility]] ∙ [[APLcart]] ∙ [[APLTree]] ∙ [[APL-Cation]] ∙ [[Dfns workspace]] ∙ [[Tatin]]<br />
|-<br />
! [[Vendors]]<br />
| [[APL2000]] ∙ [[Dyalog Ltd.|Dyalog]] ∙ [[GNU APL]] community ∙ [[IBM]] ∙ [[IPSA]] ∙ [[STSC]]<br />
|}</div>RLevinehttps://aplwiki.com/index.php?title=APL_Wiki:About&diff=5901APL Wiki:About2020-11-24T03:39:53Z<p>RLevine: Removed broken link, added brief note to link to old apl wiki</p>
<hr />
<div>'''APL Wiki''' was launched at the end of 2006 as a MoinMoin wiki. It was created and maintained by Kai Jäger of [https://aplteam.com/ APL Team Ltd], and [[APL Wiki logo|its logo]] derives from that of APL Team. In 2019, APL Wiki was reborn as a MediaWiki site, this time with content more in the style of Wikipedia. It is now maintained by Richard Park, but is not directly affiliated with any particular individuals, companies, or organisations. Migration of content from the [https://old.aplwiki.com/ old APL Wiki] is ongoing.<br />
<br />
== Contributing ==<br />
<br />
We welcome any and all contributions to APL Wiki, as long as they adhere to the general content standard as observed in existing pages and described in the [[APL Wiki:content guidelines|content guidelines]]. Currently, many links lead to [[Special:WantedPages|pages that as of yet do not exist]]. Creating and populating these missing pages is especially appreciated.<br />
<br />
MediaWiki documentation applies. Especially useful for you as a (new) contributor are:<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Editing_pages Editing pages]<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Starting_a_new_page Starting a new page]<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Links Links]<br />
* Our own [[APL Wiki:formatting|formatting]] reference.<br />
* [https://aplwiki.com/wiki/Terminology Localizing Terminology]<br />
<br />
Some advice to keep in mind:<br />
* This wiki is for general information about the APL programming language. Pages about other programming languages should be from the perspective of APL, even if they are array-oriented, as they merit their own wikis, which e.g. [[J]] has.<br />
* Remember that APL has many dialects, even if you use one. It's fine to write an [[:Category:Essays|essay]] about how to do something in a particular dialect, but encyclopedic articles should strive to be dialect neutral. Apply the principle of [[APL Wiki:Content guidelines#Due weight|due weight]] when deciding whether to mention a particular dialect, and [[APL Wiki:Formatting#Tagging dialects|tag]] code examples that don't work in all dialects.<br />
* If you don't know how to write something or think information on a page could be wrong or misleading, mention it on the page's Discussion tab.<br />
* Avoid "thread mode", where you simply add your thoughts to a page without taking the trouble to make the page a unified whole. Of course, this doesn't apply to Discussion and user pages.<br />
<br />
In the discussion tab, your voice is just one of many and you are free to express yourself as you wish, but please be nice.<br />
<br />
== External links ==<br />
<br />
* [[Main Page|APL Wiki main page]]<br />
* [https://old.aplwiki.com/ Archive of old APL Wiki] (worth perusing while content is being migrated)<br />
* [[BAA webinar]]: [https://www.youtube.com/watch?v=6qygPslrXnM Meet the new APL Wiki]<br />
{{APL community}}</div>RLevinehttps://aplwiki.com/index.php?title=User:RLevine&diff=5895User:RLevine2020-11-23T15:53:27Z<p>RLevine: </p>
<hr />
<div>As a long-time APL user, I have been privileged to witness so much extraordinary work from the APL community over the years. I am new to the APL wiki so thanks all for your help. I work in IT. Professional contact - My web site is [http://www.rmlconsultingservices.ca/ RML Consulting Services].</div>RLevinehttps://aplwiki.com/index.php?title=Talk:List_of_language_developers&diff=5891Talk:List of language developers2020-11-23T05:26:38Z<p>RLevine: </p>
<hr />
<div>[[User:RLevine|RLevine]] ([[User talk:RLevine|talk]]) 04:49, 23 November 2020 (UTC) I think it would be more useful to split the Vendors and Organizations lists into two parts: (1) active (2) inactive (for want of a better term). As it's a wiki, if an "inactive" implementation is actually "active", or vice versa, that can be easily fixed and referenced appropriately. I also think a page called "APL Implementations" could be created with a redirect to this page. The Language developer page also includes languages derived from APL such as J and K, which is fine, but also I think would be more useful if put into separate lists.<br />
[Addendum - Thanks for noting - I added tilde string.]<br />
<br />
:([[User:RLevine|RLevine]], remember to sign comments with <code><nowiki>~~~~</nowiki></code>). Given that hardware vendors are strictly a subset of inactive developers, and all the individual developers listed have been active in the past few years, we could do both: inactive developers with subheadings hardware vendors and other developers, and active developers with subheadings vendors, organizations (although I remain skeptical that the GNU APL community can really be considered an organization that develops APL), and independent developers. --[[User:Marshall|Marshall]] ([[User talk:Marshall|talk]]) 20:42, 20 November 2020 (UTC)<br />
<br />
::[[User:RLevine|RLevine]] ([[User talk:RLevine|talk]]) 05:26, 23 November 2020 (UTC) Based on your comments (and thanks) I'm glad I reached out for feedback. I think I better understand the intent of this page. I found a page closer to what I was looking for (Running APL). When I initially searched, I used "APL vendors" and was re-directed here which led to some "wheel-spinning" on my part looking for a list of APL's I can use now. Which seems to be what Running APL intends. So now I am suggesting just to add a related link on "Language Developer" page pointing to the page "Running APL". Or do we put at the top "If you're looking for current APLs click here ...". Whatever is the usual practice on this wiki.<br />
::I would suggest re-organizing (without changing) to separate APL from derivative languages in some way.<br />
::I agree with your observation on GNU Community. Not sure the intention of including it under Organizations. I think it's a user group like any other user group (As the GNU APL website state: "This web page contains links to contributions from users of GNU APL, aka. "the GNU APL community"). I suggest removing "GNU APL Community" from Organizations and replacing with the GNU APL developer Jürgen Sauermann in the list of language developers. This is based on what's in the current GNU APL website. This also seems to be in line with the purpose of the page.</div>RLevinehttps://aplwiki.com/index.php?title=Talk:List_of_language_developers&diff=5890Talk:List of language developers2020-11-23T04:49:29Z<p>RLevine: </p>
<hr />
<div>[[User:RLevine|RLevine]] ([[User talk:RLevine|talk]]) 04:49, 23 November 2020 (UTC) I think it would be more useful to split the Vendors and Organizations lists into two parts: (1) active (2) inactive (for want of a better term). As it's a wiki, if an "inactive" implementation is actually "active", or vice versa, that can be easily fixed and referenced appropriately. I also think a page called "APL Implementations" could be created with a redirect to this page. The Language developer page also includes languages derived from APL such as J and K, which is fine, but also I think would be more useful if put into separate lists.<br />
[Addendum - Thanks for noting - I added tilde string.]<br />
<br />
:([[User:RLevine|RLevine]], remember to sign comments with <code><nowiki>~~~~</nowiki></code>). Given that hardware vendors are strictly a subset of inactive developers, and all the individual developers listed have been active in the past few years, we could do both: inactive developers with subheadings hardware vendors and other developers, and active developers with subheadings vendors, organizations (although I remain skeptical that the GNU APL community can really be considered an organization that develops APL), and independent developers. --[[User:Marshall|Marshall]] ([[User talk:Marshall|talk]]) 20:42, 20 November 2020 (UTC)</div>RLevinehttps://aplwiki.com/index.php?title=User:RLevine&diff=5889User:RLevine2020-11-23T04:47:49Z<p>RLevine: </p>
<hr />
<div>Wiki statement - I feel the APL Wiki (starting with the "old" and continuing with this new one] presents an ideal opportunity to support activities in APL. I strongly support collaboration and knowledge-sharing in this wiki. As a personal statement - I work in IT focusing on business analysis and on teaching as a member of the Faculty of the School of Computer Technology, George Brown College, Toronto, Canada. My web site is [http://www.rmlconsultingservices.ca/ RML Consulting Services]. As a long-time APL user, I have been privileged to witness a lot of extraordinary work from the APL community over the years.</div>RLevinehttps://aplwiki.com/index.php?title=User:RLevine&diff=5888User:RLevine2020-11-23T04:46:36Z<p>RLevine: </p>
<hr />
<div>Wiki statement - I feel the APL Wiki (starting with the "old" and continuing with this new one] presents an ideal opportunity to support activities in APL. I strongly support collaboration and knowledge-sharing in this wiki. As a personal statement - I work in IT focusing on business analysis and on teaching as a member of the Faculty of the School of Computer Technology, George Brown College, Toronto, Canada. My web site is [http://www.rmlconsultingservices.ca/ RML Consulting Services]. As a long-time APL user, I have been privileged to witness a lot of extraordinary work over the years.</div>RLevinehttps://aplwiki.com/index.php?title=User:RLevine&diff=5887User:RLevine2020-11-23T04:43:44Z<p>RLevine: </p>
<hr />
<div>Wiki statement - I feel the APL Wiki (starting with the "old" and continuing with this new one] presents an ideal opportunity to support activities in APL. I strongly support collaboration and knowledge-sharing in this wiki. As a personal statement - I work in IT focusing on business analysis and on teaching as a member of the Faculty of the School of Computer Technology, George Brown College, Toronto, Canada. My web site is [http://www.rmlconsultingservices.ca/ RML Consulting Services]. I am a long-time APL user and have witnessed a lot of extraordinary work over the years.</div>RLevinehttps://aplwiki.com/index.php?title=User:RLevine&diff=5886User:RLevine2020-11-23T04:36:29Z<p>RLevine: Created page with "Wiki statement - I feel the APL Wiki (starting with the "old" and continuing with this new one] presents an ideal opportunity to support activities in APL. I strongly support..."</p>
<hr />
<div>Wiki statement - I feel the APL Wiki (starting with the "old" and continuing with this new one] presents an ideal opportunity to support activities in APL. I strongly support collaboration and knowledge-sharing in this wiki. As a personal statement - I work in IT focusing on business analysis and on teaching as a member of the Faculty of the School of Computer Technology, George Brown College, Toronto, Canada. I am a long-time APL user. If you wish to read more, check out my web site [http://www.rmlconsultingservices.ca/ RML Consulting Services]</div>RLevinehttps://aplwiki.com/index.php?title=APL_Wiki_talk:About&diff=5885APL Wiki talk:About2020-11-23T04:02:07Z<p>RLevine: </p>
<hr />
<div>[[User:RLevine|RLevine]] ([[User talk:RLevine|talk]]) 04:01, 23 November 2020 (UTC) The current second external link (APL Team: APL Wiki) is broken. Should this be corrected or removed? It currently leads to a location on aplteam.com that seems to involve the "old" APL Wiki and the third link (pointing to the old APL wiki my be the one intended.</div>RLevinehttps://aplwiki.com/index.php?title=APL_Wiki_talk:About&diff=5884APL Wiki talk:About2020-11-23T04:01:13Z<p>RLevine: </p>
<hr />
<div>[[User:RLevine|RLevine]] ([[User talk:RLevine|talk]]) 04:01, 23 November 2020 (UTC) The current second external link (APL Team: APL Wiki) is broken. Should this be corrected or removed? It currently leads to a location on aplteam.com that seems to involve the "old" APL Wiki and the third link seems to be the one intended.</div>RLevinehttps://aplwiki.com/index.php?title=APL_Wiki_talk:About&diff=5883APL Wiki talk:About2020-11-23T04:00:22Z<p>RLevine: Created page with "The current second external link (APL Team: APL Wiki) is broken. Should this be corrected or removed? It currently leads to a location on aplteam.com that seems to involve the..."</p>
<hr />
<div>The current second external link (APL Team: APL Wiki) is broken. Should this be corrected or removed? It currently leads to a location on aplteam.com that seems to involve the "old" APL Wiki and the third link seems to be the one intended. [[User:RLevine|RLevine]] ([[User talk:RLevine|talk]]) 04:00, 23 November 2020 (UTC)</div>RLevinehttps://aplwiki.com/index.php?title=Learning_resources&diff=5862Learning resources2020-11-22T05:51:45Z<p>RLevine: Rethought my proposed changes and tried to maintain the original "flavour"</p>
<hr />
<div>{| class=wikitable style="width:50%;float:right"<br />
|{{quote | "I have long been struck by the contrast between the success with which the adventurous learn APL by simply using it, and the frequent failure of lecture courses to communicate the simplicity and applicability of the language."|[[Ken Iverson]]. ''A Working Introduction to APL'', 1981.}}<br />
|}<br />
To facilitate self-study, the resources here are classified by target audience. However, if you get stuck, don't hesitate to request help in the [[APL Orchard]] chat room or [https://stackoverflow.com/questions/ask?tags=apl ask a question on Stack Exchange].<br />
<br />
== For non-programmers ==<br />
<br />
Some of the best resources for somebody new to APL and programming in general are:<br />
<div style="column-width:40em"><br />
* APL Wiki's [[simple examples]]<br />
* The [https://tryapl.org/?tab=3 Learn tab on TryAPL]<br />
* The book [[Mastering Dyalog APL]] by Bernard Legrand<br />
* [http://www.microapl.com/apl/learn_apl.html Learning APL with APLX] (also [http://www.microapl.com/apl/LearningAPLwithAPLX.pdf as PDF])<br />
* The [https://tutorial.dyalog.com Zark APL Tutor]<br />
* APL a Day: [https://www.sacrideo.us/apl-a-day-0-introduction/ Introduction], [https://www.sacrideo.us/apl-a-day-1-functions/ Functions], [https://www.sacrideo.us/apl-a-day-2-arrays-values/ Arrays, Values], [https://www.sacrideo.us/apl-a-day-3-arrays-have-shape/ Arrays have Shape]<br />
* [http://robertson.uk.net/Files/APL1&2.pdf A Practical Introduction to APL 1 & 2] (3 & 4 is [[#For novice APLers|for experts]])<br />
* Découvrez le langage APL: parts [https://www.youtube.com/watch?v=Nxq1BUUXobM 1], [https://www.youtube.com/watch?v=s-E7BsMg_Qc 2], [https://www.youtube.com/watch?v=csx2Z-GEGPw 3] by Eric Schrafstetter (in French)<br />
</div><br />
Follow one or a couple of these tutorials through and play around a bit. To learn APL the advice is similar to that for learning other languages: have a goal (something you want to accomplish) and try to do it. Along the way you are sure to come across the pitfalls and gotchas of the language, and with time you may come to understand what APL thinking means.<br />
<br />
== For programmers unfamiliar with APL ==<br />
<br />
This is a list of tutorials and other resources of interest to someone who knows about programming or is familiar with another programming language, but wants to learn more about APL.<br />
<div style="column-width:20em"><br />
* APL Wiki's [[advanced examples]]<br />
* APL Wiki's [[Books]]<br />
* APL Wiki's [[Papers]]<br />
* [[APL Cultivation]] (chat lessons)<br />
* [https://tryapl.org TryAPL online interpreter with lessons]<br />
* [https://rikedyp.github.io/APLWorkshop APL Workshop]<br />
* [https://github.com/nooodl/learnxinyminutes-docs/blob/master/apl.apl Learn X in Y minutes]<br />
* [https://codeburst.io/lets-learn-a-programming-language-5f374e4abae5 Let's Learn A Programming Language]<br />
* The [[Mastering Dyalog APL]] book<br />
* [https://tutorial.dyalog.com/ Zark tutorial]<br />
* [https://github.com/vendethiel/trying.apl Trying APL]<br />
* [https://github.com/annser/annser Artificial Neural Networks]<br />
* [https://codeburst.io/fizzbuzz-in-apl-a193d1954b4b FizzBuzz]<br />
</div><br />
[[Category:Lists]]<br />
<br />
== For novice APLers ==<br />
<br />
* [http://robertson.uk.net/Files/APL3&4.pdf A Practical Introduction to APL 3 & 4]<br />
<br />
If you already have a fair grasp of APL's [[primitive function]]s and [[primitive operator|operators]], you can sharpen your skills by challenging yourself with these:<br />
* [https://aplcart.info/quiz APLcart Quiz]: Be challenged to write a function for a given task or to explain what a given function does. (Based on [[APLcart]] data.)<br />
<br />
* APL Crosswords: [https://abrudz.github.io/crosswords/1/ 1] [https://abrudz.github.io/crosswords/4/ 4] [https://abrudz.github.io/crosswords/5/ 5] — Fill in expressions and snippets to fulfil all the clues.<br />
<br />
* [https://www.dyalog.com/2016-year-game.htm 2016 Year Game]: Find APL expressions involving exactly the digits 2 0 1 6 in that order to equal the numbers 0 to 100.<br />
<br />
* [https://www.dyalog.com/2017-code-golf-challenge.htm 2017 Code Golf Challenge]: Find the shortest possible APL expression that evaluates 1…52 without using any number or character literals.<br />
<br />
* [https://www.dyalog.com/student-competition.htm Previous years' problems] from the [[APL Problem Solving Competition]]. Phase I problems are [https://problems.tryapl.org available with automated testing].<br />
<br />
* [[APL-eusis]]: A game for honing your ability to "think in APL".<br />
<br />
== For advanced APLers ==<br />
<br />
Here is a list of "how-to"s on various subjects:<br />
<br />
* [[Error trapping with Dyalog APL]]<br />
<br />
* [[Error trapping in Dyalog APL forms]]<br />
<br />
* [[Calling APL from other languages]]<br />
<br />
* [[Calling other languages from APL]]<br />
<br />
* [[Performance tuning]]<br />
<br />
* [[APL on the web]]<br />
<br />
* [[Parallel computing]]<br />
<br />
* [[Cryptography]] <span style="background:yellow">← Migrate https://old.aplwiki.com/CryptographyWithDyalogAndDotNet</span><br />
<br />
* [[WPF XAML Demo]]<br />
<br />
== Haven't used APL in a while? ==<br />
Those who learned APL "in the early days" should note that several implementations have made significant extensions to the language and system in the last decade or two.<br />
<br />
* New primitive functions: <source lang=apl inline>⊢</source> [[Identity|Same]], [[Right_identity|Right]]; <source lang=apl inline>⊣</source> [[Identity|Same]], [[Left_identity|Left]]; <source lang=apl inline>⌷</source> [[Materialise]], [[Squad indexing|Index]]; <source lang=apl inline>≡</source> [[Depth]], [[Match]]; <source lang=apl inline>≢</source> [[Tally]], [[Not Match]]; <source lang=apl inline>⍸</source> [[Where]], [[Interval Index]]; <source lang=apl inline>⊆</source> [[Nest]], [[Partition]]<br />
<br />
* New primitive operators: <source lang=apl inline>∘</source> [[Bind]], [[Beside]]; <source lang=apl inline>⍤</source> [[Rank operator|Rank]]; <source lang=apl inline>⌸</source> [[Key]]; <source lang=apl inline>⌺</source> [[Stencil]]; <source lang=apl inline>⍠</source> [[Variant]]<br />
<br />
* Lambdas ([[dfns]]): [https://help.dyalog.com/16.0/Content/Language/Defined%20Functions%20and%20Operators/DynamicFunctions/Dynamic%20Functions%20and%20Operators.htm Intro]; [https://help.dyalog.com/latest/Content/Language/Defined%20Functions%20and%20Operators/DynamicFunctions/MultiLine%20Dynamic%20Functions.htm Details]; [https://help.dyalog.com/latest/Content/Language/Defined%20Functions%20and%20Operators/DynamicFunctions/Dynamic%20Operators.htm Operators]; [https://dfns.dyalog.com/n_contents.htm The dfns workspace] (collection of categorized utilities with extensive comments and notes)<br />
<br />
* [[Tacit programming]]: [[Dyalog APL]] documentation: [https://help.dyalog.com/16.0/Content/RelNotes14.0/Function%20Trains.htm Intro]; [https://help.dyalog.com/latest/Content/Language/Introduction/Trains.htm Details]; [https://www.youtube.com/watch?v=kt4lMZbn-so short video]; [https://www.youtube.com/watch?v=A2LqqBosvY0 long video]; [https://chat.stackexchange.com/rooms/52405/conversation/lesson-23-transcribing-to-and-reading-trains APL Cultivation lesson]<br />
<br />
* Other features: [[Keyword]]s; [[Object-oriented programming]];[[namespace]]s<br />
<br />
{{APL development}}</div>RLevinehttps://aplwiki.com/index.php?title=Subreddits&diff=5861Subreddits2020-11-22T04:45:10Z<p>RLevine: Minor rephrasing without losing information to quickly define a subreddit and then explain the significance to APL</p>
<hr />
<div>Subreddits are individual forums on [[wikipedia:Reddit|Reddit]]. <br />
<br />
Two subreddits are especially notable for the APL community:<br />
<br />
* '''[https://www.reddit.com/r/apljk/ r/apljk]''' is for talk about APL, [[J]], [[K]]/[[Q]] and kdb+, and all things that relate to [[array language]]s.<br />
<br />
* '''[https://www.reddit.com/r/apl/ r/apl]''' has less activity, but is exclusively for APL.<br />
<br />
{{APL community}}[[Category:Online forums]]</div>RLevinehttps://aplwiki.com/index.php?title=SIGAPL&diff=5860SIGAPL2020-11-22T04:39:41Z<p>RLevine: /* History */ corrected minor typos</p>
<hr />
<div>'''SIGAPL''', formerly '''STAPL''', is a Special Interest Group on Array Programming Languages which operates as a sub-group of [[wikipedia:SIGPLAN|SIGPLAN]] (Special Interest Group on Programming Languages) of [[wikipedia:Association for Computing Machinery|ACM]] (Association for Computing Machinery).<br />
<br />
== History ==<br />
<br />
SIGAPL was formed in 1973 as STAPL, a Technical Committee of [[wikipedia:SIGPLAN|SIGPLAN]], the [[wikipedia:Association for Computing Machinery|ACM]] Special Interest Group on Programming LANguages. It was later converted to an ACM Special Interest Group independent of SIGPLAN named SIGAPL, and in 2008 was merged back as a chapter of SIGPLAN, retaining the name SIGAPL.<br />
<br />
ACM's history with APL began in 1970. Following the [[APL70|second APL conference]] (organized by an APL committe under [[wikipedia:SHARE (computing)|SHARE]]), a group of APLers initiated the ACM's process to create a Special Interest Group by sending the required petition and signatures to form such a group for APL, SIGAPL. This request was denied on the grounds that a Special Interest Group on programming languages in general, SIGPLAN, already existed. Following this rejection, SIGPLAN reprinted issues of the [[APL Quote-Quad]] in ''SIGPLAN Notices'' for a short period before stopping in 1972. Some APLers suggested that the APL community form its own organization, while [[Alan Perlis]] led a group to convince the ACM to reverse their decision.<ref name="roots">[[Garth Foster|Foster, Garth]]. "The APL user community - its roots" at [[IPSA '80]].</ref><br />
<br />
In 1972, SIGPLAN added provisions for creating Technical Committees (TECS) to its bylaws, and the APL applied to form STAPL. This application was accepted in 1973, and STAPL was formed and organized between 1973 and 1974, taking over administration of the 1974 conference [[APL74|APL 6]] and publication of the conference proceedings and [[APL Quote-Quad]]. STAPL was the first SIGPLAN Technical Committee.<ref name="roots" /><br />
<br />
Profits from the unexpectedly large APL 6 helped establish STAPL initially. Officers were appointed initially, and the first elections held in 1975; [[Garth Foster]] retained his position as the first STAPL Chairman. In the next two elections, held in 1977 and 1979, [[Phil Abrams]] and then [[Eugene McDonnell]] would be elected Chairman. STAPL hosted [[APL 75]] and [[APL 76]] (initiating the scheme of naming conferences after the year) with growing success. However, no 1977 conference was held because STAPL was unable to find a location conforming to the rule that odd-numbered conferences be held in Europe, and the 1978 conference was also skipped because of concerns about quality of and demand for such frequent conferences. Yearly APL conferences resumed when STAPL organized [[APL 79]], attended by nearly a thousand, although [[APL 80]] was hosted by the Dutch Computer Society and the European Cooperation in Informatics, not STAPL.<ref name="roots" /> Following APL 80, STAPL and later SIGAPL organized the APL conference every year until 2005.<br />
<br />
By 1980, the process of separating STAPL from SIGPLAN had begun, and SIGAPL was eventually made an official special-interest group chartered under the auspices of the ACM (Association for Computing Machinery). In February of 2008 this group was formally de-chartered by the SIG Governing Board.<br />
<br />
As part of this change, what was formerly SIGAPL (Special Interest Group on ''APL'') became a chapter within the larger SIGPLAN (Special Interest Group on Programming Languages). One of the goals of this change was to encourage the often quite isolated APL community to cooperate with the larger group and thus reach beyond its traditional boundaries. The "APL" part of the acronym was reinterpreted to cover all array programming languages, not just the original APL language. SIGAPL is now identified as the Special Interest Group on ''Array Programming Languages''.<br />
<br />
== External links ==<br />
<br />
* [http://sigapl.org SIGAPL] (Special Interest Group on Array Programming Languages)<br />
* [http://www.sigplan.org/ SIGPLAN] (Special Interest Group on Programming Languages)<br />
<br />
== References ==<br />
<references /><br />
[[Category:User groups]]<br />
{{APL community}}</div>RLevinehttps://aplwiki.com/index.php?title=BAA&diff=5857BAA2020-11-21T04:18:29Z<p>RLevine: /* Webinar */</p>
<hr />
<div>The '''British APL Association''' ('''BAA'''; infrequently '''BAPLA''') is a [[user group]] founded in 1984 in England to promote APL, and the publisher of Vector journal. It is funded by its sustaining members, which include corporate users and the APL [[vendors]] [[APL2000]], [[Dyalog Ltd.]], [[Kx Systems]], and MicroAPL.<br />
<br />
The BAA was a Specialist Group of the [[wikipedia:British Computer Society|British Computer Society]] from its early years (possibly beginning after [[APL86]]<ref>Anthony Camacho. [http://archive.vector.org.uk/art10500330 "BAA Annual General Meeting 2010"]. Vector journal volume 24 issue 4. 2010-12.</ref>) until it left in response to increasing requirements made by the BCS in 2008.<ref>Paul Grosvenor. [http://archive.vector.org.uk/art10011900 "Changes at the BAA" (pdf)]. Vector journal volume 23 issue 4. 2008-09.</ref><br />
<br />
== Activities ==<br />
<br />
=== Symposium ===<br />
<br />
From 2008 and until the onset of the [[wikipedia:COVID-19 pandemic|COVID-19 pandemic]], the BAA London group arranged a monthly open-for-all meet-up, called ''the symposium'', at the The Hoop and Grapes pub on Farringdon Street in London. No sign-up was required.<br />
<br />
=== Vector journal ===<br />
<br />
Vector, the journal of the BAA, began publication in 1984, and gradually took the place of [[APL Quote Quad]] as the de-facto leading publishing channel for APL content. The journal featured submitted articles on array programming including [[J]] and [[K]], as well as news from APL and other array language vendors. Beginning in 2005, with volume 21 issue 4, the journal was issued online as well as in print, and some prior articles have also been made available online.<ref>Stephen Taylor. [http://archive.vector.org.uk/art10009870 "Editorial: Discover, Learn, Profit"]. Vector journal volume 21 issue 4. 2005-09.</ref> It was published quarterly until 2004, when late and sometimes skipped issues began to interrupt its formerly regular schedule. Releases slowed more significantly after 2008, and in 2016, following the completion of volume 26, the journal moved entirely to online publishing. So far a single issue has been published this way, in 2019.<br />
<br />
=== BAPLA 09 ===<br />
<br />
The British APL Association held a 2-day conference, '''BAPLA 09''', on June 8th & 9th 2009 at DeVere Hotel, Wokefield Park, near Reading, UK<br />
<br />
=== Webinar ===<br />
In response to the restrictions imposed by the COVID-19 pandemic, BAA has arranged a series of [[Wikipedia:webcast|webcast]]s to replace their regular monthly symposium.<ref>BAA. [https://britishaplassociation.org/webinar-schedule-2020/ Webinar Schedule for 2020].</ref><br />
<br />
The Webinars, are held using [[Wikipedia:Zoom (software)|Zoom]], and consist of half an hour of social interaction, followed by a single presentation of about an hour, and a Q&A session. The sessions are recorded with subsequent publication on YouTube. Some webinars are so called ''open sessions'' which are more similar to the monthly symposium, in being informal meetings where APLers discuss and present whatever they feel like, with no particular subject decided on beforehand.<br />
<br />
{| class=wikitable<br />
! No. !! Date !! Presenter(s) !! Title<br />
|-<br />
| 1 || Apr 9th 2020 || [[Richard Park]], [[Dyalog Ltd.|Dyalog]] || [https://www.youtube.com/watch?v=dbB4uxbG1ec Molecular Dynamics-in-APL]<br />
|-<br />
| 2 || Apr 23rd 2020 || MJH Software Services || [https://www.youtube.com/watch?v=8Wvrn8vtazA Introducing qWC Alpha 0.4]<br />
|-<br />
| 3 || May 7th 2020 || [[Adám Brudzewsky]], [[Dyalog Ltd.|Dyalog]] || [https://www.youtube.com/watch?v=6qygPslrXnM Meet the new APL Wiki]<br />
|-<br />
| 4 || May 21st 2020 || [[Phil Last]] || Acre source-code manager update<br />
|-<br />
| 5 || Jun 4th 2020 || Paul Grosvenor || British APL Association AGM<br />
|-<br />
| 6 || Jun 18th 2020 || [[Bob Armstrong]] || CoSy : The Shortest Path from the Chip to the Math<br />
|-<br />
| 7 || Jul 2nd 2020 || [[Adám Brudzewsky]] || aplcart.info turns 1<br />
|-<br />
| colspan=4 align=center | summer break<br />
|-<br />
| rowspan=2 | 8 || rowspan=2 | Aug 13th 2020 || John Jacob || BAA websites: New features<br />
|- <br />
| Ellis Morgan || An APL recreation<br />
|-<br />
| 9 || Aug 27th 2020 || colspan=2 | Open Session<br />
|-<br />
| 10 || Sep 10th 2020 || colspan=2 | Open session<br />
|-<br />
| 11 || Sep 24th 2020 || Ray Cannon || | Using SVG from Dyalog APL for animated visualisation<br />
|-<br />
| 12 || Oct 8th 2020 || Ray Polivka || | Seats in the House of Representatives<br />
|-<br />
| 13 || Oct 22nd 2020 || colspan=2 | Open Session<br />
|-<br />
| 14 || Nov 5th 2020 || colspan=2 | Open session<br />
|}<br />
<br />
== Organisation ==<br />
<br />
The BAA is administered by a committee of officers elected by ballot of Association members at the Annual General Meeting. Working groups are also established in areas such as activity planning and journal production. Offers of assistance and involvement with any Association matters are always welcomed.<br />
<br />
Funding for the BAA comes entirely from the sustaining members. In many cases, these sustaining members also provide manpower and administrative assistance to the association at their own cost.<br />
<br />
The current chairman is Paul Grosvenor.<br />
<br />
== External links ==<br />
<br />
* [https://britishaplassociation.org/ BAA Website]<br />
<br />
* [https://groups.google.com/forum/#!forum/baa-london BAA London Google Group] announces upcoming symposiums and other events.<br />
<br />
* [https://vector.org.uk/ ''Vector'', The BAA's Journal]<br />
<br />
* [http://archive.vector.org.uk/ The ''Vector'' archives] are significant and relevant for understanding APL and related languages today<br />
<br />
==References==<br />
<references/><br />
{{APL community}}<br />
[[Category:User groups]]</div>RLevinehttps://aplwiki.com/index.php?title=BAA&diff=5856BAA2020-11-21T04:14:56Z<p>RLevine: /* External links */ minor rephrasing of comment on Vector archives</p>
<hr />
<div>The '''British APL Association''' ('''BAA'''; infrequently '''BAPLA''') is a [[user group]] founded in 1984 in England to promote APL, and the publisher of Vector journal. It is funded by its sustaining members, which include corporate users and the APL [[vendors]] [[APL2000]], [[Dyalog Ltd.]], [[Kx Systems]], and MicroAPL.<br />
<br />
The BAA was a Specialist Group of the [[wikipedia:British Computer Society|British Computer Society]] from its early years (possibly beginning after [[APL86]]<ref>Anthony Camacho. [http://archive.vector.org.uk/art10500330 "BAA Annual General Meeting 2010"]. Vector journal volume 24 issue 4. 2010-12.</ref>) until it left in response to increasing requirements made by the BCS in 2008.<ref>Paul Grosvenor. [http://archive.vector.org.uk/art10011900 "Changes at the BAA" (pdf)]. Vector journal volume 23 issue 4. 2008-09.</ref><br />
<br />
== Activities ==<br />
<br />
=== Symposium ===<br />
<br />
From 2008 and until the onset of the [[wikipedia:COVID-19 pandemic|COVID-19 pandemic]], the BAA London group arranged a monthly open-for-all meet-up, called ''the symposium'', at the The Hoop and Grapes pub on Farringdon Street in London. No sign-up was required.<br />
<br />
=== Vector journal ===<br />
<br />
Vector, the journal of the BAA, began publication in 1984, and gradually took the place of [[APL Quote Quad]] as the de-facto leading publishing channel for APL content. The journal featured submitted articles on array programming including [[J]] and [[K]], as well as news from APL and other array language vendors. Beginning in 2005, with volume 21 issue 4, the journal was issued online as well as in print, and some prior articles have also been made available online.<ref>Stephen Taylor. [http://archive.vector.org.uk/art10009870 "Editorial: Discover, Learn, Profit"]. Vector journal volume 21 issue 4. 2005-09.</ref> It was published quarterly until 2004, when late and sometimes skipped issues began to interrupt its formerly regular schedule. Releases slowed more significantly after 2008, and in 2016, following the completion of volume 26, the journal moved entirely to online publishing. So far a single issue has been published this way, in 2019.<br />
<br />
=== BAPLA 09 ===<br />
<br />
The British APL Association held a 2-day conference, '''BAPLA 09''', on June 8th & 9th 2009 at DeVere Hotel, Wokefield Park, near Reading, UK<br />
<br />
=== Webinar ===<br />
In response to the restrictions imposed by the COVID-19 pandemic, BAA is arranging a series of [[Wikipedia:webcast|webcast]]s to replace their regular monthly symposium.<ref>BAA. [https://britishaplassociation.org/webinar-schedule-2020/ Webinar Schedule for 2020].</ref><br />
<br />
The Webinars, are held using [[Wikipedia:Zoom (software)|Zoom]], and consist of half an hour of social interaction, followed by a single presentation of about an hour, and a Q&A session. The sessions are recorded with subsequent publication on YouTube. Some webinars are so called ''open sessions'' which are more similar to the monthly symposium, in being informal meetings where APLers discuss and present whatever they feel like, with no particular subject decided on beforehand.<br />
<br />
{| class=wikitable<br />
! No. !! Date !! Presenter(s) !! Title<br />
|-<br />
| 1 || Apr 9th 2020 || [[Richard Park]], [[Dyalog Ltd.|Dyalog]] || [https://www.youtube.com/watch?v=dbB4uxbG1ec Molecular Dynamics-in-APL]<br />
|-<br />
| 2 || Apr 23rd 2020 || MJH Software Services || [https://www.youtube.com/watch?v=8Wvrn8vtazA Introducing qWC Alpha 0.4]<br />
|-<br />
| 3 || May 7th 2020 || [[Adám Brudzewsky]], [[Dyalog Ltd.|Dyalog]] || [https://www.youtube.com/watch?v=6qygPslrXnM Meet the new APL Wiki]<br />
|-<br />
| 4 || May 21st 2020 || [[Phil Last]] || Acre source-code manager update<br />
|-<br />
| 5 || Jun 4th 2020 || Paul Grosvenor || British APL Association AGM<br />
|-<br />
| 6 || Jun 18th 2020 || [[Bob Armstrong]] || CoSy : The Shortest Path from the Chip to the Math<br />
|-<br />
| 7 || Jul 2nd 2020 || [[Adám Brudzewsky]] || aplcart.info turns 1<br />
|-<br />
| colspan=4 align=center | summer break<br />
|-<br />
| rowspan=2 | 8 || rowspan=2 | Aug 13th 2020 || John Jacob || BAA websites: New features<br />
|- <br />
| Ellis Morgan || An APL recreation<br />
|-<br />
| 9 || Aug 27th 2020 || colspan=2 | Open Session<br />
|-<br />
| 10 || Sep 10th 2020 || colspan=2 | Open session<br />
|-<br />
| 11 || Sep 24th 2020 || Ray Cannon || | Using SVG from Dyalog APL for animated visualisation<br />
|-<br />
| 12 || Oct 8th 2020 || Ray Polivka || | Seats in the House of Representatives<br />
|-<br />
| 13 || Oct 22nd 2020 || colspan=2 | Open Session<br />
|-<br />
| 14 || Nov 5th 2020 || colspan=2 | Open session<br />
|}<br />
<br />
== Organisation ==<br />
<br />
The BAA is administered by a committee of officers elected by ballot of Association members at the Annual General Meeting. Working groups are also established in areas such as activity planning and journal production. Offers of assistance and involvement with any Association matters are always welcomed.<br />
<br />
Funding for the BAA comes entirely from the sustaining members. In many cases, these sustaining members also provide manpower and administrative assistance to the association at their own cost.<br />
<br />
The current chairman is Paul Grosvenor.<br />
<br />
== External links ==<br />
<br />
* [https://britishaplassociation.org/ BAA Website]<br />
<br />
* [https://groups.google.com/forum/#!forum/baa-london BAA London Google Group] announces upcoming symposiums and other events.<br />
<br />
* [https://vector.org.uk/ ''Vector'', The BAA's Journal]<br />
<br />
* [http://archive.vector.org.uk/ The ''Vector'' archives] are significant and relevant for understanding APL and related languages today<br />
<br />
==References==<br />
<references/><br />
{{APL community}}<br />
[[Category:User groups]]</div>RLevinehttps://aplwiki.com/index.php?title=BAA&diff=5855BAA2020-11-21T04:13:33Z<p>RLevine: /* External links */ amended link to Vector archive to comment on significance in today's APL world</p>
<hr />
<div>The '''British APL Association''' ('''BAA'''; infrequently '''BAPLA''') is a [[user group]] founded in 1984 in England to promote APL, and the publisher of Vector journal. It is funded by its sustaining members, which include corporate users and the APL [[vendors]] [[APL2000]], [[Dyalog Ltd.]], [[Kx Systems]], and MicroAPL.<br />
<br />
The BAA was a Specialist Group of the [[wikipedia:British Computer Society|British Computer Society]] from its early years (possibly beginning after [[APL86]]<ref>Anthony Camacho. [http://archive.vector.org.uk/art10500330 "BAA Annual General Meeting 2010"]. Vector journal volume 24 issue 4. 2010-12.</ref>) until it left in response to increasing requirements made by the BCS in 2008.<ref>Paul Grosvenor. [http://archive.vector.org.uk/art10011900 "Changes at the BAA" (pdf)]. Vector journal volume 23 issue 4. 2008-09.</ref><br />
<br />
== Activities ==<br />
<br />
=== Symposium ===<br />
<br />
From 2008 and until the onset of the [[wikipedia:COVID-19 pandemic|COVID-19 pandemic]], the BAA London group arranged a monthly open-for-all meet-up, called ''the symposium'', at the The Hoop and Grapes pub on Farringdon Street in London. No sign-up was required.<br />
<br />
=== Vector journal ===<br />
<br />
Vector, the journal of the BAA, began publication in 1984, and gradually took the place of [[APL Quote Quad]] as the de-facto leading publishing channel for APL content. The journal featured submitted articles on array programming including [[J]] and [[K]], as well as news from APL and other array language vendors. Beginning in 2005, with volume 21 issue 4, the journal was issued online as well as in print, and some prior articles have also been made available online.<ref>Stephen Taylor. [http://archive.vector.org.uk/art10009870 "Editorial: Discover, Learn, Profit"]. Vector journal volume 21 issue 4. 2005-09.</ref> It was published quarterly until 2004, when late and sometimes skipped issues began to interrupt its formerly regular schedule. Releases slowed more significantly after 2008, and in 2016, following the completion of volume 26, the journal moved entirely to online publishing. So far a single issue has been published this way, in 2019.<br />
<br />
=== BAPLA 09 ===<br />
<br />
The British APL Association held a 2-day conference, '''BAPLA 09''', on June 8th & 9th 2009 at DeVere Hotel, Wokefield Park, near Reading, UK<br />
<br />
=== Webinar ===<br />
In response to the restrictions imposed by the COVID-19 pandemic, BAA is arranging a series of [[Wikipedia:webcast|webcast]]s to replace their regular monthly symposium.<ref>BAA. [https://britishaplassociation.org/webinar-schedule-2020/ Webinar Schedule for 2020].</ref><br />
<br />
The Webinars, are held using [[Wikipedia:Zoom (software)|Zoom]], and consist of half an hour of social interaction, followed by a single presentation of about an hour, and a Q&A session. The sessions are recorded with subsequent publication on YouTube. Some webinars are so called ''open sessions'' which are more similar to the monthly symposium, in being informal meetings where APLers discuss and present whatever they feel like, with no particular subject decided on beforehand.<br />
<br />
{| class=wikitable<br />
! No. !! Date !! Presenter(s) !! Title<br />
|-<br />
| 1 || Apr 9th 2020 || [[Richard Park]], [[Dyalog Ltd.|Dyalog]] || [https://www.youtube.com/watch?v=dbB4uxbG1ec Molecular Dynamics-in-APL]<br />
|-<br />
| 2 || Apr 23rd 2020 || MJH Software Services || [https://www.youtube.com/watch?v=8Wvrn8vtazA Introducing qWC Alpha 0.4]<br />
|-<br />
| 3 || May 7th 2020 || [[Adám Brudzewsky]], [[Dyalog Ltd.|Dyalog]] || [https://www.youtube.com/watch?v=6qygPslrXnM Meet the new APL Wiki]<br />
|-<br />
| 4 || May 21st 2020 || [[Phil Last]] || Acre source-code manager update<br />
|-<br />
| 5 || Jun 4th 2020 || Paul Grosvenor || British APL Association AGM<br />
|-<br />
| 6 || Jun 18th 2020 || [[Bob Armstrong]] || CoSy : The Shortest Path from the Chip to the Math<br />
|-<br />
| 7 || Jul 2nd 2020 || [[Adám Brudzewsky]] || aplcart.info turns 1<br />
|-<br />
| colspan=4 align=center | summer break<br />
|-<br />
| rowspan=2 | 8 || rowspan=2 | Aug 13th 2020 || John Jacob || BAA websites: New features<br />
|- <br />
| Ellis Morgan || An APL recreation<br />
|-<br />
| 9 || Aug 27th 2020 || colspan=2 | Open Session<br />
|-<br />
| 10 || Sep 10th 2020 || colspan=2 | Open session<br />
|-<br />
| 11 || Sep 24th 2020 || Ray Cannon || | Using SVG from Dyalog APL for animated visualisation<br />
|-<br />
| 12 || Oct 8th 2020 || Ray Polivka || | Seats in the House of Representatives<br />
|-<br />
| 13 || Oct 22nd 2020 || colspan=2 | Open Session<br />
|-<br />
| 14 || Nov 5th 2020 || colspan=2 | Open session<br />
|}<br />
<br />
== Organisation ==<br />
<br />
The BAA is administered by a committee of officers elected by ballot of Association members at the Annual General Meeting. Working groups are also established in areas such as activity planning and journal production. Offers of assistance and involvement with any Association matters are always welcomed.<br />
<br />
Funding for the BAA comes entirely from the sustaining members. In many cases, these sustaining members also provide manpower and administrative assistance to the association at their own cost.<br />
<br />
The current chairman is Paul Grosvenor.<br />
<br />
== External links ==<br />
<br />
* [https://britishaplassociation.org/ BAA Website]<br />
<br />
* [https://groups.google.com/forum/#!forum/baa-london BAA London Google Group] announces upcoming symposiums and other events.<br />
<br />
* [https://vector.org.uk/ ''Vector'', The BAA's Journal]<br />
<br />
* [http://archive.vector.org.uk/ The ''Vector'' archives] are relevant for learning and understanding APL and related languages today<br />
<br />
==References==<br />
<references/><br />
{{APL community}}<br />
[[Category:User groups]]</div>RLevinehttps://aplwiki.com/index.php?title=BAA&diff=5854BAA2020-11-21T04:11:43Z<p>RLevine: /* External links */ amended link to Vector archive to comment on significance in today's APL world</p>
<hr />
<div>The '''British APL Association''' ('''BAA'''; infrequently '''BAPLA''') is a [[user group]] founded in 1984 in England to promote APL, and the publisher of Vector journal. It is funded by its sustaining members, which include corporate users and the APL [[vendors]] [[APL2000]], [[Dyalog Ltd.]], [[Kx Systems]], and MicroAPL.<br />
<br />
The BAA was a Specialist Group of the [[wikipedia:British Computer Society|British Computer Society]] from its early years (possibly beginning after [[APL86]]<ref>Anthony Camacho. [http://archive.vector.org.uk/art10500330 "BAA Annual General Meeting 2010"]. Vector journal volume 24 issue 4. 2010-12.</ref>) until it left in response to increasing requirements made by the BCS in 2008.<ref>Paul Grosvenor. [http://archive.vector.org.uk/art10011900 "Changes at the BAA" (pdf)]. Vector journal volume 23 issue 4. 2008-09.</ref><br />
<br />
== Activities ==<br />
<br />
=== Symposium ===<br />
<br />
From 2008 and until the onset of the [[wikipedia:COVID-19 pandemic|COVID-19 pandemic]], the BAA London group arranged a monthly open-for-all meet-up, called ''the symposium'', at the The Hoop and Grapes pub on Farringdon Street in London. No sign-up was required.<br />
<br />
=== Vector journal ===<br />
<br />
Vector, the journal of the BAA, began publication in 1984, and gradually took the place of [[APL Quote Quad]] as the de-facto leading publishing channel for APL content. The journal featured submitted articles on array programming including [[J]] and [[K]], as well as news from APL and other array language vendors. Beginning in 2005, with volume 21 issue 4, the journal was issued online as well as in print, and some prior articles have also been made available online.<ref>Stephen Taylor. [http://archive.vector.org.uk/art10009870 "Editorial: Discover, Learn, Profit"]. Vector journal volume 21 issue 4. 2005-09.</ref> It was published quarterly until 2004, when late and sometimes skipped issues began to interrupt its formerly regular schedule. Releases slowed more significantly after 2008, and in 2016, following the completion of volume 26, the journal moved entirely to online publishing. So far a single issue has been published this way, in 2019.<br />
<br />
=== BAPLA 09 ===<br />
<br />
The British APL Association held a 2-day conference, '''BAPLA 09''', on June 8th & 9th 2009 at DeVere Hotel, Wokefield Park, near Reading, UK<br />
<br />
=== Webinar ===<br />
In response to the restrictions imposed by the COVID-19 pandemic, BAA is arranging a series of [[Wikipedia:webcast|webcast]]s to replace their regular monthly symposium.<ref>BAA. [https://britishaplassociation.org/webinar-schedule-2020/ Webinar Schedule for 2020].</ref><br />
<br />
The Webinars, are held using [[Wikipedia:Zoom (software)|Zoom]], and consist of half an hour of social interaction, followed by a single presentation of about an hour, and a Q&A session. The sessions are recorded with subsequent publication on YouTube. Some webinars are so called ''open sessions'' which are more similar to the monthly symposium, in being informal meetings where APLers discuss and present whatever they feel like, with no particular subject decided on beforehand.<br />
<br />
{| class=wikitable<br />
! No. !! Date !! Presenter(s) !! Title<br />
|-<br />
| 1 || Apr 9th 2020 || [[Richard Park]], [[Dyalog Ltd.|Dyalog]] || [https://www.youtube.com/watch?v=dbB4uxbG1ec Molecular Dynamics-in-APL]<br />
|-<br />
| 2 || Apr 23rd 2020 || MJH Software Services || [https://www.youtube.com/watch?v=8Wvrn8vtazA Introducing qWC Alpha 0.4]<br />
|-<br />
| 3 || May 7th 2020 || [[Adám Brudzewsky]], [[Dyalog Ltd.|Dyalog]] || [https://www.youtube.com/watch?v=6qygPslrXnM Meet the new APL Wiki]<br />
|-<br />
| 4 || May 21st 2020 || [[Phil Last]] || Acre source-code manager update<br />
|-<br />
| 5 || Jun 4th 2020 || Paul Grosvenor || British APL Association AGM<br />
|-<br />
| 6 || Jun 18th 2020 || [[Bob Armstrong]] || CoSy : The Shortest Path from the Chip to the Math<br />
|-<br />
| 7 || Jul 2nd 2020 || [[Adám Brudzewsky]] || aplcart.info turns 1<br />
|-<br />
| colspan=4 align=center | summer break<br />
|-<br />
| rowspan=2 | 8 || rowspan=2 | Aug 13th 2020 || John Jacob || BAA websites: New features<br />
|- <br />
| Ellis Morgan || An APL recreation<br />
|-<br />
| 9 || Aug 27th 2020 || colspan=2 | Open Session<br />
|-<br />
| 10 || Sep 10th 2020 || colspan=2 | Open session<br />
|-<br />
| 11 || Sep 24th 2020 || Ray Cannon || | Using SVG from Dyalog APL for animated visualisation<br />
|-<br />
| 12 || Oct 8th 2020 || Ray Polivka || | Seats in the House of Representatives<br />
|-<br />
| 13 || Oct 22nd 2020 || colspan=2 | Open Session<br />
|-<br />
| 14 || Nov 5th 2020 || colspan=2 | Open session<br />
|}<br />
<br />
== Organisation ==<br />
<br />
The BAA is administered by a committee of officers elected by ballot of Association members at the Annual General Meeting. Working groups are also established in areas such as activity planning and journal production. Offers of assistance and involvement with any Association matters are always welcomed.<br />
<br />
Funding for the BAA comes entirely from the sustaining members. In many cases, these sustaining members also provide manpower and administrative assistance to the association at their own cost.<br />
<br />
The current chairman is Paul Grosvenor.<br />
<br />
== External links ==<br />
<br />
* [https://britishaplassociation.org/ BAA Website]<br />
<br />
* [https://groups.google.com/forum/#!forum/baa-london BAA London Google Group] announces upcoming symposiums and other events.<br />
<br />
* [https://vector.org.uk/ ''Vector'', The BAA's Journal] has a significant [http://archive.vector.org.uk/ archive] relevant for learning and understanding APL and related languages today<br />
<br />
* [http://archive.vector.org.uk/ The ''Vector'' archives]<br />
<br />
==References==<br />
<references/><br />
{{APL community}}<br />
[[Category:User groups]]</div>RLevinehttps://aplwiki.com/index.php?title=BAA&diff=5853BAA2020-11-21T04:09:41Z<p>RLevine: /* External links */ Added link to Vector archive</p>
<hr />
<div>The '''British APL Association''' ('''BAA'''; infrequently '''BAPLA''') is a [[user group]] founded in 1984 in England to promote APL, and the publisher of Vector journal. It is funded by its sustaining members, which include corporate users and the APL [[vendors]] [[APL2000]], [[Dyalog Ltd.]], [[Kx Systems]], and MicroAPL.<br />
<br />
The BAA was a Specialist Group of the [[wikipedia:British Computer Society|British Computer Society]] from its early years (possibly beginning after [[APL86]]<ref>Anthony Camacho. [http://archive.vector.org.uk/art10500330 "BAA Annual General Meeting 2010"]. Vector journal volume 24 issue 4. 2010-12.</ref>) until it left in response to increasing requirements made by the BCS in 2008.<ref>Paul Grosvenor. [http://archive.vector.org.uk/art10011900 "Changes at the BAA" (pdf)]. Vector journal volume 23 issue 4. 2008-09.</ref><br />
<br />
== Activities ==<br />
<br />
=== Symposium ===<br />
<br />
From 2008 and until the onset of the [[wikipedia:COVID-19 pandemic|COVID-19 pandemic]], the BAA London group arranged a monthly open-for-all meet-up, called ''the symposium'', at the The Hoop and Grapes pub on Farringdon Street in London. No sign-up was required.<br />
<br />
=== Vector journal ===<br />
<br />
Vector, the journal of the BAA, began publication in 1984, and gradually took the place of [[APL Quote Quad]] as the de-facto leading publishing channel for APL content. The journal featured submitted articles on array programming including [[J]] and [[K]], as well as news from APL and other array language vendors. Beginning in 2005, with volume 21 issue 4, the journal was issued online as well as in print, and some prior articles have also been made available online.<ref>Stephen Taylor. [http://archive.vector.org.uk/art10009870 "Editorial: Discover, Learn, Profit"]. Vector journal volume 21 issue 4. 2005-09.</ref> It was published quarterly until 2004, when late and sometimes skipped issues began to interrupt its formerly regular schedule. Releases slowed more significantly after 2008, and in 2016, following the completion of volume 26, the journal moved entirely to online publishing. So far a single issue has been published this way, in 2019.<br />
<br />
=== BAPLA 09 ===<br />
<br />
The British APL Association held a 2-day conference, '''BAPLA 09''', on June 8th & 9th 2009 at DeVere Hotel, Wokefield Park, near Reading, UK<br />
<br />
=== Webinar ===<br />
In response to the restrictions imposed by the COVID-19 pandemic, BAA is arranging a series of [[Wikipedia:webcast|webcast]]s to replace their regular monthly symposium.<ref>BAA. [https://britishaplassociation.org/webinar-schedule-2020/ Webinar Schedule for 2020].</ref><br />
<br />
The Webinars, are held using [[Wikipedia:Zoom (software)|Zoom]], and consist of half an hour of social interaction, followed by a single presentation of about an hour, and a Q&A session. The sessions are recorded with subsequent publication on YouTube. Some webinars are so called ''open sessions'' which are more similar to the monthly symposium, in being informal meetings where APLers discuss and present whatever they feel like, with no particular subject decided on beforehand.<br />
<br />
{| class=wikitable<br />
! No. !! Date !! Presenter(s) !! Title<br />
|-<br />
| 1 || Apr 9th 2020 || [[Richard Park]], [[Dyalog Ltd.|Dyalog]] || [https://www.youtube.com/watch?v=dbB4uxbG1ec Molecular Dynamics-in-APL]<br />
|-<br />
| 2 || Apr 23rd 2020 || MJH Software Services || [https://www.youtube.com/watch?v=8Wvrn8vtazA Introducing qWC Alpha 0.4]<br />
|-<br />
| 3 || May 7th 2020 || [[Adám Brudzewsky]], [[Dyalog Ltd.|Dyalog]] || [https://www.youtube.com/watch?v=6qygPslrXnM Meet the new APL Wiki]<br />
|-<br />
| 4 || May 21st 2020 || [[Phil Last]] || Acre source-code manager update<br />
|-<br />
| 5 || Jun 4th 2020 || Paul Grosvenor || British APL Association AGM<br />
|-<br />
| 6 || Jun 18th 2020 || [[Bob Armstrong]] || CoSy : The Shortest Path from the Chip to the Math<br />
|-<br />
| 7 || Jul 2nd 2020 || [[Adám Brudzewsky]] || aplcart.info turns 1<br />
|-<br />
| colspan=4 align=center | summer break<br />
|-<br />
| rowspan=2 | 8 || rowspan=2 | Aug 13th 2020 || John Jacob || BAA websites: New features<br />
|- <br />
| Ellis Morgan || An APL recreation<br />
|-<br />
| 9 || Aug 27th 2020 || colspan=2 | Open Session<br />
|-<br />
| 10 || Sep 10th 2020 || colspan=2 | Open session<br />
|-<br />
| 11 || Sep 24th 2020 || Ray Cannon || | Using SVG from Dyalog APL for animated visualisation<br />
|-<br />
| 12 || Oct 8th 2020 || Ray Polivka || | Seats in the House of Representatives<br />
|-<br />
| 13 || Oct 22nd 2020 || colspan=2 | Open Session<br />
|-<br />
| 14 || Nov 5th 2020 || colspan=2 | Open session<br />
|}<br />
<br />
== Organisation ==<br />
<br />
The BAA is administered by a committee of officers elected by ballot of Association members at the Annual General Meeting. Working groups are also established in areas such as activity planning and journal production. Offers of assistance and involvement with any Association matters are always welcomed.<br />
<br />
Funding for the BAA comes entirely from the sustaining members. In many cases, these sustaining members also provide manpower and administrative assistance to the association at their own cost.<br />
<br />
The current chairman is Paul Grosvenor.<br />
<br />
== External links ==<br />
<br />
* [https://britishaplassociation.org/ BAA Website]<br />
<br />
* [https://groups.google.com/forum/#!forum/baa-london BAA London Google Group] announces upcoming symposiums and other events.<br />
<br />
* [https://vector.org.uk/ ''Vector'', The BAA's Journal] has a significant [http://archive.vector.org.uk/ archive]<br />
<br />
* [http://archive.vector.org.uk/ The ''Vector'' archives]<br />
<br />
==References==<br />
<references/><br />
{{APL community}}<br />
[[Category:User groups]]</div>RLevinehttps://aplwiki.com/index.php?title=BAA&diff=5852BAA2020-11-21T04:06:38Z<p>RLevine: /* Vector journal */</p>
<hr />
<div>The '''British APL Association''' ('''BAA'''; infrequently '''BAPLA''') is a [[user group]] founded in 1984 in England to promote APL, and the publisher of Vector journal. It is funded by its sustaining members, which include corporate users and the APL [[vendors]] [[APL2000]], [[Dyalog Ltd.]], [[Kx Systems]], and MicroAPL.<br />
<br />
The BAA was a Specialist Group of the [[wikipedia:British Computer Society|British Computer Society]] from its early years (possibly beginning after [[APL86]]<ref>Anthony Camacho. [http://archive.vector.org.uk/art10500330 "BAA Annual General Meeting 2010"]. Vector journal volume 24 issue 4. 2010-12.</ref>) until it left in response to increasing requirements made by the BCS in 2008.<ref>Paul Grosvenor. [http://archive.vector.org.uk/art10011900 "Changes at the BAA" (pdf)]. Vector journal volume 23 issue 4. 2008-09.</ref><br />
<br />
== Activities ==<br />
<br />
=== Symposium ===<br />
<br />
From 2008 and until the onset of the [[wikipedia:COVID-19 pandemic|COVID-19 pandemic]], the BAA London group arranged a monthly open-for-all meet-up, called ''the symposium'', at the The Hoop and Grapes pub on Farringdon Street in London. No sign-up was required.<br />
<br />
=== Vector journal ===<br />
<br />
Vector, the journal of the BAA, began publication in 1984, and gradually took the place of [[APL Quote Quad]] as the de-facto leading publishing channel for APL content. The journal featured submitted articles on array programming including [[J]] and [[K]], as well as news from APL and other array language vendors. Beginning in 2005, with volume 21 issue 4, the journal was issued online as well as in print, and some prior articles have also been made available online.<ref>Stephen Taylor. [http://archive.vector.org.uk/art10009870 "Editorial: Discover, Learn, Profit"]. Vector journal volume 21 issue 4. 2005-09.</ref> It was published quarterly until 2004, when late and sometimes skipped issues began to interrupt its formerly regular schedule. Releases slowed more significantly after 2008, and in 2016, following the completion of volume 26, the journal moved entirely to online publishing. So far a single issue has been published this way, in 2019.<br />
<br />
=== BAPLA 09 ===<br />
<br />
The British APL Association held a 2-day conference, '''BAPLA 09''', on June 8th & 9th 2009 at DeVere Hotel, Wokefield Park, near Reading, UK<br />
<br />
=== Webinar ===<br />
In response to the restrictions imposed by the COVID-19 pandemic, BAA is arranging a series of [[Wikipedia:webcast|webcast]]s to replace their regular monthly symposium.<ref>BAA. [https://britishaplassociation.org/webinar-schedule-2020/ Webinar Schedule for 2020].</ref><br />
<br />
The Webinars, are held using [[Wikipedia:Zoom (software)|Zoom]], and consist of half an hour of social interaction, followed by a single presentation of about an hour, and a Q&A session. The sessions are recorded with subsequent publication on YouTube. Some webinars are so called ''open sessions'' which are more similar to the monthly symposium, in being informal meetings where APLers discuss and present whatever they feel like, with no particular subject decided on beforehand.<br />
<br />
{| class=wikitable<br />
! No. !! Date !! Presenter(s) !! Title<br />
|-<br />
| 1 || Apr 9th 2020 || [[Richard Park]], [[Dyalog Ltd.|Dyalog]] || [https://www.youtube.com/watch?v=dbB4uxbG1ec Molecular Dynamics-in-APL]<br />
|-<br />
| 2 || Apr 23rd 2020 || MJH Software Services || [https://www.youtube.com/watch?v=8Wvrn8vtazA Introducing qWC Alpha 0.4]<br />
|-<br />
| 3 || May 7th 2020 || [[Adám Brudzewsky]], [[Dyalog Ltd.|Dyalog]] || [https://www.youtube.com/watch?v=6qygPslrXnM Meet the new APL Wiki]<br />
|-<br />
| 4 || May 21st 2020 || [[Phil Last]] || Acre source-code manager update<br />
|-<br />
| 5 || Jun 4th 2020 || Paul Grosvenor || British APL Association AGM<br />
|-<br />
| 6 || Jun 18th 2020 || [[Bob Armstrong]] || CoSy : The Shortest Path from the Chip to the Math<br />
|-<br />
| 7 || Jul 2nd 2020 || [[Adám Brudzewsky]] || aplcart.info turns 1<br />
|-<br />
| colspan=4 align=center | summer break<br />
|-<br />
| rowspan=2 | 8 || rowspan=2 | Aug 13th 2020 || John Jacob || BAA websites: New features<br />
|- <br />
| Ellis Morgan || An APL recreation<br />
|-<br />
| 9 || Aug 27th 2020 || colspan=2 | Open Session<br />
|-<br />
| 10 || Sep 10th 2020 || colspan=2 | Open session<br />
|-<br />
| 11 || Sep 24th 2020 || Ray Cannon || | Using SVG from Dyalog APL for animated visualisation<br />
|-<br />
| 12 || Oct 8th 2020 || Ray Polivka || | Seats in the House of Representatives<br />
|-<br />
| 13 || Oct 22nd 2020 || colspan=2 | Open Session<br />
|-<br />
| 14 || Nov 5th 2020 || colspan=2 | Open session<br />
|}<br />
<br />
== Organisation ==<br />
<br />
The BAA is administered by a committee of officers elected by ballot of Association members at the Annual General Meeting. Working groups are also established in areas such as activity planning and journal production. Offers of assistance and involvement with any Association matters are always welcomed.<br />
<br />
Funding for the BAA comes entirely from the sustaining members. In many cases, these sustaining members also provide manpower and administrative assistance to the association at their own cost.<br />
<br />
The current chairman is Paul Grosvenor.<br />
<br />
== External links ==<br />
<br />
* [https://britishaplassociation.org/ BAA Website]<br />
<br />
* [https://groups.google.com/forum/#!forum/baa-london BAA London Google Group] announces upcoming symposiums and other events.<br />
<br />
* [https://vector.org.uk/ ''Vector'', The BAA's Journal]<br />
<br />
* [http://archive.vector.org.uk/ The ''Vector'' archives]<br />
==References==<br />
<references/><br />
{{APL community}}<br />
[[Category:User groups]]</div>RLevinehttps://aplwiki.com/index.php?title=Ngn/apl&diff=5851Ngn/apl2020-11-21T03:42:54Z<p>RLevine: /* External link */ Correct internal wiki link</p>
<hr />
<div>{{DISPLAYTITLE:ngn/apl}}{{Infobox array language<br />
| title = ngn/apl<br />
| array model = [[nested array model|nested]]<br />
| index origin = 0<br />
| function styles = [[dfn]], [[tacit]]<br />
| numeric types = [[complex]] floats<br />
| unicode support = full<br />
| released = 2011<br />
| developer = Nick Nickolov<br />
| latest release version = 2018 (unversioned)<br />
| implementation language = [[wikipedia:Javascript|Javascript]]<br />
| source = [https://gitlab.com/n9n/apl/blob/master/apl.js GitLab]<br />
| platforms = In-browser, [[wikipedia:Node.js|Node.js]]<br />
| license = [[wikipedia:MIT_License|MIT]]<br />
| website = [https://gitlab.com/n9n/apl gitlab.com/n9n/apl]<br />
| influenced by = [[Dyalog APL]]<br />
| run online = [https://repl.it/languages/APL REPL]<br />
}}<br />
'''ngn/apl''' is an APL bytecode compiler and interpreter by [[Nick Nickolov]]. Because it is implemented in [[wikipedia:Javascript|Javascript]], it can be run in [[wikipedia:Node.js|Node.js]] or any modern browser.<br />
<br />
ngn/apl supports most primitives, [[dfn]]s (<source lang=apl inline>{⍺ ⍵}</source>), [[nested array]]s, [[complex number]]s (<source lang=apl inline>1j2</source>), [[Infinity|infinities]] (<source lang=apl inline>¯</source> or <source lang=apl inline>∞</source>), [[Function train|forks and atops]], [[Multiple assignment|strand assignment]] (<source lang=apl inline>(a b)←c</source>), [[indexed assignment]] (<source lang=apl inline>a[b]←c</source>), [[dop|user-defined operators]] (<source lang=apl inline>{⍺⍺ ⍵⍵}</source>), but does not support [[tradfn]]s (<source lang=apl inline>∇R←X f Y</source>), non-zero [[index origin]] (<source lang=apl inline>⎕IO</source>), [[comparison tolerance]] (<source lang=apl inline>⎕CT</source>), [[prototype]]s, [[modified assignment]] (<source lang=apl inline>x+←1</source>), [[keyword]]s (<source lang=apl inline>:If</source>), [[object-oriented programming]], [[namespace]]s.<br />
[[File:Ngn/apl|center|thumb|ngn/apl's [https://n9n.gitlab.io/apl/web demo interface]]]<br />
== External link ==<br />
* [http://archive.vector.org.uk/art10501160 ''Compiling APL to JavaScript''] article in the [[Vector journal]]<br />
* [https://repl.it/languages/APL ngn/apl on REPL]<br />
* [https://tio.run/#apl-ngn ngn/APL on Try It Online]<br />
* [https://n9n.gitlab.io/apl/web Online demo]<br />
* [https://plj541.github.io/APL.js/ Online session]<br />
* [https://gitlab.com/n9n/apl Source code]<br />
<br />
{{APL dialects}}[[Category:APL dialects]][[Category:Nested array languages]][[Category:Leading axis languages]][[Category:Languages with tacit programming]][[Category:Compilers]]</div>RLevine