1728
Comment:
|
2067
|
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. | <<TableOfContents>> |
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. | == Overview == |
Line 8: | Line 8: |
The idea behind TOSAP is to provide classes ready for usage for every-day-problems programmers typically come across. | * APLAPL is a pure Dyalog project. |
Line 10: | Line 10: |
Many (so far 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. | * APLAPL is supposed to offer scripts (class scripts and namespace scrips) for every-day-problems programmers typically come across. |
Line 12: | Line 12: |
* Sub-projects of APLAPL '''must''' follow certain standards - see AplAplStandards for details. | |
Line 13: | Line 14: |
##||||||<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|| ||[: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|| |
== Utilities == ||'''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 || Legend: <<BR>> || /!\ 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: <<BR>> || /!\ contributor needed || (./) fully implemented || {*} under construction || {X} not applicable || |
Line 24: | Line 46: |
CategoryAplApl CategoryOpenSourceApl | CategoryCategory |
APL Application Programming Library (APLAPL)
Overview
- 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.
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 |