I’m reorganizing the menus for quickscript-extra and quickscript-competition–2020:
There’s a new Re&factor submenu in the Scripts menu, containing extract/put-function and abstract-variable.
Would it make sense to place the autocompletion and definition signatures in the Re&factor submenu? Or do you have a better name/organization?
Sounds good to me!
Thanks. I kept the definitions out of the Refactor menu for now, it’s not really refactoring.
That’s fair.
Can we have a discussion about including some core quickscripts in quickscript itself ? The benefits far outweigh the cost (kb’s).
We can certainly have a discussion :slightly_smiling_face: I think there’s an issue open about that?
The right way to go would be to create a new package like quickscript-essentials that contains only the essential scripts extracted from quickscript-extra, and then have them validated by the core team (robby in particular) If we do go this way, we should probably start with really just a few scripts.
One important constraint is that in the main distribution we must really enforce backward compatibility. It will be hard to remove a script, or refactor it once it sits there (that’s one reason why I’m hesitant).
I am also cautious here.
Maybe a good idea would be to have a menu item in the quickscript menu that offered a dialog listing some packages and documentation on them and offered to install them?
agreed.
And one could also remove them from that menu maybe.
Adding/removing (well, activating/deactivating) is taken care of by Quickscript already via the library. Installing is the missing bit mostly.
Maybe there could be a link in the Scripts menu to the wiki page that lists the available packages and scripts?
I could one simple script by default it would be ‘open terminal here’.
Re listing and installing quickscript packages: it’s an additional mechanism on top of the package system, which adds redundancy and opportunities for new bugs, which is like to avoid if possible.
how so?
Just links are simple enough, sure. I think Robby was mentioning something more complicated and i thought you were thinking the same
I was thinking a menu item that would list packages with the tag ‘quickscript’ and a tooltip that included the package description, each with a submenu to go to the documentation for that package, or trigger installation of the package.
I just made my own package of favourites https://github.com/spdegabrielle/stephens-favourite-quickscripts
I’m getting this when I use the shadow button: symbol->string: contract violation
expected: symbol?
given: '(name . add-menu)
context...:
/Applications/Racket v7.9/share/pkgs/quickscript/shadow-script.rkt:20:0: shadow-script-proc
/Applications/Racket v7.9/share/pkgs/quickscript/shadow-script.rkt:39:0: make-shadow-script
/Applications/Racket v7.9/share/pkgs/quickscript/library-gui.rkt:106:4: shadow-selected-file
/Applications/Racket v7.9/share/pkgs/gui-lib/mred/private/wx/common/queue.rkt:435:6
/Applications/Racket v7.9/share/pkgs/gui-lib/mred/private/wx/common/queue.rkt:486:32
/Applications/Racket v7.9/share/pkgs/gui-lib/mred/private/wx/common/queue.rkt:634:3 not sure what I did wrong
Well, that’s a bug…
@laurent.orseau I agree that implementing some big new thing that does what’s already done is a bad idea!
I was thinking if there was one specific package that had a lot of scripts that that might be something to have a menu item to install but if that’s not the case I think that a menu item with a link to some page where documentation exists is best.
Probably good to link to docs and not the wiki tho.
Let the docs do the linking to the wiki
Not on my computer right now, bit that’s very strange. Can you open an issue?
Here’s some code that links to docs in a way that’s probably what you want: https://github.com/racket/games/blob/e57376f067be51257ed12cdf3e4509a00ffd533d/show-scribbling.rkt#L9
It’t probably just me. I do terrible things to my computer. I’ll log it but fee free to close if oyu cant reproduce.
Searching for calls in that repo should clarify things I suppose. Or, god forbid, reading the docs :wink:
Thanks!
The docs are clear indeed, thanks ;)