Ticket #3474 (new enhancement)
Manual 5 Command Line Use
| Reported by: | gs99ohio | Owned by: | anonymous |
|---|---|---|---|
| Priority: | normal | Milestone: | 3.0.0 release |
| Component: | Documentation | Version: | trunk |
| Severity: | text | Keywords: | |
| Cc: |
Description
Much or all of "Roadsend Compiler" can be implemented via the IDE window or command lines.
It appears that much content within Manual part 5 Command Line Use is general information (not limited to "Command Line Use"). I don't see it outside of part 5.
Could the manual be organized to emphasize Features, with sub-sections for each implementation?
Example:
1 Introduction 2 Installation and Configuration 3 Language Reference
4 Features 4.1 Project Type Overview 4.1.1 Files not in a project 4.2 Interpreting and Compiling
4.3 Files not in a project (general info) 4.3.1 Command Line Use (specific to command line use) 4.3.2 IDE use (specific to IDE use)
4.4 Web Applications 4.4.1 Command Line Use 4.4.2 IDE use
4.5 Stand Alone Web Applications 4.5.1 Command Line Use 4.5.2 IDE Use
4.6 Desktop Applications 4.6.1 Command Line Use 4.6.2 IDE Use
4.7 Console Applications 4.7.1 Command Line Use 4.7.2 IDE Use
4.8 Libraries 4.8.1 Command Line Use 4.8.2 IDE Use
4.9 Debugging 4.9.1 Command Line Use 4.9.2 IDE Use (current 6.7.6)
4.10 Profiling 4.10.1 Command Line Use 4.10.2 IDE Use
4.11 Optimization 4.11.1 Command Line Use 4.11.2 IDE Use
4.12 Build 4.12.1 Command Line Use 4.12.2 IDE Use
4.13 Deployment 4.13.1 Command Line Use 4.13.2 IDE Use (current 6.7.7)
5 Command Line Use (general information about CLU) 5.1 Command Line Options (current 7.1)
6 IDE
7 Reference
8 Acknowedgements
9 Glossary
10 Tutorials (These could have links to this forum's Tutorials) 10.1 Web application 10.2 Stand Alone 10.3 Desktop 10.4 Console 10.5 Library
Note that I've added several parts that are needed to explain and demonstrate this product that is different than "normal" PHP products.
