This is a read-only snapshot of the ComputerCraft forums, taken in April 2020.
Sewbacca's profile picture

Has somebody an idea for a name for my API?

Started by Sewbacca, 27 September 2016 - 09:13 AM
Sewbacca #1
Posted 27 September 2016 - 11:13 AM
My API creates just separated file systems (fs (like window.create(parent, …))), by using
local fs = <API name here>.create(parent, sRootDir).
My very innovative idea was:
local fs = FileSystem.create(parent, sRootDir).

Thanks in advance
Sewbacca
Edited on 01 October 2016 - 08:23 PM
LDDestroier #2
Posted 27 September 2016 - 01:19 PM
mountFS
fsew
boxfs

Or my personal favorite,

gravelbox
Lupus590 #3
Posted 27 September 2016 - 02:20 PM
change root (it's a Linux command - or it may be Unix)
Sewbacca #4
Posted 27 September 2016 - 04:19 PM
Additional information: It works like window.create for term.
Thanks for your suggestions! :D/>
I will give it some thought.
Feel free to post more names.

Sewbacca =)
Edited on 27 September 2016 - 02:24 PM
TheRockettek #5
Posted 27 September 2016 - 08:55 PM
multiFS
FSectors
Creator #6
Posted 27 September 2016 - 10:40 PM
FStart ==> It's a word game FS + start
Sewbacca #7
Posted 29 September 2016 - 08:55 PM
FStart ==> It's a word game FS + start
Why start?
Creator #8
Posted 29 September 2016 - 09:41 PM
Because is starts (creates) new file systems. It's a stupid word game, don't look too deep into it.
thecrimulo #9
Posted 29 September 2016 - 09:49 PM
Because is starts (creates) new file systems. It's a stupid word game, don't look too deep into it.
No I can win on stupid word games.
Name it F-Word, because bytes in RAM are also called words, and yours create filesystems.

Take that Destructor
Sewbacca #10
Posted 29 September 2016 - 10:22 PM
I think of using one of these names (marked with '{…} <–')

mountFS <–
fsew
boxfs <–

Or my personal favorite,

gravelbox <–

multiFS
FSectors <–

To Lupus
change root (it's a Linux command - or it may be Unix)

I think 'change root' wouldn't quite fit, as it doesn't change the root. It creates a handle for concluded filesystems. I could implement some function like fs.redirect (which i'm currently not working on) then i could use the name =)
Edited on 29 September 2016 - 08:40 PM
Sewbacca #11
Posted 01 October 2016 - 11:59 PM
I decided, to use boxfs. Wow, am i so slowly in choosing a name?
Lupus590 #12
Posted 02 October 2016 - 06:26 PM
Wow, am i so slowly in choosing a name?

Names are important, it's how people will identify your program and needs to be a short descriptor of its use and capabilities. A bad name can be confusing and misleading, causing people to not use your program, possibly in favour of an inferior competitor.
Sewbacca #13
Posted 02 October 2016 - 07:04 PM
Wow, am i so slowly in choosing a name?

Names are important, it's how people will identify your program and needs to be a short descriptor of its use and capabilities. A bad name can be confusing and misleading, causing people to not use your program, possibly in favour of an inferior competitor.
Thanks, maybe i will more think about it. What do you mean about boxfs? What do you associating with boxfs? What the others are thinking about boxfs? And the same with FSectors and gravelbox. And what about capitalization?
BoxFS or BoxFs, boxfs or boxFS?
Feel free to post your feelings and associatings about these names.

Thanks in advance =)
Sewbacca
Edited on 02 October 2016 - 05:06 PM
LDDestroier #14
Posted 02 October 2016 - 07:27 PM
Mind you, I just name things based on how convenient it is to type on a QWERTY keyboard. I'd just call it "boxfs"
Lupus590 #15
Posted 02 October 2016 - 07:33 PM
BoxFS (my preferred capitalization) makes me thing of sandboxes, that said though, I can't think of much else you can do with a file system API - Metadata? Permissions (very similar to sandbox)? File History (keep old versions and allow restores)? OK maybe I can think of a few things, but not many with a name like BoxFS.

More name suggestions: SubFS, NestedFS
Edited on 02 October 2016 - 05:36 PM
Sewbacca #16
Posted 02 October 2016 - 09:12 PM
Things you can do with <API name here>:
  1. Sandbox programs
  2. Virtual machines (mount rom into a directory and create the handle)
  3. Virtual hard disk drives
  4. ReadOnly (for example OS or password files (to prevent setting a password to '' for example))
  5. Save storage with mounting paths into directorys
  6. handle.mount simulates (simulates, because the paths are just redirected (idk how hardl links exactly work)) hard links (such like the Windows command: mklink /J <destination> <source>)
  7. hierarchy your file systems: native fs -> hard disk drives -> hard disk drive handle or native fs -> rom/help (i mean the help files)
  8. mount disks into other directorys (for example in Drives/{0}/disk)
  9. sharing data between programs
  10. executing programs relative to their destinations (Okay, here we have the problem with performance/use proportion)
  11. maybe this.
  12. Things i forgot.
I hope that you've now a better view to the use of the API =)

Note that currently, this API has just one function yet:
<API name here>.create
Cause: I like the style of window.create.
Edited on 02 October 2016 - 07:16 PM
TheRockettek #17
Posted 02 October 2016 - 09:41 PM
A computercraft emulator, in computercraft :D/>

ComputerBox
Sewbacca #18
Posted 05 October 2016 - 05:20 PM
Bombed with names, i am hanging between the following names and i wanna post this API today:
  1. BoxFS
  2. FSectors
  3. SubFS
  4. GravelBox
I tend to SubFS and FSectors, really cool names.
Edited on 05 October 2016 - 03:51 PM
Sewbacca #19
Posted 05 October 2016 - 05:59 PM
SubFS means subtract filesystem and
FSectors / FSector means file sector.
Both are nice ideas.
Subtract a file system from another…
Create a sector for files…
I think on strings if I hear SubFS and i think on a scaffold if i hear sector.
What are you thinking?
(Wow this thread is online since 27th septembre)

EDIT:

Yeah i take FSector.
Edited on 05 October 2016 - 04:01 PM