Differences between revisions 28 and 73 (spanning 45 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	Type
ADOC		$/!\$	Automated Documentation Generation	Tool
APL2XML			Create XML files in order to compile them with HelpAndManual	Tool
APLCode2HTML		$/!\$	Create HTML code in order to display APL code properly	Tool
APLTeamUtils		$/!\$	General utilities	Utility
Compare		$/!\$	Compare fns, operators and scripts with CompareIt!	Tool
Execute			Start a new process or application	Utility
Hash		$/!\$	Managing key/value-pairs	Utility
IniFiles		$/!\$	Dealing with INI files	Utility
Logger		$/!\$	Writing Log Files	Utility
ScriptManager		$/!\$	GUI-tool for managing scripts	Tool
ShowChmHelp			Display help files and topics within help files	Utility
WindowsEventLog			Dealing with the Windows Event Log	Utility
WinFile		$/!\$	Dealing with files and directories	Utility
WinReg			Dealing with the Windows Registry	Utility

Legend:
$/!\$ contributor needed
fully implemented
under construction
not applicable

Tool: Supports a developer somehow
Utility: Potentially part of an application

CategoryCategory

-  ⇤ ← Revision 28 as of 2008-12-18 20:20:49 → 
  Size: 2221
  Editor: KaiJaeger
  Comment: Standards for test cases added
+   ← Revision 73 as of 2010-12-26 20:08:47 → ⇥
  Size: 1869
  Editor: KaiJaeger
  Comment:
-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 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 7:
-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 9:
-The basic idea behind APLAPL is to provide classes for every-day-problems programmers typically come across.
+||'''Name''' ||'''Windows''' ||'''Linux''' ||'''Description''' || '''Type''' ||
||[[ADOC]] || (./) || /!\ ||Automated Documentation Generation || Tool ||
||[[Apl2Xml|APL2XML]] || (./) || {X} ||Create XML files in order to compile them with !HelpAndManual|| Tool ||
||[[APLCode2HTML]]|| (./) || /!\ || Create HTML code in order to display APL code properly || Tool ||
||[[APLTeamUtils]] || (./) || /!\ ||General utilities || Utility ||
|| [[Compare]] || (./) || /!\ || Compare fns, operators and scripts with [[http://www.grigsoft.com/wincmp3.htm|CompareIt!]] || Tool ||
||[[Execute]] || (./) || {X} ||Start a new process or application|| Utility ||
||[[Hash]] || (./) || /!\ ||Managing key/value-pairs || Utility ||
||IniFiles || (./) || /!\ ||Dealing with INI files || Utility ||
||[[Logger]] || (./) || /!\ ||Writing Log Files || Utility ||
|| ScriptManager || (./) || /!\ || GUI-tool for managing scripts || Tool ||
||ShowChmHelp || (./) || {X} ||Display help files and topics within help files || Utility ||
||WindowsEventLog || (./) || {X} ||Dealing with the Windows Event Log || Utility ||
||WinFile || (./) || /!\ ||Dealing with files and directories || Utility ||
||WinReg || (./) || {X} ||Dealing with the Windows Registry || Utility ||
-Line 10:
+Line 25:
-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.

== Test cases: follow the standards! ==

<<SeeSaw(section="testcasestd", toshow="<<Show>> the details", tohide="<<Hide>> the details", bg="#FEE1A5", speed="Slow")>>

{{{{#!wiki seesaw/testcasestd/testcasestd-bg/hide

 * All test cases are supposed to be in a namespace {{{#.TestCases}}}.
 * At least there is one sub-namespace: "Test_001". Depending on the complexity of the tests, there may be up to 999 different test cases.
 * Every sub-namespace "Test_00n" is supposed to have a function "Run" which executes the test case.
 * There should be a function {{{#.TestCases.RunAll}}} which is supposed to run all test cases in one go.
 * When a test fails, let it stop.
}}}}
+||Legend: <<BR>> /!\  contributor needed<<BR>> (./) fully implemented<<BR>> {*} under construction<<BR>> {X} not applicable || Tool: Supports a developer somehow <<BR>> Utility: Potentially part of an application ||
-Line 26:
+Line 28:
-##||||||<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'''||
-Line 38:
+Line 30:
-CategoryOpenSourceApl
+CategoryCategory