Differences between revisions 25 and 48 (spanning 23 versions)
Revision 25 as of 2008-12-15 17:57:45
Size: 1537
Editor: KaiJaeger
Comment:
Revision 48 as of 2009-01-09 16:54:02
Size: 1261
Editor: KaiJaeger
Comment:
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.
Line 8: Line 6:
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 8:
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. 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.
Line 12: Line 10:
<<BR>>
Line 13: Line 12:
##||||||<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'''||
||<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 25: Line 24:
CategoryAplApl CategoryOpenSourceApl 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

APLTeamUtils

(./)

-

General utilities

ADOC

(./)

-

Automated Documentation Generation

Hash

(./)

-

Managing key/value-pairs

IniFiles

(./)

-

Dealing with INI files

Logger

(./)

-

Writing Log Files

ShowChmHelp

(./)

-

Display help files and topics within help files

WindowsEventLog

(./)

-

Dealing with the Windows Event Log

WinFile

(./)

-

Dealing with files and directories

WinReg

(./)

-

Dealing with the Windows Registry


CategoryOpenSourceApl

CategoryAplTree (last edited 2018-03-04 12:46:55 by KaiJaeger)