2276
Comment: New class "ShowChmFile" added
|
2175
|
Deletions are marked like this. | Additions are marked like this. |
Line 26: | Line 26: |
##||||||<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'''|| ||ShowChmHelp||Display help files||Dyalog||'''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'''|| |
||<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'''|| |
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 |