Also, this might help with the dynamic-require approach: http://docs.racket-lang.org/tools/drracket_get_extend.html?q=drracket%3Aget/extend%3Adisallow-re-extension%21#%28def._%28%28lib._drracket%2Ftool-lib..rkt%29._drracket~3aget%2Fextend~3adisallow-re-extension%21%29%29
Robby On Sat, Aug 31, 2013 at 2:57 PM, Stephen De Gabrielle < [email protected]> wrote: > Thanks Laurent & Jens, > > Much appreciated. > > Stephen > > > -- > Stephen De Gabrielle <http://www.degabrielle.name/stephen> > > > > On Sat, Aug 31, 2013 at 5:09 PM, Jens Axel Søgaard > <[email protected]>wrote: > >> When writing code that require DrRacket to restart I usually open two >> DrRackets. In one instance of DrRacket I write the code - this is usually >> in an old version. In the other I test the code. This way I don't need to >> reopen the source file after each restart. >> >> Another tip: To make DrRacket restart faster remove all tools you don't >> need. DrRacket actually start very faster with no tools. >> >> >> >> 2013/8/31 Stephen De Gabrielle <[email protected]> >> >>> Hi, >>> >>> I'm starting to fiddle with DrRacket plugin ideas (again), and I was >>> wondering if any tool developers can share their processes for developing >>> tools, >>> >>> What I used to do was dump my tool in a collects directory and run 'raco >>> -L toolname', followed by restarting-the-Doctor. If it failed I would >>> remove the tool from /collects/ and restart again. >>> >>> This is a bit frustrating as it can be quite time consuming, and I >>> disable as many tools as possible to make restarts quicker. >>> >>> Is there a better way to develop plugins? >>> >>> Cheers, >>> >>> Stephen >>> >>> ____________________ >>> Racket Users list: >>> http://lists.racket-lang.org/users >>> >>> >> >> >> -- >> -- >> Jens Axel Søgaard >> >> > > ____________________ > Racket Users list: > http://lists.racket-lang.org/users > >
____________________ Racket Users list: http://lists.racket-lang.org/users
