# \[ANN\] PackageMaker - GUI for PkgTemplates

**URL:** <https://discourse.julialang.org/t/ann-packagemaker-gui-for-pkgtemplates/124197>\
**Category:** Package Announcements\
**Tags:** package, announcement, pkgtemplates, gui\
**Created:** [December 26, 2024, 10:05pm UTC](https://discourse.julialang.org/t/ann-packagemaker-gui-for-pkgtemplates/124197 "2024-12-26T22:05:57Z")\
**Posts on this page:** 1\
**Showing post:** 24

<div class="post-metadata">

**Author:** ![Eben60](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/eben60/32/13475_2.png) [@Eben60](https://discourse.julialang.org/u/Eben60)\
**Post date:** [January 9, 2025, 10:07am UTC](https://discourse.julialang.org/t/ann-packagemaker-gui-for-pkgtemplates/124197/24 "2025-01-09T10:07:17Z")

</div>

@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](https://discourse.julialang.org/t/ann-shareadd-jl-making-easy-to-import-packages-from-multiple-environments/121261) suggest the following procedure for Julia introductions:

- install juliaup
- install VSCode (extension)
- set up global git user names & mail (this part would be nice and not that difficult to integrate into PackageMaker.jl )
- install Revise.jl & ShareAdd.jl into the main environment
- `using ShareAdd; @usingany PackageMaker`, select the default name for the new shared env, which would be `@PackageMaker`
- on a slow computer, you now get a couple of minutes to make an espresso, while some 150 packages gets precompiled 🙂
- create a package “for local use”
- start coding (and testing) your functions inside the newly created package
- voila!

---

_[View the full topic](https://discourse.julialang.org/t/ann-packagemaker-gui-for-pkgtemplates/124197)._
