(Real Studio network user group Mailinglist archive)
|Re: Documentation (FROM: [ANN] iBasic) - Garth Hjelte|
|Date: 30.09.11 08:43 (Fri, 30 Sep 2011 09:43:52 +0200 (CEST))|
you are 100% right.
But,one have to be able to do that, just that.
I'm 57 yo and I think that I've done something like that only once (I do not have REALbasic the application and the license installed) and so that was the only thing I can do to start on the project.
I used TextEdit to write the ideas on the software, organize them and so on.
------- This is an answer to:
Date: Thu, 29 Sep 2011 11:13:54 -0600
From: Dan Paymar
Subject: Re: [ANN] iBasic
To: Realbasic NUG
Message-ID: <<email address removed>>
Content-Type: text/plain; charset=UTF-8; formatðowed
When starting a project, how do you know what you're going to code
When I decide to start a new project, the first thing I do is a detailed
description in outline form so I know exactly what I want to do. I then
discuss that with potential users, editing as necessary until I'm
confident that it will be a viable product.
The next step is to start with a skeleton project and paste pieces of
that outline into project methods as comments.
All that's left to do is write code to implement what those comments say
the method will do. Sometimes it's necessary to revise parts, so the
comments are changed and pasted back into the outline.
By the time the project is ready for alpha test, all that's left to do
for the documentation is to flesh out the outline into a user manual.
Unsubscribe or switch delivery mode:
Search the archives: