DonationCoder.com Software > FARR Plugins and Aliases

FARR plugin: PuTTY (preliminary discussion)

(1/3) > >>

ewemoa:
I'm considering a PuTTY plugin.  I have some code that seems to work for various definitions of "PuTTY".

I don't understand why there are so many flavors of PuTTY.  Below is a summary of what I've learned so far about the various flavors.  If you happen to notice any of it is incorrect or something relevant is omitted, I would appreciate being informed.

   PuTTY (the original)
     http://www.chiark.greenend.org.uk/~sgtatham/putty/
     * registry-based sessions
       * putty.exe -load "session name"
       * HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\Sessions

   KiTTY
     http://kitty.9bis.com/
     * registry-based sessions
       * kitty.exe -load "session name"
       * HKEY_CURRENT_USER\Software\9bis.com\KiTTY\Sessions

   KiTTY Portable
     http://kitty.9bis.com/
     * file-based sessions
       * kitty_portable.exe -load "session name"
       * <exe-folder>/Sessions/<encodeURIComponent(session-name)>

   PuTTY Portable
     http://portableapps.com/apps/internet/putty_portable
     * registry-based sessions
       * putty.exe -load "session name"
       * HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\Sessions

   portaPuTTY
     http://code.google.com/p/portaputty/
     * file-based sessions
       * putty.exe -load "session name"
       * <exe-folder>/.putty/sessions/<encodeURIComponent(session-name)>

   PuTTY Tray
     http://www.xs4all.nl/~whaa/putty/
     * file-based sessions
       * putty.exe -loadfile "session name"
       * putty.exe -file "session name"
       * <exe-folder>/sessions/<encodeURIComponent(session-name)>
     * registry-based sessions
       * putty.exe -load "session name"
       * HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\Sessions

mouser:
I don't understand why there are so many flavors of PuTTY
--- End quote ---

not to open up a can of worms but this is one of the few things i consider troublesome about open source stuff.. the possibility of grenade-like-fragmentation-forking.

if it were me i would just write one plugin with support for file-based or registry-based sessions, depending on the putty version i personally used, and then with an option for the registry key or directory path so users could customize that.  then if someone else wants to modify your plugin to support registry (if you choose file), or vice versa, they can modify your plugin.  i think it's too much to expect you personally to write your plugin to handle all of these cases.

mouser:
of course the *ideal* solution would be if the plugin could keep a list of ALL registry paths of all the dif putty versions, and all file paths, and then display the combined list of all sessions found.. but that seems like maybe more effort than its worth.

ewemoa:
Thanks for the comments.

I considered trying something like the combined approach you described, but I wasn't sure I could come up with something consistent.  I think if all of the different forks used mutually exclusive locations it would be straight-forward, but they don't seem to (i.e. there is some overlap).  May be there is some way to make sense of this that I am not seeing :)

bgd77:
I was a little shocked to see that there are so many PuTTYs. In the company we only use the original version, I do not think that any colleague of mine has heard of the other variants.  So, thanks for the information, I'll have to research the other variants to see if they bring anything new and useful for us.  :Thmbsup:

Anyway, this plugin would be a great one! If you have problems with the various flavors, you could try, at first, to make the plugin work only with the original version of it and after that try to adapt it to all of them.

Navigation

[0] Message Index

[#] Next page