# \[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:** 18

<div class="post-metadata">

### Author: ![heliosdrm](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/heliosdrm/32/3851_2.png) [@heliosdrm](https://discourse.julialang.org/u/heliosdrm)
#### Post date: [December 29, 2024, 10:50pm UTC](https://discourse.julialang.org/t/ann-packagemaker-gui-for-pkgtemplates/124197/18 "2024-12-29T22:50:46Z")

</div>

> [@Eben60](#):
>
> I prefer to start a (possibly throwaway) package right from the beginning instead of a project. This gives me the important advantage of having all functions, which I place into the project’s module, `Revise`-ed. I do not see any disadvantages of such a procedure as compared to a bare project. Are there any?

(Perhaps this deserves another thread, even though it is in the original post?)

I think that this question is no longer needed if a package is not presented as something different from a project, but as a _special kind_ of project - characterized by the `src` folder with a `jl` file containing a module, matching the name of the package.

Under this view, the dilemma of “project or package” is like comparing e.g. “project with or without `[compat]` section”. The package structure gives the advantages that you mention, at the (minimal) cost of adding a structure that might be superfluous if you are not going to benefit from those advantages.

---

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