Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!news2.near.net!howland.reston.ans.net!ix.netcom.com!netcom.com!kcooper
From: kcooper@netcom.com (Ken Cooper)
Subject: More edIt Contest Info
Message-ID: <kcooperD7J1M3.L1n@netcom.com>
Keywords: edIt contest cooper peters editor visual smalltalk extensions
Organization: NETCOM On-line Communication Services (408 261-4700 guest)
Date: Mon, 24 Apr 1995 06:49:15 GMT
Lines: 55
Sender: kcooper@netcom8.netcom.com


I've had several people asking common questions about the edIt 
extensions contest, so I thought I'd answer them publicly. 

1) The last day for edIt contest submissions is May 1st (i.e. in 
about a week). We'll accept submissions until midnight.

2) No, the T-shirt will not be blatant advertising with the edIt logo 
plastered across the front. That's reserved for the back. :-) 
Seriously, we wanted to make it something you could proudly wear 
to OOPSLA or a beer party without feeling like a walking 
billboard.  I think we succeeded.

3) If you've got an idea, but wonder if someone else is doing it, 
sorry, we won't make a list available of what others have done. 
That wouldn't be fair to those who've already submitted. However, 
the last thing we want is repetition (and having two people do the 
same thing isn't so good either :-), so if you send me mail roughly 
describing your idea, I'll reserve that idea for you, or tell you it's 
been done.

4) Code should be submitted in filein-able format.  If you use either 
Team/V or Xoteryx, a package will be welcomed.

5) Yes, utilities that you've already written are acceptable, even if 
they've been uploaded, and are in general usage.  They just need to 
be integrated with edIt.

6) edIt integration means the following: it must run on VST Win32 
3.0, and have launchable methods from within edIt.  All 
'launchable' means is that you have a method that is bindable from 
within edIt (i.e. resides either in the CPEdIt class or a 
ViewManager subclass that is pertinent), that this method be given 
a category using the edIt public methods browser (the online help 
is excellent in describing this), and that the method have a brief 
header comment describing its functionality (this is used by edIt 
when you're browsing extensions).  Keybindings and/or toolbar 
bitmaps are also welcome.  

7) Good documentation doesn't mean it has to be a novel; in fact, it 
probably should be very concise. For guidelines, consider your 
own busy schedule, and how nice it is to scan something quickly to 
figure out how to use it. Decent user interface design usually goes a 
long way in this regard.

8) Yes, if we distribute your entry, your name will be prominently 
displayed in the source code.  

9) No, we can't be bribed.  Well, maybe if it's a big bribe. :-)

That's it for now.  If I get any more, I'll post the answers.

Ken Cooper
Cooper & Peters, Inc.
71571.407@compuserve.com
