-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Want short demos of interesting Interlisp features #4
Comments
There are a couple of videos demos listed in the Medley Wiki but nothing systematic. Writing a script would be the first order. |
@skaisler1 want to try your hand at script writing? I was thinking we could do a lot of short (2 minute) feature demos. |
* Add new GitHub action to create medley release * Update to manual trigger with release name as input * Build loadup (#1) * Add new GitHub action to create medley release * Update to manual trigger with release name as input * Cleanup * Build loadup (#2) * Add new GitHub action to create medley release * Update to manual trigger with release name as input * Cleanup * Cleanup * Build loadup (#3) * Add new GitHub action to create medley release * Update to manual trigger with release name as input * Cleanup * Cleanup * Move sysouts to correct location * Build loadup (#4) * Add new GitHub action to create medley release * Update to manual trigger with release name as input * Cleanup * Cleanup
* Build loadup (#1) * Add new GitHub action to create medley release * Update to manual trigger with release name as input * Build loadup (#2) * Add new GitHub action to create medley release * Update to manual trigger with release name as input * Cleanup * Build loadup (#3) * Add new GitHub action to create medley release * Update to manual trigger with release name as input * Cleanup * Cleanup * Build loadup (#4) * Add new GitHub action to create medley release * Update to manual trigger with release name as input * Cleanup * Cleanup * Build loadup (#5) * Add new GitHub action to create medley release * Update to manual trigger with release name as input * Cleanup * Cleanup * Move sysouts to correct location * Set root directory to medley
The explanation of how to use the Medley mouse and keyboard probably would be best a video clip; Interlisp Exec: You need a 2 or 3 button mouse, or know how to have your trackpad/buttons generate a right-mouse-button event as well as the left-mouse-button event. Then: right-mouse-button down (and hold) in the background (the gray stipple not in any window) and you'll get a pop-up menu with EXEC as one of the items, slide the mouse pointer over that until it highlights, then slide right (it has the ► to indicate it has sub-menus) and over the "Interlisp" item (it also has sub-menus) and release the mouse button on the highlighted "Interlisp" item. It will then prompt you to position and size the new Exec window -- left button down to freeze the top-left corner and drag out the region and then release it to set the lower-right corner. Click in the window to give it the keyboard focus and then you can type at it. |
@masinter I'd be honored to help create a demo. Thank you for thinking of me. :) |
I like the idea of "live" demos which are actually done inside medley, with image objects. The video is to show them that it's easy ad what to expect. |
… Windows docker build / install (#1337) * Add cygwin-sdl build to buildLoadup workflow; add installer for cygwin-sdl on windows * Change how buildLoadup computes latest maiko release to accomodate draft releases * Fix call to gh release list for maiko * Debugging call to gh release list for maiko * Debugging call to gh release list for maiko #2 * Debugging call to gh release list for maiko #3 * Debugging call to gh release list for maiko #4 * Debugging call to gh release list for maiko #5 * Debugging call to gh release list for maiko #6 * Change maiko downloads to accoiunt for draft releases * Change maiko downloads to account for draft releases #2 * Specify shell (powershell) for Download cygwin installler * Few cleanup items on cygwin-install * Update ShellWhich to use command -v instead of which because which returns to much crap on cygwin and command -v is more portable overall * Switch from using medley-loadup & -runtime tars to medley-full-*.tgz so we get full release incl notecards; delete maiko on install and replace with cygwin maiko * Make sure Notecards doesn't try to load its HASH fileon PostGreet - for apps.sysout * Add xdg-utils to cygwin install to support ShellBrowser * Odds and ends on cygwin build * Redo medley.iss install script to use tar from Windows rather than cygwin tar because cygwin tar was messing up ACLs in windows. Needed to change creation of medley.bat accordingly. * Remove junk lines from buildLoadup.yml * Restore accidently deleted line to buildLoadup.yml * Fix multiple issues with cygwin_installer filename; arrange to remove placeholder.txt from the release assets at the end of cygwin installer * Change name of job from windows_installer to cygwin_installer * Fix missing GH_TOKEN is removal of placeholder.txt; fix naming of output file in medley.iss * Fiddling with getting cygwin-installer name right * Redoing merge of medley.sh/medley.command to handle the Darwin plus Cygwin cases; is medley.iss recreate symbolic links surrounding the medley.sh script * Fix typos/syntrax errors in medley.sh/medley.command
how about a contest -- a prize for the 5 best demo videos? |
Here are some ideas for demo videos:
I added a demo video contest item to the agenda of the July 3, 2024 external meeting. |
Maybe I'mrepeating myself (arguing with myself), but looking again:
To do a demo, it really helps to have a script. A script someone can follow along is a start. A script for a demo is almost as good as a video, and a lot easier to produce. I haven't compared your list of topics to the one given in |
Thanks, now it's clear. I agree videos are hard to produce and change. Now that I think about it I may have posted something similar, i.e. a few very short, tweet-like demos (perhaps "microdemos"): |
These are great. I suppose this begs the question of where to put the actual demo/demolet? maybe just link to the feature demos or screenshots or videos from the source? SOme regular things to put in the catalog of Medley demos?
https://interlisp.org/software/using-medley/ somewhere in there. |
I find videos aren't hard to do with OBS. A more ambitious goal could be a multi-step tutorial to build a small but interesting program. |
The old series of blog posts on Lisp debugging Simon Dobson rediscovered may be another source of inspiration for demos and scripts. |
I posted another demolet on file system Exec commands. |
Historically the file system commands were DIR,NDIR,FB,CONN. An early 2020 "Lispusers" UNIXYCD added cd, ls, pwd. They are case insensitive (you can use commands in upper case too) and package-independent. This is a problem in some situations when you want to eval a variable which matches a command. There are a few things that probably SHOULD be commands, but are currently implemented as Interlisp NLAMBDA functions. The Interlisp Exec handles input of 3 kinds: EVAL format, APPLY format, and "commands". If you type in a list -- starting with a left paren -- it is EVALed (or an undoable form of the expression. (Or should be undoable, verifying and correcting those that aren't is a big TODO item). If you type a symbol immediately followed by a List, it is treated as an APPLY-style call:
This is just to avoid typing the extra punctuation But first the EXEC (The REPL that does more than read-eval-print) checks for "commands". THere is an ambiguity about what should be done when you type a single symbol on the line input, that doesn't occur otherwise, if the symbol is (case-insensitive string-equal to a command -- Did you mean to eval the variable or invoke the command. If you type in SYMBOL(LIST) without a space between the symbol and the left paren, than it prefers the APPLY format. If type in a second symbol. If you type SYMBOL stuff and there is no COMMAND matching SYMBOL AND Symbol is a NLAMBDA format, it's treated as APPLY format (which will error on case and package mismatch. I think we might make it easier for newcomers by adding some explanatory text to what's going on but experienced users can turn off. Could you possibly make a list of demolets for the website? or linked from? |
Yes, I'll make a list of demolet links for the website. A demos section with the list could go under Software > Documentation > Using Medley Interlisp Basics (after "Writing a sample Interlisp program") or Software / Documentation (after "Introductory material"). Where else? The list would fit well with the concise essentials and tidbits of the first page. |
it would be good to get some links to introductory material for those who would start oout with online.interlisp.org first without reading any documenetation. Not sure where to put that, though. |
We could add to
The link would lead to a Demos section on the website pages suggested above, or somewhere (at the end?) on the page Software / Access Medley Online. This keeps clutter to a minimum on Medley Online and decouples it from the actual content which can be updated independently. |
Another demolet: sending stream output to windows. |
the Interlisp way, file package, masterscope, versioned file system, dwim, break package, lispx commands, spy
lafite, tedit, image objects, grapher
The text was updated successfully, but these errors were encountered: