Differences between revisions 25 and 61 (spanning 36 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
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 25 as of 2008-12-15 17:57:45 → 
  Size: 1537
  Editor: KaiJaeger
  Comment:
+   ← Revision 61 as of 2009-08-02 18:59:06 → ⇥
  Size: 1381
  Editor: KaiJaeger
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 4:
-Note that this is a pure Dyalog project. Note also that by definition only classes can be part of APLAPL.
+ * APLAPL is a pure Dyalog project.
 Line 6:
-The basic idea behind APLAPL is to provide classes for every-day-problems programmers typically come across.
+ * APLAPL is supposed to offer scripts (class scripts and namespace scrips) for every-day-problems programmers typically come across.
 Line 8:
-To become part of the APLAPL project, one must ensure that proper testcases are written and executed before the class is published.
+ * Sub-projects of APLAPL '''must''' follow certain standards - see AplAplStandards for details.
 Line 10:
-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.
+||<tablebgcolor="#ffe" tablestyle="top-margin:1em; font-size:small" rowclass="odd">'''Name''' ||'''Windows''' ||'''Linux''' ||'''Description''' ||
||<rowclass="even">[[APLTeamUtils]] || (./) ||  /!\ ||General utilities ||
||<rowclass="odd">[[ADOC]] || (./) ||  /!\ ||Automated Documentation Generation ||
||<rowclass="even">[[Hash]] || (./) || /!\ ||Managing key/value-pairs ||
||<rowclass="odd">IniFiles || (./) ||  /!\ ||Dealing with INI files ||
||<rowclass="even">[[Logger]] || (./) || /!\ ||Writing Log Files ||
||<rowclass="odd">ShowChmHelp || (./) || {X} ||Display help files and topics within help files ||
||<rowclass="even">WindowsEventLog || (./) || {X} ||Dealing with the Windows Event Log ||
||<rowclass="odd">WinFile || (./) || /!\ ||Dealing with files and directories ||
||<rowclass="even">WinReg || (./) || {X} ||Dealing with the Windows Registry ||
<<BR>>
Legend:
-Line 12:
+Line 23:
+/!\  contributor needed
-Line 13:
+Line 25:
-##||||||<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'''||
+(./) fully implemented

{*} under construction

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