| Thread Previous • Date Previous • Date Next • Thread Next |
The "package exporter" is confusingly what is now used to create modules
- allowing for possible bugs in the code that zips the selected items up
into a .zip file (which can be manually renamed to .mpackage one if
desired). It is still marked as experimental and does have some rough
edges (and not much in the way of error messages) but does seem to be
what is wanted to solve this bug...
** Changed in: mudlet
Status: New => Triaged
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1261035
Title:
No way to easily create a module
Status in Mudlet:
Triaged
Bug description:
There's no really obvious way to create a module. For example, when
you work on a bunch of triggers, aliases, etc, and then think to
yourself: "I'd like to turn these into a module." - there's no menu
where you can select them, give the module a name, a location to be
stored at, and so on.
You've got to export them as a package first, then import as a module.
A bit clunky.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1261035/+subscriptions
| Thread Previous • Date Previous • Date Next • Thread Next |
