Quote:
Originally Posted by Muzamba
[*]While the results are more structurally-realistic than they
were in the first build, I think the table content is causing a
lot of the output to sound rather silly and implausible. The
primary culprit is Table4. The nouns really need to be toned
down considerably. Relatively few of the words in this list
would have been used in naming locations during the era that
most American cities were founded.
|
I pretty much created the content for Table4 by copy-pasting
from a list of the most common nouns in the english language.
I intend to edit the list at some point, but wanted to get this
version working before I did that. So, this issue was already
known and expected.
Quote:
Originally Posted by Muzamba
[*]Some sort of tagging system still needs to be applied in
order to better match concepts. This is especially true of
Tables1 and 2 combining with Table3. For instance, the more
descriptive prefixes like "Blue" and "Cold" would normally be
followed by a noun from Table4, but not a name or proper noun
from Table3.
|
I duplicated the contents in Tables1 and 2 just to get more
options. What I see is that I need to keep them separate, but
have the option of using Table1 twice for the same city name..
113 as opposed to 123... there is nothing wrong with using the
same table twice, but I wouuld make sure to not duplicate the
same word.. (There won't be a Fort Fort Smith)
Quote:
Originally Posted by Muzamba
[*]Even though they're not very common, there should probably
still be a second title suffix table (Table7?) for cities like
"Salt Lake City", "Thief River Falls" and "Hot Springs
Village".
|
I think this is already able to happen... but I will make
sure..
Quote:
Originally Posted by Muzamba
[*]Adding a second set of title prefixes, however, was a smart
move. I forgot about places like "North Little Rock", "New Port
Richey" and "Fort St. John". (However, they still need to be
grouped appropriately with tags.)
|
What I think I am going to do is keep it with 2 seperate lists.
Table1 would be "Title" prefixes (Port, Fort, etc...) and
Table2 would be "Descriptive" prefixes (Little, Blue, etc...)
and there should be the ability for them
Quote:
Originally Posted by Muzamba
[*]This isn't a big deal if it's too inconvenient or
impractical, but would it be possible to allow the user to
control the frequencies of table combinations? (I've always
been of the mindset that the more the user can customize, the
better.)
|
I plan on adding this in later. Right now, you still can make changes by editing the files, but I would to add this ability right into the program.
Quote:
Originally Posted by Muzamba
[*]Finally, on a personal note, is there any way you code the
new GUI to accept Windows colors? I'm sure this won't be a
problem for most, but because of my Windows settings, the list
output shows up as white text on a white background on my
computer. I can see them when they're highlighted, but not
otherwise. (I have my colors inverted due to a vision problem.)
|
I should be able to come up with something, even if it is only the ability to change the colors.
Quote:
Originally Posted by Muzamba
One thing that I think would really help, once all the
programming has been completed, would be to compile statistics
on place names. Some of the numbers still seem a little off to
me, but I'd rather use accurate frequencies than to speculate
on the numbers myself.
|
This could be a chore. The only thing I can think of would be to get a list of every city/village in the United States and then search for how often each part shows up ? But then you also have cities that are named after something from another language, like an indian name for instance.
Thanks for your input, I probably wouldn't have even gotten this far if not for your suggestions and enthusiastic responses..