• 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

Smalltalk-Specific Needs

• Archive your Smalltalk repository as a whole, rather than adhering tightly to an archive policy that mandates control of each "file".
  
• A simple interface to stdin can allow your Smalltalk system to be constructed from within a central make file, if that is a dictate.
  
• Synchronize your iterative process with the major milestones of corporate waterfall processes.
  
  • This will be difficult early, when the traditional process expects reams of requirements/design documents. Satisfy them (in the short term) with reams of automatically generated templates, while continuously improving your internal documentation.
    
  • This will be trivial later, when your documentation is realistic and synchronized with your code, and when your implementation is far ahead of normal waterfall expectations.
    

• Minimizing coupling -- make extensive use of lazy caching, so that your system can change independently of the legacy system.
  
• Keeping legacy interface narrow and shallow: a minimum number of methods that are relatively independent of specific legacy state.
  
• Providing a pluggable "legacy isolation" layer that encapsulates the legacy system and transforms it to the object system.
  

[ prev | top | next ]