racket / racket/drracket

update drracket/scribblings/drracket/interface-essentials.scrbl with new screenshot and change text from 'status line' to 'status area'.

Open
#289 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Racket
Stars
516
Forks
103
PR merge metrics
No merged PRs in 30d

Description

ref #172 @rfindler

  1. update drracket/scribblings/drracket/interface-essentials.scrbl with new screenshot and change text from 'status line' to 'status area'. perhaps use annotated screenshot screen shot 2017-11-26 at 21 03 03 from https://github.com/racket/drracket/pull/172#issuecomment-347038169
  • new paragraph for 'signature boxes' with images of closed 'blue quarter circle', open, locked/unlocked, link to documentation.
    (currently 'The blue quarter circle in the upper right corner provides access to the summary information from the documentation.[...]' - rest of paragraph is 'status line')
  • new paragraph for 'status area' with annotated image
    (currently '[...]The status line at the bottom of DrRacket’s window provides information about the current line and position of the editing caret, whether the current file can be modified, and whether DrRacket is currently evaluating any expression. The recycling icon flashes while DrRacket is “recycling” internal resources, such as memory.')

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Open drracket/scribblings/drracket/interface-essentials.scrbl and compare the existing interface description with the annotated screenshot linked in the issue. Update the screenshot and wording for signature boxes and the status area, including the requested paragraphs and images; done means the file reflects those UI changes and the documentation builds successfully.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
50/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.