549
Comment:
|
1709
Not vendor specific anymore, but needs classes
|
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. | The basic idea behind APLAPL is to provide classes for every-day-problems programmers typically come across. |
Line 6: | Line 6: |
Sub-projects of APLAPL '''must''' follow certain [[AplAplStandards | standards]] | |
Line 7: | Line 8: |
##||||||<tablestyle="background:#ffe; padding:0 2em 1em 0;">''''''|| ||'''Name'''||'''Description'''||'''Type'''||'''Part of [:CategoryOpenSourceApl:TOSAP]'''|| ||[:ADOC:ADOC]]||Automated Documentation Generation||Dyalog Class||Yes|| ||IniFiles||Dealing with INI files||Dyalog Class||Yes|| ||[:Logger:Logger]||Writing Log Files||Dyalog Class||Yes|| |
The columns "Win" and "Linux" are checked if the software is designed for running under this operating system '''and''' comes with test cases for that environment. By defenition all APLAPL projects must be classes, ot at least scripts. For the time being (2009-01) this restricts the APLAPL projects to Dyalog and APLX. <<BR>><<BR>> ||<rowclass="odd" tablestyle="background:#ffe;font-size:small"> '''Name''' || '''Description''' || '''Originator''' || '''Dialect''' || '''Win''' || '''Linux''' || '''.NET<<BR>>required''' || ||[[APLTeamUtils]]||General utilities||APL Team||Dyalog|| (./) || {X} || {X} || ||<rowclass="odd">[[ADOC]]||Automated Documentation Generation||APL Team||Dyalog|| (./) || {X} || {X} || ||[[Hash]]||Managing key/value-pairs||APL Team||Dyalog|| (./) || {X} || {X} || ||<rowclass="odd">IniFiles||Dealing with INI files||APL Team||Dyalog|| (./) || {X} || {X} || || [[Logger]] ||Writing Log Files||APL Team||Dyalog|| (./) || {X} || {X} || ||<rowclass="odd">ShowChmHelp||Display help files and topics within help files||APL Team||Dyalog|| (./) || {X} || {X} || ||[[WindowsEventLog]]||Dealing with the Windows Event Log||APL Team||Dyalog|| (./) || {X} || (./) || ||<rowclass="odd">[[WinFile]]||Dealing with files and directories||APL Team||Dyalog|| (./) || {X} || {X} || ||[[WinReg]]||Dealing with the Windows Registry||APL Team||Dyalog|| (./) || {X} || {X} || |
Line 14: | Line 26: |
CategoryAplApl | CategoryOpenSourceApl |
APL Application Programming Library (APLAPL)
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 comes with test cases for that environment.
By defenition all APLAPL projects must be classes, ot at least scripts. For the time being (2009-01) this restricts the APLAPL projects to Dyalog and APLX.
Name |
Description |
Originator |
Dialect |
Win |
Linux |
.NET |
General utilities |
APL Team |
Dyalog |
|
|
|
|
Automated Documentation Generation |
APL Team |
Dyalog |
|
|
|
|
Managing key/value-pairs |
APL Team |
Dyalog |
|
|
|
|
Dealing with INI files |
APL Team |
Dyalog |
|
|
|
|
Writing Log Files |
APL Team |
Dyalog |
|
|
|
|
Display help files and topics within help files |
APL Team |
Dyalog |
|
|
|
|
Dealing with the Windows Event Log |
APL Team |
Dyalog |
|
|
|
|
Dealing with files and directories |
APL Team |
Dyalog |
|
|
|
|
Dealing with the Windows Registry |
APL Team |
Dyalog |
|
|
|