Differences between revisions 26 and 64 (spanning 38 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	Windows	Linux	Description
APLTeamUtils		$/!\$	General utilities
APL2XML			Create XML files in order to compile them with HelpAndManual
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

Legend:

$/!\$ contributor needed

fully implemented

under construction

not applicable

CategoryCategory

-  ⇤ ← Revision 26 as of 2008-12-15 18:06:35 → 
  Size: 1522
  Editor: KaiJaeger
  Comment:
+   ← Revision 64 as of 2010-09-04 16:47:44 → ⇥
  Size: 1434
  Editor: KaiJaeger
  Comment: APL2XML added
-Deletions are marked like this.
+Additions are marked like this.
 Line 3:
+ * APLAPL is a pure Dyalog project.
-Line 4:
+Line 5:
-Note that this is a pure Dyalog project. Note also that by definition only classes 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 7:
-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 - see AplAplStandards for details.
-Line 8:
+Line 9:
-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.
+||<rowclass="odd">'''Name''' ||'''Windows''' ||'''Linux''' ||'''Description''' ||
||<rowclass="even">[[APLTeamUtils]] || (./) || /!\ ||General utilities ||
||<rowclass="odd">[[Apl2Xml|APL2XML]] || (./) || {X} ||Create XML files in order to compile them with !HelpAndManual||
||<rowclass="even">[[ADOC]] || (./) || /!\ ||Automated Documentation Generation ||
||<rowclass="odd">[[Hash]] || (./) || /!\ ||Managing key/value-pairs ||
||<rowclass="even">IniFiles || (./) || /!\ ||Dealing with INI files ||
||<rowclass="odd">[[Logger]] || (./) || /!\ ||Writing Log Files ||
||<rowclass="even">ShowChmHelp || (./) || {X} ||Display help files and topics within help files ||
||<rowclass="odd">WindowsEventLog || (./) || {X} ||Dealing with the Windows Event Log ||
||<rowclass="even">WinFile || (./) || /!\ ||Dealing with files and directories ||
||<rowclass="odd">WinReg || (./) || {X} ||Dealing with the Windows Registry ||
-Line 13:
+Line 22:
-##||||||<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'''||
+<<BR>> Legend:

/!\  contributor needed

(./) fully implemented

{*} under construction

{X} not applicable
-Line 25:
+Line 33:
-CategoryOpenSourceApl
+CategoryCategory