2113
Comment:
|
1195
|
Deletions are marked like this. | Additions are marked like this. |
Line 2: | Line 2: |
= APL Application Programming Library (APL) = | = APL Application Programming Library (APLAPL) = <<BR>><<BR>> * APLAPL is a pure Dyalog project. |
Line 4: | Line 6: |
At the time being, everything here refers to Dyalog APL. That might change sometime, but as long as no other stuff turns up here it keeps things simple. | * APLAPL is supposed to offer scripts (class scripts and namespace scrips) for every-day-problems programmers typically come across. |
Line 6: | Line 8: |
All classes published here '''must''' be part of '''"The Open Source APL Project"''' in short '''[[OpenSourceAplProject|TOSAP]]'''. Yes, classes, so it has to be at least version 11 of Dyalog APL you are working with. | * Sub-projects of APLAPL '''must''' follow certain standards - see AplAplStandards for details. |
Line 8: | Line 10: |
The idea behind TOSAP is to provide classes ready for usage for every-day-problems programmers typically come across. | <<BR>> |
Line 10: | Line 12: |
Note that there is a significant difference between downloading a script from the wiki and checking out the associated project from !SubVersion: * The wiki download contains the script and maybe something else you need to run the script. * The subproject comes with more stuff, especially with a development workspace which '''must''' contain a test suite. Only fully tested scripts should be offered to the public for download. 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. ##||||||<tablestyle="background:#ffe; padding:0 2em 1em 0;">''''''||''''''|| ||'''Name'''||'''Description'''||'''Type'''||'''Originator'''||'''Needs .NET'''|| ||[[APLTeamsUtil]]||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'''|| |
||<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 30: | Line 24: |
CategoryAplApl CategoryOpenSourceApl | CategoryOpenSourceApl |
APL Application Programming Library (APLAPL)
- APLAPL is a pure Dyalog project.
- APLAPL is supposed to offer scripts (class scripts and namespace scrips) for every-day-problems programmers typically come across.
Sub-projects of APLAPL must follow certain standards - see AplAplStandards for details.
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 |