APL Wiki|
Size: 702
Comment:
|
Size: 2175
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| Points to System Libraries and Addons. These are expected to be vendor specific. | 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. Scripts in this category '''must''' contain a Copyright notice according to the [[http://en.wikipedia.org/wiki/Mit_license|MIT license]] conditions. The basic idea behind APLAPL is to provide classes for every-day-problems programmers typically come across. 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. }}}} |
| Line 7: | Line 26: |
| ##||||||<tablestyle="background:#ffe; padding:0 2em 1em 0;">''''''|| ||'''Name'''||'''Description'''||'''Type'''||'''Part of [:CategoryOpenSourceApl:TOSAP]'''|| ||[:APLTeamsUtil:APLTeamsUtil]||Utilities needed by almost all classes but ADOC||Dyalog Class||Yes|| ||[:ADOC:ADOC]||Automated Documentation Generation||Dyalog Class||Yes|| ||IniFiles||Dealing with INI files||Dyalog Class||Yes|| ||[:Logger:Logger]||Writing Log Files||Dyalog Class||Yes|| ||[:Hash:Hash]||Create a hash||Dyalog Class||Yes|| |
||<tablestyle="background:#ffe; padding:0 2em 1em 0;">'''Name'''||'''Description'''||'''Originator'''||'''Needs .NET'''|| ||[[APLTeamUtils]]||General utilities||APL Team||'''No'''|| ||[[ADOC]]||Automated Documentation Generation||APL Team||'''No'''|| ||[[Hash]]||Managing key/value-pairs||APL Team||'''No'''|| ||IniFiles||Dealing with INI files||APL Team||'''No'''|| ||[[Logger]]||Writing Log Files||APL Team||'''No'''|| ||ShowChmHelp||Display help files||APL Team||'''No'''|| ||[[WindowsEventLog]]||Dealing with the Windows Event Log||APL Team||'''Yes'''|| ||[[WinFile]]||Dealing with files and directories||APL Team||'''No'''|| ||[[WinReg]]||Dealing with the Windows Registry||APL Team||'''No'''|| |
| Line 16: | Line 38: |
| CategoryAplApl | CategoryOpenSourceApl |
APL Application Programming Library (APLAPL)
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.
Scripts in this category must contain a Copyright notice according to the MIT license conditions.
The basic idea behind APLAPL is to provide classes for every-day-problems programmers typically come across.
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!
Show the details
Name |
Description |
Originator |
Needs .NET |
General utilities |
APL Team |
No |
|
Automated Documentation Generation |
APL Team |
No |
|
Managing key/value-pairs |
APL Team |
No |
|
Dealing with INI files |
APL Team |
No |
|
Writing Log Files |
APL Team |
No |
|
Display help files |
APL Team |
No |
|
Dealing with the Windows Event Log |
APL Team |
Yes |
|
Dealing with files and directories |
APL Team |
No |
|
Dealing with the Windows Registry |
APL Team |
No |