Differences between revisions 2 and 15 (spanning 13 versions)

APL Application Programming Library (APLAPL)

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.

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.

The idea behind TOSAP is to provide classes ready for usage for every-day-problems programmers typically come across.

Many (so far 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	Part of [:OpenSourceAplProject:TOSAP]
[:APLTeamsUtil:APLTeamsUtil]	Needed by all classes but ADOC, originated by APL Team	Dyalog Class	APL Team	Yes
[:ADOC:ADOC]	Automated Documentation Generation	Dyalog Class	APL Team	Yes
[:Hash:Hash]	Managing key/value-pairs	Dyalog Class	APL Team	Yes
IniFiles	Dealing with INI files without .NET	Dyalog Class	APL Team	Yes
[:Logger:Logger]	Writing Log Files	Dyalog Class	APL Team	Yes
[:WinFile:WinFile]	Dealing with files and directories without .NET	Dyalog Class	APL Team	Yes
[:WinReg:WinReg]	Dealing with the Windows Registry without .NET	Dyalog Class	APL Team	Yes

CategoryAplApl CategoryOpenSourceApl:

-  ⇤ ← Revision 2 as of 2007-06-24 12:45:55 → 
  Size: 203
  Editor: KaiJaeger
  Comment:
+   ← Revision 15 as of 2008-07-26 20:35:16 → ⇥
  Size: 1729
  Editor: KaiJaeger
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
+## page was renamed from APLAPL
-Line 3:
+Line 4:
-Points to System Libraries and Addons. These are expected to be vendor specific.
+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.

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.

The idea behind TOSAP is to provide classes ready for usage for every-day-problems programmers typically come across.

Many (so far 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.
-Line 6:
+Line 13:
-[:CategoryAplAplDyalog:Dyalog APLAPL]
+##||||||<tablestyle="background:#ffe; padding:0 2em 1em 0;">''''''||
||'''Name'''||'''Description'''||'''Type'''||'''Originator'''||'''Part of [:OpenSourceAplProject:TOSAP]'''||
||[:APLTeamsUtil:APLTeamsUtil]||Needed by all classes but ADOC, originated by APL Team||Dyalog Class||APL Team||Yes||
||[:ADOC:ADOC]||Automated Documentation Generation||Dyalog Class||APL Team||Yes||
||[:Hash:Hash]||Managing key/value-pairs||Dyalog Class||APL Team||Yes||
||IniFiles||Dealing with INI files without .NET||Dyalog Class||APL Team||Yes||
||[:Logger:Logger]||Writing Log Files||Dyalog Class||APL Team||Yes||
||[:WinFile:WinFile]||Dealing with files and directories without .NET||Dyalog Class||APL Team||Yes||
||[:WinReg:WinReg]||Dealing with the Windows Registry without .NET||Dyalog Class||APL Team||Yes||
-Line 9:
+Line 24:
-CategoryCategory
+CategoryAplApl CategoryOpenSourceApl: