Bytesmiths no longer is involved in software consulting. Maintenance of this web site is currently subsidised by unrelated business activities. Please pass the word to other interested folks, so I can continue to host this page!
Your site could be listed here, for as little as $12 per month! Go to Bytesmiths Press for details.
This site has been selected by PC Webopaedia as one of the best on this topic!
This site has been awarded a Links2Go Key Resource Award in the Smalltalk category!
- Arbitrary code units must be able to be part of multiple target
configurations.
Enforcing a strict containment hierarchy limits reuse possibilities.
- Code unit semantics -- code modules must be first class objects, with
appropriate
behavior when needed. Such behavior should include (but not be limited
to): what
happens when I am made part of an image? What happens when an image
containing me
starts up? What happens to system resources, such as the Launcher, when I
am present?
- Seamless integration with revision history -- versions of
configurations must be available,
with the same services provided to code unit versions.
- Support for conditional integration -- minor differences within one
configuration,
depending on the system environment. For instance, if Platform ==
#MessDos, load
the code unit that holds the MS-DOS system interface.
Bytesmiths no longer is involved in software consulting. Maintenance of this web site is currently subsidised by unrelated business activities. Please pass the word to other interested folks, so I can continue to host this page!
Your site could be listed here, for as little as $12 per month! Go to Bytesmiths Press for details.
This site has been selected by PC Webopaedia as one of the best on this topic!
This site has been awarded a Links2Go Key Resource Award in the Smalltalk category!