You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Build.html
+15-6Lines changed: 15 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -222,8 +222,15 @@ <h3>
222
222
</h3>
223
223
224
224
<p>
225
-
The Unicode version of the Inno setup command line compiler is needed to
226
-
create <em>CodeSnip</em>'s install program. v5.5.2(u) or later is required.
225
+
The Unicode version of the Inno Setup <strong>v5</strong> command line
226
+
compiler is needed to create <em>CodeSnip</em>'s install program. v5.5.2(u) or
227
+
later is required.
228
+
</p>
229
+
230
+
<pclass="note">
231
+
<strong>Warning:</strong> Do not use Inno Setup v6. This will fail to compile
232
+
the setup script. Inno Setup 6 does not support Windows 2000 or XE, while
233
+
<em>CodeSnip</em> still does.
227
234
</p>
228
235
229
236
<p>
@@ -283,10 +290,6 @@ <h3>
283
290
You do not need Zip if you do not intend to create release files.
284
291
</p>
285
292
286
-
<pclass="note">
287
-
<strong>Note:</strong> You can use the Delphi IDE to edit the code and test compile it. However you will need to build the code from the makefile first to ensure all the required resource files and auto-generated files are present. If you change any resource files or type libraries you also need to re-run the makefile. Final builds should always be created using the makefile.
288
-
</p>
289
-
290
293
291
294
<h2>
292
295
Preparation
@@ -538,6 +541,12 @@ <h4>
538
541
<code>CodeSnip.exe</code>. You can rename the file manually.
539
542
</p>
540
543
544
+
<p>
545
+
After you have gone through these steps you can edit Pascal code and test
546
+
compile from the Delphi IDE. However if you change any files compiled into resources, or the type library, or run a clean up, then you must repeat the
547
+
above steps and do a complete build from the IDE.
548
+
</p>
549
+
541
550
<p>
542
551
Note that building with the make file insted of the IDE performs all the above
Copy file name to clipboardExpand all lines: Docs/ReadMe.txt
+2-1Lines changed: 2 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -144,7 +144,8 @@ Uninstalling the Standard Edition
144
144
---------------------------------
145
145
146
146
CodeSnip can be uninstalled via "Apps and Features" (a.k.a. "Programs and
147
-
Features", a.k.a. "Add / Remove Programs") from the Windows Control Panel or by choosing "Uninstall DelphiDabbler CodeSnip" from the program's start menu group.
147
+
Features", a.k.a. "Add / Remove Programs") from the Windows Control Panel or by
148
+
choosing "Uninstall DelphiDabbler CodeSnip" from the program's start menu group.
148
149
149
150
Administrator privileges will be required to uninstall CodeSnip. Windows Vista
150
151
to Windows 10 with UAC prompts enabled will prompt for an admin password if
*[Bug Reports and Features](#bug-reports-and-features)
11
12
12
13
## Overview
13
14
@@ -21,41 +22,53 @@ CodeSnip requires Windows 2000 or later and Internet Explorer 6 or later, althou
21
22
22
23
## Installation
23
24
24
-
CodeSnip is installed and removed using a standard Windows installer. Administrator privileges are required for installation.
25
+
The standard edition of CodeSnip is installed and removed using a standard Windows installer. Administrator privileges are required for installation.
26
+
27
+
The portable edition has no installer. Simply follow the instructions in the [read me file](https://github.com/delphidabbler/codesnip/blob/master/Docs/ReadMe.txt) that is included in the download zip file.
25
28
26
29
## Support
27
30
28
-
The following support is available for CodeSnip:
31
+
The following support is available CodeSnip users:
29
32
30
33
* A comprehensive help file.
31
34
* A [read-me file](https://github.com/delphidabbler/codesnip/master/Docs/ReadMe.txt)<sup> *</sup> that discusses installation, configuration, updating and known issues.
There's also plenty of info available on how to compile CodeSnip from source - see below.
36
39
37
40
<sup>*</sup> These links take you to the most recent version of the documents -- they can change from release to release.
38
41
39
-
40
42
## Source Code
41
43
42
-
Up to and including release 4.13.1 the project's source code was maintained in a Subversion repository on [SourceForge](https://sourceforge.net/p/codesnip/code/). The Subversion repo was converted to Git in October 2015 and imported to GitHub. All releases from v3.0.0 are marked by tags in the form `version-x.x.x` where `x.x.x` is the version number.
44
+
CodeSnip's source code is maintained in the [`delphidabbler/codesnip`](https://github.com/delphidabbler/codesnip) Git repository on GitHub†.
45
+
46
+
[Git Flow](http://nvie.com/posts/a-successful-git-branching-model/) methodology has been adopted, with the exception of some branches that have been used in abortive attempts to start work on CodeSnip 5.
47
+
48
+
The following branches existed at the time when CodeSnip v4.16.0 was released:
49
+
50
+
*`master`: Always reflects the state of the source code as of the latest release.‡
51
+
*`develop`: Main development branch. The head of this branch contains the latest development code.
52
+
*`pagoda`: An abortive attempt at developing CodeSnip 5. Work on this branch has halted. It does not follow GitFlow methodology. ***Do not use this branch: it may be pruned.***
53
+
*`pavilion`: Another attempt at working on CodeSnip 5. It branched off `pagoda` and it's future is uncertain. Again it does not follow GitFlow methodology.
54
+
55
+
New features and most bug fixes are worked on in `feature/xxxx` branches locally. They are merged into `develop` as they are completed and the branches are deleted.
43
56
44
-
> Note that any branches that were created and deleted in the Subversion repo are missing from the Git history. So, for full details of the the project's history from v3.0.0 to v4.13.1 please refer to the old Subversion repo on SourceForge.
57
+
**Note** that the default branch on GitHub is `develop` rather than `master`. This is because that's where all the work takes place. If you want to see the state of play at the last release make sure to switch to `master`.
45
58
46
-
Following tag `version-4.13.1` the [Git Flow](http://nvie.com/posts/a-successful-git-branching-model/) methodology was adopted. The exception is the `pagoda` branch that sits outside Git Flow. This branch was originally planned to be the CodeSnip v5 development branch (see [below](#codesnip-5-development) for details).
59
+
> † Up to and including v4.13.1 the source code was kept in a Subversion repository on SourceForge. It was converted to Git in October 2015 and imported into GitHub. All releases from v3.0.0 are marked by tags in the form `version-x.x.x` where `x.x.x` is the version number. None of the Subversion branches made it through the conversion to Git, so to see a full history look at the old [SourceForge repository](https://sourceforge.net/p/codesnip/code/).
47
60
48
-
Up to and including release 4.13.1, `master` is simply a copy of the old Subversion `trunk` and, as such, contains various development commits along with numerous commits related to management of Subversion. After release 4.13.1, and the addition of this read-me file, `master` contains only commits relating to an actual release.
61
+
> ‡ All the converted Subversion code was committed to `master`, making it a copy of the old Subversion `trunk`. As such`master`contains various development commits along with numerous commits related to management of Subversion. After release 4.13.1, and the the first commit of this read-me file, `master` contains only commits relating to actual releases.
49
62
50
63
### Contributions
51
64
52
-
To contribute to the project please fork the repository on GitHub. Create a feature branch off the development branch. Make your changes to that branch then submit a pull request on GitHub.
65
+
To contribute to the project please fork the repository on GitHub. Create a feature branch off the `develop` branch. Make your changes to the feature branch then submit a pull request via GitHub.
53
66
54
67
### Compiling
55
68
56
-
`master`and each branch will have a file in the root directory named `Build.html` that gives detailed information about how to compile CodeSnip.
69
+
`master`has a file in the root directory named [`Build.html`](https://htmlpreview.github.io/?https://github.com/delphidabbler/codesnip/blob/master/Build.html) that gives detailed information about how to compile the current release of CodeSnip.
57
70
58
-
There is also an [FAQ](https://github.com/delphidabbler/codesnip-faq) -- (see [Support](#support) above).
71
+
There is also a [Compiling & Source Code FAQ](https://github.com/delphidabbler/codesnip-faq/blob/master/SourceCode.md).
59
72
60
73
## Change Log
61
74
@@ -65,7 +78,7 @@ The program's current change log can be found in the file `CHANGELOG.md` in the
65
78
66
79
## License
67
80
68
-
The program's EULA, which gives full details of the license applying to the latest release, can be found in the file `Docs\License.html` in the `master` branch. The license has changed between releases, so if you need to see an older one, select the appropriate `version-x.x.x` tag and read the older version of the file.
81
+
The program's EULA, which gives full details of the license applying to the latest release, can be found in the file [`Docs\License.html`](https://htmlpreview.github.io/?https://github.com/delphidabbler/codesnip/blob/master/Docs/License.html) in the `master` branch. The license has changed between releases, so if you need to see an older one, select the appropriate `version-x.x.x` tag and read the older version of the file.
69
82
70
83
Most of the original code is made available under the [Mozilla Public License v2](https://www.mozilla.org/MPL/2.0/).
0 commit comments