Create Command Line Interface

[romibi]

Things to do for the Command Line Interface

• [x] define cli arguments
• [x] list files/folders
  • [X] basic list
  • [x] #7
  • [x] show additional info (properly)
  • [x] tree structure
• [x] add
  • [x] file to new
  • [x] file to existing
  • [x] replace file in existing
  • [x] folder to new
  • [x] folder to existing
• [x] remove
  • [x] file
  • [x] folder
• [x] extract
  • [x] file
  • [x] folder
• [x] rename
  • [x] file
  • [x] folder
• [ ] support multipart archive files
• [ ] search content (maybe)
• [ ] copy file between packed (maybe)
• [ ] copy folder between packed (maybe)

[Strongleong]

Now with -s and -f I think this one done

• [X] show additional info (properly)

[romibi]

@Strongleong

• [ ] tree structure

This you wanted me to implement, right?

And:

• [ ] support multipart archive files

How's the status of this?

Evaluating if the remaining tasks here should get their own issues and this issue be closed.

[Strongleong]

• [ ] tree structure

This you wanted me to implement, right?

I couldn't implement this with our current way of storing list of files in RAM. I suggested you to store them in tree rather that list, you declined

• [ ] support multipart archive files

How's the status of this?

Didn't event thought starting this

[romibi]

Regarding tree structure: Of course for outputting it the filenames and paths need to be converted to a tree structure before displaying it. That can either be done locally in some function in cli app. Or I've done that for the Gui already … mabye that logic can be extracted to some common place.

But the PackedMetaData and ScrapPackedFile classes should stay representing how the packed fileformat is structured.

I might do this myself at some point … but it's not important …

Regarding multipart archive files Don't worry. If you want and have a good idea on how to do it you can do it … if not … For me it's not a hight priority. Just was wondering if it hinders your cli scripting or not.

[Strongleong]

I have a question about multipart containers.

What if I want to check what is on one specific packed file. Let's say data01.packed Should be this option opt-in and the app will open packed files in multipart mode by default? Something like this

ScrapPackedExplorerCli data01.packed list                 # Will search for all dataXX.packed files and combine them
ScrapPackedExplorerCli data01.packed list --single   # Will open only data01.packed

Or opt-out?

ScrapPackedExplorerCli data01.packed list                       # Will open only data01.packed
ScrapPackedExplorerCli data01.packed list --multipart   # Will search for all dataXX.packed files and combine them

[Strongleong]

search content (maybe)

You can mark it as done scine we have -q flag in list command

[romibi]

I have a question about multipart containers.

I'd say on the first part default behaviour is consodering all files except when disabled by argument. On other parts only consider that one file.

Btw, do you know? Is there any marker in the files that they are multipart or is it just the names? (regarding the packed files in remaster)

[romibi]

search content (maybe)

You can mark it as done scine we have -q flag in list command

Isn't that only for searching filenames? (currently not on PC to check)

[Strongleong]

Do you want to search by content too?

[romibi]

• [x] #7

is already done and ticked off …

And there's a reasone there's a "(maybe)" in

• [ ] search content (maybe)

😄

[Strongleong]

Oh. I thought that this is search by content (of the packed file)

[Strongleong]

Btw, do you know? Is there any marker in the files that they are multipart or is it just the names? (regarding the packed files in remaster)

To my knowledge - no. And to my lesser knowledge - this is how multipart archives (rar, zip, gz) works.