@shu—hung has joined the channel
I understand ‘projects’, like in other IDE’s are forbidden in DrRacket - but is the rationale written up anywhere?
What do you mean by forbidden?
I think ‘extra-linguistic’ mechanisms like projects are considered a failure
My view was that it was too cumbersome to include and maintain into DrRacket directly, and that plugins are welcome
I think this https://felleisen.org/matthias/manifesto/sec_intern.html\|https://felleisen.org/matthias/manifesto/sec_intern.html might be what I’m looking for but I just found it so I’ll have to read, and perhaps understand. (I am so far out of my depth I can’t even see the bottom)
Since now you can ask drr to open files from quickscript, it should be fairly easy to make a script to do most of the process
Could be that just no one implements tham and if project stuff are just another Racket #lang w/ DrRacket plugin support (or so) then they won’t be extra-linguistic
I think the main reason DrRacket doesn’t require users to create a project is that they don’t want to add an extra layer that will interfere with students’ learning
But project support is in itself not a bad thing
I’d like at least something that saves the open files and caret positions, so that I can re-open all my files at the same place after rebooting
“Project” could just be defined as “a directory” and having a side bar (or second window) that easily let you say within a user-defined scope.
Personally, I typically find any IDE where I need to define what belongs to it, what doesn’t, have special config files for it to determine how/where to build, etc. to be extremely frustrating (especially so when first trying it out initially).
I do kinda like the idea of a #lang project
, though, where it could define an initial set of files to open, perhaps change drracket preferences, etc.
> I’d like at least something that saves the open files and caret positions, so that I can re-open all my files at the same place after rebooting You are in for a treat! https://github.com/sorawee/drracket-restore-workspace
^ @laurent.orseau
wonderful!
I just need to remember the close the drr project window last :smile:
yep
(@spdegabrielle still worth a qs :wink: )
Only support one workspace right now