Changes between Version 1 and Version 2 of WikiStart
- Timestamp:
- Oct 8, 2018, 4:05:25 PM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WikiStart
v1 v2 1 = Welcome to Trac 1.0.9=1 = CUBE = 2 2 3 Trac is a '''minimalistic''' approach to '''web-based''' management of 4 '''software projects'''. Its goal is to simplify effective tracking and handling of software issues, enhancements and overall progress. 3 CUBE is a REXX procedure used to modify a CONFIG.SYS-like ASCII file (the Target File), based on a set of CUBE's commands (the Procedure File). 5 4 6 All aspects of Trac have been designed with the single goal to 7 '''help developers write great software''' while '''staying out of the way''' 8 and imposing as little as possible on a team's established process and 9 culture. 5 CUBE was initially developed to automatically create/update CONFIG.SYS or STARTUP.CMD files. It may be integrated in dynamic processes used to customize PS/2 configurations. Any other ASCII file (such as profiles, commands files, etc...) may also be customized with CUBE. 10 6 11 As all Wiki pages, this page is editable, this means that you can 12 modify the contents of this page simply by using your 13 web-browser. Simply click on the "Edit this page" link at the bottom 14 of the page. WikiFormatting will give you a detailed description of 15 available Wiki formatting commands. 7 CUBE has its own set of commands (described below) that provide editing functions at the line and string levels. This set of commands includes ADD, REPLACE and DELETE functions. 16 8 17 "[wiki:TracAdmin trac-admin] ''yourenvdir'' initenv" created 18 a new Trac environment, containing a default set of wiki pages and some sample 19 data. This newly created environment also contains 20 [wiki:TracGuide documentation] to help you get started with your project. 9 Most of CUBE's commands require identification of the Target File line they act upon: the line will be identify by its leftmost characters (as many as necessary for a precise or generic identification) starting from column 1. This was inherited from the CONFIG.SYS type of file CUBE was created for. However, the option '*ID', wherever available, tells CUBE to identify the Target File line as any line containing the identification string, starting at any position. Furthermore, the command LINEID may specify that leading characters in Target File lines should be ignored (stripped) for identification. 21 10 22 You can use [wiki:TracAdmin trac-admin] to configure 23 [http://trac.edgewall.org/ Trac] to better fit your project, especially in 24 regard to ''components'', ''versions'' and ''milestones''. 11 Commands in a Procedure File may be further customized at CUBE's execution time: strings may contain 'variables' names that will be replaced by their current value at execution time. This is known as 'substitution' and comes in two flavors: command line substitution and environment variable substitution. 25 12 13 Command line substitution: values of variables are passed in the command line. Environment variable substitution: values of variables are those of currently defined OS/2 environment variables at CUBE's execution time. Substitution in CUBE's commands always occurs, while substitution in a Target File line only occurs if this line is processed by a CUBE's command. 26 14 27 TracGuide is a good place to start. 28 29 Enjoy! [[BR]] 30 ''The Trac Team'' 31 32 == Starting Points == 33 34 * TracGuide -- Built-in Documentation 35 * [http://trac.edgewall.org/ The Trac project] -- Trac Open Source Project 36 * [http://trac.edgewall.org/wiki/TracFaq Trac FAQ] -- Frequently Asked Questions 37 * TracSupport -- Trac Support 38 39 For a complete list of local wiki pages, see TitleIndex. 15 Variable names are always identified by delimiters: any single character you wish, unique for a given variable name, to avoid conflict with other characters in a string or system interpretation. Variable names ARE case sensitive.
