Change name

[superMDguy]

Change name

[amahabal]

I am open to suggestions. How about the following approach: let's press forth with the current name for a bit, and when we are in a slightly better shape (say, met milestone 0.3), rope Doug in for coming up with a name?

…

On Tue, Jan 10, 2017 at 10:51 AM Matthew D. ***@***.***> wrote: The current name, PySeqsee, doesn't reflect what this project has become, a library for creating projects using Hofstadter's ideas. Could we rename it throughout to something that better represents what it does? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#26>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADFvNWeamMDjS-BgoTF9E1DF8SgLzONks5rQ9NIgaJpZM4Lfw43> .

[superMDguy]

Ok, that sounds good. I had another related question, though. I'm currently working on setting up a command to simplify creating new apps. For example, instead of doing /usr/bin/python3 -m farg.tools.pyseqsee_create_app bongard, you'd use just run <some command> create bongard. I'll also try to add other things so that <some command> could run an app, or do other things. What do you think I should call <some command> for now?

[amahabal]

What about "create_project"?

[superMDguy]

I was thinking of a more generalized name, so I can add more functions, like <some command> run <app name> or <some command> add-codelet <codelet name>, where <some command> is the same throughout.

[amahabal]

Ah, I see. Yes, that would be very useful to have.

One possibility is "farg" (for "Fluid Analogies Research Group"). Maybe "fluid"? Other suggestions?

[superMDguy]

I think farg goes better with the rest off the app (e.x. the farg folder), so I'll use that for now. I can always change it by modifying a line of the setup.py though.