Differences between revisions 32 and 81 (spanning 49 versions)
Revision 32 as of 2008-12-19 07:29:22
Size: 2175
Editor: KaiJaeger
Comment:
Revision 81 as of 2011-06-01 14:04:10
Size: 2064
Editor: KaiJaeger
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was copied from CategoryAplApl
Line 4: Line 5:
Note that this is a pure Dyalog project. Note also that by definition only scripts (either class- or namespace-scripts) can be part of APLAPL. <<TableOfContents>>
Line 6: Line 7:
Scripts in this category '''must''' contain a Copyright notice according to the [[http://en.wikipedia.org/wiki/Mit_license|MIT license]] conditions. == Overview ==
Line 8: Line 9:
The basic idea behind APLAPL is to provide classes for every-day-problems programmers typically come across.  * APLAPL is supposed to offer scripts (class scripts and namespace scrips) for every-day-problems programmers typically come across.
Line 10: Line 11:
To become part of the APLAPL project, one must ensure that proper test cases are written and executed before the class is published. Although that does not guarantee that the scripts are free of bugs, this certainly decreases the danger of bugs.  * Sub-projects of APLAPL should follow certain standards - see AplAplStandards for details.
Line 12: Line 13:
== Test cases: follow the standards! == == Utilities ==
Line 14: Line 15:
<<SeeSaw(section="testcasestd", toshow="<<Show>> the details", tohide="<<Hide>> the details", bg="#FEE1A5", speed="Slow")>> ||'''Name''' ||'''Windows''' ||'''Linux''' ||'''Description''' ||
||[[APLTeamUtils]] || (./) || /!\ ||General utilities; `:Include`d in many of the following scripts||
||[[Apl2Xml|APL2XML]] || (./) || {X} ||Create an *.CHM file by creating XML files in order to compile them with !HelpAndManual||
||[[Execute]] || (./) || {X} ||Start a new process or application||
||[[Hash]] || (./) || /!\ ||Managing key/value-pairs ||
||IniFiles || (./) || /!\ ||Dealing with INI files ||
||[[Logger]] || (./) || /!\ ||Writing Log Files ||
||ShowChmHelp || (./) || {X} ||Display help files and topics within help files ||
||WindowsEventLog || (./) || {X} ||Dealing with the Windows Event Log ||
||WinFile || (./) || /!\ ||Dealing with files and directories ||
||WinReg || (./) || {X} ||Dealing with the Windows Registry ||
||WinSys || (./) || {X} ||Get information closely related to Windows ||
Line 16: Line 28:
{{{{#!wiki seesaw/testcasestd/testcasestd-bg/hide Legend: <<BR>>
|| /!\ contributor needed || (./) fully implemented || {*} under construction || {X} not applicable ||
Line 18: Line 31:
 * All test cases are supposed to be in a namespace {{{#.TestCases}}}.
 * At least there is one sub-namespace: "Test_001". Depending on the complexity of the tests, there may be up to 999 different test cases.
 * Every sub-namespace "Test_00n" is supposed to have a function "Run" which executes the test case.
 * There should be a function {{{#.TestCases.RunAll}}} which is supposed to run all test cases in one go.
 * When a test fails, let it stop.
}}}}
== Tools ==
Line 25: Line 33:
Tools are designed to help a developer somehow during the development process.
Line 26: Line 35:
||<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||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'''||
||'''Name''' ||'''Windows''' ||'''Linux''' ||'''Description''' ||
||[[ADOC]] || (./) || /!\ ||Automated Documentation Generation ||
||[[APLCode2HTML]]|| (./) || /!\ || Create HTML code in order to display APL code properly ||
|| [[Compare]] || (./) || /!\ || Compare fns, operators, scripts and namespaces ||
|| ScriptManager || (./) || /!\ || GUI-tool for managing scripts ||

Legend: <<BR>>
|| /!\ contributor needed || (./) fully implemented || {*} under construction || {X} not applicable ||
Line 38: Line 45:
CategoryOpenSourceApl CategoryCategory

APL Application Programming Library (APLAPL)

Overview

  • APLAPL is supposed to offer scripts (class scripts and namespace scrips) for every-day-problems programmers typically come across.
  • Sub-projects of APLAPL should follow certain standards - see AplAplStandards for details.

Utilities

Name

Windows

Linux

Description

APLTeamUtils

(./)

/!\

General utilities; :Included in many of the following scripts

APL2XML

(./)

{X}

Create an *.CHM file by creating XML files in order to compile them with HelpAndManual

Execute

(./)

{X}

Start a new process or application

Hash

(./)

/!\

Managing key/value-pairs

IniFiles

(./)

/!\

Dealing with INI files

Logger

(./)

/!\

Writing Log Files

ShowChmHelp

(./)

{X}

Display help files and topics within help files

WindowsEventLog

(./)

{X}

Dealing with the Windows Event Log

WinFile

(./)

/!\

Dealing with files and directories

WinReg

(./)

{X}

Dealing with the Windows Registry

WinSys

(./)

{X}

Get information closely related to Windows

Legend:

/!\ contributor needed

(./) fully implemented

{*} under construction

{X} not applicable

Tools

Tools are designed to help a developer somehow during the development process.

Name

Windows

Linux

Description

ADOC

(./)

/!\

Automated Documentation Generation

APLCode2HTML

(./)

/!\

Create HTML code in order to display APL code properly

Compare

(./)

/!\

Compare fns, operators, scripts and namespaces

ScriptManager

(./)

/!\

GUI-tool for managing scripts

Legend:

/!\ contributor needed

(./) fully implemented

{*} under construction

{X} not applicable


CategoryCategory

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