Differences between revisions 22 and 27 (spanning 5 versions)

APL Application Programming Library (APLAPL)

Note that this is a pure Dyalog project. Note also that by definition only scripts (either class- or namespace-scripts) can be part of APLAPL.

Scripts in this category must contain a Copyright notice according to the MIT license conditions.

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

To become part of the APLAPL project, one must ensure that proper test cases are written and executed before the class is published. Although that does not guarantee that the scripts are free of bugs, this certainly decreases the danger of bugs.

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.

Name	Description	Type	Originator	Needs .NET
APLTeamUtils	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

CategoryOpenSourceApl

-  ⇤ ← Revision 22 as of 2008-10-03 06:27:59 → 
  Size: 2110
  Editor: KaiJaeger
  Comment:
+   ← Revision 27 as of 2008-12-15 18:28:13 → ⇥
  Size: 1824
  Editor: KaiJaeger
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 2:
-= APL Application Programming Library (APL) =
+= APL Application Programming Library (APLAPL) =
 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.
+Note that this is a pure Dyalog project. Note also that by definition only scripts (either class- or namespace-scripts) can be part of APLAPL.
 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.
+Scripts in this category '''must''' contain a Copyright notice according to the [[http://en.wikipedia.org/wiki/Mit_license|MIT license]] conditions.
 Line 8:
-The idea behind TOSAP is to provide classes ready for usage for every-day-problems programmers typically come across.
+The basic idea behind APLAPL is to provide classes for every-day-problems programmers typically come across.
 Line 10:
-Note that there is a significant difference between downloading a script from the wiki and checking out the associated project from !SubVersion:

 * 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.
+To become part of the APLAPL project, one must ensure that proper test cases are written and executed before the class is published. Although that does not guarantee that the scripts are free of bugs, this certainly decreases the danger of bugs.
-Line 20:
+Line 17:
-||[[APLTeamsUtil]]||General utilities||Dyalog||APL Team||'''No'''||
+||[[APLTeamUtils]]||General utilities||Dyalog||APL Team||'''No'''||
-Line 30:
+Line 27:
-CategoryAplApl CategoryOpenSourceApl
+CategoryOpenSourceApl