Differences between revisions 27 and 49 (spanning 22 versions)

APL Application Programming Library (APLAPL)

APLAPL is a pure Dyalog project.
APLAPL is supposed to offer scripts (class scripts and namespace scrips) for every-day-problems programmers typically come across.
Sub-projects of APLAPL must follow certain standards - see AplAplStandards for details.

Name	Dyalog	APLX	Description
APLTeamUtils		-	General utilities
ADOC		-	Automated Documentation Generation
Hash		-	Managing key/value-pairs
IniFiles		-	Dealing with INI files
Logger		-	Writing Log Files
ShowChmHelp		-	Display help files and topics within help files
WindowsEventLog		-	Dealing with the Windows Event Log
WinFile		-	Dealing with files and directories
WinReg		-	Dealing with the Windows Registry

CategoryOpenSourceApl

-  ⇤ ← Revision 27 as of 2008-12-15 18:28:13 → 
  Size: 1824
  Editor: KaiJaeger
  Comment:
+   ← Revision 49 as of 2009-01-13 14:48:22 → ⇥
  Size: 1195
  Editor: KaiJaeger
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 3:
+<<BR>><<BR>>
 * APLAPL is a pure Dyalog project.
-Line 4:
+Line 6:
-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.
+ * APLAPL is supposed to offer scripts (class scripts and namespace scrips) for every-day-problems programmers typically come across.
-Line 6:
+Line 8:
-Scripts in this category '''must''' contain a Copyright notice according to the [[http://en.wikipedia.org/wiki/Mit_license|MIT license]] conditions.
+ * Sub-projects of APLAPL '''must''' follow certain standards - see AplAplStandards for details.
-Line 8:
+Line 10:
-The basic idea behind APLAPL is to provide classes for every-day-problems programmers typically come across.
+<<BR>>
-Line 10:
+Line 12:
-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.


##||||||<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'''||
+||<rowclass="odd" tablestyle="background:#ffe;font-size:small">'''Name'''||'''Dyalog'''||'''APLX'''||'''Description''' ||
||[[APLTeamUtils]]     || (./) || - ||General utilities||
||<rowclass="odd">[[ADOC]]|| (./) || - ||Automated Documentation Generation||
||[[Hash]]     || (./) || - ||Managing key/value-pairs||
||<rowclass="odd">IniFiles     || (./) || - ||Dealing with INI files||
|| [[Logger]]     || (./) || -  ||Writing Log Files||
||<rowclass="odd">ShowChmHelp     || (./) || - ||Display help files and topics within help files||
||[[WindowsEventLog]]     || (./) || - ||Dealing with the Windows Event Log||
||<rowclass="odd">[[WinFile]]     || (./) || - ||Dealing with files and directories||
||[[WinReg]]     || (./) || - ||Dealing with the Windows Registry||