As usual, I am sure there is more than one way to do things. From what I've read, a module is just one mxml or actionscript file, right? It can't be a collection of files.
So that begs the question, what is the best way to separate a collection of related files. For instance, if you have managers, presenters, vo's, events and views, then a collection of related files might have a manager, a presenter, a couple of events, a couple of views and a couple of vo's. Typically when you have to use functionality from one, you need all the files to make it work. It seems unweildy to make modules out of all the files then to load or unload all of them as needed. It seems in this case a library might be easier to use. Perhaps you could make modules out of the views and presenters (maybe within the library) since you may not always need those. How have other people tackled this? Thanks.
You can have a collection of stuff in a module. You can also pack a module
with other stuff and have other modules share that stuff. It depends on how
you set up the applicationDomains. There is a shared code module example in
the modules presentation on my blog
Flex SDK Team
Adobe System, Inc.