What is on Your Mind?

Sorry for taking some time - some urgent project followed by some even more urgent illness took my attention.

My suggestion is to abandon "TUI" for some catchy name. Like, for instance, "Samba" - derived from "SMB", yes, but still more rememberable than, maybe, "SFMU - SMB filesystem mounting utilities" or something such.

How about:

"HardCore - the core of script programming made easy and reliable"
"Riot - a robust I/O toolset for your scripts"
"IOdine - the antidote for your scripts I/O goitre"
"CLIO - let the muse kiss your script to make it famous" *)

You might want to consult a latin dictionary for verbs of the fourth (-i) conjugation. The first person singular indicative praesens active (like "i do" for "to do") ends in "-io" so there are many possible plays on words.

bakunin

________
*) actually the meaning of the name of the muse of history, "Clio" (greek 'Κλειώ') means "made famous".

Just in case someone is interested in an ironic fact of my life: This is about the second time in my life that 4 years of learning ancient greek in Gymnasium (similar to Highschool) has helped me anything.

tcusses

Was too early to write.

---------- Post updated at 12:39 ---------- Previous update was at 10:27 ----------

I thought i asked for a 'catchphrase', refering to the project name 'comment', not its very own name.
But should have expected new names along the way.

Noone wants to rename their 3.5 year old child.
Specialy when its already used in other projects (of mine at least).

But since i'm currently rewriting the internal core functions/variables, NOW would be the time to rename it along the way...

If/when i consider renaming the project, I do like:Bold ones beeing my favorites.

Any thoughts?

swarm - shell wrapper and runner modificator :P

Issue is, i want something meaningfull to use as prefix for the 40+ commands.

And (for example) riot belongs to a list of words i dont want to repeat in my mind without a reasonable reason.
swarm, would be too long to type before each command, wouldnt it?

Well that is my opinion.

Would you like to type: (top 3)
clio-echo or clio-conf-get or clio-browser
clif-echo or clif-conf-get or clif-browser
swarm-echo or swarm-conf-get or swarm-browser

Or could i just leave the command-names as they are now, and just rename the project?
I'd very much like this idea, as this would cause much less work for me, and preserve the (imo) meaningfull command prefixes i currently use (tui-*).

What do you think?

No, i think you should undergo the extra effort. The problem is that the "good names" are usually already used and the more common your names are the more likely you are clashing with something already existing.

Personally i am a fan of Hungarian Style Notation, although i stripped it down and modified it for my personal needs, so take the following as a template and modify it until it suits you. Here is my (personal) convention for my own library and internal script functions:

f_Name - external function, all of these come from /usr/local/lib/ksh
pName - internal function in a script returning <void> (aka "procedure")
fName - internal function returning something meaningful (aka "function")

So i can tell from the name alone where i will have to look. If you would at least provide a common beginning, like, for instance, "hcFunctionOne", "hcFunctionTwo", etc. or "ClioFunctionOne", "ClioFunctionTwo" and so on it would help immensely. Not only because it helps keeping track of where a function came from but also because it would avoid possible name clashes. How many functions are out there named "Clio*" or "hc*"?

I hope this helps.

bakunin

You misunderstand the concept there is, i think.
tui-<*> IS the function, procedure, command or whatsoever.

Code:

ls /usr/bin/tui*|wc -l
44

Functions i used in more than one script, became scripts themself.
tui-printf was the very first 'exported' function, and stuff like tui-str-extension from tui-str-genfilename are the most recent ones.

Thats why i think it still makes sense to keep the command names 'as-is': tui-echo, tui-header, tui-dd, etc.
As they represent that these commands belong to each other, and have a meaningfull prefix while reading a script.

The only files the user (you ; is supposed to) change/s are the config files in $HOME/.config (default), or the theme in the rc file.
Other than that, in some sense, its like grep, echo, dd, and read or select, just matching the same output-theme.

There is a naming sheme, like:

Code:

$ tui-bol-
tui-bol-dir   tui-bol-gui

They will return true (0) or false(1) wether the last item is valid/applies.

Code:

$ tui-conf-
tui-conf-editor  tui-conf-get     tui-conf-set

Gets or sets a value of a variable within a conf file.

Code:

$ tui-str-
tui-str-bol-conv     tui-str-encrypt      tui-str-extension    tui-str-genfilename  tui-str-usb

They return strings according to their description, tui-str-usb could even be used to select a connected/pluged in usb-storage.

Guess i'm missing this part in the README?