-
-
Notifications
You must be signed in to change notification settings - Fork 9
Update Reviving Medley page #325
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -14,13 +14,15 @@ We started with the most recent working files from Venue sources. This was not a | |
|
|
||
| Among other improvements, Medley 3.5 increased the address space by a factor of 16. But the changes to the address space affects some highly optimized code which took advantage of short-cuts. | ||
|
|
||
| Our goal is to maintain compatibility with old code and not introduce breaking changes at the source level or subtle semantic changes. | ||
|
|
||
| ## Common Lisp and Interlisp file manager | ||
|
|
||
| While Medley 3.5 has a Common Lisp implementation, it is compatible with the Common Lisp of its time -- the first edition of Common Lisp the Language (aka CLtL1). There are files that purport to implement CLtL2, but they have not yet been merged. | ||
|
|
||
| In addition, the integration of Common Lisp and Interlisp is extensive, there are still some rough edges -- along the way of integrating the two, the result is not quite seamless. | ||
|
|
||
| While Interlisp and Medley implement international character processing and hardcopy through use of 16-bit characters, the character coding system used is XCCS (the Xerox Character Code Standard). | ||
| While Interlisp and Medley implement international character processing and hardcopy through use of 16-bit characters, the character coding system initially used for the external format was XCCS (the Xerox Character Code Standard). The system can now read and write files in a number of formats, including UTF-8, and we are aspiring towards UTF-8 and Unicode for external file representation. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ... we are aspiring to use the UTF-8 encoding for Lisp source files. |
||
|
|
||
| ### CPU and operating system | ||
| * originally: 32 bit systems, big endian | ||
|
|
@@ -49,22 +51,23 @@ Scroll wheel implementation, middle button menu commands are awkward. | |
|
|
||
| We have yet to gain mastery over the complex way that Medley handles the keyboard. | ||
|
|
||
| ### Character encoding | ||
| ### Character encoding for external file representation | ||
| * originally: XCCS (Xerox Character Code Standard) | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. All of the lowercase "originally" should have the "o" capitalized: "Originally".
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Let's capitalize "Now", too. |
||
| * Now: Unicode | ||
| * Transitioning to: UTF-8 and Unicode | ||
|
|
||
| ### Display | ||
| * originally: 768x808 one bit per pixel | ||
| * now: larger, color displays | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. "Now: larger displays" |
||
|
|
||
| Color support seems like it might have been a Medley feature that was taken out, for reasons that are unclear. Running on a large 4K display at full-screen isn't possible. We have yet to integrate modern fonts. | ||
| Color support seems like it might have been a Medley feature that was taken out, for reasons that are unclear. Running on a large 4K display at full-screen isn't possible. We are integrating modern fonts. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. "Medley supported color displays on certain platforms, but the underlying code has been removed." |
||
|
|
||
| ### Available compilers | ||
| * Originally: "K&R" book of standard C | ||
| * now: gcc, cmake and Posix standards | ||
| * now: Clang, gcc, Make, CMake and Posix standards | ||
|
|
||
| ### Version Management | ||
| * Originally: versioned file system | ||
| * now: path names via "pseudo hosts"; GITFNS, structure comparison | ||
|
|
||
|
|
||
| ### Modernization | ||
| We are introducing new features to make the Medley environment more accessible and familiar to modern users. We implemented scrolling with a mouse wheel, access to the clipboard of the host system, and mouse gestures for window management such as clicking and dragging the title bar to move a window, or clicking and dragging a corner to resize it. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. "We are introducing new features to make the Medley environment more accessible and familiar to modern users. We have implemented scrolling with a mouse wheel, host system clipboard access, and click and drag mouse gestures to move or resize windows." |
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Parallel structure grammar problem.
It should read
Our goal is to maintain compatibility with old code and not introduce breaking changes at the source level or introduce subtle semantic changes.