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
- Added new buttons to display the contents of the system and per-user config files.
17
+
- Renamed tab as "Paths & Files".
18
+
+ Implemented feature request #83 (https://sourceforge.net/p/codesnip/feature-requests/83/) to enable the name and port of any web service test server to be passed on command line by using the new "--test-server" command line option. This replaces hard-wired test server name & port that was activated using the now removed "-localhost" command line switch.
19
+
+ Fixed bug #96: "Some open / save dialogues too small" (https://sourceforge.net/p/codesnip/bugs/96/). The height of customised dialogue boxes was increased.
20
+
+ Updated operating system detection code to detect Windows 10 TH2.
21
+
+ New photo of Sophie the dog added to the Easter egg slide show!
22
+
+ Updated help file re About Box changes.
23
+
14
24
Release v4.13.2 of 20 February 2016
15
25
+ Updated and corrected hints displayed in main window.
16
26
+ Changed some menu options and associated dialogue box captions.
CodeSnip is an open source code bank for storing and viewing your code snippets. While it can manage snippets in any source language, it is focussed mainly on Pascal and Delphi code for which additional features are available.
@@ -18,21 +27,47 @@ CodeSnip requires Windows 2000 or later and Internet Explorer 6 or later, althou
18
27
19
28
CodeSnip is installed and removed using a standard Windows installer. Administrator privileges are required for installation.
20
29
30
+
## Bugs & Feature Requests
31
+
32
+
Bugs can be reported using the [Bug Tracker](https://sourceforge.net/p/codesnip/bugs/) on SourceForge. Info on how best to report bugs is provided on the tracker.
33
+
34
+
Feature requests can be made on the [Feature Request Tracker](https://sourceforge.net/p/codesnip/feature-requests/) on SourceForge. Once again info on how to proceed is provided.
35
+
36
+
> In time the bug and feature request trackers will be moved to GitHub.
37
+
38
+
## Support
39
+
40
+
There's quite a lot of support available for CodeSnip:
41
+
42
+
* A comprehensive help file.
43
+
* A [read-me file](https://raw.githubusercontent.com/delphidabbler/codesnip/master/Docs/ReadMe.txt)<sup>*</sup> that discusses installation, configuration, updating and known issues.
44
+
* A dedicated set of [web pages](http://delphidabbler.com/url/codesnip-home).
45
+
* An [FAQ](http://wiki.delphidabbler.com/index.php/FAQs/CodeSnipAppUsing).
46
+
* A [discussion group](https://sourceforge.net/p/codesnip/discussion) on SourceForge (albeit barely used!).
47
+
* An [RSS news feed](http://delphidabbler.com/feeds/site-news-feed?id=codesnip). This can also be accessed via the program.
48
+
* A [Google+ page](https://plus.google.com/u/0/b/108251259814638768561/108251259814638768561/posts).
49
+
* A [Blog](http://codesnip-app.blogspot.co.uk/).
50
+
* A [privacy statement](https://raw.githubusercontent.com/delphidabbler/codesnip/master/Docs/Privacy.txt)<sup>*</sup> that provides information about any personal information stored by the program and what info is transmitted over the net.
51
+
52
+
There's also plenty of info available on how to compile CodeSnip from source - see below.
53
+
54
+
<sup>*</sup> These links take you to the most recent version of the documents -- they can change from release to release.
55
+
21
56
## Source Code
22
57
23
58
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 on 21 5 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.
24
59
25
-
> 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.
60
+
> 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.
26
61
27
-
Following tag `version-4.13.1` the [Git Flow](http://nvie.com/posts/a-successful-git-branching-model/) methodology was adopted, with the exception that development work on CodeSnip v5 exists outside Git Flow in the `pagoda`and `parsnip` branches (See below for details).
62
+
Following tag `version-4.13.1` the [Git Flow](http://nvie.com/posts/a-successful-git-branching-model/) methodology was adopted, with the exception that development work on CodeSnip v5 exists outside Git Flow in the `pagoda`branch (See below for details).
28
63
29
-
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. After release 4.13.1, and the addition of this read-me file, `master` contains only commits relating to an actual release.
64
+
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.
30
65
31
66
### Contributions
32
67
33
68
Contributions are welcome. Just fork the repo and create a feature branch off the `develop` branch. Commit your changes to your feature branch then submit a pull request when ready.
34
69
35
-
If you are contributing to CodeSnip 5 development please create your feature branch off the `pagoda` branch instead.**Don't use the `parsnip` branch.**
70
+
If you are contributing to CodeSnip 5 development please create your feature branch off the `pagoda` branch instead.
36
71
37
72
### Compiling
38
73
@@ -46,11 +81,11 @@ The program's current change log can be found in the file `Docs/ChangeLogs/Chang
46
81
47
82
## License
48
83
49
-
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` and read the older version of the file.
84
+
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.
50
85
51
86
Most of the original code is made available under the [Mozilla Public License v2](https://www.mozilla.org/MPL/2.0/).
52
87
53
-
The [CodeSnip Compiling & Source Code FAQ](http://wiki.delphidabbler.com/index.php/FAQs/CodeSnipAppSource) may be useful if you have any queries about re-using CodeSnip source in other projects.
88
+
The [CodeSnip Compiling & Source Code FAQ](http://wiki.delphidabbler.com/index.php/FAQs/CodeSnipAppSource) may be useful if you have any queries about re-using CodeSnip source in other projects.
54
89
55
90
## CodeSnip 5 Development
56
91
@@ -62,4 +97,8 @@ At present the direction CodeSnip is being taken is to:
62
97
2. Increase the focus on the user's own code while downplaying the importance of code downloaded from the DelphiDabbler [Code Snippets database](http://snippets.delphidabbler.com/). This will still be available but will be very much an add on, like [SWAG](http://swag.delphidabbler.com/) is at present.
63
98
3. Remove the program's dependency on web services provided by [DelphiDabbler.com](http://delphidabbler.com) given the current uncertainty over that websites future.
64
99
65
-
Comments on these ideas are welcome - just create an [issue](https://github.com/delphidabbler/codesnip/issues) and label it "CodeSnip 5 pagoda".
100
+
Comments on these ideas are welcome - just create a [feature request](https://sourceforge.net/p/codesnip/feature-requests/) and select the `v5 (pagoda)` milestone.
101
+
102
+
## Donate
103
+
104
+
If you've found the program useful please consider making a donation to help cover costs. Donations are accepted by [PayPal](http://delphidabbler.com/url/donate-cs) in British Pounds (GBP) -- [see common exchange rates](http://www.xe.com/currency/gbp-british-pound).
0 commit comments