Differences between revisions 14 and 56 (spanning 42 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

CategoryAplApl

-  ⇤ ← Revision 14 as of 2008-07-26 13:42:25 → 
  Size: 1708
  Editor: KaiJaeger
  Comment:
+   ← Revision 56 as of 2009-04-07 20:35:51 → ⇥
  Size: 1291
  Editor: KaiJaeger
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 4:
-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.
+ * APLAPL is a pure Dyalog project.
 Line 6:
-All classes published here '''must''' be part of '''"The Open Source APL Project"''' in short '''[:CategoryOpenSourceApl:TOSAP]'''. Yes, classes, so it has to be at least version 11 of Dyalog APL you are working with.
+ * APLAPL is supposed to offer scripts (class scripts and namespace scrips) for every-day-problems programmers typically come across.
 Line 8:
-The idea behind TOSAP is to provide classes ready for usage for every-day-problems programmers typically come across.
+ * Sub-projects of APLAPL '''must''' follow certain standards - see AplAplStandards for details.
 Line 10:
-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.
+<<BR>>
||<tablebgcolor="#ffe" tablestyle="font-size:small"rowclass="odd">'''Name''' ||'''Windows''' ||'''Linux''' ||'''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 || (./) || {X} ||Display help files and topics within help files ||
||WindowsEventLog || (./) || {X} ||Dealing with the Windows Event Log ||
||<rowclass="odd">WinFile || (./) || /!\ ||Dealing with files and directories ||
||WinReg || (./) || {X} ||Dealing with the Windows Registry ||
-Line 12:
+Line 22:
-##||||||<tablestyle="background:#ffe; padding:0 2em 1em 0;">''''''||
||'''Name'''||'''Description'''||'''Type'''||'''Originator'''||'''Part of [:CategoryOpenSourceApl: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||
+Legend:
|| /!\ ||contributor needed|| (./) ||fully implemented||
|| {*} ||under construction|| {X} ||not applicable||
-Line 24:
+Line 27:
 CategoryAplApl