Somewhat related to easy creation of new project assuming a large fraction of Julia users already use VScode which is a rather complex GUI :
I wonder what is the state of
related to this thread
?
Somewhat related to easy creation of new project assuming a large fraction of Julia users already use VScode which is a rather complex GUI :
I wonder what is the state of
related to this thread
?
Well, what I liked less about PkgTemplates.jl, and which was my motivation: Though with PkgTemplates.jl there is kind of interactivity, it is one option at a time in a quite complex system of options and sub-options. After you made a click, there is (I think) no way back. The videos under âNew project creation commandâ look like it is essentially the same process, except the input is on the top on the screen and not on the bottom. Well, there is file selection dialog.
With PackageMaker.jl, you get a GUI where you can evaluate (and re-evaluate) all options, click onto embedded links if need more information, and only after you are sure, you finally click onto âSubmitâ button.
Furthermore, PackageMaker.jl is already here, and it wouldnât absorb any of the (scarce) resources of the maintainers of VSCode. And still further, while PackageMaker.jl can be used from VSCode, having VSCode installed on the computer is not a pre-requisite to use it (bar the current issue on Ubuntu).
Admittedly opening PackageMaker.jl GUI in a VSCode pane instead of an independent window would be nice and must be doable, but I do not think currently it is worth the effort.
I like PackageMaker.jl especially because it helps me advocating the use of Julia to new users : âsee how it is easy to create a new packageâŚâ.
Since I always start these Julia introductions with two steps :
it would be great if the PackageMaker.jl (functionality) could be already available at Step 2.
It is indeed not a big deal for my personal use, but I think that every improvements on the smoothness of first steps are useful for Juliaâs adoption : Julia is cool and productive !
@LaurentPlagne, first, thank you for your nice words. However let me say it directly: Integrating PackageMaker.jl into VSCode is at best at the very bottom of my list of priorities. It is supposedly (supposedly, as I have no idea how implement it - do you?) quite a lot of programming to save a few keystrokes for a fraction of potential users.
May I shamelessly suggest the following procedure for Julia introductions:
using ShareAdd; @usingany PackageMaker
, select the default name for the new shared env, which would be @PackageMaker