Modules FAQ
Last updated at 5:10 pm UTC on 16 January 2006
Questions asked at least twice ;-) Also many questions are answered by other pages around here. They won't always be answered here too.
Q: Is there an explanation of the Temporary category and how some things ended up there
You had added things in the image that weren't part of the base distribution, so the converter didn't know where to put them, so it moved them to Temporary.
...and whether it's safe to move them elsewhere)? Somewhere ?
Yup. For example #(People [yourInitials] [yourThing]) or #(Project [theProjectName]). Cf. Choosing locations for your modules'
Q: How do I load an older (3.2 or earlier) changeset into the modules-based 3.3alpha image?
See How to port old code to modules for examples on how to do this.
Q: How do I create a module with an uncapitalized name, e.g. #(People hg) ?
If the module doesn't already exist in the image, the old-style class creation message won't do this since it is made to "correct" former system category names and therefore removes spaces and capitalizes names. If the module already exists, the old-style definition will correctly find the module from an uncapitalized category name.
If you use anything that uses the module path, such as the modular class creation message, to create the module then it will work. So
CelesteComposition subclass: #MyClass
instanceVariableNames: ''
classVariableNames: ''
module: #(People xy)
works, but this doesn't work unless the module already exists:
CelesteComposition subclass: #MyClass
instanceVariableNames: ''
classVariableNames: ''
poolDictionaries: ''
category: 'People-xy'
