Differences between revisions 19 and 51 (spanning 32 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

CategoryOpenSourceApl

-  ⇤ ← Revision 19 as of 2008-08-03 20:50:03 → 
  Size: 1715
  Editor: KaiJaeger
  Comment:
+   ← Revision 51 as of 2009-01-13 15:34:50 → ⇥
  Size: 1171
  Editor: KaiJaeger
  Comment: Adapt to changes
-Deletions are marked like this.
+Additions are marked like this.
 Line 3:
+<<BR>>
-Line 4:
+Line 5:
-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:
+Line 7:
-All classes published here '''must''' be part of '''"The Open Source APL Project"''' in short '''[:OpenSourceAplProject: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:
+Line 9:
-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:
+Line 11:
-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.
+<<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 13:
+Line 24:
-##||||||<tablestyle="background:#ffe; padding:0 2em 1em 0;">''''''||''''''||
||'''Name'''||'''Description'''||'''Type'''||'''Originator'''||'''Needs .NET'''||
||[:APLTeamsUtil:APLTeamsUtil]||General utilities||Dyalog||APL Team||'''No'''||
||[:ADOC:ADOC]||Automated Documentation Generation||Dyalog||APL Team||'''No'''||
||[:Hash:Hash]||Managing key/value-pairs||Dyalog ||APL Team||'''No'''||
||IniFiles||Dealing with INI files||Dyalog||APL Team||'''No'''||
||[:Logger:Logger]||Writing Log Files||Dyalog||APL Team||'''No'''||
||[:WindowsEventLog]||Dealing with the Windows Event Log||Dyalog||APL Team||'''Yes'''||
||[:WinFile:WinFile]||Dealing with files and directories||Dyalog||APL Team||'''No'''||
||[:WinReg:WinReg]||Dealing with the Windows Registry||Dyalog||APL Team||'''No'''||
-Line 25:
+Line 27:
-CategoryAplApl CategoryOpenSourceApl
+CategoryOpenSourceApl