As discussed here #29

I will provide more info if needed.

Have a boolean, default to false, that checks if you're generating project names.

If you are generating project names replace parts in words that have "*it" with "bit". Add -o to the end of words that end in to consonants or replace final vowel with o. Replace [H,P,C,K,T]-[AP,AC,AQ,Ak,AT] with Hack.

Ex:
Sphere -> Sphero
Capital -> Hackital

I will work on this shortly if @mattjegan would add it.

This is a response to your blog post and modification to RanCat regarding a a supposed 100% performance improvement.

It's not acceptable to only consider the first 1000 elements of a file when selecting one at random when, more than likely, the dictionary will be presorted and have much more than 1000 elements.

I suggest you take the following approach:

1. Get the size of the file in bytes size = os.stat(filename).st_size
2. Open the file f= open(filename)
3. Jump to a random spot in said file f.seek(random.randint(0, size)
4. Move backward(or forward) until you hit a newline
5. Read the entire line word = f.readLine()
6. Close file f.close()

I wanted to see what you thought before putting together a PR.

I am currently looking for feature requests for the next release of RanCat. If you think you have an interesting feature, with a plausible use case, please feel free to open an issue so we can discuss it before a pull request 😄

A user should be able to chain together suitable commands. E.g:

r = RanCat().load(...).load(...).set_conversion(...).set_unique(...).next()

Something along the lines of

r = RanCat()
r.load(...)
r.load(...)
for i in r:
    print(i)

We want to be able to override the string conversion. E.g. the default will strip trailing whitespace, however a user should be able to do this:

r = RanCat()
r.set_convert_func(String.upper)

So users don't need to write their own conversion methods except for unusual cases, RanCat should support conversion methods for major use cases. Primarily:

ascii_lower - forces ascii and lowercase with RanCat._separator
ascii_upper - forces ascii and uppercase with RanCat._separator
camel_case - camel case separated by RanCat._separator

I would like to investigate ways of documenting the project. At the moment I am leaning towards ReadTheDocs

This can be fixed by allowing devs to install the from the git repo. I think this is possible via -e . in requirements.txt which I will add.

readme, changlog, license

Can use a switch --use-default-text to load some text from lorem ipsum so as to get a quick combination of random words.

Also maybe text could be loaded from url instead of just static files.

The field total_combinations in the class RanCat (https://github.com/mattjegan/rancat/blob/master/rancat/RanCat.py#L34) seems to be populated only once a RanCat.next() is called which in turn triggers a call to RanCat.refresh_all.
This looks to me like a bug, because you have the information required to calculate this as soon as you load a new file and in the future if we were to make calls other than RanCat.next() which were to use this field, they would fail.

@mattjegan: If this seems acceptable I shall open a PR to fix this.

Need to remove coveralls and code-climate. codecov and landscapeio are good for the current needs.

Copy the contents of docs/contributing.md into the end of README.md as info about contributing should be on the main page on github.

Would like to have:

RanCat().load_structure('file1', 'file2')
RanCat().load_structure('file1', ['the'], 'file2')
RanCat().load_structure(['Orange', 'Red'], ['Cat', 'Dog'])

be equivalent to:

RanCat().load('file1').load('file2')

Include more motivation as to why to use the project.

Must use RanCat.set_unique(True), as _unique should default to False.