1
0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-01-09 17:38:00 +00:00
putty-source/macosx
Simon Tatham a1f3b7a358 Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.

User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).

One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.

[originally from svn r9214]
2011-07-14 18:52:21 +00:00
..
info.plist Thanks to D H Becker for sending in an icon. I'd have liked to have 2005-03-10 20:11:27 +00:00
osx.h Initial checkin of a native Mac OS X port, sharing most of its code 2005-02-15 21:45:50 +00:00
osxclass.h Bring the OS X front end up to date with recent changes to the main 2007-02-18 15:59:38 +00:00
osxctrls.m Support for Windows PuTTY connecting straight to a local serial port 2006-08-28 10:35:12 +00:00
osxdlg.m Bring the OS X front end up to date with recent changes to the main 2007-02-18 15:59:38 +00:00
osxmain.m r8305 made platform_x11_best_transport[] obsolete, but there still seem to be a 2009-01-04 23:36:24 +00:00
osxsel.m Initial checkin of a native Mac OS X port, sharing most of its code 2005-02-15 21:45:50 +00:00
osxwin.m Centralise generation of the control sequences for arrow keys into a 2010-03-06 15:50:26 +00:00
putty.icns Thanks to D H Becker for sending in an icon. I'd have liked to have 2005-03-10 20:11:27 +00:00
README.OSX Post-release destabilisation! Completely remove the struct type 2011-07-14 18:52:21 +00:00

This directory contains a Mac OS X port of PuTTY/pterm, running as a
native Aqua GUI application.

THIS PORT IS CURRENTLY UNFINISHED AND EXPERIMENTAL. It is _not_
considered to be of release quality, even if you've found it (and
are reading this) in a PuTTY release source archive. You are welcome
to try using it, but don't be surprised at unexpected behaviour. I'm
not kidding.

In particular, I have not yet decided where OS X PuTTY should store
its configuration data. Options include storing it in ~/.putty to be
compatible with Unix PuTTY, storing it wherever is compatible with
Mac Classic PuTTY, storing it in a natively OS X location, or
sorting out the `config-locations' wishlist item and doing all
three. Therefore, if you start using this port and create a whole
load of saved sessions, you should not be surprised if a future
version of the port decides to look somewhere completely different
for the data and therefore loses them all. If that happens, don't
say you weren't warned!

Other ways in which the port is currently unfinished include:

Bit rot
-------

 - the conversion of the old fixed-size 'Config' structure to the
   new dynamic 'Conf' was never applied to this directory

 - probably other things are out of date too; it would need some
   work to make it compile again

Missing terminal window features
--------------------------------

 - terminal display is horribly slow

 - fonts aren't configurable

 - several features are unimplemented in the terminal display:
   underlining, non-solid-block cursors, double-width and
   double-height line attributes, bold as font rather than as
   colour, wide (CJK) characters, combining characters.

 - there's no scrollbar

 - terminal window resizing isn't implemented yet

 - proper window placement (cascading down and right from the
   starting position, plus remembering previous window positions per
   the Apple HIG) is not implemented

Missing alert box features
--------------------------

 - warn-on-close isn't implemented

Missing input features
----------------------

 - use of Alt+numberpad to enter arbitrary numeric character codes
   is not yet supported

 - there's no Meta key yet. (I'd like to at least have the
   possibility of using Command rather than Option as the Meta key,
   since the latter is necessary to send some characters, including
   the rather important # on Apple UK keyboards; but trapping
   Command-<key> and sending it to the window rather than the
   application menu requires me to make a positive effort of some
   sort and I haven't got round to it yet. For those Mac users who
   consider their Command key sacrosanct, don't worry, this option
   _will_ be configurable and _will_ be off by default.)

 - there's no specials menu

 - mouse activity isn't supported (neither cut-and-paste nor xterm
   mouse tracking)

Missing terminal emulation features
-----------------------------------

 - currently no support for server-side window management requests
   (i.e. escape sequences to minimise or maximise the window,
   request or change its position and size, change its title etc)

 - window title is currently fixed

Other missing features
----------------------

 - no Event Log

 - no mid-session Change Settings