Here's a discussion on IRC about Categories and Structures to formalize some of the thinking from that discussion.
Perhaps we can all start putting together out thinking about how Categories and Structures work or should work in the future. This is long term planning not something that has been defined for a particular version. Lets develop the requirements for what we want.
albrown | | what is wrong with structures?
|
mose | | delete a file don't delete it from struct
|
albrown | | should it, I think that I can argue that either way
|
mose | | interesting move
|
albrown | | ;-))
|
mose | | structure can be considered many ways
|
mose | | for me, it's just a list
|
albrown | | if you delete the page without deleting it from the structure you would still have the chance to rebuild the page perhaps completely differently without losing your position within the structure
|
gmuslera | | is a way to give order to wiki pages
|
mose | | but because we lack of structuration for content, it can be considered as a skeleton
|
albrown | | I thought that that was the intent of the structure — Skeleton
|
mose | | skeleton is inside
|
mose | | I see something that is apart
|
teedog | | it'd be nice if we could keep it that way
|
albrown | | I don't know if I ever agreed with using existing pages in a structure
|
teedog | | how come? (marc requested that btw)
|
gmuslera | | albrown: manual is a good example .)
|
gmuslera | | manual should have some order, in general is a way to do multipage documents
|
albrown | | I like the idea of outlining using a structure, butr unless you could use an existing page in many structures and have it properly displayed as a member of the correct structure when it is used in a structure then using it would be wrong, I think
|
gmuslera | | you can do a cooperative work with a lot of people separating permissions at page level
|
teedog | | gustavo, al is not concerned about structures, but adding pre-existing pages to structures
|
gmuslera | | albrown: lets separate concepts from implementation. Concept is great, implementation is fixable
|
teedog | | right, al?
|
albrown | | gmisera, I understand what you mean
|
albrown | | For structures to be completely useful and valid we need to be able to use "any" page as a member of any structure and for the page to be smart enough to know if it is being accedssed by structure a or structure c or all alone, i think
|
albrown | | now you can use a page in two structures but the next and previous for both structures would show on the page and a user would have to be "smart" enough to folow the correct structure. Even if you access the page stand alone the next and previous links still show up.
|
albrown | | how would be the best way to seperate the concept and implementation guys
|
marclaporte | | I think cat and strucuture should be tied
|
albrown | | absolutely marc!
|
marclaporte | | we improve category system to add ordering and depth
|
gmuslera | | when following an structure, the "next" link should carry the structure you are viewing
|
marclaporte | | then we retire the "structure" feature
|
albrown | | then some sort of {toc-Cat_Struct}
|
gmuslera | | category=collection, structure=order
|
marclaporte | | advantage: cat system is also for other objetcs than wiki pages
|
marclaporte | | Gus: tes, but it has to be managed all at one place
|
marclaporte | | yes, but
|
gmuslera | | but you can have ordered collections, the next step of a page could be an image or an image gallery
|
albrown | | when starting from or following that cat_struct the struct= could part of the url?
|
marclaporte | | yup
|
albrown | | we should be able to use anything in this ordering-category thing
|
gmuslera | | integration, remember? could be nice to follow with order categories and from a page jump to a blog to an image to a quiz
|
albrown | | a blog or a post within a blog?
|
gmuslera | | maybe a listing of the blog
|
albrown | | I think that any object should be fair game within this |