2201
Comment:
|
2113
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
## page was renamed from APLAPL = APL Application Programming Library (APLAPL) = |
## page was copied from CategoryAplApl = CategoryAPLTree: APL tools and utility library = |
Line 4: | Line 4: |
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 6: |
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 8: |
The basic idea behind APLAPL is to provide classes for every-day-problems programmers typically come across. | * APLTree is supposed to offer scripts (class scripts and namespace scrips) for every-day-problems programmers typically come across. * APLTree is an Open Source project - see AplTreeLicensing for details. * Sub-projects of !AplTree should follow certain suggestions - see AplTreeSuggestions for details. |
Line 10: | Line 12: |
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. | == Utilities == |
Line 12: | Line 14: |
== Test cases: follow the standards! == | ||'''Name''' ||'''Windows''' ||'''Linux''' ||'''Description''' || ||[[APLTreeUtils]] || (./) || /!\ ||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 14: | Line 27: |
<<SeeSaw(section="testcasestd", toshow="<<Show>> the details", tohide="<<Hide>> the details", bg="#FEE1A5", speed="Slow")>> | Legend: <<BR>> || /!\ contributor needed || (./) fully implemented || {*} under construction || {X} not applicable || |
Line 16: | Line 30: |
{{{{#!wiki seesaw/testcasestd/testcasestd-bg/hide | == Tools == |
Line 18: | Line 32: |
* 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 are designed to help a developer somehow during the development process. |
Line 25: | Line 34: |
||'''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 || |
|
Line 26: | Line 40: |
##||||||<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'''|| |
Legend: <<BR>> || /!\ contributor needed || (./) fully implemented || {*} under construction || {X} not applicable || |
Line 39: | Line 44: |
CategoryOpenSourceApl | CategoryCategory |
CategoryAPLTree: APL tools and utility library
Overview
- APLTree is supposed to offer scripts (class scripts and namespace scrips) for every-day-problems programmers typically come across.
APLTree is an Open Source project - see AplTreeLicensing for details.
Sub-projects of AplTree should follow certain suggestions - see AplTreeSuggestions for details.
Utilities
Name |
Windows |
Linux |
Description |
|
|
General utilities; :Included in many of the following scripts |
|
|
|
Create an *.CHM file by creating XML files in order to compile them with HelpAndManual |
|
|
|
Start a new process or application |
|
|
|
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 |
|
|
|
Get information closely related to Windows |
Legend:
contributor needed |
fully implemented |
under construction |
not applicable |
Tools
Tools are designed to help a developer somehow during the development process.
Name |
Windows |
Linux |
Description |
|
|
Automated Documentation Generation |
|
|
|
Create HTML code in order to display APL code properly |
|
|
|
Compare fns, operators, scripts and namespaces |
|
|
|
GUI-tool for managing scripts |
Legend:
contributor needed |
fully implemented |
under construction |
not applicable |