• All in the Memory -- bookkeeping services
• Arabella -- a dynamic musical duo
• Bytesmiths Editions -- large, archival, fine-art photography on unusual materials
• Bytesmiths Press -- artists' services: web design/hosting, jury slides, giclee reproductions, opening announcements, brochures, etc.
• Champagne Beadworks -- handcrafted jewelry and beadwork
• Crafted By Carol -- handcrafted jewelry and beadwork
• Dana Fontaine -- unique photography-derived art
• Dymond Graphics -- note cards, pet/people photography
• Fountains & Funktini -- glass art and more from Beth Keenan and JoAnn Rawley
• Gemini Gypsy -- Carole Good-Hanson's fused glass frames
• Mary Kollman Fine Art -- lovely floral watercolor originals
• Primrose Studio -- terra cotta switch plate covers and wall art
• Ratso's Studio -- astoundingly realistic bronze sculpture
• The Spiral Gallery -- local artists exhibit in the Oregon Cascades foothills
• The Roaming Artist -- info and resources for artists "on the road"
• Van Dyke Sepias -- Jan Van Dyke's nostalgic sepia toned photography
• Veggiemog -- life and times of Kelly O'Toole's Unimog, running on biodiesel
• Village of Willamette Arts Festival -- annual visual/performing arts festival, third weekend of September
• Whitehorse Designs -- Gwen Miller's beadwork and fused glass
• West Linn Arts Commission -- city support for the arts

Software Component Lifecycle

You cannot delete components from the library. Be careful when choosing names, because you cannot rename classes, applications, subapplications, or configurations.

Versioning and Releasing

Versioning classes is a lightweight operation. Within a week, for example, a developer might want to version a class more than once. One reason is obvious -- to be able to return to that state of the class if you are about to try an experiment. Another reason is to allow another developer to load the class -- developers cannot load each other's editions of classes.

Releasing classes is less frequent. When you have tested the classes in your subapp or app and want others to automatically get those versions when they load the app/subapp, you release the classes. Generally all classes are released when a trial build is to be done for integration testing. At this point we suggest not versioning the apps and subapps.

Versioning applications and subapplications is a heavyweight operation that should not be done until the app has been tested. However, contrary to the normal pattern, it is a good idea to immediately release to the parent app any new edition you make of its subapp. A subapp does not need to be a version before it is released to an app. This is tricky for beginners in ENVY to remember.

Versioning a configuration is only possible when all of its applications are versioned and the configuration has successfully been loaded. One generally versions configurations after integration testing, for periodic development milestones. Another typical configuration version is for builds done for special demos (such as for OOPSLA '94!).

Methods are an exception to the versioning and releasing cycle. Method editions are automatically released to the class or class extension in which they are created. The developer can always decide to load a different edition of a method, thereby "releasing" that method edition to its class or class extension edition.

[ prev | top | next ]