[TYPO3-dev] Moving pages in workspaces - brainstorm

[Daniel Pötzinger]

Martin Kutschker wrote:
> Kasper Skårhøj schrieb:
>  >
>> We could even implement some sort of relation between the deleted 
>> original and created copy  which makes sure that IDs are maintained 
>> during the publishing  process. 
> 
> Not really related but it touches the problem of FE-linking.
> 
> The idea is that you don't link against the "uid" but against an "oid" 
> (object id). I'm not sure if "t3ver_oid" is such an "oid". This is what 
> I understand:
> 
> The "oid" is the same for all versions of an element (object).
> 
> You can move any element around as you like. It doesn't matter if the 
> real "uid" changes as long as the "oid" stays the same and is used for 
> linking.
> 
Hello

When I understand correct t3ver_oid (stand for online -id?) points to 
the uid of the online version. (so linking to uid is ok while swapping 
versions)

But I like the idea of an object based view in common since all version 
features could be mapped to this... (I like it much :-))

So there are three "objects": branch, page, content

A branch is an object witch is composed of page-objects

A page is an object witch is composed of content-objects (all 
contentelements could be derived from a common content-object)


All Objects have a system-wide unique id and can have versions (and 
history..)

This is what an object-based database will manage for you. And it would 
be more complex (and less maintainability because copying of data must 
be done manual) to use relational-data to simulate that. But the 
versioning feature does something from that if we look from that point 
of view...
So the think which is missing is to introduce a objectid and a relation 
"pagebranch" ?