Differences between revisions 22 and 47 (spanning 25 versions)
Revision 22 as of 2008-10-03 06:27:59
Size: 2110
Editor: KaiJaeger
Comment:
Revision 47 as of 2009-01-09 15:25:13
Size: 1709
Editor: KaiJaeger
Comment: Not vendor specific anymore, but needs classes
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
= APL Application Programming Library (APL) = = APL Application Programming Library (APLAPL) =
Line 4: Line 4:
At the time being, everything here refers to Dyalog APL. That might change sometime, but as long as no other stuff turns up here it keeps things simple. The basic idea behind APLAPL is to provide classes for every-day-problems programmers typically come across.
Line 6: Line 6:
All classes published here '''must''' be part of '''"The Open Source APL Project"''' in short '''[[OpenSourceAplProject|TOSAP]]'''. Yes, classes, so it has to be at least version 11 of Dyalog APL you are working with. Sub-projects of APLAPL '''must''' follow certain [[AplAplStandards | standards]]
Line 8: Line 8:
The idea behind TOSAP is to provide classes ready for usage for every-day-problems programmers typically come across. The columns "Win" and "Linux" are checked if the software is designed for running under this operating system '''and''' comes with test cases for that environment.
Line 10: Line 10:
Note that there is a significant difference between downloading a script from the wiki and checking out the associated project from !SubVersion: By defenition all APLAPL projects must be classes, ot at least scripts. For the time being (2009-01) this restricts the APLAPL projects to Dyalog and APLX.
Line 12: Line 12:
 * The wiki download contains the script and maybe something else you need to run the script.
 * The subproject comes with more stuff, especially with a development workspace which '''must''' contain a test suite. Only fully tested scripts should offered to the public for download.
<<BR>><<BR>>
Line 15: Line 14:
Many but not all classes do not use .NET at all. That might look strange: there are tons of useful .NET classes available, and they are free, so why not using them? Well, it all depends. Try to get a directory listing of a directory which contains 100,000 files and you know what I mean.


##||||||<tablestyle="background:#ffe; padding:0 2em 1em 0;">''''''||''''''||
||'''Name'''||'''Description'''||'''Type'''||'''Originator'''||'''Needs .NET'''||
||[[APLTeamsUtil]]||General utilities||Dyalog||APL Team||'''No'''||
||[[ADOC]]||Automated Documentation Generation||Dyalog||APL Team||'''No'''||
||[[Hash]]||Managing key/value-pairs||Dyalog ||APL Team||'''No'''||
||IniFiles||Dealing with INI files||Dyalog||APL Team||'''No'''||
||[[Logger]]||Writing Log Files||Dyalog||APL Team||'''No'''||
||[[WindowsEventLog]]||Dealing with the Windows Event Log||Dyalog||APL Team||'''Yes'''||
||[[WinFile]]||Dealing with files and directories||Dyalog||APL Team||'''No'''||
||[[WinReg]]||Dealing with the Windows Registry||Dyalog||APL Team||'''No'''||
||<rowclass="odd" tablestyle="background:#ffe;font-size:small"> '''Name''' || '''Description''' || '''Originator''' || '''Dialect''' || '''Win''' || '''Linux''' || '''.NET<<BR>>required''' ||
||[[APLTeamUtils]]||General utilities||APL Team||Dyalog|| (./) || {X} || {X} ||
||<rowclass="odd">[[ADOC]]||Automated Documentation Generation||APL Team||Dyalog|| (./) || {X} || {X} ||
||[[Hash]]||Managing key/value-pairs||APL Team||Dyalog|| (./) || {X} || {X} ||
||<rowclass="odd">IniFiles||Dealing with INI files||APL Team||Dyalog|| (./) || {X} || {X} ||
|| [[Logger]] ||Writing Log Files||APL Team||Dyalog|| (./) || {X} || {X} ||
||<rowclass="odd">ShowChmHelp||Display help files and topics within help files||APL Team||Dyalog|| (./) || {X} || {X} ||
||[[WindowsEventLog]]||Dealing with the Windows Event Log||APL Team||Dyalog|| (./) || {X} || (./) ||
||<rowclass="odd">[[WinFile]]||Dealing with files and directories||APL Team||Dyalog|| (./) || {X} || {X} ||
||[[WinReg]]||Dealing with the Windows Registry||APL Team||Dyalog|| (./) || {X} || {X} ||
Line 30: Line 26:
CategoryAplApl CategoryOpenSourceApl CategoryOpenSourceApl

APL Application Programming Library (APLAPL)

The basic idea behind APLAPL is to provide classes for every-day-problems programmers typically come across.

Sub-projects of APLAPL must follow certain standards

The columns "Win" and "Linux" are checked if the software is designed for running under this operating system and comes with test cases for that environment.

By defenition all APLAPL projects must be classes, ot at least scripts. For the time being (2009-01) this restricts the APLAPL projects to Dyalog and APLX.



Name

Description

Originator

Dialect

Win

Linux

.NET
required

APLTeamUtils

General utilities

APL Team

Dyalog

(./)

{X}

{X}

ADOC

Automated Documentation Generation

APL Team

Dyalog

(./)

{X}

{X}

Hash

Managing key/value-pairs

APL Team

Dyalog

(./)

{X}

{X}

IniFiles

Dealing with INI files

APL Team

Dyalog

(./)

{X}

{X}

Logger

Writing Log Files

APL Team

Dyalog

(./)

{X}

{X}

ShowChmHelp

Display help files and topics within help files

APL Team

Dyalog

(./)

{X}

{X}

WindowsEventLog

Dealing with the Windows Event Log

APL Team

Dyalog

(./)

{X}

(./)

WinFile

Dealing with files and directories

APL Team

Dyalog

(./)

{X}

{X}

WinReg

Dealing with the Windows Registry

APL Team

Dyalog

(./)

{X}

{X}


CategoryOpenSourceApl

CategoryAplTree (last edited 2018-03-04 12:46:55 by KaiJaeger)