1. 28 Nov, 1997 1 commit
  2. 03 Oct, 1997 2 commits
    • Andrew Hodgkinson's avatar
      Version in Messages taken to 1.22 (03 Oct). · 4d616ea4
      Andrew Hodgkinson authored
      Updated Res files in appropriate builds to hold various (similar) Choices
      designs.
      
      Choices related menus were flagged as Shared, but none of the dialogues
      (including ColourDBox) were - potential future problems, though shouldn't
      cause any leaks at present. This has been sorted out anyway.
      
      Encoding function encoding_init no longer returns an error from
      toolbox_create_object, so the Encoding menu and all those attached
      to it do not have to be present (e.g. the Customer build).
      
      SUB, SUP, STRIKE and U supported. U underlines the baseline of the body text
      font, whilst STRIKE will go through roughly the middle of the lower case
      chars even if the font is SUP or SUB. Note that Navigator appears to shift
      the underline point for SUB and SUP; it may be necessary to copy this
      behaviour, but testing on real sites must proceed before that. There could
      also be a problem with the automatic lowering of font size, which Navigator
      doesn't do, so any FONT SIZE = -n commands could make it too small. Again,
      this needs testing on real sites.
      
      'http://' is added to URLs with no protocol specified, unless they start with
      'ftp.', in which case the new behaviour is to add 'ftp://'.
      
      Choices code altered to do less error checking on components! They should be
      able to be missing without raising errors. Referencing of the subwindow
      array changed from *(subwindows + number) to subwindows[number].
      
      Made trace_tag_name code look pretty...
      
      reformat_useless_token now checks tagno is non-zero.
      
      User Agent string setting now done through URL_GetURL, on a per-session
      basis.
      
      Ellipsis character removed from all Messages files, replaced with '...'.
      There's little difference between the two in an outline font, and in System
      font the latter looks much better. Smart quotes left in, as they look
      better in all cases.
      4d616ea4
    • David Brown's avatar
  3. 01 Oct, 1997 1 commit
  4. 29 Sep, 1997 1 commit
  5. 26 Sep, 1997 1 commit
    • Andrew Hodgkinson's avatar
      Added support for HTMLLib HttpEndParse call. · 8c9a9091
      Andrew Hodgkinson authored
      Text items with no VALUE specified in the HTML were not cleared on
      hitting a Reset button as the text field of the token is NULL; fixed.
      SELECT lists with no default selection item were not being changed
      on hitting a Reset button; fixed. In radio groups with no default
      selection specified, no item will be selected. This goes against
      the HTML 2 spec but allows broken Navigator-esque forms behaviour.
      In consequence, radios can be deselected by clicking on the same
      one twice. I'd fixed the flickering experienced when doing this
      recently, but that, now, is irrelevant, since the state of a radio
      must always change.
      
      Reformatter's new 'find width of a SELECT field' didn't account for
      the width of <none> and <many> items, and now does (particularly
      important for broken items with no OPTION contents).
      
      Under certain circumstances, illegally named targets would open in the
      ancestor rather than a new window - a deliberate decision in the code,
      but now reversed due to a test suite failure; they'll open in a new
      window instead.
      
      Altered the left hand indent handling for lists so that headings and
      body text follow the Navigator 48 pixel indent and the bullet point
      items drop to the left of the left hand margin, rather than sitting
      on the margin with the text indented to the right.
      
      Tightened up the hotlist_load_directory checking of URLs, so that
      only those with '://' in - i.e. look fully specified - are accepted.
      HTML files are loaded into a new directory now.
      
      Items without a descriptive title in hotlist_new_url will have the URL
      substituted in instead. White space before and after descriptions and
      after URLs is stripped. Directories with zero length names or null
      strings (after white space is stripped) will still be created, with a
      generic name (see Messages, token 'HotlistUntitled').
      8c9a9091
  6. 22 Sep, 1997 1 commit
    • Andrew Hodgkinson's avatar
      Now working on source merged with Kevin Bracey's internationalisation support.... · f61afadd
      Andrew Hodgkinson authored
      Now working on source merged with Kevin Bracey's internationalisation support. UNIFONT is undefined in the Make File for now. All Res and
      
      Choices files updated appropriately.
      
      Having sorted out the old Choices and Messages to form Choices, Controls
      and Messages, this build has had the same cleaning up done internally.
      This includes greater consistency in naming schemes and the removal of
      the inconsitent choices items - e.g. Choices file entries saying 'delay
      images' and 'plain backgrounds' where internally all the flags say 'show
      images' and 'show backgrounds'. ChoiceDefs.h and CtrlDefs.h added to
      clarify the meaning of some fields, though usage of these is not 100%
      in the source (there are cases where parameters are passed through to
      functions as ints, and those functions still check these against hard
      coded values rather than the #define stuff).
      
      Fetcher status return bits (connected, sent request, etc.) now reflected
      in status bar. Progress during fetchs to files are reported by %, where
      the size of the object is known. Exceeding 100% drops back to a byte
      counter, in case the estimated size was wrong. The progress counter
      may be updated after specific delays, rather than 'as often as possible',
      to reduce flicker (as requested by D.Brown some time ago).
      
      I've done a small rewrite of the fetch prioritisation scheme in FetchPage.c;
      how well this performs in general use across different processor speeds
      remains to be tested, but certainly it has some advantages. For each small
      fetch window before the rewrite, a 4cs tight loop was entered - this gave a
      noticable and substantial drain to the Desktop performance if more than one
      was opened. Now, several can be up at once with little hit. The actual file
      fetch is on half the priority it was before, with all others taken back
      just a bit - e.g. from 20cs per poll to 15cs per poll for flat out
      reformatting. You don't seem to lose much time on the format in practice,
      and the Desktop feels quite a bit lighter at the same time. There's the
      potential for smoother frameset loading in this scheme, too.
      
      When Shift+Clicking on a link meant you still fetched inside the main
      browser window, several fetches could occur in a frameset - one per frame.
      However, now that you can only do this by clicking on a link that leads to
      non-displayable data - or by turning off the small fetch windows by
      setting UseSmall to 'no' in Choices - a bug where fetchpage_preprocessed
      would stop such fetches as new ones were started was revealed.
      The API to frames_abort_fetching has now been extended to include a
      'stop file spooling too' flag, allowing a fix to be made by having
      fetchpage_preprocess's calls not set this (and it doesn't check the
      savelink flag is unset before proceeding, since frames_abort_fetching
      does that implicitly now).
      
      Had left the RAM transfer buffer at 16 bytes (from testing) accidentally...
      Oops. Upped it to 4K. In addition, when loading data by RAM transfer,
      the browser didn't notice if a RAMFetch bounced during the transfer. It
      would be treated as a 'first' RAMFetch bounce, basically, and try to go to
      file transfer - oops. Fixed.
      f61afadd
  7. 18 Sep, 1997 1 commit
    • Kevin Bracey's avatar
      Encoding support added: if UNIFONT is defined then the browser will attempt to... · 9dba8115
      Kevin Bracey authored
      Encoding support added: if UNIFONT is defined then the browser will attempt to use the system font to render Unicode characters (new
      
      International module required). If not defined, the browser will just
      handle Acorn Latin-1 characters, but HTMLLib will convert other encodings
      into Latin-1. Must keep the UNIFONT define in sync with HTMLLib (if
      defined HTMLLib outputs UTF-8, otherwise Acorn Latin-1).
      
      Still needed:
      
      Reverse encoding (converting form input etc back into the server's
      character set).
      Reparse when encoding changes.
      Setting of charset from an attribute on the <A> tag.
      9dba8115