Message-ID: <3B0ACCF3.6AA9@attglobal.net>
Date: Tue, 22 May 2001 13:32:51 -0700
From: "J. Fatula" <fatula3@attglobal.net>
Reply-To: fatula3@attglobal.net
Organization: Dis- or sometimes Un-
X-Mailer: Mozilla 3.01C-PBWG  (Win95; U)
MIME-Version: 1.0
Newsgroups: rec.arts.int-fiction
Subject: Re: [Inform] Getting an object to respond differently to different
	 names?
References: <B72C9C19.5DF7%amerenbach@mac.com> <emshort-2005010210370001@user-2inim66.dialup.mindspring.com> <3B0916FD.73759041@csi.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: slip-12-64-54-190.mis.prserv.net
X-Trace: 22 May 2001 09:07:41 GMT, slip-12-64-54-190.mis.prserv.net
Lines: 46
X-Complaints-To: abuse@prserv.net
Path: news.duke.edu!newsgate.duke.edu!nntp-out.monmouth.com!newspeer.monmouth.com!europa.netcrusader.net!208.184.7.66!newsfeed.skycache.com!Cidera!news-reader.ntrnet.net!uunet!ash.uu.net!newsfeed.us.prserv.net!prserv.net!news1.prserv.net!slip-12-64-54-190.mis.prserv.net
Xref: news.duke.edu rec.arts.int-fiction:87375

Hey all,

  I'm a relative newbie, myself, but I've found one thing that really
works when you've got lots of good ideas, but not enough programming
knowledge.  Hold off on the parts you can't do yet, and try a toned-down
version.  Think up a real short game to make first.  Don't touch the
really good but really tough ideas until you understand the basics of
the part you're stuck on.
   This will force you to give yourself some experience before you
tackle the tough parts, and it will give you a finished product to give
a little closure and sense of accomplishment.

Joe Fatula

--

John Colagioia wrote:
>
> Emily Short wrote:
> [...]
>
> > If you really really really can't stand the thought of reading the whole
> > DM, one alternate approach is to put aside your most difficult coding
> > challenges for a bit.  Code up the parts of the game that are accessible
> > to you; make notes about the rest to remind yourself to come back and do
> > them.  Then mentally sort them into types ('aha! this problem looks like
> > it has something to do with handling player input!') and teach yourself
> > from the relevant chapters bit by bit.  Learning to teach yourself this
> > sort of thing is key; we can keep pointing you to sections of the DM, but
> > it will be, I fear, with lessening patience -- and be of decreasing use to
> > you.
>
> I should also point out something which I've learned from experience:  Coding up
> simpler bits in Inform will give you ideas as to how to approach the more
> complicated bits.  More, as Ms. Short mentions, than pregenerated excerpts from
> either the list or the Designer's Manual.
>
> No, it won't cover everything.  But trust me, that, and a "steady diet" of "pearls
> of wisdom" from the Designer's Manual will send you along very quickly.
>
> Of course, this is advice from someone who's never actually finished a game, but
> I'm getting there...
>
> [...]


