Liz, For me, the codes have been an ongoing concern. For our users, the source codes were always the biggest stumbling block to comfort with v1. It was an easy fix, though - source codes were simply ignored and life went on. In v2, however, it's a different matter - codes are an essential part of the system. This worries me, since I hope that v2 will be accepted by our users. So far, I haven't dared show v2 to any of them out of concern that they will be so daunted by the code scheme that they will turn against upgrading. We have an older staff, including some reluctant computer users, whose reasons for working here don't include technological mastery. I'm hoping that there will be a rapid evolution to friendlier coding standards.
As I look back on the goals of v2, it appears that many were well met. Although it is not important to us, there are now web features. The architecture has changed dramatically, enabling a higher level of fit to many diverse organizations, including ours (a large historic preservation advocacy). In the same way, upgrading should become dramatically easier. This is a huge issue to those of us so heavily customized that we haven't been able to move from v1.00. But the tradeoff which enabled the new architecture, the coding scheme, imposes a challenging learning curve. One of the v2 goals, as I recall, was to ease the learning curve. I'm not certain that has happened. Obviously, it's too late to fully rethink the approach. But I think that efforts now should be largely focused (excepting bug fixes) on making the code system more friendly. I feel that improving this will be the key to gaining user buy-in for ebase 2. Gary > Subject: RE: Ebase v2.00 - Designing Codes, anyone? > From: "Liz Gans" <[EMAIL PROTECTED]> > Date: Thu, 14 Mar 2002 15:46:34 -0800 > X-Message-Number: 6 > > Linda, > You've caught a bug in the Code Tutorial that I noticed only yesterday. > I'm > checking on the workaround and will post another response soon. > > About the complexity - I'm interested in including a simpler set of sample > codes with the next version (2.01, to be released in early April). The > sample set I developed is geared to larger organizations...I'd appreciate > it > if you would give me an idea of the types of things you want to track in > your organization (send to me at [EMAIL PROTECTED]). > > I'd like to hear from others who feel put-off by the complexity of the > codes...what do you want to track in your organization? Your feedback will > help in this next round of sample code design. > > Thanks, > Liz > > ---------------------------------------------- > Liz Gans > Director, ebase Community Support > TechRocks > 432 Last Chance Gulch, Ste K, Helena, MT 59601 > 406.442.0082 > [EMAIL PROTECTED] > ---------------------------------------------- > ------------------ Reminder to each recipient: To change your list account preferences, go to http://email.sparklist.com/scripts/lyris.pl?enter=support and enter the email address you used to subscribe to the ebase support list:: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] --------------------------------------------------------------------- ebase - Relationship Management for Nonprofits, http://www.ebase.org ---------------------------------------------------------------------
