• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

NX: Choices.txt and Pure Text Editors

 
Javini Javono
Ranch Hand
Posts: 286
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
Completing the choices.txt file can become rather difficult, if for no other
reason than to easily deal with all the categories and topics that one,
presumably, has to address.
Given that the choices.txt file must be a pure ASCII text file, does anyone
know of any tools that make it easier to edit these types of files (such as
quickly getting to chapters)? I work different operating systems (Windows
and Mac OS X).
Tonight I decided to rename my file, temporarily, of course, to choices.txt.java
and use JEdit to edit it. I label each chapter as a class, and each section within
that chapter as a method. Has anyone tried this before? Or is this a very bad
idea?
The advantage, is that I can then use JEdit's class browser feature to easily get
to any chapter or section within a chapter.
Here is a sample, though the content is not what I would actually submit:

Thanks,
Javini Javono
 
Ken Krebs
Ranch Hand
Posts: 451
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Javini,
On Windoze, notepad.exe will also produce plain text.
Consider this:
In regard to choices.txt, the instructions say "...describing the significant design choices...". The important word here is ***significant***. Look at it from the tester's point of view. The last thing you want to do is irritate the tester and make his/her job difficult by writing a novel that exhaustively documents every tiny decision and alternate possibility. My advice is to keep it simple and focus on what's important.
 
Javini Javono
Ranch Hand
Posts: 286
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Ken,
Thanks for your response.
I got the impression by reading through posts in this group that
it appeared that almost everything, such as whether or not the
program will handle null values in the fields, had to be addressed.
As I tend to think "everything" is obvious, which is definitely not
the correct mind-set to have, perhaps I'm over reacting and I am
considering convering too much ground in choices.txt.
Your advice is very good: keep choices.txt reasonably short.
But, is it also true that choices.txt should be thorough?
If choices.txt was in a fixed 9-point font, how many pages,
approximately should it be: 3 to 5, 5 to 8, 8 to 12?
For instance, this morning I'm going to read through the postings
in this group for the last month or so to see that my choices.txt
file addresses every issue at least where another poster said
something like this: "What you're doing is fine, as long as its
documented or justified in choices.txt."
So, thorough but short is the key to choices.txt?
Also, what I think I'll do is organize my topics within choices.txt
so that "must" conditions are addressed first, then lesser
choices and design issues are discussed. In this way, the
examiner is free to stop reading from top to bottom at any
time.
Thanks,
Javini Javono
 
Javini Javono
Ranch Hand
Posts: 286
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Ken,
I also found references to the size in bytes of your files:
choices.txt = 10584 bytes.

userguide.txt = 5477 bytes
Thanks,
Javini Javono
 
Nicholas Cheung
Ranch Hand
Posts: 4982
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Javini,
For your reference, my choice.txt contains 51642 bytes while my userguide.html contains 14533 bytes.
Nick.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic