Fundamentally change object structure #98

Open
lordscarlet opened this Issue Jan 27, 2012 · 5 comments

Comments

Projects
None yet
3 participants
Owner

lordscarlet commented Jan 27, 2012

From informal conversation with @bricas:
as for archives-in-archives, this is trickier.
a "pack" is:

* archive
  +- file1
  +- dir1
    +- file2
  (etc)

so it's easy to represent that as Pack---(has many)--->File
an archive in the structure is "similar" to a dir
except that with our schema, we've flattened that all down
so, one possible way to handle it would be:
File---(might have)--->Pack Info
File/parent---(belongs to)--->File
(parent being a column)
so, a pack just becomes a file, but at the top of a tree structure
thus, we can represent an archive-in-archive as a branch off of the tree.
our Pack object becomes a view, which combines the Pack Info+File objects that have NULL parents

Owner

lordscarlet commented Jan 27, 2012

I assume we would then stop flattening directories? That way when you go to a pack there will be some way to visually represent that something was in a file/archive?

Owner

bricas commented Jan 27, 2012

We should visualise the tree structure -- how that looks, i dunno.

Owner

lordscarlet commented Jan 27, 2012

That's what I figured. It'll probably be easiest to wait until we have the data/logic working and then toy with it.

Is this really a big issue? I don't recall packs being often structured with multiple directories. I think the directory could just be an attribute of a file that can be displayed, and files could be shown in the order they were compressed but not affect the object structure itself... Am I missing something?

Owner

lordscarlet commented May 21, 2013

He larger issues at play are a) the current object structure and b) zips
inside packs

Packs with a nested structure are rare, though.

On Monday, May 20, 2013, frandroid wrote:

Is this really a big issue? I don't recall packs being often structured
with multiple directories. I think the directory could just be an attribute
of a file that can be displayed, and files could be shown in the order they
were compressed but not affect the object structure itself... Am I missing
something?


Reply to this email directly or view it on GitHubhttps://github.com/sixteencolors/sixteencolors/issues/98#issuecomment-18182511
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment