APL Wiki|
Size: 811
Comment:
|
Size: 1824
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. 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. |
| Line 7: | Line 15: |
| ##||||||<tablestyle="background:#ffe; padding:0 2em 1em 0;">''''''|| ||'''Name'''||'''Description'''||'''Type'''||'''Originator'''||'''Part of [:CategoryOpenSourceApl:TOSAP]'''|| ||[:APLTeamsUtil:APLTeamsUtil]||Needed by classes (but ADOC) originated by APL Team||Dyalog Class||APL Team||Yes|| ||[:ADOC:ADOC]||Automated Documentation Generation||Dyalog Class||APL Team|||Yes|| ||IniFiles||Dealing with INI files||Dyalog Class||APL Team|||Yes|| ||[:Logger:Logger]||Writing Log Files||Dyalog Class||APL Team|||Yes|| ||[:Hash:Hash]||Creating and managing hashes (key/value-pairs)||Dyalog Class||APL Team|||Yes|| |
##||||||<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 16: | Line 27: |
| 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.
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.
Name |
Description |
Type |
Originator |
Needs .NET |
General utilities |
Dyalog |
APL Team |
No |
|
Automated Documentation Generation |
Dyalog |
APL Team |
No |
|
Managing key/value-pairs |
Dyalog |
APL Team |
No |
|
Dealing with INI files |
Dyalog |
APL Team |
No |
|
Writing Log Files |
Dyalog |
APL Team |
No |
|
Dealing with the Windows Event Log |
Dyalog |
APL Team |
Yes |
|
Dealing with files and directories |
Dyalog |
APL Team |
No |
|
Dealing with the Windows Registry |
Dyalog |
APL Team |
No |