Update documentation

This commit is contained in:
cyd01
2022-01-24 09:11:50 +01:00
parent d0b53ec0b9
commit dd009f24e4
7 changed files with 11 additions and 1304 deletions
-1
View File
File diff suppressed because one or more lines are too long
-1286
View File
File diff suppressed because it is too large Load Diff
-6
View File
File diff suppressed because one or more lines are too long
+1 -1
View File
@@ -60,7 +60,7 @@
[Download](pages/download.md)
[Chanlog](pages/chanlog.md)
[Donation](pages/donation.md)
[DONATION](pages/donation.md)
[Contact](pages/contact.md)
[comment]: # [gimmick:theme](united)
+1 -1
View File
@@ -3,7 +3,7 @@
| ![English](../img/en.gif) KiTTY is completely free | ![French](../img/fr.gif) Bien sur KiTTY est complètement gratuit |
|:--:|:--:|
|Development and maintenance takes much time and effort.<br/> <br/>Donations of any amount are welcomed to offset the costs of hosting the website. Thank you for downloading KiTTY, and please consider a donation to support this project.<br/> <br/>We consider 10 USD / 10 EUR / 0.03 BTC as a fair award regarding the whole work that has been done.<br/> <br/>Thanks in advance, but feel perfectly free not to donate if you don't like to, or if you don't appreciate the result.|Mais comme tout logiciel il a demandé beaucoup de temps et de sueur.<br/> <br/>Toute donation, même petite est la bienvenue. Elle seront utilisées notamment pour payer la maintenance du site web. Si vous souhaitez participer, vous pouvez faire un don.<br/> <br/>10 USD / 10 EUR / 0.03 BTC nous semble être une juste récompense en regard du travail effectué.<br/> <br/>D'avance merci, mais ne vous sentez pas obligé si vous n'en avez pas envie, ou si vous n'appréciez pas le travail réalisé. |
|Development and maintenance takes much time and effort.<br/> <br/>Donations of any amount are welcomed to offset the costs of hosting the website. Thank you for downloading KiTTY, and please consider a donation to support this project.<br/> <br/>We consider 12 USD / 10 EUR / 0.0003 BTC as a fair award regarding the whole work that has been done.<br/> <br/>Thanks in advance, but feel perfectly free not to donate if you don't like to, or if you don't appreciate the result.|Mais comme tout logiciel il a demandé beaucoup de temps et de sueur.<br/> <br/>Toute donation, même petite est la bienvenue. Elle seront utilisées notamment pour payer la maintenance du site web. Si vous souhaitez participer, vous pouvez faire un don.<br/> <br/>12 USD / 10 EUR / 0.0003 BTC nous semble être une juste récompense en regard du travail effectué.<br/> <br/>D'avance merci, mais ne vous sentez pas obligé si vous n'en avez pas envie, ou si vous n'appréciez pas le travail réalisé. |
| Using [www.paypal.com](https://www.paypal.com "Paypal") | Using [www.bitcoin.org](../bitcoin.html "bitcoin") |
|:--:|:--:|
+8 -8
View File
@@ -1,26 +1,26 @@
Waou so much passion !
First let's share some history.
I've started to work on PuTTY in **2003** with the version **0.53** of the project. At that time, no source management solution (no git, svn, cvs or any other). Remember I was not a developer. I was an ops that need a software to connect servers through telnet (yes!). I liked PuTTY but I though features were missing. My first need was to automate the password negotiation on solaris or hp-ux servers: no Linux one ... and no GUI. The second need was to be able to define a specific icon for each terminal window ... the story has begun. That was the creation of **MOD_PERSO** patch (called **PERSOPORT** at this time).
Let's share some history.
I've started to work on PuTTY in **2003** with the version **0.53** of the project. At that time, I did not use any source management solution (no git, svn, cvs or any other). The fact is that I was not a developer. I was an ops that need a software to connect servers through telnet (yes!). I liked PuTTY but I though features were missing. My first need was to automate the password negotiation on solaris or hp-ux servers: no Linux one ... and no GUI. The second need was to be able to define a specific icon for each terminal window ... the story has begun. That was the creation of **MOD_PERSO** patch (called **PERSOPORT** at this time).
My fork was build directly on my desktop computer (under Windows and GCC) and my work remains into a directory on my professional machine, nothing else.
Each time a new PuTTY version was released I worked to merge it with my modifications.
In **2006** I've started to share my work. That was the creation of the [KiTTY web site](https://www.9bis.net/kitty) with the version **0.58**. After that version, people that found KiTTY useful began to ask for integration with other PuTTY forks (LePuTTY, PuTTYTray, TuTTY, RuTTY ...). Here began **MOD_*** patches. The KiTTY source files were now downloadable from the web site: a simple **.tar.gz** file that is always available [here](https://www.9bis.net/kitty/files/kitty_src.tar.gz).
In **2005** I've started to share my work. That was the creation of the [KiTTY web site](https://www.9bis.net/kitty) with the version **0.58**. After that version, people that found KiTTY useful began to ask for integration with other PuTTY forks (LePuTTY, PuTTYTray, TuTTY, RuTTY ...). Here began **MOD_*** patches. The KiTTY source files were now downloadable from the web site: a simple **.tar.gz** file that is always available [here](https://www.9bis.net/kitty/files/kitty_src.tar.gz).
KiTTY became more and more popular and many requests were integrated.
In **2010** I've started to use a version control system to be able to trace all the modifications I've made. In my company we used **subversion** and the very first versioned KiTTY version was **0.60.66.30**.
Late in **2013** the **0.63** PuTTY version was released. It was a big bang. The internal session settings structure was completely rewritten. It was a huge work to accomplish the merge with KiTTY. I've decided that I need help to maintain KiTTY in the future. Few months after, I've decided to share not only the source code, but the version control system too. That was the beginning of **svn** on my [web site](https://ken.9bis.com/public/websvn/listing.php?repname=Sandbox&) in **2015**.
Finally in **2018** I've switch to **git** with version **0.70**, and this Gihub repository opened in october the same year.
Finally in **2018** I've switch to **git** with version **0.70**, and the [Gihub repository](https://github.com/cyd01/KiTTY) opened in october the same year.
Version **0.71** was another revolution. Some of the MOD_* patches, I did not write (remember I've merge them), became broken by the last PuTTY release and I had to sacrifice some of them (cygterm, background image ...). I've asked for some help, and decided to switch completely to English (web site, comment, release notes ...) in early **2019**. At mid **2019** I abandoned the old multi-language version of the web site to the current English-only one, based on markdown files.
Version **0.71** was another revolution. Some of the MOD_* patches, I did not write (remember I've merge them), became broken by the last PuTTY release and I had to sacrifice some of them (cygterm, background image ...). I've asked for some help, and decided to switch completely to English (web site, comment, release notes ...) in early **2019**. At mid **2019** I abandoned the [old multi-language version of the web site](https://web.archive.org/web/20181231164209/http://www.9bis.net/kitty/) to the current English-only one, based on markdown files.
Now, why not to make KiTTY compatible with Linux. First because in 2003 I simply did not think of it. Second, like I wrote, I'm not the author of all KiTTY patches, and I don't know if they are all compatible. And last, I am also a KiTTY user and I use KiTTY on Windows machine only (remember it is the only platform that does not have a ssh client in standard). When I am on a Linux GUI, I simply use **ssh** to jump to other machine. So I won't work on the Linux compatibility: I don't even know how to achieve it, and I really don't have time to make it. KiTTY is not my real job even if I really like to work on it.
Now, why not to make KiTTY compatible with Linux. First because in 2003 I simply did not think of it. Second, like I wrote, I'm not the author of all KiTTY patches, and I don't know if they are all compatible. And last, I am also a KiTTY user and I use KiTTY on Windows machine only (remember it is the only platform that did not have a ssh client in standard). When I am on a Linux GUI, I simply use **ssh** to jump to other machine. So I won't work on the Linux compatibility: I don't even know how to achieve it, and I really don't have time to make it. KiTTY is not my real job even if I really like to work on it.
Anyway I will try to add all the comments people need to understand my modifications. I agree with you @lars18th, I could add some generic informations to **kitty.h** file.
And above all, I've never refused to merge interesting patch in KiTTY ... but the fact is that along these 13 years I don't receive much help. I think people often mix open source with free software. Anyway feel free to propose such a patch.
And above all, I've never refused to merge interesting patch in KiTTY ... but the fact is that along these 17 years I don't receive much help. I think people often mix open source with free software. Anyway feel free to propose such a patch.
All the best
Cyd
+1 -1
View File
@@ -10,7 +10,7 @@ document.forms['paypal'].submit();
<center>
<form action="https://www.paypal.com/cgi-bin/webscr" name="paypal" method="post"><input type="hidden" name="cmd" value="_s-xclick">
<input type="hidden" name="hosted_button_id" value="65VYL8F5AD57G"><input type="image" alt "Donate" title="cyril.dupont (at) libertysurf.fr" src="img/paypal_donate.png" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!">
<input type="hidden" name="hosted_button_id" value="65VYL8F5AD57G"><input type="image" alt "Donate" title="cyril.dupont (at) free.fr" src="img/paypal_donate.png" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!">
<img alt="" border="0" src="https://www.paypalobjects.com/fr_FR/i/scr/pixel.gif" width="1" height="1"></form>
</center>