mirror of
https://git.tartarus.org/simon/putty.git
synced 2025-04-15 01:58:05 -05:00
a101444d40
This gets us scalable icons that will go to extremely large sizes without the problems that arise from scaling up the output of mkicon.py, in which outlines become too thin because the script was mostly concerned with trying to squeeze all the desired detail into _tiny_ sizes. The SVG icons are generated by mksvg.py, which is a conversion of the existing mkicon.py. So the SVG files themselves are not committed in this repo; 'make svg' in the icons subdir will generate them. (I haven't decided yet whether this state of affairs should be permanent. Perhaps _having_ generated the SVGs via a similar program to the bitmap icons, we should regard the script as a discardable booster stage and redesignate the SVGs themselves as the source format for future modifications, so that they can be edited in Inkscape or similar rather than by tinkering with Python. On the other hand, perhaps keeping the script will make it easier to keep the icon family consistent, e.g. if changing the style of one of the shared visual components.) My plan is that we should stick with the output of the previous bitmap-generating script for all the _small_ icons, up to and including 48 pixels, because it does a better job at low resolution. (That was really what it was for in the first place: you can think of it as an analogue of a scalable-font hinting system, to tune the scaling for very low res so that all the important features are still visible.) I think probably I want to switch the 128-pixel icons used in the Mac icon file over to being rendered from the SVG (though in this commit I haven't gone that far, not least because I'll also need to prepare a corresponding black and white version). I haven't done extensive research yet to decide where I think the crossover point in between is.
This is the README for PuTTY, a free Windows and Unix Telnet and SSH
client.
PuTTY is built using CMake <https://cmake.org/>. To compile in the
simplest way (on any of Linux, Windows or Mac), run these commands in
the source directory:
cmake .
cmake --build .
Documentation (in various formats including Windows Help and Unix
`man' pages) is built from the Halibut (`.but') files in the `doc'
subdirectory using `doc/Makefile'. If you aren't using one of our
source snapshots, you'll need to do this yourself. Halibut can be
found at <https://www.chiark.greenend.org.uk/~sgtatham/halibut/>.
The PuTTY home web site is
https://www.chiark.greenend.org.uk/~sgtatham/putty/
If you want to send bug reports or feature requests, please read the
Feedback section of the web site before doing so. Sending one-line
reports saying `it doesn't work' will waste your time as much as
ours.
See the file LICENCE for the licence conditions.