1522
Comment:
|
1438
Information added regarding operating systems
|
Deletions are marked like this. | Additions are marked like this. |
Line 4: | Line 4: |
Note that this is a pure Dyalog project. Note also that by definition only classes can be part of APLAPL. | Note that this is a pure Dyalog project. |
Line 8: | Line 8: |
To become part of the APLAPL project, one must ensure that proper testcases are written and executed before the class is published. | Sub-projects of APLAPL '''must''' follow certain [[AplAplStandards | standards]] |
Line 10: | Line 10: |
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. | The columns "Win" and "Linux" are checked if the software is designed for running under this operating system '''and''' come with test cases for that environment. <<BR>><<BR>> |
Line 12: | Line 13: |
##||||||<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'''|| |
||<tablestyle="background:#ffe; "> '''Name''' || '''Description''' || '''Originator''' || '''Windows''' || '''Linux''' || '''Needs .NET''' || ||<rowclass="odd">[[APLTeamUtils]]||General utilities||APL Team|| (./) || {X} || {X} || ||<rowclass="even">[[ADOC]]||Automated Documentation Generation||APL Team|| (./) || {X} || {X} || ||[[Hash]]||Managing key/value-pairs||APL Team|| (./) || {X} || {X} || ||IniFiles||Dealing with INI files||APL Team|| (./) || {X} || {X} || || [[Logger]] ||Writing Log Files||APL Team|| (./) || {X} || {X} || ||ShowChmHelp||Display help files and topics within help files||APL Team|| (./) || {X} || {X} || ||[[WindowsEventLog]]||Dealing with the Windows Event Log||APL Team|| (./) || {X} || (./) || ||[[WinFile]]||Dealing with files and directories||APL Team|| (./) || {X} || {X} || ||[[WinReg]]||Dealing with the Windows Registry||APL Team|| (./) || {X} || {X} || |
APL Application Programming Library (APLAPL)
Note that this is a pure Dyalog project.
The basic idea behind APLAPL is to provide classes for every-day-problems programmers typically come across.
Sub-projects of APLAPL must follow certain standards
The columns "Win" and "Linux" are checked if the software is designed for running under this operating system and come with test cases for that environment.
Name |
Description |
Originator |
Windows |
Linux |
Needs .NET |
General utilities |
APL Team |
|
|
|
|
Automated Documentation Generation |
APL Team |
|
|
|
|
Managing key/value-pairs |
APL Team |
|
|
|
|
Dealing with INI files |
APL Team |
|
|
|
|
Writing Log Files |
APL Team |
|
|
|
|
Display help files and topics within help files |
APL Team |
|
|
|
|
Dealing with the Windows Event Log |
APL Team |
|
|
|
|
Dealing with files and directories |
APL Team |
|
|
|
|
Dealing with the Windows Registry |
APL Team |
|
|
|