Differences between revisions 11 and 25 (spanning 14 versions)

APL Application Programming Library (APLAPL)

Note that this is a pure Dyalog project. Note also that by definition only classes can be part of APLAPL.

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 testcases are written and executed before the class is published.

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

CategoryAplApl CategoryOpenSourceApl

-  ⇤ ← Revision 11 as of 2007-10-09 06:50:21 → 
  Size: 807
  Editor: KaiJaeger
  Comment:
+   ← Revision 25 as of 2008-12-15 17:57:45 → ⇥
  Size: 1537
  Editor: KaiJaeger
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 4:
-Points to System Libraries and Addons. These are expected to be vendor specific.
+Note that this is a pure Dyalog project. Note also that by definition only classes can be part of APLAPL.

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 testcases are written and executed before the class is published. 

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.
-Line 7:
+Line 13:
-##||||||<tablestyle="background:#ffe; padding:0 2em 1em 0;">''''''||
||'''Name'''||'''Description'''||'''Type'''||'''Originator'''||'''Part of [:CategoryOpenSourceApl:TOSAP]'''||
||[:APLTeamsUtil:APLTeamsUtil]||Needed by classes (but ADOC) originated by APL Team||Dyalog Class||APL Team||Yes||
||[:ADOC:ADOC]||Automated Documentation Generation||Dyalog Class||APL Team||Yes||
||IniFiles||Dealing with INI files||Dyalog Class||APL Team||Yes||
||[:Logger:Logger]||Writing Log Files||Dyalog Class||APL Team||Yes||
||[:Hash:Hash]||Creating and managing hashes (key/value-pairs)||Dyalog Class||APL Team||Yes||
+##||||||<tablestyle="background:#ffe; padding:0 2em 1em 0;">''''''||''''''||
||'''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'''||
-Line 16:
+Line 25:
-CategoryAplApl
+CategoryAplApl CategoryOpenSourceApl