#GitHub - darkfated/gluamanager: 🧰 Deskt...

1 messages · Page 1 of 1 (latest)

warped sequoia
#

only local? add luasocket support.

#

or dhtml version mb, its tuari anyways

#

could be useful for gmodstore addons config integration eg, but not the current state

sharp crown
#

Looks interesting

Not sure if this is just me but opening it on Windows also opens up a windows terminal window as well as the application itself. Closing the terminal window also closes the application. Not the end of the world, but I assume it isn't meant to be showing up.

It also seems a bit limited due to the requirement of a .addon file, which means things have to be specifically made to work with this. I get why, but I don't see many others adding support for this in its current form.

warped sequoia
#

dependencies auto download makes no sence also

#

its MANAGER, not DOWNLOADER

tender burrow
#

I don't personally have a preference for whether a tool like this includes downloading functionality, but I do think it's incorrect to assume that downloading is fundamentally separate from management

warped sequoia
tender burrow
#

Many people have tried it but I don't think it really works well for Garry's Mod

placid helm
#
  1. Add support for remote metadata. Not every developer wants to create a .addon file, so it should be optional. For example, a user could provide a URL to a JSON metadata file that describes what to download and other parameters. The app would fetch it and generate a local .addon file from it.
  2. Rework dependency downloading into a warning-based system. Instead of auto-installing everything, the app would show that an addon may not work (or may work incorrectly) without certain dependencies and provide links. Then the user can install them manually or through the app (if .addon support exists). This is not intended to be a full package manager, but rather a simplification of the installation process, since many users don’t fully understand what they need to install even with documentation.
  3. Add a CLI mode. For example:
    gluamanager download <url_to_metainfo>
    The metadata would contain download and setup info, and the tool would install everything accordingly, with the dependency behavior described above. This would be especially useful for documentation and automation.