R. Baecker and A. Marcus. Human Factors and Typography for More Readable Programs. Addison--Wesley, Reading, MA, USA, 1990.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....an opportunity for review by replaying the entire film at 12 times normal speed, thereby generating visual patterns unique to each method and not obvious at normal speed. The film goes beyond a step by step presentation of the algorithms, commu48 Figure 5. Page 1 of a designed and typeset program [3] Output is on looseleaf 8.5x11 inch pages, each separated into four regions header (1) footnote area (17) main text column for code and most comments (3, right) and marginalia comments (3, left) Each file is a separate chapter with the filename as a large, bold title (2) Extra ....

....and therefore should be useful for debugging. Source Code Presentation: How Should Programs Look To debug a program, one must also view and think about source code from different perspectives. We therefore developed techniques for enhancing source code readability and comprehensibility [3, 13]. Program appearance has changed little since the first high level languages were developed in the 1960s. Unlike symbolic systems, such as circuits, maps, mathematics, and music, we lack sophisticated notations and conventions employing the tools of design and typography, such as typefaces, ....

[Article contains additional citation context not shown here]

Baecker, R.M., and Marcus, A. Human Factors and Typography for More Readable Programs. ACM Press, Addison-Wesley, Reading, Mass., 1990.

....part of its human computer interaction: visualizations of programs. There have been many contributions related to this topic: pretty printing in text editors [6] and syntax directed editors [8] program visualization [9] documentation of programs [4] and application of typography to programs [1]. However the interaction with these systems is far from satisfactory: it is usually made in a batch fashion and it is isolated from common programming tools such as compilers and debuggers. Our claim is that visualizations should be as easily customizable as in commercial applications. For ....

....(e, e] insert (e,x: l) if e x then e: x: l) else x: insert(e,l) dec insertsort: list(num) list(num) insertsort [ insertsort (x: l) insert(x,insertsort(l) The two expressions visualized in Fig. 4 are obtained on evaluating the expression insertsort[1,6,4,3] . The first one shows an expression where the two last elements of the original list are sorted, and the two first must still be inserted. The second figure shows the expression resulting after one rewriting step. The example shows that there are two rectangles for representing visually ....

Baecker, R.M., Marcus, A., Human Factors and Typography for More Readable Programs, ACM Press, 1990

....The user should be able to use a representation that facilitates comprehension; not one that has been designed to ease translation. On the other hand, the input to the language translator need not be burdened with formatting motivated syntax rules. An interesting study by Baecker and Marcus [1] suggests some ways in which appearance can affect human understanding of language documents. They devised a variety of ways of presenting C programs to improve their readability. 9 An example appears in Figure 1. Many other researchers have proposed particEncode phone number as a vector of ....

Ronald M. Baecker and Aaron Marcus. Human Factors and Typography for More Readable Programs. Addison-Wesley, Reading, Massachusetts, 1990.

....services and user interfaces of Pan are designed around familiar models, to encourage smooth integration into existing working environments. High quality typography is used for the visual presentation of text, a feature often not realized in editing interfaces. Studies by Baecker and Marcus [4] and by Oman and Cook [49] suggest the value of typography for program presentation. Language Description. Pan supports many languages, driven by a description of each. The descriptive medium is largely declarative. It supports the de nition of languages, but also includes speci cations for usage ....

Baecker, R. M., and Marcus, A. Human Factors and Typography for More Readable Programs. ACM Press, New York, New York, 1990. 29 Submitted to Transactions on Software Engineering and Methodology

....others, and in some cases, readability has been an issue when designing some languages. Visual enhancement can also be of assistance when understanding source code. Program visualization focuses on enhancing presentation of existing programs, their code and documentation. According to Baecker [BM90] the goal of program visualization is to facilitate the clear and correct expression of the mental images of the writer of computer programs and the communication of these mental images to the readers of such programs. Despite the importance of readability, most programs are not readable ....

.... the programmer a pretty printer view of the code plus hypertext capabilities: the user can point to the usage of a function and jump to its definition Baecker and Marcus proposed that programming languages must include a description of how they must be typeset as part of their definition [BM90] They also emphasized that program visualization must benefit not only from lexical but from syntactic and semantic information. In 1 Several tools are available under operating systems which until recently were not commonly used for most software development. 2 particular they focused on C, ....

Ronald M. Baecker and Aaron Marcus. Human Factors and Typography for More Readable Programs. Addison-Wesley, 1990.

....work with annotation of code led Belady, Evangelisti and Power to develop a diagrammatic annotation called a GREENPRINT [10] However this approach has now been outdated by typographic techniques made possible by high resolution graphics terminals and laser printers. Work by Baeker and Marcus [7, 8] saw the development of SEE, a pretty printer that formatted code in a book type style utilizing presentation techniques equivalent to those available in modern desktop publishing packages. SEE produces a device independent output using TROFF [44] Oman and Cook [56] showed empirically that the ....

Baecker R. M., Marcus A. Human Factors and Typography for more readable programs. Addison-Wesley Publishing Company, USA, 1990.

....relatively simple; however recent extentions to this work have used computerized typesetting and laser printing to provide a much improved presentation of source code. This has ranged from a simple utility to change the style of the font depending on keywords 1 to the SEE Program Visualizer ([36]) which automatically takes a set of C programs and formats a program book out of them. Knuth s ( 33] 1 BSD Unix Distribution, 1988 11 WEB system is similar, but combines the documentation and program in one document using a markup language. The 1980 s saw the beginning of modern SV ....

Baecker, R. M. & Marcus, A. Human Factors and Typography for More Readable Programs. Addison-Wesley, Reading(MA). 1990.

....stream of bits in the way an interpreter or compiler does. Even the programmers who used a simple VT100 style terminal in a single color, fixed pitch font can get a mental image that aids comprehension from the appearance of the indenting in their code ( 25] and the relative sizes of code blocks ([26]) 2.2.2 Visualization Because it contains the root word visual , visualization is often considered to be restricted to visible images (hence the coining of words like auralization) In fact, its primary meaning is to picture in the mind ( 24] so a visualization can result from input from ....

Baecker, R.M. & Marcus, A. Human Factors and Typography for More Readable Programs. Addison-Wesley, Reading, MA 1990.

....or implicit. It is important to note that this implies that concrete presentations of software documents are concrete visualisations. Concrete visualisations depict the actual document content either directly or by eliding part or all of the content. Much work has been done on such visualisations [4, 5, 6, 13, 16, 22, 26]. However, when people refer to software visualisation they are typically referring to abstract visualisations. Abstract visualisations also elide content, but typically depict implicit relationships between the elements of document content that are displayed. For example, a visualisation which ....

R.M. Baecker and A. Marcus.Human Factors and Typography for more readable programs. Addison-Wesley Publishing Company, USA, 1990.

.... editors presenting these languages graphically by simply sharing the textual representation and so implicitly sharing the objects (Watt, 1993) Finally, there is one other enhancement that can be made to traditional editing techniques; in the use of advanced typography in the presentation of text (Baecker and Marcus, 1988). As the syntax tags the text according to its syntactic category a further mapping from syntactic category to typographic style is possible. For instance, names used in defining OPS5 rules could always be presented in 12 point Times Bold, with the rest of the rule source text in 12 point Monaco. ....

Baecker, R. M., & Marcus, A. (1988). Human Factors and Typography for More Readable Programs: ACM Press.

.... 29, 34, 36] Another class of tools shows the dynamic execution of programs for debugging, profiling and for understanding run time behavior [15, 28] Other software visualization tools mainly focus on showing textual representations, some of which may be pretty printed to increase understanding [1, 13] or use hypertext in an effort to improve the navigability of the software [24] Typography plays a significant role in the usefulness of these textual visualizations. Many tools present relevant information in the form of a graph where nodes represent software objects and arcs show the relations ....

R. Baecker and A. Marcus. Human Factors and Typography for More Readable Programs. ACM Press, Addison-Wesley Publishing Company, 1990.

....of teaching widely used algorithms and data structures. Another class of tools shows the dynamic execution of programs for debugging, profiling and to understand run time behaviour. Other tools focus on showing textual representations, some of which may be pretty printed to increase understanding [18]. This paper is concerned with the class of software visualization tools designed for exploring software structures. The next section describes a hierarchy of cognitive issues which should be considered when designing a tool to assist in the exploration of software structures. 4 Cognitive design ....

R.M. Baecker and A. Marcus. Human Factors and Typography for More Readable Programs. ACM Press, AddisonWesley Publishing Company, 1990.

....and data structures. Another class of tools shows the dynamic execution of programs for debugging, profiling and for understanding run time behavior. Other software visualization tools mainly focus on showing textual representations, some of which may be pretty printed to increase understanding [4, 5] or use hypertext in an effort to improve the navigability of the software [6] Typography plays a significant role in the effectiveness of these textual visualizations. One class of software visualization tools, which we refer to as software exploration tools, presents graphical representations ....

R.M. Baecker and A. Marcus. Human Factors and Typography for More Readable Programs. ACM Press, Addison-Wesley Publishing Company, 1990.

....for hypermedia links. This source code documents will require the development of a novel formatting model that properly integrates the formal and informal material. The central problem is that automatic pretty printers operate not from lines of text, but rather from an abstract syntax tree [1, 15]. But in this new representation, the leaves of the abstract syntax tree will be intermixed with some other tree based representation for the informal material. No existing formatter or editor must coordinate between two tree representations, so a new formatting model will be required. The ....

Ronald M. Baecker and Aaron Marcus. Human Factors and Typography for More Readable Programs. Addison-Wesley, Reading, Massachusetts, 1990.

....data structures such as computer programs, distance may be measured in terms of path distance between nodes, rather than as an absolute measure. If the interest measure for data point x falls below a threshold k, then the information at that point is suppressed or elided (not displayed) [2]. In our experience, it is necessary to normalise the values returned by the DOI formula: this issue is further discussed in Section 3.5. Furnas describes several example systems, including a visualisation mechanism for C programs. In this system, program details around the user s focus of ....

....None of the systems reviewed above, nor the fisheye program visualisations presented in Section 2.3, provide contextual information about the contents of abstracted units when they are suppressed. Holophrasting, folding editors (such as Tioga) and Furnas s program fisheye views totally elide [2] suppressed text, replacing it with ellipses. They therefore o#er 19 Property OK Comment on Jaba s support 1. Integrated environment for editing and browsing 4 . Supports abstracted browsing of documentation as well as editing details (unlike Javadoc which only supports abstracted ....

[Article contains additional citation context not shown here]

RM Baecker and A Marcus. Human Factors and Typography for More Readable Programs. Addison-Wesley, 1990.

....information. Needless to say, a general system like AOPS does not handle specific details very well. One of its limitations is that since it is programming language independent, program code cannot be formatted. Language dependent automatic tools such as prettyprinters [10] and visual compilers [2] can be used to perform typographic duties on program code. Another limitation of AOPS is that the hypertext browser recognizes only ASCII characters and does not understand formatting commands. Hence users might want to strip the special formatting characters from the source file before using the ....

Baecker, R. and Marcus, A., Human Factors And Typography For More Readable Programs, Addison-Wesley, 1990.

....rather than individual files. This implied the use of implicit and explicit hypertext links and live links to special purpose editors. We also wanted to make full use of the power of modern displays by providing the user with a high quality textual display such as recommended by Baecker and Marcus [1]. To meet these objectives we chose to build our editor on top of the commercial word processing system FrameMaker. FrameMaker is available on a wide variety of platforms. It has built in hypertext capabilities as well as powerful editing operations. Moreover, it is user extensible using the Frame ....

Ronald M. Baecker and Aaron Marcus, Human Factors and Typography for More Readable Programs, Addison-Wesley (1990).

....It involves the use of colour and font styles and sizes along with code formatting in order to present code in a meaningful way. Practitioners of this method of using the code itself to impart the meaning of a program include Gellenbeck and Cook [4] and Baecker [1] and Baecker and Marcus [2] [3]. Gellenbeck and Cook investigated the effectiveness of including module header comments and mnemonic module names, along with the use of a larger font size for the module headers, in code. The presence of all three factors aided program comprehension, but the addition of larger font sizes for the ....

R. M. Baecker and A. Marcus. Human Factors and Typography for More Readable Programs. ACM Press, Reading, Massachusetts, 1990.

....than others, and in some cases, readability has been an issue when designing some languages. Visual enhancement can also be of assistance when understanding source code. Program visualization focuses on enhancing presentation of existing programs, their code and documentation. According to Baecker [1] the goal of program visualization is to facilitate the clear and correct expression of the mental images of the writer of computer programs and the communication of these mental images to the readers of such programs. Despite the importance of readability, most programs are not readable [2] This ....

.... giving the programmer a pretty printer view of the code plus hypertext capabilities: the user can point to the usage of a function and jump to its definition Baecker and Marcus proposed that programming languages must include a description of how they must be typeset as part of their definition [1]. They also emphasized that program visualization must benefit not only from lexical but from syntactic and semantic information. In particular they focused on C, presenting different ways in which the semantic information of a C program can be used to enhance readability. Source code presentation ....

R. M. Baecker and A. Marcus, Human Factors and Typography for More Readable Programs. Addison-Wesley, 1990.

No context found.

Baecker, R. & Marcus, A. (1990). Human Factors and Typography for More Readable Programs, ACM Press.

....by calls to animation routines which the user has inserted in the source code at locations of interesting events. The user can also write his own animation routines in Pascal. The most recent version, BALSA II (Brown, 1988) supports colour and rudimentary sound. The SEE Program Visualizer (Baecker and Marcus, 1990) is a UNIX based system for typesetting programs written in C. This work combines human factors research with modern typography and laser printing technology to format C programs automatically and produce a kind of program book with cross references and indices that facilitate navigation through ....

Baecker, R.M. and A. Marcus (1990). Human Factors and Typography for More Readable Programs. Addison-Wesley.

No context found.

R. Baecker and A. Marcus. Human Factors and Typography for More Readable Programs. Addison--Wesley, Reading, MA, USA, 1990.

No context found.

Baecker, R., Marcus, A., Human Factors and Typography for More Readable Programs, ACM Press, 1990, especially Appendix C: An Essay on Comments.

No context found.

Ronald Baecker and Aaron Marcus. Human Factors and Typography for More Readable Programs. Addison-Wesley, Reading, MA, USA, 1990.

No context found.

R. Baecker and A. Marcus, Human Factors and Typography for More Readable Programs, AddisonWesley, Reading, MA, 1990.

First 50 documents

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC