807
Comment:
|
1261
|
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'''||'''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|| |
By definition all APLAPL projects must be classes, or at least scripts. For the time being (2009-01) this restricts the APLAPL project to Dyalog and APLX. <<BR>> ||<rowclass="odd" tablestyle="background:#ffe;font-size:small">'''Name'''||'''Dyalog'''||'''APLX'''||'''Description''' || ||[[APLTeamUtils]] || (./) || - ||General utilities|| ||<rowclass="odd">[[ADOC]]|| (./) || - ||Automated Documentation Generation|| ||[[Hash]] || (./) || - ||Managing key/value-pairs|| ||<rowclass="odd">IniFiles || (./) || - ||Dealing with INI files|| || [[Logger]] || (./) || - ||Writing Log Files|| ||<rowclass="odd">ShowChmHelp || (./) || - ||Display help files and topics within help files|| ||[[WindowsEventLog]] || (./) || - ||Dealing with the Windows Event Log|| ||<rowclass="odd">[[WinFile]] || (./) || - ||Dealing with files and directories|| ||[[WinReg]] || (./) || - ||Dealing with the Windows Registry|| |
Line 16: | Line 24: |
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
By definition all APLAPL projects must be classes, or at least scripts. For the time being (2009-01) this restricts the APLAPL project to Dyalog and APLX.
Name |
Dyalog |
APLX |
Description |
|
- |
General utilities |
|
|
- |
Automated Documentation Generation |
|
|
- |
Managing key/value-pairs |
|
|
- |
Dealing with INI files |
|
|
- |
Writing Log Files |
|
|
- |
Display help files and topics within help files |
|
|
- |
Dealing with the Windows Event Log |
|
|
- |
Dealing with files and directories |
|
|
- |
Dealing with the Windows Registry |