1826
Comment:
|
1111
|
Deletions are marked like this. | Additions are marked like this. |
Line 4: | Line 4: |
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. | Note that this is a pure Dyalog project. |
Line 6: | Line 6: |
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. | The basic idea behind APLAPL is to provide classes for every-day-problems programmers typically come across. |
Line 8: | Line 8: |
The idea behind TOSAP is to provide classes ready for usage for every-day-problems programmers typically come across. 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. |
Sub-projects of APLAPL '''must''' follow certain [[AplAplStandards | standards]] <<BR>><<BR>> |
Line 13: | Line 12: |
##||||||<tablestyle="background:#ffe; padding:0 2em 1em 0;">''''''|| ||'''Name'''||'''Description'''||'''Type'''||'''Originator'''||'''Part of [:OpenSourceAplProject:TOSAP]'''|| ||[:APLTeamsUtil:APLTeamsUtil]||Needed by all classes but ADOC, originated by APL Team||Dyalog Class||APL Team||Yes|| ||[:ADOC:ADOC]||Automated Documentation Generation||Dyalog Class||APL Team||Yes|| ||[:Hash:Hash]||Managing key/value-pairs||Dyalog Class||APL Team||Yes|| ||IniFiles||Dealing with INI files without .NET||Dyalog Class||APL Team||Yes|| ||[:Logger:Logger]||Writing Log Files||Dyalog Class||APL Team||Yes|| ||[:WindowsEventLog]||Dealing with the Windows Event Log with .NET||Dyalog Class||APL Team||Yes|| ||[:WinFile:WinFile]||Dealing with files and directories without .NET||Dyalog Class||APL Team||Yes|| ||[:WinReg:WinReg]||Dealing with the Windows Registry without .NET||Dyalog Class||APL Team||Yes|| |
||<tablestyle="background:#ffe; padding:0 2em 1em 0;">'''Name'''||'''Description'''||'''Originator'''||'''Needs .NET'''|| ||[[APLTeamUtils]]||General utilities||APL Team||'''No'''|| ||[[ADOC]]||Automated Documentation Generation||APL Team||'''No'''|| ||[[Hash]]||Managing key/value-pairs||APL Team||'''No'''|| ||IniFiles||Dealing with INI files||APL Team||'''No'''|| ||[[Logger]]||Writing Log Files||APL Team||'''No'''|| ||ShowChmHelp||Display help files and topics within help files||APL Team||'''No'''|| ||[[WindowsEventLog]]||Dealing with the Windows Event Log||APL Team||'''Yes'''|| ||[[WinFile]]||Dealing with files and directories||APL Team||'''No'''|| ||[[WinReg]]||Dealing with the Windows Registry||APL Team||'''No'''|| |
Line 25: | Line 24: |
CategoryAplApl CategoryOpenSourceApl | CategoryOpenSourceApl |
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
Name |
Description |
Originator |
Needs .NET |
General utilities |
APL Team |
No |
|
Automated Documentation Generation |
APL Team |
No |
|
Managing key/value-pairs |
APL Team |
No |
|
Dealing with INI files |
APL Team |
No |
|
Writing Log Files |
APL Team |
No |
|
Display help files and topics within help files |
APL Team |
No |
|
Dealing with the Windows Event Log |
APL Team |
Yes |
|
Dealing with files and directories |
APL Team |
No |
|
Dealing with the Windows Registry |
APL Team |
No |